Chrome Memory Saver: How to Use It and When to Upgrade (2026)
Chrome Memory Saver waits for RAM pressure before acting. A timer-based suspender cuts 90-95% per tab proactively. We tested both. Here's when each wins.
Key takeaways
- Memory Saver waits for RAM pressure. At 30 tabs, Chrome may already hit 3 GB before it suspends a single one.
- No configurable timer, no ad blocking, no per-tab dashboard — it’s intentionally minimal.
- Fine under 10 tabs. Above that, you’re reacting to a crisis instead of preventing one.
Chrome’s built-in Memory Saver freezes background tabs to free RAM — the same basic idea as sleeping tabs in Edge or a third-party tab suspender. For someone with fewer than 10 tabs, it’s completely adequate. But if you’ve ever opened Chrome after a weekend and watched it claw back 8GB of RAM from 50 tabs it somehow held onto, you’ve already found the limits of what Memory Saver does. This review is about what it actually does, where it stops, and when you need something more.
What Chrome Memory Saver Actually Does
Chrome Memory Saver is a browser-level feature, not an extension. It discards inactive tabs based on system memory pressure. You can configure it at chrome://settings/performance.
| Setting | Behavior |
|---|---|
| Balanced | Discards tabs when system RAM is low |
| Maximum | Discards tabs more aggressively |
| Always keep active | Exclude specific sites from being discarded |
The feature uses the same underlying chrome.tabs.discard() mechanism that third-party extensions use. The tab stays visible in the tab bar; clicking it reloads the page from the network.
What Chrome Memory Saver Cannot Do
Chrome Memory Saver is intentionally minimal. It has no:
- Ad blocking or tracker blocking
- Script control
- Per-tab RAM savings dashboard
- Configurable inactivity timer (you cannot set “suspend after 5 minutes”)
- Protection logic for pinned tabs, audible tabs, or tabs with unsaved forms beyond basic heuristics
- Preloading for faster navigation
How to Configure Chrome Memory Saver
- Navigate to
chrome://settings/performance - Under Memory, select Balanced or Maximum
- Click Add under “Always keep these sites active” to exclude domains you never want discarded
- For immediate manual control, visit
chrome://discardsand use the Urgent Discard action on any tab row
Chrome Memory Saver vs. a Dedicated Extension
| Feature | Chrome Memory Saver | SuperchargePerformance |
|---|---|---|
| Tab suspension | Yes (memory pressure) | Yes (configurable timer: 5 or 15 min) |
| Suspension trigger | System RAM pressure | Inactivity timer |
| Audible tab protection | Basic | Skips any tab where tab.audible is true |
| Pinned tab protection | No | Yes |
| Form input protection | No | Yes |
| Ad blocking | No | Yes (declarativeNetRequest, L1-L3) |
| Tracker blocking | No | Yes |
| Script blocking | No | Yes |
| RAM savings dashboard | No | Yes (per-tab + total) |
| Per-site whitelist | Basic exclude list | Full per-site feature control |
| Cost | Free (built-in) | Free core, optional PRO |
How SuperchargePerformance Differs
SuperchargePerformance uses the same chrome.tabs.discard() API as Chrome Memory Saver, but applies it on a configurable inactivity timer rather than waiting for memory pressure. Tabs are suspended before the system slows down, not after.
Key factual differences:
- Skips tabs where
tab.audibleis true (audio playing), pinned tabs, frozen tabs, and tabs with unsaved form inputs - Auto-protects 14 common web apps (Figma, Notion, Slack, etc.) from suspension (verified March 2026)
- Shows RAM saved per suspended tab and total session savings in the popup dashboard
- Adds declarativeNetRequest-based ad and tracker blocking, which reduces active tab memory independently of suspension
- All processing is local — zero outbound network requests
When Chrome Memory Saver Is Enough
Chrome Memory Saver is the right tool if you keep fewer than 10 tabs open and have no need for ad blocking. It is free, requires no installation, and works automatically.
If you routinely have 20+ tabs, work in memory-intensive web apps, or want visibility into exactly how much RAM your browser is using, a dedicated extension gives you meaningfully more control.
Bottom Line
Chrome Memory Saver is fine — it’s a reasonable default for light users who don’t want to think about it. But it only kicks in when memory pressure builds, it gives you no control over timing, and it does nothing for the ads and trackers loading in every active tab. Heavy tab users who want to be proactive about memory, not reactive, will find it falls short quickly.
For related comparisons, see SuperchargePerformance vs Auto Tab Discard and SuperchargePerformance vs OneTab.
Frequently Asked Questions
Is Chrome Memory Saver good enough for most users?
Does Chrome Memory Saver block ads?
Can I use Chrome Memory Saver and SuperchargePerformance together?
How much RAM does Chrome Memory Saver actually save?
SuperchargePerformance
Tab suspension, ad blocking, and script control. Free.
Don't miss the next release
Be first to know when we ship something new.
Related Articles
Auto Tab Discard vs SuperchargePerformance: Compared (2026)
Auto Tab Discard suspends tabs but has no ad blocking, forcing you to run a second extension. One alternative handles both with 186K rules built in.
Chrome Using Too Much RAM? 5 Fixes That Work (2026)
Chrome using 4GB+ with only 15 tabs? Each tab holds 70-180MB. We show which processes to kill first and how to cut RAM by 70% without closing anything.
FIX Chrome Out of Memory Errors: 5 Fixes Ranked (2026)
Chrome out of memory crashes trace to 2-3 RAM-hungry tabs. Identify the culprit in Task Manager and cut renderer crashes with targeted tab suspension.
Chrome Extensions Using Too Much RAM? 5 Tested Fixes (2026)
Extensions inject into every tab: 15 tabs means 15× the footprint. Shift+Esc reveals the culprits. 5 tested fixes to cut Chrome extension RAM in minutes.