How to keep background tabs awake and active

The music cuts off a few minutes after you switch tabs. An upload that ran fine while you watched it stalls the moment you don't. A dashboard that should refresh every thirty seconds is an hour stale when you come back. None of these are bugs in the site — the browser is slowing the tab down on purpose.

Why Chrome slows background tabs down

A tab you're not looking at gets its timers throttled almost immediately. After about five minutes in the background, Chrome escalates to intensive throttling: the page's timers run roughly once per minute, which is why "every 30 seconds" jobs quietly become "once a minute, maybe". Left alone long enough, the tab can be frozen outright — still in memory, but not running at all — and eventually discarded. It's a sensible default for the hundred tabs you don't care about. It's wrong for the one you do.

Workarounds people try

Keep audio playing. Chrome exempts tabs that are audibly playing sound. It works, but only if the page actually produces audio you want to hear.

Keep the tab visible. A separate window arranged so the tab stays on screen never counts as "background". Effective, and costs you half your screen.

Launch Chrome with flags. Command-line switches like --disable-background-timer-throttling exist, but they apply to every site at once and vanish the moment Chrome is started normally. Fine for a developer's test run, unworkable as a daily setup.

Protect the tab instead

FreezeFence takes the approach the browser itself respects: while a tab is protected, it holds the same kind of standard browser signals a video call holds, so Chrome treats the page as doing something important and leaves it running. It also marks the tab as not auto-discardable, covering the freeze-then-discard path end to end.

In practice: open the page, click the FreezeFence icon, flip the switch. Chrome asks once for site access the first time; after that it's flip, green check, done. Three protection levels let you choose how hard it pushes back, and the status panel reports the real state — including when the OS or the browser is fighting the protection under memory pressure.

When not to keep tabs awake

A protected tab keeps using CPU, which on a laptop means battery. Protect the tabs doing real work — the upload, the notebook, the monitor — and let the rest sleep. The point isn't to disable the browser's power management; it's to overrule it in the handful of places it's wrong.