Background tab throttling in Chrome, and how to turn it off
On this page
Chrome slows down JavaScript timers in tabs you can't see. After a tab has been hidden for five minutes and silent for 30 seconds, chained timers may run only once a minute. The old chrome://flags switch for this is reportedly gone, but the IntensiveWakeUpThrottlingEnabled policy still turns the heaviest tier off.
That is the short version. If a dashboard stops refreshing, a countdown drifts, or a web app falls behind when you leave its tab, the details below tell you which rule you hit and what you can change.
The three tiers of timer throttling
Chrome's rules are laid out in Jake Archibald's post on the Chrome developer blog, written when the heaviest tier shipped in Chrome 88. "Timers" here means setTimeout and setInterval. A timer is "chained" when it is scheduled from inside another timer's callback, which is how every repeating timer works.
1. Minimal throttling
Applies when the page is visible, or when it has played sound in the last 30 seconds. Timers run normally, except that a chained timer asking for less than 4 ms gets 4 ms. Browsers have done this for years.
The post is explicit that a silent audio track does not count as making noise.
2. Throttling (once per second)
Applies to a hidden, silent page when any of these is true:
- the timer chain is shorter than 5,
- the page has been hidden for less than 5 minutes,
- WebRTC is in use (an open data channel or a live media track).
Chrome checks these timers once per second and runs whatever is due in one batch. A setInterval set to 100 ms behaves like a one-second interval.
3. Intensive throttling (once per minute)
Applies when all of these are true:
- the page has been hidden for more than 5 minutes,
- the timer chain is 5 or longer,
- the page has been silent for at least 30 seconds,
- WebRTC is not in use.
Chrome then checks those timers once per minute. This is the tier that breaks things people notice, like a clock that jumps by a minute when you come back.
What "hidden" means
Hidden usually means another tab is in front, or the window is minimized. The Chrome post notes that browsers may also treat a page as hidden whenever its content is completely out of view, so a window fully covered by another window can count. The page's own document.visibilityState tells you what Chrome currently thinks.
requestAnimationFrame is a separate case
requestAnimationFrame (rAF) isn't throttled, it stops. The same Chrome post says rAF "will wait for the page to be visible", so animation code, canvas games and anything that counts frames simply pause in a hidden tab. Video frame callbacks behave much the same. We go deeper on this in requestAnimationFrame in background tabs.
MDN's setTimeout reference also notes that browsers enforce a minimum delay in inactive tabs, so none of this is unique to Chrome. Firefox and Safari throttle too, with their own rules.
Throttling is not the same as sleeping
Throttling slows a page down. Sleeping (Chrome's Memory Saver, Edge's sleeping tabs) unloads it, and the page reloads when you return. If your tab reloads, the fix is an exclusion list, covered in how to prevent a tab from sleeping. Turning throttling off does nothing for discards, and excluding a site from Memory Saver does nothing for timer throttling.
How to turn throttling down or off
Ordered from the easiest to the most involved.
Let the tab play audio
Pages that have made sound in the last 30 seconds stay in the minimal tier. If the page plays real audio (music, a stream, a call), it is already exempt. A silent track won't work, per the Chrome post, and a muted <video> doesn't count as sound either.
Keep it visible
Put the tab in its own window and leave part of that window on screen. A visible page is never throttled. A small window off to the side, or a second monitor, is enough. A window that's fully covered may still count as hidden.
The chrome://flags option: probably gone
Older guides tell you to open chrome://flags/#intensive-wake-up-throttling and set Throttle Javascript timers in background to Disabled. That flag existed when the feature was new. Users on Stack Overflow and Reddit reported it disappearing from chrome://flags around Chrome 90 in 2021, and Stack Overflow answers from 2024 still describe it as missing. You will also see #expensive-background-timer-throttling mentioned, which is older still.
Flags come and go between versions, so search chrome://flags for "throttl" in your own build. If nothing relevant shows up, the flag has been removed and the policy below is what's left.
The IntensiveWakeUpThrottlingEnabled policy
Chrome still ships an enterprise policy for the once-per-minute tier. Google's policy page says that when it's set to disabled, the feature "will be force disabled, and users will not be able to override this". It covers intensive throttling only. The once-per-second tier and the rAF pause stay.
On Windows, you can set it in the registry. Run this in an administrator Command Prompt:
reg add "HKLM\Software\Policies\Google\Chrome" /v IntensiveWakeUpThrottlingEnabled /t REG_DWORD /d 0 /f
Edge has the same policy under its own key (Microsoft's documentation):
reg add "HKLM\Software\Policies\Microsoft\Edge" /v IntensiveWakeUpThrottlingEnabled /t REG_DWORD /d 0 /f
On Linux, Chrome reads policies from JSON files in /etc/opt/chrome/policies/managed/. Create a file there containing:
{ "IntensiveWakeUpThrottlingEnabled": false }
On macOS, policies are normally deployed with a configuration profile, which is more work than most people want for one setting.
Then quit the browser completely and reopen it. The policy page says it applies when each renderer process starts, so a full restart is needed. Open chrome://policy (or edge://policy) to confirm it shows up. Chrome will also show "Managed by your organization" in its menu once any policy is set. That's expected.
Command-line switches (for developers)
Chromium has launch switches such as --disable-background-timer-throttling and --disable-renderer-backgrounding. Automation tools like Playwright pass them when they start a browser. They only apply to a browser launched with them, and Chromium's own bug tracker has reports of them not covering every case, so treat them as a testing tool rather than an everyday setting.
If you build the page: work with throttling
Chrome's post argues that most timers in background tabs are doing polling that an event could do better. Some swaps it suggests:
IntersectionObserver,ResizeObserverorMutationObserverinstead of polling the DOM.- WebSockets, server-sent events or fetch streams instead of polling a server.
timeupdateandendedevents instead of checking a video's position on a timer.- On return, compare against
Date.now()instead of counting ticks, so a clock catches up the moment the tab is visible again.
When the page pauses itself
Some pages stop in the background for a reason that has nothing to do with throttling: they read document.hidden or listen for visibilitychange and pause on purpose. Video players do this a lot. Focus Spoofer (which we make) is a free extension for Chrome, Edge and Brave that, on the tabs you choose, keeps the page reporting itself as visible and focused, blocks those events, and keeps requestAnimationFrame firing while hidden. It is not a replacement for the policy above for timer throttling, and it doesn't stop tabs from being discarded. To see what a site detects when you leave, try the live test page, or read about the extension at focus.oddworks.us. Other ways to keep one specific tab going are in how to keep a tab active in Chrome.
FAQ
Can I disable background tab throttling in Chrome?
You can turn off the heaviest tier, intensive throttling, with the IntensiveWakeUpThrottlingEnabled policy set to false. The once-per-second throttling of hidden tabs has no user setting, though a tab playing audible sound or staying visible avoids it.
Where did the "Throttle Javascript timers in background" flag go?
Users reported it vanishing from chrome://flags around Chrome 90. If your build doesn't list it, use the policy instead.
Does playing silent audio stop throttling?
No. Chrome's developer blog says a silent audio track doesn't count as the page making noise, so the tab is still throttled.
Is a minimized window throttled the same as a background tab?
Yes. Both count as hidden. A window that is open but fully covered by other windows may count as hidden too.
Does throttling cause my tab to reload?
No. Throttling slows a tab down without unloading it. Reloads come from Memory Saver or sleeping tabs, which you control with an exclusion list.