How to Stop Chrome Tabs from Sleeping (6 Working Fixes + Advanced Diagnostics)

2

You switch back to a tab you opened twenty minutes ago, and it blinks. The page reloads. Your half-finished form is gone. Your SSH terminal disconnected. Your trading chart reset to the default timeframe.

Chrome put that tab to sleep. Officially, the feature is called Memory Saver, and as of Chrome 149 (June 2026), it is enabled by default for most users. The idea is simple: inactive tabs get unloaded from RAM so your active tabs stay fast and your laptop battery lasts longer. The reality is messier. Some tabs should never sleep localhost servers, dashboards, web apps with live data and Chrome’s built-in heuristics don’t always know the difference.

This guide covers every reliable way to stop it, from the obvious settings toggle to hidden diagnostic pages and OS-level fixes.

What “Tab Sleeping” Actually Means

People use “sleeping” loosely, but Chrome operates on three distinct mechanisms. Knowing which one is hitting you matters because the fix differs.

Table

Mechanism	What happens to the tab	Your experience
Throttling	JavaScript timers slow down dramatically (sometimes to once per minute)	Background apps feel sluggish; game loops stutter; live counters lag
Freezing	The tab’s scripts are paused entirely, but the page stays in memory	Tab appears fine but stops updating; WebSockets may drop
Discarding	The tab is fully unloaded from RAM; only the title and favicon remain	Tab reloads from the network when you click back; form data is lost

Memory Saver primarily triggers discarding, but throttling and freezing can happen independently, especially on laptops running battery saver modes. Chrome 140 (September 2025) added an on-device machine learning model that predicts how likely you are to return to each tab. Tabs with low “revisit probability” get discarded first. In Balanced mode, that model drives the timing. In Maximum mode, Chrome ignores the prediction and discards faster.

Why Chrome Decides to Sleep Your Tabs

Chrome doesn’t flip a coin. It watches several signals:

• Available RAM. If system memory is plentiful, Memory Saver may do nothing for hours. If RAM is tight, it acts fast.
• Battery status. Laptops on battery power face more aggressive discarding and throttling than desktops plugged into the wall.
• Tab activity. Tabs playing audio or video are usually spared. Tabs with active downloads, screen shares, or visible forms get some protection too.
• Background permissions. Sites with notification permissions or active service workers are treated differently than passive article pages.

Here’s the catch: these heuristics are designed for general browsing. They don’t know that your localhost:3000 tab is a Vite dev server, or that your Figma board is a design review in progress. That’s where manual intervention comes in.

Method 1: Disable Memory Saver Entirely

The blunt but effective option. If you have plenty of RAM and would rather Chrome stay out of your tabs, turn the feature off.

1. Open Chrome and type chrome://settings/performance in the address bar, or click the three-dot menu → Settings → Performance.
2. Find the Memory Saver toggle.
3. Switch it off.

Done. Chrome will keep all tabs fully resident in memory. The tradeoff is real: on a system with 8 GB of RAM and 30+ tabs open, you will feel it. On a 32 GB workstation, you probably won’t.

Method 2: Add Specific Sites to the Exceptions List

Disabling Memory Saver globally is overkill if only three or four tabs matter. Chrome lets you maintain an “Always keep these sites active” list.

1. Go to chrome://settings/performance.
2. Under Always keep these sites active, click Add.
3. Enter the domain. Use localhost for local dev servers, or figma.com to cover all Figma subdomains.

A few formatting tips:

• google.com covers all Google subdomains.
• .google.com (with the leading dot) excludes subdomains but covers the root domain.
• http://localhost:* does not work in the exceptions UI; use localhost or 127.0.0.1 instead.

This is the best compromise for most users: Memory Saver stays on for news articles and random searches, but your tools stay alive.

Method 3: Use Chrome Flags (Advanced)

Flags are experimental features. They change between Chrome versions, and some get removed entirely. As of Chrome 149, the landscape has shifted the old #automatic-tab-discarding flag that existed in Chrome 57 is long gone. But background throttling flags still exist and can help if your issue is timer slowdown rather than full discarding.

To access flags, type chrome://flags in your address bar.

Relevant flags to check:

