Help for owners
My Google Sheet has become slow and keeps freezing
Short answer
Google lists a limit of 20 million cells or 100MB for a spreadsheet created in or converted to Sheets, and slowness usually starts long before that. The common causes are huge ranges, formulas that read other files, and everything stored in one tab. Copy the file, archive old rows, and simplify formulas before anything else.
Does this sound like your situation?
- The sheet takes a long time to open or shows a spinner.
- Typing in a cell hangs for seconds.
- Browser tab crashes or says the page is not responding.
- Formulas show loading for a long time.
- It was fast last year and slows a little more each month.
Why does this happen?
The sheet is bigger than it looks
Google states a limit of up to 20 million cells or 100MB for spreadsheets created in or converted to Google Sheets. Cells count even when they are empty, so hundreds of unused columns and thousands of blank rows add weight.
Confirmed by support.google.com
Every formula recalculates
Formulas that look at whole columns, or that depend on other formulas in long chains, are recalculated whenever anything changes. Many of them together make each edit slow.
Formulas that reach into other files
Importing ranges from other spreadsheets, or pulling live data from the web, adds waiting time on every refresh.
History piles up in one place
Years of old orders or logs sit in the same tab as today's work, so every view and formula has to carry them.
Heavy formatting and many viewers
Conditional formatting over huge ranges, many charts and pivot tables on the same data, and several people editing at once all add load.
What can I do about it today?
- Make a copy before touching anythingUse File, then Make a copy, and work on the copy. Google also keeps a version history you can restore from, but a copy is the safest.
- Archive old rowsCopy last year's rows into a separate file, check they are complete, and only then remove them from the live one.
- Delete unused columns and rowsBlank columns and rows still count as cells. Remove the ones that are truly empty, in the copy first.
- Replace whole-column formulasLimit formulas to the rows that hold data, and turn rarely changing results into plain values after checking them.
- Count your importsList every formula that pulls from another file or the web. Each one is a reason for waiting.
When should I bring someone in?
- The sheet is something your business cannot run without and it keeps crashing.
- Several staff use it all day and you cannot archive old data.
- Trimming it helps for a month and then it is slow again.
How do I handle it?
- Measure what is actually heavyI find which tabs, ranges and formulas cost the most, instead of guessing.
- Split live from archiveCurrent work stays small, history moves to a separate place that is still searchable and reportable.
- Rewrite the formulas that are heavyWhole-column lookups, chains and repeated imports are simplified, and results are checked against the old ones.
- Decide if a sheet is still the right toolIf size and use are growing, the next step is moving the data to a database with a simple screen over it, one process at a time.
- Keep a way backA backup copy and a written list of changes make every step reversible.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is it the browser or the sheet?
Try opening it in another browser or in a private window. If a fresh blank sheet is fast and this one is slow, the sheet is the cause.
Will deleting rows delete history?
Deleting rows removes them from the live file. Archive them first and keep the copy.
Is there a page about the quota errors?
Yes, the help page on Google Sheets API quota errors covers automations that fail with 429. This page is about a sheet that is slow to use.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.