How to Enable Chrome Memory Saver: Step-by-Step (2026)

Key takeaways

• Three steps to enable: open chrome://settings/performance, toggle Memory Saver on, pick a mode.
• Balanced mode uses ML to time discards; Maximum mode suspends most aggressively for the largest RAM reduction.
• Native Memory Saver has no configurable timer, no RAM dashboard, and no awareness of productivity apps — relevant for heavy tab users.

Chrome Memory Saver has been built into Chrome since version 108 (December 2022). In Chrome 149 (current stable as of June 2026), it sits at chrome://settings/performance with three intensity modes powered by an ML discard model introduced in Chrome 140. Enabling it takes under 30 seconds.

The Short Answer: Where Memory Saver Lives

The setting is at chrome://settings/performance. Scroll to the Memory section, toggle Memory Saver on, then pick a mode. That is the full enable flow — three steps, no restart required.

If you want the full walkthrough with mode explanations and exception site setup, keep reading. If you are already enabled and something is not working, jump to Troubleshooting.

Step-by-Step: Enabling Memory Saver in Chrome 149

Step 1. Open Chrome and type chrome://settings/performance in the address bar, then press Enter. You can also get here via the three-dot menu → Settings → Performance.

Step 2. Scroll to the Memory section. You will see a toggle labeled Memory Saver. Click it to switch on. The toggle turns blue.

Step 3. Select your mode. Three options appear below the toggle:

Step 4 (optional). Add exception sites. Under Always keep these sites active, click Add, then enter domains you never want discarded. Type notion.so to keep Notion always live, linear.app for Linear, and so on. Domain format: google.com covers all subdomains; .google.com excludes subdomains but covers the root.

That is everything required to enable Memory Saver. Chrome begins discarding eligible inactive tabs based on your chosen mode immediately — no restart needed.

How Memory Saver Works Under the Hood

Memory Saver calls chrome.tabs.discard(), the same browser API that third-party tab suspender extensions use. When Chrome discards a tab:

• The renderer process and its memory are freed
• The tab title and favicon stay visible in the tab strip
• Clicking the tab triggers a fresh network reload from the server
• A discarded tab typically retains 5–10MB for metadata versus 80–300MB when active

What triggers the discard depends on the mode. In Moderate and Balanced, Chrome’s ML model (introduced in Chrome 140, September 2025) estimates how likely you are to return to each tab. Tabs with low revisit probability get discarded first. Maximum mode applies a shorter inactivity window regardless of revisit probability.

What never gets discarded: tabs currently playing audio or video, tabs with active media sessions, and tabs you have added to the exception list. Pinned tabs are protected in most cases but not guaranteed. Chrome’s heuristics can still discard a pinned tab under sustained memory pressure.

When Native Memory Saver Is Not Enough

Memory Saver is reactive. It monitors system memory and acts when pressure signals appear, not before. At 10 tabs, that timing rarely matters. At 30+ tabs on a machine with 8–16GB RAM, Chrome may already be consuming 2–3GB before Memory Saver discards a single tab.

Four specific gaps:

No configurable timer. You cannot tell Chrome to suspend a tab after 5 minutes of inactivity. The ML model decides, and you have no visibility into when it will act.

No RAM dashboard. Chrome does not show you how much RAM Memory Saver has actually freed. The hover tooltip over a discarded tab shows a per-tab estimate, but there is no running total.

No productivity app awareness. Memory Saver does not know that Figma, Notion, Slack, or Linear tabs should never be discarded mid-session. If RAM pressure spikes, these are candidates like any other tab.

No exception UI for tab categories. You can exclude individual domains, but there is no “never discard anything in this group” or workspace-level protection.

For users with fewer than 10 tabs and no productivity web apps, these gaps rarely surface. For users with 20+ tabs or tools like Figma or Notion open, they become daily friction.

Layering a Tab Suspender Extension

A timer-based tab suspender and Chrome’s native Memory Saver work on different trigger conditions. Running both simultaneously causes no conflicts. The extension typically suspends tabs before Memory Saver’s pressure-based trigger activates.

What a dedicated extension adds on top of Memory Saver:

• Configurable timer: suspend after 5 minutes or 15 minutes of inactivity, before RAM pressure builds
• Live RAM dashboard: see total memory freed per session, shown in the extension popup
• Auto-protected web apps: skip suspension for productivity tools automatically, without manual exception entry
• Audio and pinned tab protection: explicit skip logic for tabs where tab.audible is true and for pinned tabs

SuperchargePerformance auto-protects 25+ web apps from suspension (Figma, Notion, Slack, Discord, Gmail, Google Docs, Sheets, Slides, Drive, Calendar, Linear, Miro, Canva, Lucid, Airtable, Asana, Monday, Teams, Spotify, YouTube Music, and more). Manual exception lists in native Memory Saver require you to add each domain yourself.

The two work best in combination: Memory Saver as the browser’s baseline safety net, the extension as the proactive first line that acts on a timer.

Troubleshooting Memory Saver Not Working

“Memory Saver is on but RAM usage looks the same.” Discard only happens after a tab has been inactive long enough. In Balanced mode, that can be 10–30 minutes depending on the ML model’s estimate for that tab. Check chrome://discards to see which tabs Chrome currently considers eligible for discard and their time-to-discard.

“Tabs reload every time I switch to them.” That is normal post-discard behavior. The renderer process was freed; clicking the tab triggers a network reload. If this is happening to tabs you actively use, add them to the exception list at chrome://settings/performance or switch from Maximum to Balanced mode.

“A site I added to Always Keep Active is still getting discarded.” Confirm the domain format. notion.so covers all subdomains. If you entered www.notion.so, only that exact subdomain is protected. Also check chrome://discards — it lists each tab’s current protection status and discard eligibility.

“Memory Saver toggle is grayed out.” This usually means a device policy has locked the setting. On corporate-managed Chrome, system admins can disable Memory Saver via the MemorySaverModeSavings enterprise policy. Check chrome://policy and look for Memory Saver-related policies. On unmanaged Chrome, the toggle should always be accessible.

“After enabling, a specific site behaves differently.” Some single-page apps lose client-side state when discarded and reload from the initial URL rather than the last position. Add that domain to the Always Keep Active list.

If you have fewer than 10 tabs: Balanced mode is the right default, set it and leave it. If you have 20+ tabs or keep productivity web apps open: Maximum plus a timer-based extension gives you proactive suspension before pressure hits, with automatic protection for apps that should never go idle.