• Throttle JavaScript timers in background: Set to Disabled if background web apps (like self-hosted dashboards or incremental games) are stuttering.
• Calculate window occlusion on Windows: Set to Disabled if tabs throttle merely because another window is covering Chrome.

After changing any flag, click the Relaunch button that appears in the bottom-right corner.

A warning: flags are unsupported. What works in Chrome 149 may vanish in Chrome 150. Don’t build a workflow around them without a fallback plan.

Method 4: Read Chrome’s Hidden Diagnostic Page

Chrome maintains an internal page that shows exactly what it thinks about every open tab. It’s called chrome://discards, and it’s one of the most underutilized troubleshooting tools in the browser.

Type chrome://discards in your address bar. You’ll see a table with columns like:

• Utility Rank: Lower numbers are “more important” to Chrome.
• Loading State: Whether the tab is currently loaded or already discarded.
• Auto Discardable: A toggle you can click to mark a specific tab as non-discardable for this session.
• Lifecycle State: Active, passive, hidden, frozen, or discarded.
• Discard Count: How many times this tab has been discarded and reloaded.

The “Auto Discardable” toggle is useful for temporary fixes. If you’re about to step away from a critical dashboard but don’t want to add it to your permanent exceptions list, flip the toggle to X on that row. It resets when you restart Chrome, so it’s not a permanent solution but it’s perfect for one-off sessions.

Method 5: Stop Background Throttling for Web Apps

If your problem isn’t full tab discarding but rather JavaScript timers slowing to a crawl, the fix lives outside Memory Saver. Chrome throttles background tabs to save power. Since Chrome 57, background tabs using excessive CPU have their timer fire rate limited. By Chrome 88, this evolved into “intensive wake-up throttling,” which limits DOM timers to once per minute after a tab has been hidden for five minutes.

For developers running hot reload, WebSocket clients, or browser-based terminals, this is often the real culprit.

Option A: Flags (covered above)
Disable Throttle JavaScript timers in background at chrome://flags.

Option B: Command-line flag
Launch Chrome from the terminal or modify your shortcut with:

plain

--disable-background-timer-throttling

This is the nuclear option. It tells Chrome to never slow JavaScript timers in background tabs, regardless of power state. Use it if you’re running a development environment where background tabs must stay responsive. Don’t use it if you’re just trying to save battery on a laptop.

Method 6: Check OS-Level Power Settings

Sometimes Chrome isn’t the one putting your tabs to sleep. The operating system is.

Windows

• Battery Saver mode aggressively suspends background processes. Check Settings → System → Power & battery.
• Power mode set to “Best power efficiency” can trigger more throttling. Switch to “Balanced” or “Best performance” if you’re plugged in.
• Some OEM power management tools (Dell Power Manager, Lenovo Vantage) add their own browser process restrictions.

macOS

• App Nap slows or suspends background applications. You can disable it per-app via Get Info on Chrome in Finder, but this is rarely necessary unless you’re on an older MacBook.
• Low Power Mode in macOS Monterey and later behaves similarly to Windows Battery Saver.

Linux

• Desktop environments like GNOME or KDE have power profiles. Check your settings panel for “Power Saving” modes that may freeze background windows.

If you’ve disabled Memory Saver, added exceptions, and checked Chrome flags but tabs still sleep when you unplug your laptop look here first.

Extensions That Can Help (And Their Risks)

Browser extensions can fill the gaps Chrome leaves open. The main advantage is proactive suspension: instead of waiting for RAM pressure, extensions discard tabs after a fixed idle timer (e.g., 5 or 15 minutes). They also tend to offer per-tab RAM dashboards and auto-protection for productivity apps.

A few options as of mid-2026:

• Auto Tab Discard – Open-source, lightweight, uses Chrome’s native chrome.tabs.discard() API. Last updated February 2024, so maintenance is a question mark.
• SuperchargePerformance – Actively maintained (updated June 2026). Bundles tab suspension with ad blocking and a RAM dashboard. Auto-protects 25+ web apps.
• Tab Wrangler – Auto-closes idle tabs and logs them to a “Corral” for easy restoration. Not a suspender, but achieves similar memory goals.
• The Marvellous Suspender / Great Suspender Reloaded – Forks of the original Great Suspender (removed from the Web Store in 2021 for malware). Volunteer-maintained. Use with caution.

