Skip to Content
Platform.Ontology

Display refresh rate (measured)

Estimated by timing animation frames; 60, 90, 120 or 144 Hz.

Gets silentlyScreen and windowsScreenWeb browsersWhen the page loadsWhile you use it

In one line

Can estimate your screen's refresh rate by timing about one second of animation

Estimated by timing animation frames; 60, 90, 120 or 144 Hz.

No API reports refresh rate; scripts measure the gap between requestAnimationFrame callbacks. Distinguishes high-refresh phones and gaming monitors, but is noisy under load.

What it can and can't do

What the user does: Nothing. It runs for about a second when the page loads or an animation starts.

It can

  • Count animation frames to guess 60, 90, 120 or 144 Hz
  • Tune animations and games to match
  • Add the result to a browser fingerprint

It cannot

  • Get an exact value, since busy or power saving devices give slightly wrong numbers
  • Measure while the tab is hidden
  • Learn your monitor model

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported242013-01-10None
EdgeSupported122015-07-29None
FirefoxSupported232013-08-06None
SafariSupported6.12012-07-25None
Safari on iPhoneSupported72013-09-18None
Chrome on AndroidSupported252013-02-27None
Samsung InternetSupported1.52013-09-25None

How a site asks for it

APIrequestAnimationFrame timestamp deltas over about 1 second
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnone needed (no grant)
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: object
How often: static per session

FieldTypeUnitRangePrecision
refreshfloatHz30, 48, 60, 75, 90, 120, 144, 165, 240within about 1 Hz

Technical limits

  • Throttled in background tabs
  • Safari low power mode caps at 30 or 60

The story

What it is

A page estimates how fast your screen redraws, such as 60, 120 or 144 times a second.

For you

You never see the test. The page counts how quickly the screen redraws. It is why a game can feel smoother on a fast gaming screen.

For makers

Games use it to set a smooth frame rate and spare weak devices. Ad and fraud teams use it too, because real screens redraw in a steady rhythm and bots often do not.

Where you see it

TypeExampleApps
gamesA browser game matches its frame rate to a 120 Hz display so motion looks silky.None named
gamesA cloud gaming site asks the server for a stream at 60 or 120 frames to match your screen.Xbox Cloud Gaming, GeForce NOW
videoA video player picks smoother playback modes on high refresh screens.None named
creativeA drawing app updates ink as fast as the screen allows, so pen strokes feel instant.Figma
securityA bot check sees a browser with odd frame timing, such as a virtual machine or a headless browser.None named
adsA measurement script uses the display speed as one more clue in a device ID.None named
analyticsA team measures page smoothness on real devices to find slow spots.None named

Risks

  • Fingerprint clue
  • Reveals device power

Good uses and abuse

Legitimate uses

  • Smooth animation pacing

Known abuse

  • Hardware class

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits2Rough identifying entropy, when known

Sources

How well checked: Inferred from related behavior.

On this page