Background tab timer throttling
Hidden tabs get slower timers: 1 per second, then 1 per minute after 5 minutes in Chrome.
In one line
Can't keep its timers running fast once you switch to another tab
Hidden tabs get slower timers: 1 per second, then 1 per minute after 5 minutes in Chrome.
Tells the site whether the tab is visible and caps how much it can do while hidden. Useful for battery, but sites also detect tab switches via visibilitychange.
What it can and can't do
What the user does: You switch to another tab or app and leave the page.
It can
- Run its code once a second while the tab is hidden
- Keep playing sound, if the page plays audio
- Slow down by itself to save battery
It cannot
- Keep fast timers in a hidden tab; they drop to once a second, then once a minute after 5 minutes in Chrome
- Stay running as normal after you lock your phone
- Turn off the browser's own power saving limit
- Do heavy work in the background without a background task such as a worker or a service worker
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 33 | 2014-02-20 | None |
| Edge | Supported | 12 | 2015-07-29 | None |
| Firefox | Supported | 18 | 2013-01-08 | None |
| Safari | Supported | 7 | 2013-10-22 | None |
| Safari on iPhone | Supported | 7 | 2013-09-18 | All iOS browsers use WebKit |
| Chrome on Android | Supported | 33 | 2014-02-26 | None |
| Samsung Internet | Supported | 2.0 | 2014-10-17 | None |
How a site asks for it
| API | document.visibilityState, visibilitychange; setTimeout/setInterval; Page Lifecycle freeze/resume |
| Browser compat keys | api.Document.visibilityStateapi.Document.visibilitychange_eventapi.Document.wasDiscarded |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| Activation | none |
| How long it lasts | While hidden |
| How to take it back | Nothing to revoke (no permission is stored) |
| Inside an iframe | Applies per page, including iframes |
Typical flow
- Tab becomes hidden
- Chrome aligns timers to 1 s; after 5 min with chained timers it runs them once per minute
- Page can be frozen then discarded
Data you get
Shape: none
No individual data fields. The signal is the access itself.
Technical limits
- Chrome 57: budget based throttling; hidden timers wake about once per second
- Chrome 88 intensive throttling: after 5 min hidden, timer chains of 5 or more run once per minute (page silent 30 s, not using WebRTC or audio)
- Exempt: audible tabs, active WebRTC data channels or media streams, pages with Web Locks or IndexedDB transactions in flight
- requestAnimationFrame pauses completely in hidden tabs; Safari throttles to 1 s then suspends; Firefox clamps to 1 s (and 10 s in some setups)
- Memory Saver (Chrome 108+) can discard inactive tabs; wasDiscarded reveals prior discard
The story
What it is
When a tab is hidden, the browser slows its clocks to save battery.
For you
You switch away from a tab and your laptop fan stays quiet. The cost is that some live things, like a countdown or a game, may lag or stall until you return.
For makers
Makers must design around it: pause animations, use server time, and keep calls and live connections alive for real time apps. Browsers use it to keep ads and trackers from burning battery.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | An idle game or a browser multiplayer game must handle the tab being frozen, or it drops you from the match. | Agar.io, Krunker.io |
| live | A live auction or sports score page catches up with the server when you return to its tab. | eBay |
| video | A video call tab keeps audio running even when hidden, because audio is allowed to play. | Google Meet, Zoom web |
| ads | Ad measurement counts a view only when the tab is visible, so hidden tabs do not inflate numbers. | Google Ad Manager |
| productivity | A web chat app uses a push connection so it notifies you even when throttled. | Slack |
| analytics | Time on page tools pause counting when the tab is hidden. | Google Analytics |
Risks
- Stalled live pages
- Time on page distortions
What the platform says
- Google: Timer throttling in Chrome 88. Chrome explains that background tabs get less frequent timers, to save power and CPU.
Good uses and abuse
Legitimate uses
- Pause polling
- Save battery
Known abuse
- Detecting tab switches (attention tracking)
- Hidden miners hiding in background
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2017-03, Chrome 57: Budget-based background timer throttling
- 2018-07, Chrome 68: Page Lifecycle API with freeze and resume
- 2021-01, Chrome 88: Intensive wake up throttling after 5 minutes hidden
Sources
How well checked: Based on official documentation.