Refresh Rate Test

This free refresh rate test measures your screen's actual Hz live, right in your browser, and lets you compare what different frame rates look like side by side. No download, no sign-up.

RUNS ENTIRELY IN YOUR BROWSER · NOTHING ABOUT YOUR DEVICE IS RECORDED OR SENT ANYWHERE

Last updated: · Reviewed for accuracy against current browser APIs

Measuring your screen's refresh rate…
–Hz
Keep this tab focused and other heavy apps closed for the most accurate reading.
See the difference: motion at different frame rates
24 FPS
30 FPS
60 FPS
Your display

Each panel moves the dot at a genuinely different, independent frame rate — not a video — so what you see is an accurate live comparison, not a pre-recorded clip.

Frame pacing check

The number above is an average. This records the arrival time of every frame for 10 seconds and shows each one as a bar, so a stutter shows up as a spike. Keep this tab in front and leave the page alone while it runs.

Not run yet.

Frame pacing check: is every frame on time?

The big number at the top of the page is an average, and averages hide things. A screen that hitches for 60 ms every few seconds still reads 59 or 60 Hz. You'd feel every one of those hitches, and the Hz readout would never mention them. The pacing check records when each frame actually arrived over ten seconds and draws them as bars, so a hitch is a tall red spike instead of a rounding error.

It reports six numbers. Typical frame time is 16.7 ms on a 60 Hz screen and about 6.9 ms on 144 Hz. The 1% low is the rate of your slowest one percent of frames, and it is the number that tracks how smooth things feel. A late frame is anything that took more than 1.5 times the typical time. On a quiet machine with a healthy 60 Hz screen I'd expect an average of 59.9 or 60.0, a 1% low within a hertz or two of that, and maybe one late frame out of 600. If you see a 1% low of 51 Hz, fifteen late frames and a worst frame of 70 ms, the browser is being starved. Look at background apps, battery saver and the graphics driver before you blame the panel.

The other thing it catches is a rate that changes while you watch. Compare the first half of the run with the second half; if the typical frame time moves by more than 5%, the verdict says so. That's what a phone sold as 120 Hz does when it quietly falls back to 60 after a minute of heat, or a laptop does the moment you unplug it.

  1. Set up the conditions you care about.

    Plugged in or on battery, game mode on or off. Close heavy tabs first.

  2. Press "Run 10-second pacing check".

    Keep the tab in front and don't scroll or switch windows. Switching away cancels the run.

  3. Read the verdict, then look at the graph.

    Evenly short green bars are what you want. Isolated red spikes point to hitches; a graph that steps up or down halfway means the rate changed.

  4. Change one thing and run it again.

    Cable, power mode, refresh setting. Compare the 1% low, not just the average.

Limits, honestly. This measures when the browser hands frames to the screen, not what the panel does with them, so it says nothing about response time or smearing (the Ghosting Test covers that). Some browsers cap animation at 60 Hz in power-saving modes, and a phone with adaptive refresh will drop its rate on purpose when little is moving. That's by design and not a fault. And a ten-second run can miss a stutter that only shows up in one particular game.


Comparison of 60 Hz and 144 Hz: more frames drawn in the same time at the higher rate
Comparison of 60 Hz and 144 Hz: more frames drawn in the same time at the higher rate

Does a 120 Hz phone really hold 120 Hz? Reading the pacing result

Say you own a phone sold as 120 Hz and you run the pacing check right after a long gaming session. The run finishes with the verdict "The rate changed during the run: about 120 Hz in the first half, about 60 Hz in the second. That looks like adaptive refresh, power saving or heat throttling." The average readout shows roughly 90 Hz. That number matches neither half, and the arithmetic explains why: 5 seconds at 120 Hz is about 600 frames, 5 seconds at 60 Hz is about 300, and 900 frames over 10 seconds averages 90. Frame time went from about 8.3 ms to about 16.7 ms midway, and the graph steps up at the halfway point.

The next move is to let the phone cool, run it plugged in with battery saver off, and compare. If it now holds about 120 Hz from start to finish, the earlier drop was heat or power management, which is normal behaviour on many phones. If it still falls to 60 after a few seconds with everything off, look for a refresh-rate or smooth-display setting that was left on a lower option.

