Skip to Content
Platform.Ontology

Background tab timer throttling

Hidden tabs get slower timers: 1 per second, then 1 per minute after 5 minutes in Chrome.

Works without askingThings a page can doSchedulingWeb browsersWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported332014-02-20None
EdgeSupported122015-07-29None
FirefoxSupported182013-01-08None
SafariSupported72013-10-22None
Safari on iPhoneSupported72013-09-18All iOS browsers use WebKit
Chrome on AndroidSupported332014-02-26None
Samsung InternetSupported2.02014-10-17None

How a site asks for it

APIdocument.visibilityState, visibilitychange; setTimeout/setInterval; Page Lifecycle freeze/resume
Browser compat keysapi.Document.visibilityState
api.Document.visibilitychange_event
api.Document.wasDiscarded
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
Activationnone
How long it lastsWhile hidden
How to take it backNothing to revoke (no permission is stored)
Inside an iframeApplies per page, including iframes

Typical flow

  1. Tab becomes hidden
  2. Chrome aligns timers to 1 s; after 5 min with chained timers it runs them once per minute
  3. 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

TypeExampleApps
gamesAn idle game or a browser multiplayer game must handle the tab being frozen, or it drops you from the match.Agar.io, Krunker.io
liveA live auction or sports score page catches up with the server when you return to its tab.eBay
videoA video call tab keeps audio running even when hidden, because audio is allowed to play.Google Meet, Zoom web
adsAd measurement counts a view only when the tab is visible, so hidden tabs do not inflate numbers.Google Ad Manager
productivityA web chat app uses a push connection so it notifies you even when throttled.Slack
analyticsTime on page tools pause counting when the tab is hidden.Google Analytics

Risks

  • Stalled live pages
  • Time on page distortions

What the platform says

Good uses and abuse

Legitimate uses

  • Pause polling
  • Save battery

Known abuse

  • Detecting tab switches (attention tracking)
  • Hidden miners hiding in background

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough 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.

On this page