Airtable view to dashboard
Airtable's grid view, exported and actually readable.
Export a grid view from Airtable, drop the CSV here, and the columns that Airtable flattens into text are unpacked again. Multi-select and linked record fields arrive as comma-joined values inside one quoted cell, so Tags becomes a real multi-value dimension rather than a hundred unique strings. Dates are parsed against the field's display format rather than assumed to be ISO.
Prefer the full explorer? Open the app, or start from the generic dashboard builder.
Everything rich becomes a string on the way out
Airtable's field types are the whole point of Airtable. A multi-select is a set. A linked record is a relationship. A collaborator is a person object. CSV has none of those concepts, so the export flattens each one to text, and the flattening rule is comma joining inside a quoted cell. A Tags field holding enterprise and renewal becomes the single string containing both, and a naive group-by treats that combination as its own distinct category, sitting next to a row tagged only enterprise as though they had nothing in common.
Dates go through a similar loss. Airtable writes them using the display formatting configured on the field, so a base set to a friendly format exports something like 3 September 2026 rather than an ISO date, and switching that display setting changes every future export without changing any data. If a base has one date field set to US format and another to European, one file carries both conventions in different columns. This page reads each date column on its own terms.
How to export from Airtable
- Open the table and pick a view Airtable exports a view, not a table, so switch to the grid view you want first. A filtered or grouped view exports only its visible rows, which is either exactly what you want or a trap.
- Check hidden fields Fields hidden in the view are excluded from the export. Open the hide fields control and turn on anything you will need, because a hidden field leaves no trace in the file at all.
- Use the view menu to download CSV Click the view name, then Download CSV. It downloads immediately in the browser rather than being emailed, which is one of the friendlier export flows in this list.
- Open the first line and look at the dates Confirm what format your date fields exported in. That single glance saves the classic argument about whether the third of April is the fourth of March.
- Drop the file on this page Multi-select cells are split, Stage and Priority become breakdown chips, and Value becomes the metric behind every panel.
Formula and rollup fields export as their computed result, not their formula, so the file is a snapshot. Re-exporting after any upstream change gives different values with no indication that anything moved.
Try with sample Airtable data (the same columns, 82 rows, no upload needed).
What the dashboard shows
Every panel below is built from a column that is actually in the export, named the way Airtable names it.
- Value by stage. Stage as an ordered breakdown with Value summed, giving the pipeline shape a base like this is usually tracking.
- Tags as a real dimension. The comma-joined cell is split so each tag is counted on its own, which is the difference between eight tags and forty combinations.
- Owner workload. Owner by count and by value, so an uneven distribution is visible before it becomes a capacity problem.
- Created against Close Date. Two date fields on one axis, each parsed against its own display format, which is how long things actually take.
- Priority mix. A single select field, so it behaves normally, and it makes a good cross-filter for every other panel on the page.
- Source breakdown. Where records came from, ranked by value rather than count, which usually reorders the list completely.
Name,Stage,Owner,Value,Source,Priority,Created,Close Date,Tags,NotesWhat Airtable loses on the way to CSV
- Multi-select values share one cell. Comma joined inside quotes. Group by that column and every combination of tags becomes its own category, which fragments the breakdown into uselessness.
- Linked records flatten to display names. You get the primary field text of the linked row, not an id, so two records with the same name are indistinguishable after the export.
- Dates follow the field display format. Not ISO, and not necessarily consistent between two date fields in the same table. Changing the display setting silently changes future exports.
- Attachments become URLs. Long, signed and expiring. They are links, not values, and counting distinct attachment cells tells you nothing useful.
- The export is a view, not a table. Filters, sorts and hidden fields all apply. A hidden field is simply absent, with no column and no clue that it existed.
- Long text keeps its line breaks. A Notes field with paragraphs exports as a quoted cell containing real newlines, which is valid CSV that plenty of parsers still mishandle.
Airtable is a database wearing a spreadsheet costume, and the CSV export is where the costume comes off. Split the multi-value cells, check which view you exported, and the file behind it is clean.
Frequently asked questions
Why is my Tags column full of strange combinations?
Because a multi-select field exports as its selected values joined by commas inside one quoted cell. A record tagged enterprise and renewal becomes a single string holding both, which any grouping treats as a distinct category separate from records tagged with only one of them. This page splits those cells so each tag counts on its own and a record with two tags contributes to both.
What format are Airtable dates exported in?
Whatever display format the field is configured with, which might be ISO, US, European or a friendly written format. Two date fields in the same table can differ. Nothing in the file records the setting, so the same base exported after a formatting change produces a different looking file with identical data. Each column here is examined separately rather than assuming one convention.
Why are some of my fields missing from the CSV?
Because Airtable exports a view rather than a table, and any field hidden in that view is excluded entirely. There is no empty column left behind to hint at it. Filters and sorts apply too, so a filtered view exports only the rows it shows. Unhide the fields you need and clear the filter before downloading if you want the whole table.
What happens to linked records?
They flatten to the primary field text of whatever they linked to, joined by commas when a cell links to several rows. The underlying record identifiers are gone, so you cannot rejoin to the linked table reliably if two of its records share a primary field value. If you need a real join key, add a formula field exposing the record id before you export.
Do formula and rollup fields export?
Yes, as their computed value at the moment of export rather than as the formula. That makes the CSV a point-in-time snapshot. If a rollup depends on a linked table that someone edits an hour later, re-exporting gives different numbers with nothing in either file to explain the change, so date your exports if you plan to compare them.
Does this page connect to my Airtable base?
No, and it deliberately cannot. There is no integration, no API key and no OAuth step. You download a CSV from Airtable yourself and drop it here, where it is parsed in the browser tab. That means no permission grant to a third party over a base that may hold client data, and nothing to revoke afterwards.
Related tools
Load an Airtable export with the tags split apart
82 records with multi-select tags comma-joined in one cell, two date fields on different display formats, and a long notes column carrying real line breaks.
Open the sample Airtable dashboard