Display refresh rate (measured)
Estimated by timing animation frames; 60, 90, 120 or 144 Hz.
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
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 24 | 2013-01-10 | None |
| Edge | Supported | 12 | 2015-07-29 | None |
| Firefox | Supported | 23 | 2013-08-06 | None |
| Safari | Supported | 6.1 | 2012-07-25 | None |
| Safari on iPhone | Supported | 7 | 2013-09-18 | None |
| Chrome on Android | Supported | 25 | 2013-02-27 | None |
| Samsung Internet | Supported | 1.5 | 2013-09-25 | None |
How a site asks for it
| API | requestAnimationFrame timestamp deltas over about 1 second |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
refresh | float | Hz | 30, 48, 60, 75, 90, 120, 144, 165, 240 | within 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
| Type | Example | Apps |
|---|---|---|
| games | A browser game matches its frame rate to a 120 Hz display so motion looks silky. | None named |
| games | A cloud gaming site asks the server for a stream at 60 or 120 frames to match your screen. | Xbox Cloud Gaming, GeForce NOW |
| video | A video player picks smoother playback modes on high refresh screens. | None named |
| creative | A drawing app updates ink as fast as the screen allows, so pen strokes feel instant. | Figma |
| security | A bot check sees a browser with odd frame timing, such as a virtual machine or a headless browser. | None named |
| ads | A measurement script uses the display speed as one more clue in a device ID. | None named |
| analytics | A 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
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
Sources
How well checked: Inferred from related behavior.