Why Background Tabs Slow Down in Chrome (Tab Throttling, Explained)

Switch back to a tab you left open in the background and the countdown timer is behind, the live chart hasn't updated in a while, or a notification badge took a beat to catch up. Nothing crashed. Chrome does this on purpose — background tabs get deliberately slowed down to save CPU and battery on work you're not looking at, and knowing where the line sits helps you tell "expected" from "actually broken."

The basic rule: hidden tabs get slower timers

The moment a tab loses focus and becomes hidden, Chrome starts clamping how often its JavaScript timers (setTimeout, setInterval) are allowed to fire — capping repeated timer calls to roughly once per second instead of running at whatever rate the page's code requested. A page doing frequent, low-priority work (polling for updates, animating something off-screen) barely notices; a page counting down to the second can visibly drift.

This is separate from requestAnimationFrame, which Chrome stops calling almost entirely in hidden tabs — there's nothing to paint if you can't see it, so there's no reason to keep running the animation loop.

Intensive throttling: it gets slower the longer it's hidden

A tab that's stayed in the background for several minutes gets throttled further still. Chrome's intensive timer throttling can push repeated timer wake-ups down to roughly once a minute for tabs that have been hidden a while, on top of the base once-per-second clamp. The intent is specifically for tabs you've forgotten about, not ones you're actively flipping back to every few seconds — a tab you're checking on regularly stays comparatively responsive because it isn't hidden long enough to hit the more aggressive tier.

Freezing: a step beyond throttling

Past throttling, Chrome has a further tier: freezing. A background tab that's been hidden for around five minutes with nothing exempting it can have its JavaScript execution paused outright — not just slowed, stopped — while the page stays loaded in memory. Switch back to it and it resumes instantly, no reload, no lost scroll position; it's simply been on pause. This is distinct from Memory Saver discarding a tab, which frees the tab's memory entirely and forces a real reload when you return to it — freezing is reversible in an instant, discarding isn't.

If a background tab feels like it's reloaded rather than just resumed when you click back to it, that's more likely Memory Saver or system memory pressure discarding it outright than throttling or freezing — both of those keep the page in memory the whole time.

What's exempt from the aggressive tiers

Chrome specifically carves out exceptions so throttling doesn't break things people rely on:

• Playing audio — a background music or podcast tab keeps running at full speed so playback doesn't stutter.
• Active webcam, microphone, or screen capture — a video call in a background tab isn't throttled the way a static page would be.
• Real-time connections doing active work — a page mid-transfer or actively holding a lock isn't paused mid-task.

Everything else — a countdown, a slowly-updating dashboard, a page just sitting there polling — is fair game for throttling, and that's the overwhelming majority of "why did my background tab fall behind" cases.

Why this trade-off exists

Every tab that's allowed to run at full speed in the background is CPU time and battery you're spending on something you're not currently looking at. Multiply that by however many tabs are typically open at once, and unthrottled background tabs would be a meaningful, constant drain — particularly on laptops running on battery. Throttling (and eventually freezing) is Chrome trading a small amount of background-tab freshness for a real, continuous reduction in the resources every open-but-unused tab costs you. It's a similar trade to what Memory Saver does for RAM, just applied to CPU and running continuously rather than only after extended idle time.

When it's not throttling — and how to check

If a background tab looks completely unresponsive rather than just behind — no title update, no favicon change, nothing — for longer than a few minutes, check Chrome's Task Manager (Shift+Esc on Windows/Linux, or the Window menu on Mac). A throttled or frozen tab still shows up with a process and a small, steady CPU/memory footprint; a genuinely crashed or hung tab's row tends to look different — pinned at high CPU with no change over time, or missing entirely if the process died.

Fewer background tabs to throttle in the first place

Throttling makes background tabs cheaper to leave open, but it's still cheaper — in CPU, memory, and mental overhead — not to have forty of them sitting there in various states of frozen. Amazing Tabs gives the "I might need this later" tabs somewhere to go that isn't just another background tab:

• Save a tab, then close it for real — no process left running, throttled or otherwise.
• Find it again in seconds with ⌘K / Ctrl+K, by title or page content, instead of hunting through a strip of look-alike favicons.
• Free for up to 100 saved links.

Stop paying CPU and battery for tabs you've forgotten about. Add Amazing Tabs to Chrome — free, no signup to install.

Quick recap

• Hidden tabs get their timers clamped to roughly once a second immediately, and further to roughly once a minute after several minutes hidden (intensive throttling).
• requestAnimationFrame effectively stops in hidden tabs — there's nothing to paint.
• Freezing goes further still: JS execution pauses entirely after ~5 minutes hidden, but the page stays in memory and resumes instantly — no reload.
• Playing audio, an active call, or a real-time connection exempts a tab from the aggressive tiers.
• Discarding (Memory Saver) is different from all of the above — it frees the tab's memory completely and forces a real reload, unlike throttling or freezing.

Further reading: Why Chrome Uses So Much Memory for how Memory Saver's discarding differs from throttling, Why Do Your Tabs Keep Reloading Themselves? if a background tab seems to restart rather than resume, or Chrome Task Manager: Which Tab Is Using Memory? for checking a suspect tab's actual resource use directly.

Add Amazing Tabs to Chrome — free → Install from the Chrome Web Store. 100 saved links free, upgrade only if you want unlimited and cross-device sync. See pricing for the full breakdown — including the $99 lifetime deal (capped at 200 spots).