Paste 30 rows into a quote list and the screen freezes every time, leaving you waiting ten-plus seconds. The same happens when you fix a single row. If you run order management on a spreadsheet, you may run into this situation.
The manual calculation setting, which began rolling out in stages on September 21, helps with some of these symptoms. But there is also slowness it does not help with. Start by working out which kind your file has.
What is added is an option to "pause"
According to the Google Workspace Updates announcement, a setting is being added that lets editors of complex or data-heavy spreadsheets pause automatic recalculation, batch their edits and then run a sheet-wide update whenever they choose. It is OFF by default, and users turn it on under "File" → "Settings" → "Calculation". It is available to all Google Workspace customers and Workspace Individual subscribers. A gradual rollout began on September 21, 2026, and the official guidance says it can take up to about 15 days for the setting to appear, so some environments may not see it yet.
This is not a change that gets switched ON in bulk from the Admin console (there is no admin setting); it is a setting that the people editing a file choose for themselves. According to Google's official help, only editors can use manual calculation, and it is not available in the Google Sheets app on smartphones. In other words, this is not a procedure for the IT team to roll out company-wide, but something to tell the people struggling with heavy files: "here is a way out."
Slowness it helps with, and slowness it doesn't
Pausing recalculation speeds things up mainly when "the calculations rerun every time you do something." For files that are heavy from the moment they open, the total volume of calculation is likely to matter more than how often it runs, so pausing should not make much of a noticeable difference.
| Symptom | Primary cause | Effect of manual calculation |
|---|---|---|
| Freezes on every paste or bulk edit | The web of formulas is re-evaluated on every edit | Helps. Batch your edits, then update |
| Slow right after opening; scrolling stutters | The sheer volume of formulas, conditional formatting and rows | Unlikely to help. A matter of slimming down the design |
| Values from other files stay outdated | Update intervals and permissions for external references | A separate problem. Pausing makes them even more outdated |
The order for isolating the cause is simple. Open the file and, without touching anything, see whether it is slow. If it is, you can surmise that the problem is mainly the total volume; if it is not, the problem is recalculation on each operation. Applying manual calculation to the former should have little effect, so do this check first.
Leave it paused and outdated numbers get passed around
With manual calculation, the sheet keeps showing "the values as of the last time an update was run." Calculation settings apply to the entire spreadsheet and are reflected for everyone working on the same file. The person who paused it may remember, but someone else who opens it from a shared link may well take those values as the current numbers.
If you adopt the practice of pausing, decide at least these two things. Who runs the update, and when to switch back to automatic calculation. And that the file is not shared with others while it is paused. Leave it paused on sheets such as invoicing or inventory, where a discrepancy in values translates directly into a discrepancy in amounts, and you trade speed for more errors.
Whether to pause depends on whether you are the only person looking at the file or several people are. A realistic line is to allow pausing while you are building something on your own, and not to pause a list that someone is always referring to.
What to think about after the stopgap
Manual calculation does not remove the cause of the slowness; it reduces how often you run into it. If you are kept waiting after pastes many times a month, and several people are working on the same file, that is a sign that your use of spreadsheets has reached its limit.
We treat the higher cell limit and whether you should keep running operations on spreadsheets as separate questions in where to draw the line now that the cell limit has doubled. For an approach that builds only the input screen and moves the back end to a database, see how to provide input screens for business systems; for a starting point on automation that reduces manual work, see automating Google Sheets.
The first thing to do is pick one heavy file and record how slow it is right after opening separately from how slow it is while editing. Once you know that much, you can tell whether changing a setting is enough or whether the way the file is built has to change.
On September 24, 2026, we rechecked the Google Workspace Updates announcement and the Google Docs Editors Help, using the excerpts of each page included in search results. We have not turned on the manual calculation setting in an actual environment or measured speed. The distinction between slowness it helps with and slowness it does not is the editorial team's own framework, not a product specification.
For taking stock of the operations you run on spreadsheets or deciding how much to move into a system, please consult GleamHub.
