FIX Google Sheets Freezing and Calculation Lag in Chrome (2026)

Key takeaways

• “Calculation Pending” means Chrome’s single JavaScript thread is blocked. Sheets can’t render a new frame while computing.
• Volatile formulas (NOW, TODAY, OFFSET) recalculate on every single edit. One edit triggers 20 recalculations if you have 20 of them.
• Discard background tabs and eliminate volatile formulas first. If lag persists with no other tabs, the fix is in the spreadsheet itself.

You type a value, hit Enter, and Sheets freezes for 10 seconds with “Calculation Pending.” Then you scroll, and it freezes again. Google Sheets runs entirely as a JavaScript application — when a spreadsheet contains complex formulas, large datasets, or many conditional formatting rules, Chrome’s main JavaScript thread stalls while processing the dependency graph. The frozen UI is Chrome unable to render a new frame while Sheets is computing.

Quick Diagnosis

Fix 1: Disable Iterative Calculation

Iterative calculation enables circular references by recalculating repeatedly until values converge. On large sheets, this multiplies the calculation workload for every cell change.

1. In Google Sheets, click File in the menu bar.
2. Select Settings.
3. Click the Calculation tab.
4. Find Iterative Calculation and set it to Off if you do not need it.
5. Click Save settings.

If you do need iterative calculation for specific formulas, reduce the Max iterations setting (the default is 50 — try 10 or fewer).

Fix 2: Reduce Conditional Formatting Rules

Conditional formatting evaluates every rule against every cell in its range on each render pass. Large ranges with many rules are the most common cause of scroll lag in Sheets.

1. In Google Sheets, click Format in the menu bar.
2. Select Conditional formatting.
3. Review all rules in the sidebar. Look for rules applied to entire columns (e.g., column A:A) — these evaluate millions of cells.
4. Change column-wide rules to apply only to the data range with actual content (e.g., A2:A500 instead of A:A).
5. Delete any rules that are no longer needed.
6. Keep the total number of conditional formatting rules under 20 for large sheets.

Fix 3: Free Chrome Memory for Large Sheets

If the Sheets tab itself is approaching Chrome’s per-process memory limit, it will crash or stop responding entirely.

1. Press Shift + Esc to open Chrome Task Manager.
2. Find the Google Sheets tab and check its Memory Footprint.
3. If it exceeds 1.5 GB, consider splitting the sheet data across multiple files.
4. Discard other open tabs: go to chrome://discards/ and click Urgent Discard on inactive tabs.
5. Reload the Sheets tab after freeing memory — the sheet reloads from Google’s servers with a fresh memory allocation.

Fix 4: Reduce Volatile and External Formulas

Volatile formulas — NOW, TODAY, RAND, RANDBETWEEN, OFFSET, INDIRECT — recalculate every time any cell in the spreadsheet changes, not just when their own dependencies change. If you have 20 of these scattered across a large sheet, every single edit triggers 20 full recalculations. External formulas like IMPORTRANGE add network latency on top of that.

1. Identify volatile formulas by searching for =NOW(, =TODAY(, =RAND(, =OFFSET(, =INDIRECT( in your sheet.
2. If you use NOW or TODAY only for display purposes, replace them with static values and update manually.
3. For IMPORTRANGE: reduce update frequency by restructuring to avoid circular dependencies.
4. For large datasets, replace QUERY formulas that span entire columns with formulas that reference only the rows containing data.

Fix 5: Close Background Tabs Before Working in Sheets

Chrome’s JavaScript engine is shared across all tabs running in the same process group. Background tabs running JavaScript — auto-refreshing dashboards, news sites with live content, social media feeds — consume CPU that Sheets needs for calculations.

1. Before opening a large spreadsheet, go to chrome://discards/ and discard all tabs you do not need.
2. In Chrome Task Manager (Shift + Esc), verify that CPU usage from other tabs is low before opening Sheets.
3. Keep only Sheets and the tabs you need for your work session active.
4. For critical calculation work, restart Chrome first to clear all accumulated background CPU usage.

Fix 6: Set Zoom to 100%

Browser zoom levels other than 100% force Chrome to apply subpixel rendering calculations to every element on screen, adding rendering overhead on top of the calculation workload.

1. Check the current zoom level in the Chrome address bar (zoom indicator appears on the right side).
2. Press Ctrl + 0 (Windows) or Cmd + 0 (Mac) to reset to 100%.
3. If you need a larger UI for accessibility, consider using Sheets’ built-in zoom controls (View > Zoom) instead of browser zoom.

Freeing CPU for Sheets Recalculation

If background tabs are the bottleneck — you’re seeing lag in Sheets but it clears up after a Chrome restart — SuperchargePerformance can help by automatically discarding those idle tabs. This eliminates their JavaScript execution entirely, not just reduces it, freeing CPU for Sheets calculations. It also blocks third-party scripts in other open tabs, reducing background JavaScript activity.

If your Sheets lag persists even with no other tabs open, the fix is in the spreadsheet itself (Fixes 1–4), not the browser environment.

Technical Background

Google Sheets calculates cell dependencies using an internal dependency graph. When you change a cell value, Sheets identifies all formulas that depend on the changed cell and recalculates them in order. For sheets with hundreds of interconnected formulas, this dependency traversal involves thousands of JavaScript operations on the main thread.

Chrome’s JavaScript engine is single-threaded per tab. All calculation work, UI rendering, and event handling for the Sheets tab shares a single thread. When a calculation run takes more than 16 milliseconds — the budget for a 60 fps frame — Chrome cannot update the UI and the tab appears frozen until the calculation completes.

Background tabs running JavaScript reduce the CPU resources available to Sheets because Chrome’s process scheduler shares CPU time across all renderer processes. Discarding background tabs eliminates their CPU consumption entirely, not just reducing it — a discarded tab has zero running JavaScript.

For related issues, see Fix Chrome High Memory Usage and Fix Figma Out of Memory in Chrome.