Tab Suspension
Troubleshooting guides, comparisons, and practical tips for tab suspension issues in Chrome. Free solutions from SuperchargeBrowser.
1 article
Tab suspension — discarding a tab's renderer process to free RAM while keeping it visible in the tab bar — is the highest-leverage memory optimization available in Chrome. A suspended tab uses under 1MB of memory instead of 150–500MB. The tab stays in the bar, its title and favicon are preserved, and clicking it reloads the page from the network.
Chrome calls this Memory Saver. Edge calls it sleeping tabs. The mechanism is identical: chrome.tabs.discard() terminates the renderer process. The behavior differences are in control granularity. Chrome Memory Saver in Chrome 147 has three modes — Moderate, Balanced (ML-predicted), and Maximum — but no configurable timeout and no per-site whitelist UI visible in settings.
The tradeoff is page reload latency. A fast news site reloads in 1–2 seconds. A large Figma file reloads in 30–60 seconds and loses unsaved work. The right setup is aggressive suspension everywhere except a whitelist of apps where reload cost is high: Figma, Miro, Google Docs, Notion, ChatGPT, and similar stateful tools.
Chrome 147 adds ML-based prediction (Balanced mode) that estimates which tabs you are unlikely to return to and suspends those specifically, rather than suspending all inactive tabs uniformly. In practice, Maximum mode with a domain whitelist is still more predictable for users who want explicit control over what gets suspended.
Frequently Asked Questions
What is the difference between Chrome Memory Saver and a tab suspender extension?
Chrome Memory Saver (available since Chrome 108, improved in Chrome 126/147) suspends inactive tabs automatically. As of March 2026, it has three modes but no configurable timeout, no visual indicator on suspended tabs, and limited whitelist control in the UI. Extensions like SuperchargePerformance add a configurable timer, auto-protect named app categories, and display a RAM savings counter. Both use the same chrome.tabs.discard() API underneath.
Will suspended tabs lose my data or scroll position?
Yes. Tab suspension discards the renderer process entirely — all JavaScript state, scroll position, unsaved form data, media playback, and WebSocket connections are lost. When you click back to the tab, it reloads from the network. As of March 2026, the only way to preserve state is to whitelist specific sites from suspension. Stateful apps like Figma, Notion, and Google Sheets should always be on the whitelist.
How much RAM does tab suspension actually save?
Significant amounts. A typical active tab uses 150–300MB. A suspended tab uses under 1MB. Suspending 20 inactive tabs on a typical browsing session frees 3–6GB of RAM. As of March 2026, the measured impact on ad-heavy pages with scripts loaded is even higher — those tabs can use 300–600MB each, so suspending them frees proportionally more memory.
SuperchargePerformance
Tab suspension, ad blocking, and script control. Free.