The short answer
Use Google Sheets when the work is numbers: budgets, forecasts, commission maths, reporting, cleaning a CSV, anything with a formula in it, and anything that will grow past 50,000 rows. Use Airtable when the work is records that point at other records, and the people using it need to see those records as a kanban board, a calendar or a gallery of cards rather than a grid. If you already pay for Google Workspace and your team is under ten people, start in Sheets and only move the parts that genuinely need a database.
What each one actually is
Google Sheets is a spreadsheet. Every cell can hold a value or a formula, and the formulas are the product: about five hundred functions, plus QUERY, ARRAYFORMULA, IMPORTRANGE and XLOOKUP, plus Apps Script, which is a full JavaScript runtime with access to Gmail, Drive, Calendar and any REST API. A file can hold 10 million cells and up to 18,278 columns. It is free with any Google account and included in every Workspace plan.
Airtable is a relational database with a grid on the front. The unit is a record, not a cell, and each field has a type: single line text, attachment, checkbox, date, or a link to a record in another table. Linked records, lookups and rollups do the work that joins do in SQL, and the same records can be viewed as a grid, a kanban board, a calendar, a gallery, a form or a Gantt chart. The free plan allows 5 editors and 1,000 records per base. The Team plan is $20 per editor per month billed annually, or $24 monthly, and lifts that to 50,000 records per base. Business is $45 per editor per month billed annually. Only editors are billed; people who just view or submit forms are free. Check airtable.com/pricing before you budget, because the record caps have changed more than once.
Side by side
| Google Sheets | Airtable | |
|---|---|---|
| Data model | Cells in a grid. Tables are a convention, not a structure. | Typed fields, records, and links between tables. |
| Views | Grid, filter views, pivot tables, charts. | Grid, kanban, calendar, gallery, form, Gantt, timeline. |
| Formulas | About 500 functions, QUERY, ARRAYFORMULA, IMPORTRANGE, LAMBDA. | Field formulas, lookups, rollups. No cross-table query language. |
| Automation | Apps Script: unlimited, free, any API, scheduled triggers. | Built-in automations with a monthly run cap per plan; scripting on paid plans. |
| Integrations | Sheets API, Apps Script, every connector tool supports it. | Clean REST API, webhooks, native sync to common tools. |
| Sharing and permissions | File, sheet and range level. Protected ranges, view-only links. | Per base, per table and per view; interface pages for non-editors. |
| Free tier limits | 10 million cells per file, unlimited editors. | 5 editors, 1,000 records per base, limited automation runs. |
| Paid price | Included in Workspace; no per-seat charge for Sheets itself. | $20 per editor per month (Team, annual), $45 (Business, annual). |
| Learning curve | Everyone has used a spreadsheet. | Gentle for viewing, steeper once you design tables and links. |
| Data ownership | Lives in your Drive, exports to CSV or Excel in one click. | Hosted by Airtable; CSV export loses links, views and automations. |
Pick Google Sheets if
- The work is calculation. Budgets, pricing, commissions, cohort tables, cash flow, anything where one number depends on another. Airtable field formulas can do arithmetic on a record, but they cannot run a
QUERYacross a table or spill a result down a column withARRAYFORMULA. - You have, or will have, a lot of rows. Order lines, transactions, log exports, ad platform data. Airtable Team stops at 50,000 records per base. A Sheets file takes 10 million cells, so a 20-column table runs to half a million rows before you notice.
- You need reports and dashboards. Pivot tables, charts, conditional formatting and a QUERY that summarises a raw tab into a clean one are all native. Airtable's charting lives in Interfaces and is thinner.
- Nobody wants another subscription. A ten-person team on Airtable Team is $2,400 a year billed annually. The same team already has Sheets.
- Automation matters and you have anyone who can write JavaScript. Apps Script sends the email, calls the API, writes the PDF and runs on a timer, for nothing.
Pick Airtable if
- Records relate to other records and that relationship is the point. A content calendar where each post links to a campaign, a writer and three assets. A hiring pipeline where candidates link to roles and interviews. In Sheets you can fake this with IDs and lookups; in Airtable the link is a field and it never breaks when someone sorts a column.
- The team thinks in boards and cards, not grids. Kanban by status, calendar by due date, gallery of product photos, all on the same records, with one click to switch. Sheets has none of these.
- You need forms that write straight into typed fields, with attachments, and then a view for the person who processes them. Google Forms into Sheets works, but attachments and validation are weaker.
- Different people should see different slices. Airtable Interfaces give a non-editor a page with only their records and only the fields they need. Sheets can protect ranges, but one file is still one file.
- The dataset is small and the structure is the value. Under 50,000 records, a few related tables, people updating fields rather than running maths.
The two mistakes people make
Running a database in Sheets. The sign is a file with eight tabs, an ID column on each, and twenty VLOOKUPs holding it together. It works until someone inserts a row in the wrong place, sorts a single column, or pastes over a key. If the file has become a system of record for things that link to other things, and nobody is doing maths on it, it wants to be a database. That might be Airtable, or it might be a proper database with Sheets reading from it.
Doing finance in Airtable. The sign is a base where someone has built a monthly P&L out of rollup fields and a dozen summary tables, and it takes a page of formula fields to get a running total. Airtable has no concept of a range, so anything that needs the row above, a cumulative sum, a scenario toggle or a 12-month projection is painful. Export the records to Sheets and model there.
Using both
The split that works in practice: Airtable holds the records that people edit by hand through forms and boards, and Sheets holds the numbers. A sync, a scheduled Apps Script pulling from the Airtable API, or a weekly CSV export moves the records into a Sheets tab, and the reporting, forecasting and dashboards sit on top of that. Each tool is doing the thing it is built for, and the only thing you maintain is one direction of data flow.
Moving from Airtable to Google Sheets
Export every table as CSV from the view menu and import each into its own sheet. Linked record fields export as the primary field of the linked record, comma separated, so make sure each table has a unique ID column before you export and link on that. Rebuild the joins with XLOOKUP or QUERY. Attachments export as URLs that expire, so download them to Drive if you need them. Views, automations and Interfaces do not export at all and have to be rebuilt as filter views, Apps Script and separate tabs. Budget a day for a base of five tables.
Going the other way, Airtable imports CSV directly and guesses field types. Fix the types by hand, split your ID columns into real linked-record fields, and expect to lose every formula, since Sheets formulas have no equivalent on the Airtable side.
Questions people ask
Is Airtable better than Google Sheets?
Neither is better in general. Airtable wins when records link to other records and people need boards and galleries. Sheets wins for calculation, reporting, large tables and cost. Decide by the job.
Is Airtable free?
There is a free plan with 5 editors, 1,000 records per base and a small monthly automation allowance. Past that it is $20 per editor per month billed annually on Team. Sheets is free with a Google account.
Can Google Sheets do what Airtable does?
Partly. Lookups, Google Forms and Apps Script get you a long way. You will not get native linked-record fields, rollups or kanban and gallery views without building an app layer on top.
Which is better for a CRM?
For a small sales team that lives in a pipeline board, Airtable. For a team that wants to forecast revenue off the same data and already has Workspace, Sheets, with the pipeline as one tab and the model as another.
If you would describe the problem with the word "calculate", use Google Sheets. If you would describe it with the word "track", and the things you are tracking point at each other, use Airtable. If you are not sure, start in Sheets, because moving out of it is cheap and moving out of Airtable is not.
For the three-way version with Notion, see Google Sheets vs Airtable vs Notion.