For Monitor refresh rate test, reset the run and repeat check 1 with the same device. If the observed value stays near 60 hz, change one connection or system setting, then compare a fresh sample before deciding that the hardware has failed.
Monitor refresh rate test
Run a monitor refresh rate test and read the frame frequency this browser observes in the current window.
Also known as: monitor refresh rate test, refresh rate test, monitor refresh rate tester, screen refresh rate test online, 120hz test, 144hz test, hz test. Free, online, and no download required.
Keep this tab visible, close busy pages, then start a five-second or longer sample.
What the monitor refresh rate test checks
| Check | How it is measured | Fails when |
|---|---|---|
| Observed refresh rate | Animation-frame timestamps are converted into a median frame frequency in hertz. | Fewer than 60 valid frame intervals arrive before the test stops. |
| Estimated range | Median absolute deviation produces a lower and upper browser-observed range. | The range remains wide because frame delivery changes during the sample. |
| Run conditions | The page records sample duration, delayed frames and whether the tab became hidden. | The tab hides, power saving intervenes or background work disrupts the sample. |
How to run the monitor refresh rate test
- Prepare the device and close any application that could reserve the same input or media stream.
- Start the monitor refresh rate test, follow the live prompt and complete every named control or direction.
- Finish the run, record the verdict and repeat once before changing one setting or connection.
If something failed
For Monitor refresh rate test, reset the run and repeat check 2 with the same device. If the estimate jumps between ranges, change one connection or system setting, then compare a fresh sample before deciding that the hardware has failed.
For Monitor refresh rate test, reset the run and repeat check 3 with the same device. If the tab became hidden during the run, change one connection or system setting, then compare a fresh sample before deciding that the hardware has failed.
How to read the result
Refresh rate test or FPS test?
Refresh rate test or FPS test? starts with the live monitor refresh rate test result. Complete the relevant control, record the displayed value and repeat it before changing another condition.
For refresh rate test or fps test?, compare the same device and connection in a second run. A repeatable missing event matters more than one isolated browser delay.
The browser cannot inspect physical parts while answering refresh rate test or fps test?. Use the visible evidence to choose one next check and confirm it in the application where the symptom occurs.
How the monitor refresh rate test works
The result is a browser observation. After Start test, requestAnimationFrame supplies one timestamp for each frame the page is allowed to present. The tool stores the intervals between those timestamps, rejects invalid gaps and reports the median as hertz. Median absolute deviation supplies the displayed range, while intervals at least 50 percent longer than the median are counted as delayed frames. Samples stay in memory and are discarded when the page closes. Nothing is uploaded. This method answers a narrow question: how often did this visible page receive an animation frame during this run? Follow the how to test monitor when you need a complete troubleshooting sequence.
Use the monitor refresh rate test in a visible foreground tab and keep the device, connection and duration unchanged. Repeat the same action enough times to separate one missed browser event from a persistent pattern. Record the displayed value before changing one setting, then run the same sequence again.
During Monitor refresh rate test, the live readouts update from bounded counters and recent samples. Complete every requested direction, key, channel or phase before finishing. Reset between devices so events from an earlier run cannot alter the next verdict, and keep the tab focused whenever timing or event frequency is part of the result.
What the result can establish
Run the test for at least five seconds with the window visible and still. Close animated tabs and heavy applications, connect a laptop to power and turn off battery saver for the comparison. If the result is near 60 Hz when you expected 120 or 144, open the operating system's display settings and confirm the selected refresh mode. Then repeat in a second browser. Change one condition at a time. A result that moves after the system setting changes supports that explanation; a result that does not move calls for checking the cable, dock, display input and browser limits without treating this page as the final hardware diagnosis.
Use the monitor refresh rate test in a visible foreground tab and keep the device, connection and duration unchanged. Repeat the same action enough times to separate one missed browser event from a persistent pattern. Record the displayed value before changing one setting, then run the same sequence again.
Read pass as confirmation of the collected sample, warn as a repeatable concern that needs comparison, fail as a missing or abnormal signal with a direct next action, and inconclusive as too little valid input. The number in the detail explains which threshold or count produced the status for Monitor refresh rate test.
Measurement limits
The page cannot read the monitor's EDID, rated mode, cable bandwidth or panel electronics. It also cannot certify a 120 Hz or 144 Hz hardware setting. Variable refresh rate can change frame timing on purpose. The browser engine, operating-system compositor, window size, battery saver, thermal limits and background load can lower or vary the observed result. Some browsers align animation callbacks to their own scheduling policy. A stable browser-observed value is useful evidence about this page, but it is not a hardware specification and it does not prove that every application uses the same display mode.
The Monitor refresh rate test reads only signals that the operating system and browser expose to this page. It cannot inspect physical wear, firmware queues, electrical contacts, analogue circuitry or another application's private processing. A clean run confirms the observed sample, while an intermittent fault may require a longer repeat under the same conditions.
Browser scheduling, power saving, wireless transport, display timing and background work can alter the values shown by Monitor refresh rate test. Compare results only when those conditions match. Do not treat a small difference as a hardware change unless it repeats across several controlled runs.
Monitor refresh rate test questions
What does this monitor refresh rate tester measure?
It measures the timing of animation frames delivered to this visible browser page. The estimate includes browser scheduling and operating-system composition, so it can show whether the current page is behaving near a common refresh band without reading the monitor's rated hardware mode.
Why can a 120hz test still show about 60 Hz?
Check the selected refresh mode in system display settings first. Battery saver, a dock or cable limit, browser scheduling, duplicated displays and background load can also hold the observed page near 60 Hz. Repeat after changing one condition, then compare another browser before blaming the panel.
Can a 144hz test prove that my monitor is running at 144 Hz?
No. A stable result near 144 Hz means this page received animation frames at about that rate during the sample. It does not read display firmware or certify the panel. The screen refresh rate test online result should be checked against the operating system's selected mode and the monitor's own information display.
What is the difference between refresh rate and FPS?
What is the difference between refresh rate and FPS is answered by the live values in this monitor refresh rate test. Complete every named input, repeat the failed action and compare one changed connection or setting. The browser can confirm only the events or media it receives. Use additional check 1 to decide whether the same symptom follows the device into another application.
How should I repeat the monitor refresh rate test fairly?
For monitor refresh rate test, keep the same browser window, foreground state, device connection and test duration for both runs. Reset the counters, repeat the requested actions in the same order and compare the displayed values. If the samples disagree, collect a third run before changing hardware or settings so one scheduling delay does not control the decision.
What can the monitor refresh rate test not prove?
The monitor refresh rate test cannot see hidden firmware, switch wear, electrical faults or processing inside another application. It confirms only the events, media tracks or rendered frames delivered to this page during the sample. Use the result to select one next check, then verify any change in the application where the original symptom occurs.