Result
Waiting for enough samples to estimate your live refresh rate.
The measurement starts automatically when this section loads.
Check your monitor’s actual refresh rate. See motion smoothness at different speeds. No install required.
Browser-based refresh rate measurement with live motion patterns and no permissions required.
Run a browser-based refresh rate check to estimate your monitor Hz, compare motion smoothness, and inspect frame pacing stability.
Result
Waiting for enough samples to estimate your live refresh rate.
The measurement starts automatically when this section loads.
Detected
—
Rounded to the nearest common refresh tier.
Measured
—
Raw requestAnimationFrame estimate from this browser session.
Frame time
—
Average time between rendered frames.
Frame pacing
Waiting for samples
Lower variance usually means smoother pacing.
Jitter
—
Basic frame pacing variance across the capture window.
Live FPS
—
Tracks the current RAF cadence against the detected refresh tier.
Frame pacing stability
Lower jitter means smoother pacing and less visible frame inconsistency.
What to check next
The measurement starts automatically when this section loads.
Ready to measure
Compare how motion looks at different travel speeds. Faster lanes make dropped smoothness easier to spot.
UFO lane
Best for spotting smooth tracking and ghosting.
Pursuit bars
Good for noticing repeated edge separation.
Pixel trail
Useful for checking clarity at faster motion speeds.
Measure the actual screen refresh rate using requestAnimationFrame and show both raw and rounded Hz output.
Compare multiple moving patterns at different speeds to make monitor smoothness easier to see.
Refresh rate describes how many times your display updates the image every second. It is measured in hertz, usually written as Hz. A 60Hz monitor refreshes the image 60 times per second, while a 144Hz monitor refreshes 144 times per second. Higher refresh rates can make motion look smoother, reduce perceived blur, and improve responsiveness in games and fast interface interactions. A refresh rate test helps you check whether your display is actually running at the rate you expect, because a monitor rated for 144Hz or 240Hz may still be operating lower due to browser limits, operating system settings, cable bandwidth, battery saver mode, or display configuration mistakes.
This refresh rate checker uses requestAnimationFrame to estimate how often your browser is painting frames. The measured value gives you an approximate live refresh rate, and the rounded value maps that result to a common monitor refresh tier such as 60Hz, 120Hz, 144Hz, 165Hz, 240Hz, or 360Hz. The moving patterns below the readout are there to help you judge smoothness visually. Faster patterns make differences between lower and higher Hz easier to spot. If the motion looks inconsistent or the FPS counter fluctuates, the display path may be dropping frames or the browser may not be running at the panel’s full rated speed.
A 60Hz display is still common and perfectly usable for general work, but motion will look less smooth than on higher-refresh monitors. Moving objects and scrolling can appear blurrier, and latency feels more noticeable in competitive games. At 144Hz, the jump is large enough that most users can see smoother animation and faster-feeling input immediately. At 240Hz, the gains become more subtle for casual use but still matter to users who care about motion clarity and reaction-sensitive tasks. A refresh rate test is useful here because many people buy a high-Hz monitor and assume it is active, while the system is actually still outputting 60Hz or 120Hz.
There are several reasons a browser refresh rate test can show a lower number than the specification on your monitor box. The operating system might still be set to 60Hz. The browser may be limited by battery saver mode, power settings, or external display routing. Certain cables and adapters can also cap the signal. On laptops, integrated graphics behavior and mirrored displays may reduce the active refresh rate. Some browsers also cap animation timing in certain low-power or background conditions. That is why this tool should be used as a practical estimate of the live display path, not as a guaranteed hardware certification.
On Windows, open display settings, choose the correct monitor, then look for advanced display settings and refresh rate selection. On macOS, open System Settings, go to Displays, choose the active display, and check whether a higher refresh rate or ProMotion option is available. If your monitor supports 120Hz, 144Hz, 165Hz, or 240Hz but the option does not appear, check your cable, adapter, and input standard. DisplayPort often allows higher rates more reliably than older HDMI paths, depending on the monitor generation. After changing the OS setting, rerun this refresh rate test to confirm the browser is seeing the higher rate too.
A browser refresh rate checker is best treated as a practical live estimate, not a hardware lab instrument. It can tell you whether the browser is rendering near 60Hz, 120Hz, 144Hz, 165Hz, 240Hz, or another common tier, and it is very useful for catching configuration mistakes. But the result still reflects the whole active path, not only the panel specification. Browser scheduling, background tabs, battery saver mode, mirrored displays, dock adapters, and OS-level frame throttling can all change the observed number. That limitation does not make the tool weak. It makes it honest. The value of this page is that it shows the refresh behavior you are actually using right now in the browser, which is often more useful than reading the number printed on the monitor box.
If the page consistently detects a value close to a common refresh tier and the motion preview feels visually consistent, the result is usually good enough for real troubleshooting. If your monitor is advertised at 144Hz and the browser repeatedly measures near 143Hz to 145Hz, that is a strong sign the display path is configured correctly. If the result jumps around heavily, gets stuck near 60Hz when you expect much higher, or changes depending on power mode or window focus, you should double-check system display settings, cables, adapters, and browser conditions. This tool is strongest as a practical verification page. It helps answer the simple but important question most users actually have: is my screen really running at the refresh rate I think it is?
It counts requestAnimationFrame callbacks over time and uses that to estimate how often your browser is rendering frames on the current display path.
It can estimate the live refresh behavior reasonably well, but the result still depends on browser timing, OS settings, power mode, and how your display is configured.
The most common reasons are OS refresh rate settings, battery saver mode, cable limits, mirrored displays, or a browser session that is not running at full refresh.
For many users, 120Hz or 144Hz is a strong step up from 60Hz. Competitive players may prefer 240Hz or higher if the full system can sustain it.
Only in a limited way. The tool can hint at fluctuation and pacing behavior, but it should not claim full VRR certification or detailed adaptive sync diagnostics.
Small fluctuations can be normal, but larger changes may point to browser scheduling, dropped frames, power limits, or unstable display timing.
Yes. Some browsers and power-saving states can reduce or cap refresh behavior, which is why the measured number may come in below the panel’s advertised rate.
Yes, if your browser and display path are actually running at those rates, the measured and rounded output should move toward that tier.
Because refresh rate is easier to understand when users can both read the detected Hz and see smoothness differences visually.
No. This is a browser-based monitor Hz test with no install required.