Is Chrome Memory Saver Good in 2026? Tested Review

Key takeaways

• Memory Saver waits for RAM pressure and a revisit-prediction model — not a timer you set. In our 32-tab test, Chrome sat near 3 GB before it discarded anything.
• No configurable timer, no ad blocking, no per-tab readout. It’s deliberately minimal, and that’s fine under 10 tabs.
• Above 20 tabs you’re reacting to a crisis instead of heading it off.

You open Chrome after the weekend. The fans spin up, the laptop gets warm, and Task Manager says the browser is eating 6 GB across the 40 tabs you forgot to close. Chrome’s built-in Memory Saver is supposed to stop exactly this. So does it? As of August 2026 (Chrome 151), the answer is: under 10 tabs, completely. Above 20, it works, but only once your RAM is already under strain. This review covers what it does, the numbers we measured, and where it runs out of road.

The Verdict in One Table

We rated Memory Saver on the four things people actually want from a tab-memory tool. Original test run on Chrome 149, Windows 11, 16 GB RAM; settings and behavior re-checked on Chrome 151.

Overall: 3 / 5. A solid default for light tab users, thin for anyone who keeps 20+ tabs or wants to see what’s happening.

What We Measured

We loaded 32 tabs — a mix of docs, news, two video sites, a Figma board, and a dozen articles — then left Chrome idle and watched RAM in Windows Task Manager.

Two things stood out. First, nothing discarded until Chrome was already past 3 GB — the savings are real but they arrive late. Second, Figma, the audio tab, and our two pinned tabs were never touched, which is correct behavior but means a chunk of the heaviest RAM stayed put. The ~38% on Maximum lines up with Google’s own “up to 40%” headline figure, so the feature delivers what it claims. It just claims a session-wide average, not aggressive per-tab reclaim.

Set Your Own Before/After Baseline

Our test above used Windows Task Manager for a quick read on total RAM. If you want to confirm Memory Saver is doing something on your own machine, Chrome’s own Task Manager gives a cleaner before/after than watching one OS-level number drift.

1. Open it with Shift+Esc on Windows and Linux, or the Window menu on macOS. Right-click any column header and turn on Memory footprint — that column reflects real per-process RAM, not CPU or network activity.
2. Set the baseline with your normal tab count, not a pile of tabs assembled for the test. Note the figure next to the “Browser” row and each tab you aren’t actively using. If you typically run 8-10 tabs, don’t expect much movement at all — Memory Saver reacts to RAM pressure, and light sessions rarely produce enough of it to matter.
3. Keep working normally instead of clock-watching. Balanced mode’s revisit model and the pressure threshold both run on numbers Google hasn’t published, so there’s no fixed number of minutes to wait out.
4. Come back later and reopen Task Manager. A tab Memory Saver actually discarded doesn’t just show a smaller figure — its row disappears from the list entirely, because the renderer process behind it is gone. A tab whose footprint merely dipped from a background script or a sync cycle is still sitting there; it only shrank.
5. Cross-check against chrome://discards. Once a tab’s Discarded column flips to Yes, that’s confirmation. A number moving on its own in Task Manager is not.

The distinction this settles: a shrinking figure can be noise, a vanished row can’t. If chrome://discards shows nothing discarded after a normal day of use, Memory Saver isn’t broken — see our breakdown of why it stays idle on lighter setups for the pressure-threshold explanation.

What Chrome Memory Saver Actually Does

Memory Saver is a browser-level feature, not an extension. It discards inactive tabs based on system memory pressure and, since Chrome 140 (September 2025), an on-device model that estimates how likely you are to revisit each tab. Configure it at chrome://settings/performance.

The discarded tab stays in the tab strip. Clicking it reloads the page from the network. Under the hood this is the same chrome.tabs.discard() call that third-party suspenders use — the difference is entirely in when and which tabs get hit.

Where It Stops

Memory Saver is minimal by design. As of August 2026 it has no:

• Configurable inactivity timer (you cannot set “suspend after 5 minutes”)
• Per-tab or per-session RAM readout
• Ad blocking, tracker blocking, or script control
• Preloading for faster navigation
• Granular protection beyond the built-in audio / pinned / form / download heuristics

The timer gap is the one most people hit. Balanced and Maximum are coarse buckets; if your machine has plenty of headroom, Memory Saver may sit idle for a long time before pressure crosses the threshold and it acts. You can nudge it manually at chrome://discards with Urgent Discard on any tab row, but doing that by hand defeats the “automatic” promise.

Memory Saver vs. a Dedicated Suspender

Memory Saver and a dedicated suspender call the same API. The extension’s edge is control and timing, not magic. It discards on a clock you set, shows an estimate of the memory it freed, and stacks ad blocking on the active tabs Memory Saver never touches. SuperchargePerformance runs fully local with no account and no telemetry, which matters more to some readers than the RAM numbers do.

When Memory Saver Is the Right Pick

Stay with the built-in feature if you keep fewer than 10 tabs, don’t run heavy web apps, and have no interest in ad blocking. It’s free, installs nothing, and asks for no attention.

Reach for a dedicated suspender if any of these is you:

• You routinely hold 20+ tabs and want them suspended before the laptop heats up.
• You want to see, per tab, how much RAM you reclaimed.
• You’d rather one tool handle both memory and ads than juggle two.

If you mostly want the timing control and don’t need ads handled, read the full tab suspender vs Chrome Memory Saver breakdown. If you just need to switch the built-in feature on first, the step-by-step enable guide covers the three settings that matter.