Sleeping Tabs Don't Exist in Chrome — But This Does (2026)

Chrome has no feature called “sleeping tabs.” The equivalent is Memory Saver, shipped in Chrome 108 (December 2022) and upgraded with ML prediction starting in Chrome 147. Same mechanism as Edge sleeping tabs — different name.

Key takeaways

• Edge calls this feature sleeping tabs. Chrome calls it Memory Saver. Same underlying mechanism, different branding.
• Chrome 147 has three suspension modes including a new ML-based Balanced mode that predicts which tabs you’ll revisit.
• Both Chrome and Edge discard tab state entirely — scroll position, form data, and media playback are gone on reload.

You switched from Edge to Chrome. You go looking for sleeping tabs in the settings. Nothing. No “sleeping tabs” toggle anywhere.

That’s because Chrome never adopted Edge’s terminology. The feature shipped in Chrome 108 under the name Memory Saver, and it lives at chrome://settings/performance. The behavior is identical in principle — inactive tabs get their renderer process discarded to free RAM — but Google picked a different label for it.

Edge Sleeping Tabs vs Chrome Memory Saver

Microsoft Edge enabled sleeping tabs by default in Edge 88, released January 2021. Google shipped the equivalent as Memory Saver in Chrome 108, December 2022 — about two years later. Both features use the browser’s tab discard mechanism under the hood.

The practical differences matter less than you’d expect:

Edge wins on timer granularity. If you want tabs to sleep after exactly 45 minutes, Edge does that natively. Chrome gives you no timer control at all — Memory Saver decides when based on system pressure or ML predictions depending on which mode you select.

Chrome edges ahead on modes. The three-mode system in Chrome 147 gives you more nuance about how aggressive you want suspension to be.

How to Set Up Memory Saver in Chrome 147

The path is chrome://settings/performance. Type that directly into the address bar and press Enter — it will not show up if you search through Settings menus.

Step 1: On the Performance page, find the Memory section. Toggle Memory Saver on if it is not already enabled.

Step 2: Choose a mode.

For most users coming from Edge sleeping tabs, Maximum most closely matches what they are used to. It is the most proactive of the three options.

Step 3: Add site exceptions. Click Add under “Always keep these sites active.” Type in any domain you never want Chrome to discard — your note-taking app, your time tracker, anything with state you cannot afford to lose. These exceptions persist across restarts.

Step 4 (optional): For manual control, visit chrome://discards. This page lists every open tab with its current state. The Urgent Discard button on any row forces that tab to suspend immediately. Useful for testing or for manually clearing a tab you know you won’t need for a while.

What You Lose When a Tab Goes to Sleep

This part Edge and Chrome handle identically, and it is the most important thing to understand before relying on tab suspension.

When a tab is discarded:

• Scroll position: Gone. The page reloads to the top.
• Unsaved form data: Gone. Anything typed into a form field is erased.
• Media playback: Gone. Video paused mid-stream will restart from the beginning or, more commonly, show a stale thumbnail.
• WebSocket connections: Severed. Apps that maintain live connections — chat apps, collaboration tools, live dashboards — will reconnect on reload but lose any unacknowledged messages.
• JavaScript state: Gone. Single-page apps lose their in-memory state.

The tab itself remains in the tab bar with its title and favicon intact. Chrome shows a small reload indicator when you return to it. The reload happens from the network, not from a local cache — so if the page is slow to load, the discarded version is slow to reload.

Research suggests a significant portion of discarded tabs are revisited within 24 hours. The ML-based Balanced mode is trained on this pattern — it is trying to avoid discarding tabs you are about to use while still clearing ones that have been actually abandoned.

Where Chrome Memory Saver Falls Short

For users switching from Edge sleeping tabs, there are three gaps worth knowing about.

No timer. Edge lets you say “sleep tabs after 2 hours.” Chrome does not. You cannot set “suspend after 10 minutes of inactivity.” Chrome decides timing entirely — either based on system pressure (Moderate) or ML predictions (Balanced) or aggressive heuristics (Maximum). If you have a workflow that depends on specific timing, Chrome’s built-in cannot deliver it.

No per-tab RAM display. Edge shows you a memory savings estimate in the sleeping tab tooltip. Chrome shows nothing. You have no visibility into how much RAM each suspended tab was using or how much total memory Memory Saver has freed in your current session.

No smart app protection. Edge and Chrome both let you add exceptions manually. Neither one auto-detects that you have ChatGPT open in a tab that should not be interrupted, or that your Google Doc has unsaved changes, or that your Notion workspace is mid-edit. You have to add these manually or risk losing work.

Upgrading Beyond the Built-In

SuperchargePerformance uses the same chrome.tabs.discard() API as Chrome Memory Saver — same underlying mechanism. The difference is in the decision logic on top.

The auto-protection list covers 14 app categories that should not be interrupted: ChatGPT, Google Docs, Notion, Slack, Figma, and others (verified March 2026). No manual exception list to maintain.

The RAM dashboard is the other gap filler. You can see exactly how much memory each suspended tab was holding, and what your total session has freed. Chrome Memory Saver gives you none of that visibility.

The ad blocking is independent of suspension — it reduces per-tab memory by preventing ads and third-party scripts from loading in the first place. A tab blocked from loading 40 trackers starts lighter, so suspension saves proportionally more when it does trigger.

When the Built-In Is Enough

Chrome Memory Saver in Maximum mode is a reasonable default if:

• You typically keep fewer than 15 tabs open
• You do not rely on any web app that keeps live state (chat, live dashboards, collaborative docs)
• You have no need for visibility into how much RAM you’re saving
• You are coming from Edge and just want something that works automatically without setup

The honest answer is that for light browsing, the built-in handles it fine. The tab suspension mechanism is identical. The difference is all in timing control, protection logic, and visibility.

Which Option Fits Your Situation

You just switched from Edge and want sleeping tabs to work again: Enable Memory Saver in Maximum mode at chrome://settings/performance. Add your most important apps to the exceptions list. That’s the closest Chrome gets to Edge’s default behavior natively.

You have 20+ tabs open regularly and Chrome still feels slow: Memory Saver’s reactive model will not keep up. A timer-based extension suspends after 5 minutes of inactivity regardless of system state — the RAM stays low before pressure builds, not after.

You rely on ChatGPT, Google Docs, or Notion staying loaded: Add them to the Memory Saver exceptions list manually, or use an extension with auto-protection that handles the list for you.

You want to see the actual numbers: The built-in gives you no dashboard. If knowing how much RAM your browser is using matters to you, a dedicated extension with a per-tab display closes that gap.

You just want zero configuration: Memory Saver Balanced mode in Chrome 147 handles it via ML. Install nothing, configure nothing, and let Chrome decide. For casual users, this is the right answer.

You want to try the extension path: Install SuperchargePerformance from the Chrome Web Store — free, no account. Open the popup to see your current RAM usage and which tabs are consuming the most. The difference from Memory Saver is visible immediately: you control the timing, you see the numbers, and your important tabs stay protected.