STOP Chrome Reloading Tabs When You Switch Back (2026 Fix)

Chrome reloads tabs because Memory Saver (available since Chrome 110) discards background tabs after roughly 5 minutes of inactivity when RAM gets low. The fastest fix: add affected sites to the exception list at chrome://settings/performance. Takes 30 seconds and requires no extension.

You are mid-sentence in a document, tab over to the research page you had open, and it reloads. The scroll position is gone. The filter you set on that table is gone. If you were halfway through a form, that is gone too. Chrome does not warn you. It just reloads, quietly, as if nothing happened.

This is Memory Saver doing exactly what it was designed to do. Whether that feels like a feature depends entirely on which tabs it chose to discard.

Why Chrome Reloads Your Tabs

Memory Saver (found at chrome://settings/performance) is Chrome’s built-in answer to a real problem: 30 open tabs can consume 3-6 GB of RAM, and on most laptops that is a meaningful chunk of the machine’s total. Chrome’s solution is to terminate the renderer process of background tabs after a period of inactivity, freeing that RAM immediately.

When you return to a discarded tab, Chrome reloads the page from the network. Same URL, but a full new navigation — no cached scroll position, no JavaScript state, no form data.

In Chrome 140 (September 2025), Google introduced a machine-learning model that informs discard decisions. The model factors in how long ago you visited the tab, how much RAM the tab is using, and signals from your recent browsing patterns. Chrome 149 continues with this approach. The heuristics are not perfect, and they are not designed to know that the tab you discarded was the one you needed most.

The key distinction: this is not a bug you can patch with a cache clear or a Chrome restart. Memory Saver will keep discarding background tabs until you either disable it, add exceptions, or reduce the memory pressure that triggers it.

The One Setting That Stops It

Chrome’s Memory Saver has a native per-site exception list. Sites on this list are never discarded, regardless of how long they have been in the background.

How to add a site:

1. Navigate to chrome://settings/performance
2. Under Memory Saver, confirm the toggle is on (you need it on to access the exception list)
3. Click Add next to “Always keep these sites active”
4. Enter the domain — for example, notion.so or docs.google.com
5. Click Add to confirm

Chrome applies the exception immediately. You do not need to relaunch.

A note on format: Chrome matches on the full origin, so docs.google.com and sheets.google.com are separate entries. If you want to protect all Google Docs apps, add each subdomain individually.

If tabs reload specifically on battery power but not when plugged in, check chrome://flags for energy-saver-related flags — Chrome has experimented with additional tab freezing when on battery. Disabling the relevant flag (if present in your Chrome version) stops that behavior.

The tradeoff is honest: every site you add to the exception list is a tab that stays resident in RAM. If you have 5 protected sites but 40 other tabs open, Memory Saver still does its job on the other 35. If you add 30 exceptions, you have effectively disabled Memory Saver for most of your session.

Why the Tradeoff Exists

Chrome runs in a multi-process architecture — each tab gets its own renderer process. That design is why one tab crashing does not take down your whole browser. It is also why Chrome’s RAM usage looks alarming in Task Manager.

Thirty tabs at an average of 100-200 MB each puts Chrome between 3-6 GB before you have opened any other applications. On a machine with 8 GB of RAM, that is half the system, and on 16 GB, it is still enough to cause swapping and slowdowns under load.

Memory Saver is Chrome’s binary answer to this: keep or discard. The problem with binary is that Chrome has no way to know which tab is actually important to you right now. It does not know that the discarded tab had a half-finished expense report. It only knows that the tab has been in the background for several minutes and is consuming memory Chrome could use elsewhere.

Chrome’s heuristics optimize for system stability, not for your particular browsing pattern.

A Smarter Approach: Suspend Tabs Without Losing What Matters

Tab suspension works the same way as Memory Saver under the hood — it calls chrome.tabs.discard() on background tabs to free their memory. The difference is in the targeting.

Chrome’s Memory Saver picks targets reactively based on its own model. An extension can suspend tabs proactively, on a predictable timer, with explicit rules about which tabs are off-limits.

SuperchargePerformance approaches it this way:

The 25+ auto-protected apps cover the ones most people have open constantly: Gmail, Google Docs, Sheets, Slides, Drive, Calendar, Figma, Notion, Linear, Miro, Canva, Lucid, Airtable, Asana, Monday, Slack, Discord, Teams, Spotify, YouTube Music, Google Meet, Zoom, and others. You do not need to add these manually.

For everything else, the extension suspends tabs on a predictable schedule. You always know which tabs are sleeping (they show a suspension indicator) and which are protected. There is no ML model making opaque decisions about what matters to you.

No account, no telemetry, free core tier.

When Memory Saver Is Actually Enough

If you have fewer than 15 tabs open and none of them are heavy web apps with significant state, Chrome’s built-in Memory Saver handles the problem well. Add two or three sites to the exception list, leave everything else to Chrome, and move on.

The extension approach earns its keep when:

• You consistently have 20+ tabs open across multiple projects
• You use apps like Notion, Linear, or Figma where a reload breaks your context
• You find yourself adding site after site to Chrome’s exception list
• You want to see which tabs are suspended and which are running

If the extension does more than you need, uninstall it — nothing is locked in.

Quick Fix Reference

If you have fewer than 15 tabs: use chrome://settings/performance exceptions. Five minutes of setup, no extension needed.

If you have 20+ tabs or use heavy web apps daily: SuperchargePerformance gives you the same RAM savings with smarter targeting — your important tabs stay loaded, idle ones get suspended on a predictable schedule.

Both paths stop the reloads. Pick the one that matches your tab count.