Monitor Refresh Rate (Hz) Tester

Refresh Rate Tester Guide

How the Hz measurement actually works, why it can vary run to run, and how to get the most accurate reading.

How the Test Works

The test uses requestAnimationFrame, a browser API that calls your code right before each screen repaint - which is synced to your monitor's actual vertical refresh signal, not an arbitrary timer. Over a 3-second window, the tool records the time gap between consecutive frames, then averages the most consistent samples (trimming the highest and lowest 15% to reduce the effect of any brief stutter) to estimate frames-per-second, which is your refresh rate in Hz.

If the result is close to a common display rate - 60, 75, 90, 120, 144, 165, or 240 Hz - it's shown as a "closest common rate" badge underneath the number.

Getting an Accurate Reading

Keep the browser tab visible and in focus for the full 3 seconds - if you switch tabs or minimize the window, most browsers throttle or pause background timers and the test will cancel itself with a warning. Close any heavy background apps (video encoding, other games) before testing, and run it two or three times to see a consistent range rather than trusting a single result.

Result Lower Than Expected?

If you see...Likely cause
Result is capped near 60Hz on a 120Hz+ monitorWrong cable/port (older HDMI can't carry high Hz) or refresh rate not actually applied in OS settings
Result fluctuates a lot between runsVariable refresh rate (VRR/G-Sync/FreeSync) display intentionally varying Hz, or background CPU load
Test cancels immediately with "tab was hidden"The browser tab lost focus or was minimized during the 3-second test window
Result is a non-round number like 58 or 61Normal - browser frame timing has slight jitter; treat results within a couple Hz of a common rate as a match

Frequently Asked Questions

Why does the test trim the highest and lowest samples before averaging?

An occasional frame-time outlier - a brief stutter from garbage collection or a background task - would skew a simple average. Trimming the extreme 15% on each end before averaging the rest yields a steadier number closer to the display's true frame interval.

What is the Window Management API's getScreenDetails(), and why does it need a permission prompt?

It's a newer browser API that lets a page query real OS-reported details - position, resolution, and refresh rate - for every connected screen, not just the one showing the current window. Because that's more information than a page normally gets about your desktop setup, browsers gate it behind an explicit permission grant.

Why is requestAnimationFrame a good basis for measuring Hz at all?

Browsers deliberately schedule requestAnimationFrame callbacks to fire right before the next screen repaint, in sync with the display's actual vertical refresh signal, rather than on an arbitrary timer. That means the gaps between consecutive callbacks closely track real frame intervals.

Why does the tool round a reading like 143Hz to a common rate like 144Hz?

requestAnimationFrame-based timing carries a small amount of natural jitter from OS scheduling and JavaScript engine overhead, so a raw reading a couple of Hz off from a standard rate (60, 120, 144, and so on) is treated as a match to that rate rather than as a separate, unusual number.

Can this test detect the refresh rate of a monitor that isn't showing the browser window?

Only through the separate all-monitors check using the Window Management API (Chrome/Edge desktop only). The main frame-timing test can only measure whichever screen is currently displaying the browser tab, since requestAnimationFrame is tied to the window that's actually rendering.

Open Refresh Rate Tester