Key takeaways
- Airtable exports a view, not a table, so the filters and hidden fields on that view decide what lands in the sheet.
- Linked records arrive as the plain text of the primary field, which means the relationships between your tables do not survive the export.
- Attachment fields export as URLs that stop working within hours, so images and documents have to be downloaded separately.
- Airtable’s own import limit is 100MB for a CSV and 5MB for an Excel file.
- Exporting the same view every week is a sign you needed a sync or a system, not an export.
We build operations systems on Airtable, and we do not sell a connector, so there is no tool being recommended at the end of this.
Can you export data out of Airtable?
Yes, one view at a time, as a CSV. Open the Views menu, right-click the view you want, and click Download CSV. There is no button that exports a whole base in one file, and there is no native export to Google Sheets, PDF, TSV or Numbers. Everything goes through CSV first.
That single sentence hides the decision that causes most of the surprises later. Airtable exports the view you clicked on, with that view’s filters applied and that view’s hidden fields left out. Two people exporting “the same table” on the same afternoon can produce two different files.
If you want the whole table, make a view with no filters and every field visible, and export that one.
How do I export into Google Sheets?
Download the CSV from the Airtable view, go to sheets.new, then click File → Import → Upload and choose the file. Set the import location and separator if Sheets guesses wrong, and click Import data. The rows arrive in seconds. Column widths and text wrapping will need tidying.
That is the manual route. There are three in total, and the right one depends on how often you are going to do this.
| Method | Good for | What it costs you |
|---|---|---|
| Download CSV, import to Sheets | A one-off copy, a backup, a hand-off to someone outside the base | Manual every time, and stale the moment anyone edits either side |
| Airtable automation → Google Sheets | New records appended to a sheet as they are created | Appends rows only. It cannot update a row that already exists, and the sheet needs a header row set through File → Print before the action will accept it |
| Make, n8n or a connector tool | Scheduled exports, transformations, more than one destination | A second system that has to keep running, and a second bill |
The automation route has a failure mode that shows up in Airtable’s own community forum: the Google Sheets action loses its authorization and stops, with a message that the automation is no longer authorized to use the configured account. It reconnects in a few clicks, and nothing warns you in between, so whoever depends on that sheet usually finds out by noticing the numbers are old.
What does not survive the export
A relational base does not export the way a spreadsheet does.
Linked records flatten. A link to a client record exports as the words in that client’s primary field. “Acme Corp” arrives as the characters A-c-m-e, not as a relationship. A base where clients link to projects which link to invoices lands in Sheets as three disconnected lists, and rebuilding the connection is manual work or an API job.
Attachments become expiring links. Airtable exports the filename and a URL rather than the file. Those URLs stop working within a few hours of the export, so if the images matter, download them straight away or pull them through the API.
Hidden and filtered data is simply absent. This follows from exporting a view, and it is the most common cause of “the file is missing half our records”.
Some things never come out at all. Record comments, field descriptions, base guide content, colour coding, and anything held inside an extension stay in Airtable. None of it appears in a CSV.
The file is a snapshot. It is out of date the moment anyone edits either side, which is what sends most people looking for a sync instead.
When the export keeps coming back
A repeating export is usually a missing system
If the same view gets exported every week so somebody can see it, the requirement is access rather than a copy. Working out which system owns which data is the first thing we map for service businesses.
See how we build systemsDoes Airtable integrate with Google?
Yes, in both directions, but the two directions work differently. Airtable can import a Google Sheet through + Add or import → Google Sheets, either as a new table or into an existing one. Going the other way, Airtable has no native Sheets export, only an automation action that appends rows.
The native import caps at 100MB for a CSV and 5MB for an Excel file. And once a sheet has been imported into Airtable, the two stop being connected: edits in Airtable do not flow back to the original sheet, and edits in the sheet do not appear in the base.
When the export is the wrong answer
Almost every guide on this subject is written by somebody selling a connector. A repeating export is usually a symptom.
If you export the same view every Monday so that somebody can see it, the actual requirement is access, and a filtered view shared as a link or a portal does that without a second copy of the data existing. If you export so that somebody can edit and send it back, the requirement is a form or an interface, because the returning file has to be reconciled by hand. If you export so a report can be built, the requirement is a dashboard on the live base.
A one-off export is a fine thing. A scheduled export is a system with no owner, and the copy in the sheet slowly becomes a second source of truth that disagrees with the first.
If the sheet and the base disagree tomorrow morning, which one is right, and who decides? When nobody can answer that, the export is holding a design decision that has not been made yet.
Frequently asked questions
Can you export an entire Airtable base at once?
Not as a single file. Airtable can export a base as one CSV per table, and each file has to be imported into Sheets separately, because Sheets will not take them as a set. The links between tables are lost in every file.
Why did my Airtable to Google Sheets automation stop working?
The most common cause is the Google account authorization expiring, which shows up as a message that the automation is no longer authorized to use the configured Google Sheets account. Reconnecting the account in the automation step usually fixes it.
Can Airtable update an existing row in Google Sheets?
The native automation appends rows. It does not match on a key and update a row that already exists, which is why sheets fed this way fill up with duplicates over time. Updating in place needs Make, n8n or a connector that supports it.
Can I export Airtable to Excel, PDF or Numbers?
Not directly. Airtable exports CSV only, and converting to another format happens after the download. The same applies to TSV.
How do I automate the export on a schedule?
Airtable has no native scheduled export. An automation in Make or n8n can pull a view and write it to a sheet on a timer, and connector products sell the same thing packaged. Both work, and both mean something outside Airtable now has to keep running.
Is Airtable basically Excel?
No. Excel and Google Sheets are spreadsheets, where the cell is the unit and relationships are faked with lookup formulas. Airtable is a relational database with a spreadsheet-like interface, where the record is the unit and records link to each other. That difference is exactly why exports lose the links. The longer version is in Airtable vs Google Sheets.
If what you actually need is the two systems staying in agreement rather than one copying the other, the methods, the limits and the failure modes are in how to connect Airtable and Google Sheets. If the export is a symptom of the base being asked to do a job it was not designed for, that is the operations side of what we do.