Image to Dashboard · Your App Cloud
Rebuild a dashboard from a screenshot
Upload a screenshot of a dashboard you use or a photo of your sketch. Take the tiles, charts and filters from the picture and every figure from your own rows. Keep the screenshot's numbers as totals to check against.
From a picture of figures to figures you can trace.
Treat the screenshot as the layout and as the answer key. Note the moment it captured, name the rows behind each tile, then rebuild that exact view and compare.
01
Capture the view and its settings
Upload the screenshots with the button above, one for each band of panels, or a photo of your sketch. In the prompt, type every tile and chart title as it appears. Then write down the moment the picture shows: the day it was taken, the date range and each filter's setting.
02
Name the rows behind every tile
For each tile, write what it counts and the rule it follows, such as members on a paid plan on the last day of the range. Say where those rows come from: an export from the old tool that you import, or records people enter in the app. Ask for placeholder values until the rows arrive.
03
Rebuild the screenshot's view and compare
With your rows in, set the dashboard to the range and filters you noted in step 1 and go tile by tile against the uncovered original. For a chart, read the same bar's value in the old tool, usually by hovering over it. Where a figure differs, look first at the filters, a hidden series and any definition nobody wrote down.
What each part of the screenshot becomes.
Each row starts with something you can see in a dashboard screenshot. The example is invented: the reports page of the membership software used by a climbing gym with two locations, Harbor and Midtown, in Ventura, California. Names and figures are sample data.
| In the screenshot | On your dashboard | What to check |
|---|---|---|
| A tile reading 'Active members 1,248 ▲ 3.1%', with a small (i) icon beside its title | A measure defined in one sentence and counted from your member rows, with the comparison you choose | Hover the (i) in the old tool and copy its text into the prompt. Active might mean a paid plan on the last day of the range, or any check-in within 30 days, and the two give different counts. |
| A bar chart, 'Check-ins by day of week', with no values printed on the bars | The same chart type and grouping, drawn from the check-in rows you import | A bar's height in a picture tells you its value only to the nearest gridline. After the rebuild, hover Saturday's bar in the old tool for the same 30 days and compare its exact value with yours. |
| A donut, 'Revenue by plan', whose legend shows Day pass in gray | Revenue broken down by plan, with every plan included unless you name one to leave out | A grayed legend entry often means someone clicked it to hide that slice before taking the screenshot, so the donut's total may leave day passes out. Decide whether yours counts them, and say so in the prompt. |
| A date control reading 'Last 30 days' in the top corner | A period filter that opens on a range you name, such as the last 30 complete days | A rolling range moves every day, and some tools include today's unfinished day. Take the capture date from the screenshot's file name or file details, and rebuild that exact range before you compare. |
| A 'Location: Midtown' dropdown beside the date control | A location filter offering Harbor, Midtown and All | Every figure in this screenshot covers Midtown only, so compare Midtown first. Then check All: a member who climbs at both gyms should count once in Active members, not once for each location. |
| A table, 'Top members by visits', with rows like 'Sofia Alvarez · 22' | A ranked table drawn from check-in rows, with a length and a tie rule you set | Say how many rows the table shows, whether two check-ins on one day count as two visits, and what decides a tie at 22. Then compare its first three rows with the old tool over the same range. |
| A green ▲ 12% under 'Cancellations' | A change marker whose color follows whether the change is good for that measure | The old tool may color every rise green, cancellations included. List the measures that should go down, then look at a week when cancellations rose and check that the marker turns red. |
| 'Updated 12 min ago' under the page title | A data-as-of date taken from your last import or entry | The old tool recounts as its own records change. Yours shows only what has reached it, so import the next export and check that the date and the tiles move with it. |
| A 'Member health 82' tile carrying the software's own score, beside its logo and a 'Powered by' footer | Your gym's name and colors, and a score only if you can write down how it is counted | A vendor's score comes from a formula the screenshot doesn't show. Look for it in the tool's help pages, define your own from rows you have, or drop the tile. Then read chart titles and the browser tab for the old product's name. |
What a dashboard screenshot holds still.
A screenshot keeps one moment of a dashboard: one date range, one set of filters, hover text closed and the lower panels out of view. It keeps none of the rows the figures were counted from. Record that moment before you upload, because step 3 rebuilds it.
The day it was taken
This week and Last 30 days mean nothing without a date. Screenshot file names often carry one, such as Screenshot 2026-09-14 at 9.12.40 AM. Write the capture date and the range into the prompt, and take fresh screenshots if the old ones have no date you trust.
Definitions behind the hover
Many reporting tools keep a measure's definition in a tooltip or an info icon, and a screenshot catches none of it. Hover each one in the old tool and copy the text. Where a tile has no definition, check the tool's help pages or ask whoever set it up.
Cover the figures, keep the labels
Every figure on the rebuilt dashboard should come from your rows, so you lose nothing by covering revenue, member names and email addresses with solid boxes. Leave tile titles, axis labels and legends readable. Keep the uncovered original on your own computer for the comparison in step 3.
Panels below the first screen
Dashboards often run longer than one screen. Take a screenshot for each band of panels, overlapping the previous one a little so no tile is cut in half, and number them from the top. Type in the title of any panel that was cut off at the edge.
Work the tool does off screen
A screenshot shows the page, not the Monday email report, the alert when a figure passes a limit or the export someone downloads each week. List those in the prompt with who receives each one, so they are planned rather than discovered after you cancel.
An illustrative starting point
The layout people know, counted from your rows.
The tiles, charts and filters from your screenshot, each figure counted from your own rows with its definition on screen, and a data-as-of date.
Layout from your screenshot
Ask for tiles in the order people already scan, the same chart types, and filters where they expect them, without the old tool's logo or colors. The published app opens in a browser, including on phones, so check how the tiles stack on a narrow screen.
Figures from your rows
Ask for every number to be counted from rows you import or records people enter in the app. After the first import, look for a tile that didn't change: it is still showing a placeholder. Keeping those rows needs a backend.
Definitions where the (i) used to be
Ask for each tile's definition on screen, such as members on a paid plan on the last day of the range. Use the hover text you copied, or write your own. Anyone who wonders what Active means can then read it without asking.
A comparison you can repeat
The uncovered screenshot stays useful after you publish. Whenever you change how a figure is counted, set the dashboard back to the screenshot's range and filters. Check every tile again, so one fix doesn't move another number unnoticed.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
Database
Keep data and context for apps and agents
Authentication
Give the right people access
Email
Keep conversations moving
A little more context
Good questions.
Can it read the numbers in my screenshot?
Treat them as a record of what the old tool showed, not as data. They reflect one day and one set of filters, rounded for display, with no rows behind them. Type the titles and labels that matter into the prompt, count the figures from your own rows, and keep the screenshot's numbers as the totals to match.
Which export should I bring for the figures?
Bring the rows each tile counts, with one row per event or record. For the gym, that's a check-in log (a row per visit), a member list with plan and status, and a payment list (a row per charge). An export of the summary view usually carries the same totals as your screenshot and nothing underneath. CSV to Dashboard covers checking an export's dates, refunds and IDs.
Can I start from a sketch instead of a screenshot?
Yes. Draw a box for each number, a rough shape for each chart and the filters along the top. Under each box, write what it counts, and circle the one number people should read first. A sketch has no figures to match, so check the first build against two or three totals you work out by hand from your rows.
What if the chart in my screenshot came from a spreadsheet?
Then the workbook holds what the picture flattened: the rows, the formulas and any hidden series. Start from Excel to Dashboard with the file itself, and describe the screenshot's chart style and arrangement in that prompt. Keep this page for figures whose rows sit in another tool, where the screenshot is all you have of the layout.
We pay for the tool in the screenshot. Can this dashboard replace it?
That depends on where its rows start. If the tool only reports on records kept elsewhere, the dashboard can take over its page. Those rows then reach the app by import, by entries in the app or through a supported integration. If the tool also records the work, as the gym's software logs each check-in, canceling it ends the exports you count from. Run both for a full month, compare them weekly, and export any history you need first.
Can the front desk see check-ins without seeing revenue?
Plan it with the access you describe for each collection. For example, keep payments in a collection only the owners can open, while front-desk staff sign in and see check-ins and active members. Then sign in with a front-desk test account and confirm the revenue donut shows nothing it shouldn't.
Our old tool emailed a weekly summary. Can the dashboard do that?
Apps can send email and run tasks on a schedule you set. The dashboard screenshot doesn't show that email, so upload a screenshot of the last one too, with the recipients' addresses covered, and list who should get it. Schedule the new one after your weekly import. For the first few weeks, send it only to yourself and compare it with the dashboard before the owners rely on it.
Which plan does a dashboard rebuilt from a screenshot need?
A layout review can start as a one-page site, which Free publishes: your arrangement with placeholder figures, shown to the people who read the old dashboard. Keeping imported rows, counting figures from them and asking front-desk staff to sign in need a backend, so the dashboard itself is an app with data, and putting it live needs a paid plan. Model and service usage is metered separately, and the pricing page compares the plans.
Explore Pricing for plans, included capabilities, and usage details.
Keep exploring.
Connect the data behind each tile ↗
See the outcome and the capabilities behind it.
Why a chart in a picture needs a dataset ↗
The blog guide to what a screenshot implies but never defines: where the data comes from, how each figure is calculated and what each control does.
Define every figure before the first chart ↗
The dashboard method, worked through on a sample Excel report: a written definition per metric, one total checked by hand and a plan for next week's figures.
Before you cancel the reporting tool ↗
Map the process the tool sits in, from where figures are entered to who decides on them, before choosing what moves into one app.
Understand data and context ↗
Give information the right place in your app.
Prepare to publish ↗
Check the experience you will share.
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building