The risks: Extensions require broad tab permissions. A malicious or compromised extension can read every page you visit. The original Great Suspender was pulled for exactly this reason. If you install one, pick an actively maintained option with a transparent open-source repository, and review its permissions.

Why Developers Hate Tab Sleeping

If you’re not a developer, this section might seem like overkill. If you are, you already know.

Tab discarding breaks workflows that depend on persistent browser state:

• Hot reload stops. Vite, Webpack, and other dev servers push updates via WebSocket. If the tab is discarded, the connection drops. You save a file, nothing happens, and you waste thirty seconds figuring out why.
• Localhost tunnels die. Tools like ngrok or Cloudflare Tunnel require an active browser tab to maintain certain authentication flows. A discarded tab kills the tunnel.
• Admin dashboards go stale. A monitoring tab that discarded two hours ago shows green status for services that are actually down. You make decisions on bad data.
• AI tools lose session context. Some browser-based AI assistants maintain conversation state in memory. Discarding wipes it.
• Browser terminals disconnect. Web-based SSH clients (like those in cloud consoles) drop the session and require re-authentication.

For these use cases, the exceptions list isn’t a convenience it’s a requirement. Add localhost, your tunnel domains, and any SaaS tools you rely on for real-time work.

Common Myths About Tab Sleeping

Myth: Pinned tabs never sleep.
False. Pinned tabs get preferential treatment, but under sustained memory pressure, Chrome can and will discard them. The only guaranteed protection is the “Always keep these sites active” list or a third-party suspender with explicit pinned-tab protection.

Myth: Playing audio always prevents discarding.
Mostly true, not guaranteed. If a tab is audible, Chrome’s heuristics strongly weight against discarding it. But if RAM is critically low, audio alone may not save it.

Myth: Extensions always solve it.
Extensions work until Chrome updates and changes an API. The Great Suspender was the gold standard until it wasn’t. Auto Tab Discard hasn’t seen an update since early 2024. Extensions are tools, not permanent infrastructure.

Myth: Disabling Memory Saver fixes timer throttling.
These are separate systems. Memory Saver discards tabs. Timer throttling slows JavaScript in background tabs. You can have Memory Saver off and still see your background app stutter because of throttling. Fix one, check the other.

If Tabs Still Sleep A Troubleshooting Checklist

Run through this before assuming Chrome is broken:

1. Is Memory Saver actually off? Check chrome://settings/performance. Corporate device policies can gray out the toggle.
2. Is the site in the exceptions list? Verify the domain format. www.notion.so and notion.so are treated differently.
3. Is the OS in power-saving mode? Windows Battery Saver and macOS Low Power Mode override Chrome settings.
4. Are extensions interfering? Some “performance” extensions conflict with each other. Try disabling all extensions temporarily.
5. Is RAM actually exhausted? If you have 4 GB of RAM and 50 tabs open, Chrome will discard tabs regardless of settings. Hardware limits are real.
6. Check chrome://discards. See if the tab is marked “Auto Discardable” and what its utility rank is.

FAQ

Does Chrome Memory Saver block ads or trackers?
No. Memory Saver only discards inactive tabs. It has no ad blocking, tracker blocking, or script control. Active tabs load everything at full weight.

How much RAM does suspending a tab actually save?
A discarded tab retains roughly 5–10 MB for metadata and favicon data, versus 80–300 MB when active. Across a full session, Google claims up to 40% / 10 GB savings under ideal conditions. Independent testing on Maximum mode with 32 tabs showed roughly a 38% drop in total Chrome RAM.

Can I run Memory Saver and a tab suspender extension at the same time?
Yes. They operate on different triggers. The extension typically acts first (on a timer), and Memory Saver acts as a safety net (on RAM pressure). No conflicts.

Why does the “Auto Discardable” toggle at chrome://discards reset?
It’s session-only by design. For permanent protection, use the exceptions list in Settings.

Is there a way to keep tabs active without disabling Memory Saver?
Yes. Use the exceptions list for specific domains, or set the mode to Moderate, which waits the longest before discarding.