How to back up Airtable automatically: every option compared

July 11, 2026 · Basestash

Airtable holds your operations — and Airtable’s built-in safety nets (7-day trash, plan-limited revision history) are recovery features, not backups. Here are the four real ways to back a base up, with the failure modes of each.

Option 1: Manual CSV exports

Every view has “Download CSV”. Free, simple — and it exports one view of one table at a time, loses linked-record relationships, attachments, field types, and comments, and only happens when a human remembers. As a backup strategy this fails precisely when you need it: nobody exports right before an accident.

Option 2: Airtable snapshots

Airtable takes periodic snapshots of each base, and you can trigger one manually before risky changes. Better than nothing, but they live inside the same account they protect (account compromise or base deletion takes them with it… a deleted base’s snapshots ride along), retention follows your plan, and restore is all-or-nothing: the whole base rolls back, clobbering every change made since.

Option 3: DIY — scripts against the Airtable API

The API exposes records and schema, so a scheduled script (or a Zapier/Make scenario) can pull tables to JSON/CSV on a cron. Full control, and for one small base it’s a fine weekend project. The costs show up later: you must handle pagination and rate limits (5 requests/second per base), schema changes that silently break field mappings, monitoring (a backup script that died in March and nobody noticed is the classic disaster-recovery story), storage, retention, and — the part everyone skips — restore tooling. A folder of JSON is not a restore plan; writing records back through the API with linked fields intact is its own project.

Option 4: A dedicated backup service

Purpose-built tools run scheduled backups, watch the API limits, alert on failure, and — the important part — give you a working restore path. They split into two models:

Export-to-your-storage (e.g. On2Air Backups): files delivered to your Google Drive/Dropbox/Box. You own the storage; recovery is manual re-import. Right choice when compliance demands custody of the files — full comparison here.

Hosted, restorable snapshots (Basestash): versioned snapshots you can browse and search in the browser, with one-click restore of a lost record back into Airtable — plus schema history and comment capture, the parts file exports miss. Right choice when the scenario you care about is “get the lost thing back, fast”.

How to choose

One personal base, low stakes → snapshots plus an occasional CSV are fine. Engineer with time and one base → a script works until it doesn’t; put a dead-man alert on it. Business data, multiple editors, real cost to loss → use a dedicated service; pick by restore model (files-in-your-drive vs click-to-restore). Whatever you pick, test a restore once — a backup you’ve never restored from is a hypothesis, not a backup.