Not every dip is a fault. On a 60 Hz screen, a result of "A few hiccups: 3 late frames (roughly 3 frames missed)" out of around 600 is 0.5% of frames. It is worth a second run with background apps closed, but you won't feel it in everyday use.


How to test your refresh rate

Here's how to test your screen's refresh rate online without an app, in a few seconds — no software, no account.

  1. Just open this page.

    The measurement starts automatically the moment the page loads — there's nothing to click to begin.

  2. Close other heavy tabs and apps.

    Anything competing for your CPU or GPU can cause a slightly low or unstable reading, since the browser has to share resources.

  3. Wait a couple of seconds.

    The Hz number will settle once enough frames have been measured — a jumpy number for the first moment or two is normal.

  4. Compare frame rates side by side.

    Watch the four panels below to see how 24, 30, 60 FPS, and your display's actual rate genuinely look and feel different in motion.

  5. Click "Test again" any time.

    Useful after changing a display setting, switching cables, or plugging into a different monitor.


Who tests their refresh rate, and why

Gamers run this after buying a new monitor to confirm it's actually running at its rated 144 Hz or 240 Hz, rather than silently falling back to 60 Hz because of a display setting or the wrong cable. Phone buyers use it to check whether a phone advertised with a 90 Hz or 120 Hz screen is genuinely running at that rate, since some phones quietly drop to a lower rate to save battery unless a setting is changed. People troubleshooting choppy scrolling or laggy-feeling video use this to rule out the display itself before assuming it's a software problem. Video editors and content creators check refresh rate to understand why footage recorded at one frame rate can look subtly wrong when played back on a screen running at another. If smooth motion matters to you, it's worth also running our Ghosting Test, since a high refresh rate alone won't save you from a slow panel that smears and trails during fast motion. And anyone simply curious what all the "120Hz" and "144Hz" marketing actually means can see it — and feel it — for themselves in the comparison panels above.


What is screen refresh rate?

Refresh rate is how many times per second your screen redraws the image it's showing, measured in Hertz (Hz). A 60Hz screen redraws up to 60 times a second; a 144Hz screen, up to 144 times. A higher number means the screen is physically capable of showing more updates per second — smoother motion, more responsive-feeling input, and less blur when something on screen is moving quickly.

It's worth being clear that you don't strictly need a high refresh rate. For reading, writing, browsing, and most video content, 60 Hz is genuinely enough for most people. Where a higher refresh rate earns its keep is fast motion — competitive gaming, fast-scrolling content, and anything where responsiveness matters more than usual.


Common refresh rate values compared

Refresh rateCommonly seen onWhat it feels like
24–30 HzTV, cinema, most online videoThe familiar, natural look of film and standard video
60 HzMost monitors, laptops, budget phonesSmooth for everyday use; the long-standing standard
90 HzMid-range phonesNoticeably smoother scrolling than 60 Hz
120 HzFlagship phones, gaming monitorsVery smooth; the point where most people stop noticing further gains
144 HzGaming monitorsA popular sweet spot for competitive gaming
240 Hz+High-end esports monitorsDiminishing returns for most people beyond this point

Refresh rate vs. FPS — what's the difference?

The two terms get used interchangeably, but they're not quite the same thing. Refresh rate is a fixed property of your screen — how many times it's physically capable of redrawing per second, regardless of what's being shown on it. Frames per second (FPS) is how many new images your computer, phone, or game actually produces per second, which depends on processing power and how demanding the content is.

You could have a 144Hz monitor, but if you're running a demanding game your graphics card can't quite keep up with, the actual FPS might be 70 or 80 — well below what the screen could display. Refresh rate is the ceiling; FPS is what you're actually getting under it. This is also why the comparison panels above are useful: they show what a genuinely fixed frame rate looks like, independent of your screen's own maximum. If you want to check whether every frame at that rate is actually arriving on schedule rather than being skipped or repeated, our Frame Skipping Test covers that specifically.


Refresh rate problems at a glance

SymptomLikely causeQuick fix
Reading shows 60Hz on a higher-rated monitorOS display setting not set to the max rateCheck your display settings and select the higher refresh rate
High rate won't stay selectedCable or port doesn't support it at your resolutionUse DisplayPort or a higher-spec HDMI cable
Screen tearing during motionFPS and refresh rate out of syncEnable V-Sync, G-Sync, or FreeSync if your hardware supports it
Phone feels less smooth than its rated HzBattery-saving mode limiting refresh rateCheck your phone's display settings for a refresh rate or battery-saver toggle
Reading is unstable or jumps aroundOther apps competing for system resourcesClose other tabs and heavy apps, then test again

