The Google Sheets cell limit is 20 million cells or 100 MB per spreadsheet, counted across every tab. For converted bank statements that is a lot of room: a household account fills a few thousand cells a year. Business files and multi-client workbooks get closer, mostly through helper columns and unused grid rather than transactions.
What does the Google Sheets cell limit count?
The limit applies to one spreadsheet file, not to one tab. Google's page on the files you can store in Google Drive gives it as up to 20 million cells or 100 MB for spreadsheets created in or converted to Google Sheets. Whichever you reach first is the ceiling.
Cells are the grid itself: rows multiplied by columns, on every tab, added together. A tab with 1,000 rows and 26 columns holds 26,000 cells, whether you typed in ten of them or all of them. Five tabs of that size hold 130,000.
The 100 MB figure matters less for statement data. Dates, short descriptions and amounts are small. Long notes, many formulas and pasted images grow a file faster than plain transaction rows do.
How many years of statements fit under the Sheets cell limit?
For most people, decades. One transaction is one row, and a statement table usually needs six to ten columns. Multiply transactions per year by columns and you have the cells a year uses. Divide 20 million by that and you get a rough count of years.
Worked example
The three setups below use made-up but typical volumes. Each assumes one row per transaction and nothing else in the file.
| Example setup | Transactions per month | Columns | Cells per year | Years that fit in 20 million |
|---|---|---|---|---|
| Household checking | 60 | 7 | 5,040 | about 4,000 |
| Small business, two accounts | 2,000 | 10 | 240,000 | about 83 |
| Bookkeeper, 50 clients in one file | 15,000 | 10 | 1,800,000 | about 11 |
The household line shows why most people never meet the limit. The bookkeeper line is where planning starts. Eleven years sounds comfortable, but add the extra columns in the next section and the margin shrinks quickly.
Speed usually becomes a problem well before the cap does. A file with a few hundred thousand rows and many formulas can feel slow long before it is full; the guide to a Google Sheets file slow with large data covers how to lighten one.
Helper columns and blank grid that eat the cell allowance
Cells you never filled count the same as cells you did. The usual culprits in a statement workbook are empty columns to the right of the data, thousands of blank rows below it, and helper columns that hold one formula per row. Each one multiplies across every row of the table.
Three habits keep the count honest:
- Delete unused columns. A sheet that runs to column Z when your data stops at H carries 18 empty columns on every row.
- Delete unused rows below the last transaction, instead of leaving room for growth. Add rows when you need them.
- Replace per-row helper formulas with one array formula, or move the calculation to a summary tab that holds a few hundred cells instead of a column of a million.
Copies count too. A tab duplicated "just in case" doubles its cells. If you keep reference copies, keep them in a separate file.
Excel uploads that break the Sheets per-cell text cap
There is a second limit to watch when you bring in an Excel file. The same Google page says that when Excel files convert to Sheets, any cell with more than 50,000 characters is removed. Statement lines never get near that, but a notes column with pasted email threads can.
The full file also has to fit under 20 million cells after conversion. An XLSX that worked in Excel can be larger than that, because Excel worksheets allow more rows. If the conversion refuses or the result is missing tabs, split the workbook in Excel first.
Balance sheets and reports converted from PDFs are rarely large, but they can carry long text cells from footnotes. The guide to converting a balance sheet PDF to Excel shows how to keep notes out of the figures.
Splitting a statement workbook before the Sheets cell cap
When a file passes about half the limit, split it on a boundary that matches how people use it: one file per year, per client or per account. Keep a small summary file that pulls totals from each, so reports still work without the raw rows sitting in one place.
A practical split for the bookkeeper example:
- Create one spreadsheet per client, or per client and year.
- Keep the same column order in every file, so summaries and formulas can be copied between them.
- Build a summary spreadsheet that brings in totals with IMPORTRANGE, rather than copying every transaction.
- Archive closed years: download them, keep the copy, and remove them from the working file.
Smaller files are also easier to share safely. A client can see their own file without seeing anyone else's, and you can give view-only access to a summary; sharing a Google Sheet view-only explains the settings.
New statements then go into the right file from the start. FastBankConvert, which is getting ready to open, is built to produce one CSV or Excel file per statement, a size that slots into a per-client workbook. Get started to hear when trial conversions begin.