What happens when an Airtable base hits its record limit?
- Your data stays. Airtable says “you’ll still be able to use your bases” and “we will never remove your data.”
- New records stop. You “will not be able to add more records or attachments” until you upgrade, so forms and connected apps stop adding them too.
- Every table counts. “Your plan’s record limit is cumulative over different tables.”
- Synced records count in the base they’re synced into.
- The warning can linger. Over-limit alerts “can last up to 24-48 hours after taking the necessary steps.”
The limits on Airtable’s plans page, checked November 7, 2026:
| Plan | Records per base | Automation runs a month (per workspace) | API calls a month (per workspace) |
|---|---|---|---|
| Free | 1,000 | 100 | 1,000 |
| Team | 50,000 | 25,000 | 100,000 |
| Business | 125,000 | 100,000 | Unlimited |
| Enterprise Scale | Not listed | Not listed | Not listed |
How do you see what’s filling your base?
- Check the base total. Go to airtable.com/account and select the workspace under Workspace settings. The page shows how much data each base uses.
- Count each big table. Open a grid view with no filters, click the ˅ icon next to the view’s name and select Download CSV. Filters leave records out of the file. Each file’s row count is that table’s size, and the files are your first backup.
- Work out your runway. Divide the records you have left by the records you add in a typical month.
Example:
| Table | Records |
|---|---|
| Line items | 31,000 |
| Orders | 9,500 |
| Activity log | 4,600 |
| Customers | 2,400 |
| Total | 47,500 of 50,000 |
At about 1,200 new records a month, the 2,500 left last about two months, and line items are where the space comes from.
How do you free up records without breaking anything?
Records have to leave the base. Airtable’s archive method, a filter that hides old records from views, keeps them in it: “Keep in mind that archiving doesn’t free up record limits.”
- Take a snapshot. Click the base history icon in the upper right, then Snapshots, then Take a snapshot. Team keeps one year of snapshot history.
- Pick a cutoff. Use a date field, or a formula field with
CREATED_TIME(), and make a view of older records, such as orders closed before January 1, 2025. Ask your bookkeeper what you need to keep, and for how long. - Freeze the totals you rely on. Rollups update as linked records go away. Copy figures like lifetime sales per customer into a plain number field first.
- Make the archive base. Click the ˅ icon next to the base’s name, select the ... icon, then Duplicate base with records included. In the copy, delete everything after the cutoff and check that its automations are off, since the copy has the same ones. The copy has its own record limit.
- Delete from the live base. In the cutoff view, tick the records’ checkboxes, right-click and choose Delete all selected records. Start with the biggest table. Deleted records stay in the trash for 7 days (base history icon, then Trash, then Restore).
- Check it worked. Recheck the base on the workspace settings page, allowing up to 48 hours for the alert to clear. Then add one test record through each form and connected app.
How do you split a base with Airtable Sync?
Sync shows a view from one base inside another, on any paid plan. It suits a table that grows much faster than the rest, such as orders or logs.
- In the source base, make a grid view with only the records the other base needs.
- Click Share and sync, then Sync data to another base, and turn on Allow data in this view to be synced to other bases.
- Click Sync this view and choose the destination, or click Copy shared view link for someone who has access.
- In the destination base, click + Add or import, then Airtable base under Add from other sources. Pick the view, set sync frequency and what happens to deleted records, then click Create table.
What breaks:
- Synced records still count in the destination. Sync a filtered view, such as this year’s orders, rather than the whole table.
- Links arrive as plain text unless the linked table is synced too. Convert to linked records then matches on the primary field, so duplicate names give wrong links; Airtable recommends a unique identifier as the primary field.
- Team syncs one way. Editing synced records from the other base (“Allow edits from other bases”) needs Business or Enterprise Scale.
- Team allows 10 synced tables per base, Business 20.
- Links you add in the destination stay there. They don’t sync back to the source.
- Automations, interfaces and connected apps that touch the moved tables need repointing. List them before you start.
When is upgrading or moving out the better answer?
Business raises the ceiling to 125,000 records per base, with 100,000 automation runs a month, unlimited API calls and two-way sync. To upgrade, go to airtable.com/account, select the workspace under Workspace settings, click Change plan in the Workspace plan section, click Business, then Upgrade.
Above that, Airtable’s HyperDB lets Enterprise Scale customers work with large datasets, up to 100 million rows per import or sync by default.
If you move the data out, prepare the base so the links survive:
- Add a formula field with
RECORD_ID()to every table. Airtable says this ID “cannot be altered in any way.” - Add a lookup of that ID through each linked record field, so every link exports as an ID instead of a name.
- Download a CSV of every table from a view with no filters, and keep the snapshot.
- List every automation, form, interface and connected app, with what it does and who relies on it.
For the choice between buying a product and building your own, see off-the-shelf and custom software compared. If one person built the base and holds the rules in their head, start with documenting a spreadsheet only one person understands. If you’re thinking of moving back to a spreadsheet, check the size first with the Google Sheets cell limit checker.
What are your options?
| Option | Good when | Watch for |
|---|---|---|
| Move old records to an archive base | Most records are closed history | Rollup totals change; Airtable’s archive filter frees no space |
| Split the base with Sync | One table grows much faster than the rest | Synced records still count; links arrive as text; one-way on Team |
| Upgrade to Business | Growth is steady and the base works well | The next ceiling is 125,000 records per base |
| Move to software of your own | Several bases held together by sync and automations | Rebuilding links, automations and forms; who maintains it |
| Bring in an outside team (Custom software) | The base runs daily work and has to keep running during the move | Time from whoever built the base; agree in writing who owns the code and data |
FAQ
Is the Airtable record limit per base or per workspace? Per base. Automation runs and API calls are counted per workspace.
Do archived records count toward the limit? Yes. Airtable says “archiving doesn’t free up record limits,” so records have to be deleted or moved to another base.
Do synced tables count toward the record limit? Yes, in the base they’re synced into. Sync a filtered view to keep the count down.
What is the record limit on Enterprise Scale? Airtable’s plans page doesn’t list one.
Can I get deleted records back? For 7 days, from the base’s trash. After that, restore from a snapshot, which creates a new base with a new base ID.
Sources
- Airtable plans overview, Airtable Support,
- What happens when I hit my usage limits?, Airtable,
- Airtable workspace settings overview, Airtable Support,
- Adding, duplicating and deleting Airtable records, Airtable Support,
- Creating and managing Airtable bases, Airtable Support,
- Managing trash in Airtable, Airtable Support,
- Taking and restoring snapshots in Airtable, Airtable Support,
- Getting started with Airtable sync, Airtable Support,
- Linking records across synced bases in Airtable, Airtable Support,
- Upgrading and downgrading your Airtable workspace plan, Airtable Support,
- HyperDB in Airtable, Airtable Support,
- Returning record data in Airtable, Airtable Support,