How to recover deleted Airtable records, and what to do when the built-in options can't help

Undo, the trash, record revision history, and base snapshots each cover a different window. Here is which to use, in what order, and why an off-site copy is the only one that always works.

Someone deleted the wrong records. Or the wrong table. Or, on a bad day, ran an automation that cleared a field across the base. Airtable gives you several ways back, each with a different window. Work through them in this order.

1. Undo, right now

If the deletion just happened and you are still in the base, press Cmd+Z or Ctrl+Z. Airtable's undo covers recent actions in your current session, including record deletions. It stops working once you leave the base or too much time passes, so this is the first thing to try and the first thing to stop trying after a minute.

2. The trash

Deleted records, fields, and tables go to the base's trash, reachable from the base menu. Items can be restored from there for a limited period, on the order of a week at the time of writing. Restoring a record from the trash brings it back with its field values and its links to other records intact.

Check here before anything else once undo has failed. It solves most "I deleted a row yesterday" problems.

3. Record revision history

Every record keeps a history of changes, visible from the record's expanded view. This helps when a record still exists but a field was overwritten, since you can see the previous value and copy it back. It does not resurrect a deleted record by itself, but combined with the trash it lets you undo a bad edit as well as a deletion.

How far back the history goes depends on your plan. Free plans keep a short window, paid plans keep much longer ones. Check Airtable's current plan comparison for the exact figures, because they have changed more than once.

4. Base snapshots

Airtable takes snapshots of a base automatically, and you can take one manually before a risky change. Restoring a snapshot brings the entire base back to that moment. Two things to know before you reach for it: the restore is all or nothing, so every edit since the snapshot is lost too, and snapshots only exist inside Airtable. You cannot download one, and they go away with the workspace.

When none of these work

Each option above fails in a predictable situation:

The deletion happened longer ago than the trash retains.
The base was deleted, not just records in it.
Access to the workspace was lost, whether through a billing lapse, a departed admin, or an account compromise.
You need the data outside Airtable, for a migration, an audit, or a legal request.

In every one of these cases the only thing that helps is a copy of the base that exists somewhere Airtable does not control, taken before the problem. That is what an off-site backup is, and it is the one option on this list you have to set up in advance.

Setting that up

The minimum is a dated archive containing every table, the schema with linked-record targets, and every attachment as a file, stored outside Airtable. Tablevault's free export produces exactly that for one base as a single zip, using a read-only token you create and revoke, and emails it to you. One export is a start. If the base is business-critical, the follow-up question is how old a copy you could live with, and the honest answer is usually "yesterday's", which is where a daily schedule comes in.

The best time to take the first copy is before you need it. The second best time is now, while the trash still has what you lost.