Fixing common refresh rate problems

Your monitor isn't running at its rated Hz. On Windows, go to Settings → System → Display → Advanced display, select your monitor, and check the refresh rate dropdown — it's common for this to quietly default back to 60Hz after a driver update — worth getting the latest one directly from NVIDIA, AMD, or Intel, whichever matches your graphics card. On macOS, check System Settings → Displays for a refresh rate option (not all Macs support this).

A high refresh rate won't stick. This is very often the cable. Older HDMI versions and cheap cables can cap out well below what your monitor and graphics card can otherwise do — DisplayPort or a certified high-bandwidth HDMI cable usually resolves it.

Motion looks torn or glitchy. This is a sync issue between your FPS and your screen's refresh rate rather than the refresh rate itself being wrong. Enabling V-Sync, G-Sync, or FreeSync (depending on your hardware) lines the two up.


Frequently asked questions

How do I test my screen's refresh rate?

Just open this page — the test starts automatically and measures how many times your screen actually redraws per second, showing the result in Hz within a few seconds. Click "Test again" to re-run it any time.

What is a good refresh rate?

For everyday browsing, reading, and video, 60 Hz is plenty. For gaming, 120–144 Hz is a popular sweet spot, and competitive players sometimes go higher. Most people can't reliably tell the difference above about 120–144 Hz.

Why does this test show a different number than my monitor's rated Hz?

This usually means your operating system isn't actually set to use the monitor's maximum refresh rate, or the cable or port you're using doesn't support it at your current resolution. Check your display settings and cable type.

What's the difference between refresh rate and FPS?

Refresh rate is a fixed property of your screen — how many times it can redraw per second. FPS is how many new images your computer or game actually produces per second, which can be lower than your screen's refresh rate if the content isn't demanding enough hardware to keep up.

Can a browser accurately measure very high refresh rates?

Browsers can measure refresh rate reasonably accurately up to around 240 Hz, since the measurement is tied to how often the browser itself is allowed to update the page. For extremely high rates, dedicated software will generally be more precise.

Why does my phone feel smoother than my monitor even at a similar Hz?

Touchscreens often combine a high refresh rate with a high touch-sampling rate, so your finger's movement is tracked and reflected on screen extremely quickly, which can feel smoother than the refresh rate number alone suggests.

Does a higher refresh rate use more battery or power?

Yes, generally. Redrawing the screen more often takes more processing and power, which is why many phones and laptops offer an adaptive or variable refresh rate that drops lower when the extra smoothness isn't needed.

Does this test work on a phone or tablet?

Yes. It works the same way on any modern mobile browser, and is a good way to confirm whether a phone advertised with a 90 Hz or 120 Hz display is actually running at that rate.

Is this test free and does it record anything?

Yes, it's completely free and runs entirely in your browser. Nothing about your screen or device is recorded, uploaded, or stored.

What does the frame pacing check show that the Hz number doesn't?

The Hz number is an average. The pacing check records the arrival time of every frame for ten seconds and reports the 1% low, the count of late frames, the worst single frame and whether the rate changed partway through. A screen can average 60 Hz and still stutter, and this is how you see it.


Testing a monitor vs. a phone or tablet

This test works the same way on either one, but what's worth checking differs slightly.

On a monitor, the number you see here should match what your operating system's display settings claim — if it doesn't, that's almost always a settings or cable issue rather than a monitor fault, since the hardware itself is fixed and can't quietly change its own maximum. On a phone or tablet, it's much more common for the actual rate to shift on its own: many devices automatically drop to a lower refresh rate to save battery, especially in low-power mode or when the screen content is static, so testing right after unplugging from a charger or with battery saver on can give a genuinely different reading than testing under normal use.

If you're comparing two devices before deciding which to buy or keep, test both under the same conditions — same power state, same battery-saving settings — so you're comparing the numbers fairly rather than catching one of them in a temporarily reduced mode.


More tools on ProDeviceTest

Troubleshooting a whole setup rather than just your display? These run the same way — instant, no download, right in your browser.