How to back up Airtable, automatically

Is Airtable data already backed up?

Partly. Airtable gives you three safety nets, all inside Airtable:

• Trash: deleted records, fields, tables and views for 7 days; deleted bases for 30.
• Snapshots: taken automatically based on how busy a base is, or by hand. Kept for 2 weeks on Free up to 3 years on Enterprise Scale.
• Revision history: earlier values of each record, one record at a time.

What none of them do:

• Live outside Airtable. If the account is locked, the workspace is deleted, billing lapses or the service is down, the safety net goes with it.
• Run on your schedule. You can't schedule snapshots, so you can't say “we have a copy from every morning”.
• Download. Snapshots can't be exported, and restoring one makes a new base rather than rolling yours back.
• Tell you anything changed. Nothing alerts you when 300 rows disappear on a Tuesday.

Every way to keep your own copy

What a good backup includes

• Every table, with its structure: field names and types, select options, formulas, which tables link to which. Without that, a pile of CSVs is hard to rebuild from.
• Record IDs and linked records by name, so links can be reconnected on import.
• The attachment files themselves. Attachment links from Airtable's API expire after a couple of hours, so a backup that only saves links can't give you the files later.
• History, not just today. If the only copy is from this morning and the mistake happened last week, the copy has the mistake too.
• A signal when something goes wrong: the backup failed, the connection broke, or a large chunk of a table vanished.

How restoring works

No outside tool can rebuild automations or interfaces, because Airtable's API doesn't expose them. In practice, restoring from an outside backup means one of three things: a tool writes records back into your base (it needs write access to do that); you re-import a CSV into the table; or you rebuild a base from the saved structure and import every table. For a few deleted rows, the trash is still the best tool if you're within 7 days, which is why noticing quickly matters as much as having the copy.

A disaster-recovery checklist for Airtable

1. List the bases the business can't run without, and who owns each one.
2. Make sure at least two people are owners of each workspace, so one locked account can't lock out the data.
3. Keep a daily copy of those bases outside Airtable, with at least a few months of history.
4. Get told when a backup fails or when a lot of records disappear.
5. Write down how you'd restore: who does it, from what, into where.
6. Test it once: restore one table from your copy into a scratch base and check the links and attachments.

A note on API limits

Backups read your data through Airtable's API, which allows 5 requests a second per base and, on the Free plan, 1,000 calls a month per workspace. A backup uses roughly one call per 100 records per table, so daily backups of a big base on a Free workspace can run out of calls. Team plans get 100,000 a month and Business has no monthly cap.

Why people are asking about this now

Airtable changed hands in September 2026, when Bending Spoons completed its acquisition, and the new team has announced a faster release pace and new admin logs. None of that puts your data at risk by itself. But a change of owner is a sensible moment to make sure the bases your work depends on also exist somewhere you control.

Questions

Sources, checked October 15, 2026: Airtable: snapshots · Airtable: trash · Airtable: API call limits · Airtable: rate limits · Airtable: attachment URLs · Airtable: Back to bases (Oct 2026). Nightclerk is not affiliated with Airtable. Compare backup options.