How to Check Monitor Refresh Rate (and Verify It)

You bought a 144Hz monitor. There is a real chance Windows has been feeding it 60Hz since the day you plugged it in. Here is how to check your monitor's refresh rate — and, more importantly, how to verify what your screen is actually doing.

Side-by-side frame timing diagram comparing 60Hz, 144Hz and 240Hz monitor refreshes
Same monitor, three very different experiences — it all comes down to how often the panel actually refreshes.

The classic trap: a 144Hz monitor running at 60Hz

Windows does not automatically pick the fastest refresh rate your monitor supports. It negotiates a safe, conservative mode — very often 60Hz. The box says 144Hz, the on-screen menu says it can do 144Hz, but the signal arriving at the panel is 60Hz until you change it yourself.

This is one of the most common hardware own-goals in PC gaming. People play for months at 60Hz on a 144Hz or 240Hz panel, blaming the mouse or the game for the heavy, smeary feel — never the dropdown menu in Settings. Support forums are full of the same confession: 'I finally checked, and I feel sick.'

Before you touch any settings, get a baseline. Open our monitor Hz test on the screen you want to check and let it sample for a few seconds. If it reports a median around 60Hz on a monitor you paid 144Hz money for, you have found the problem in under a minute.

How to check refresh rate in Windows and macOS

The operating system setting is the first place to look, because it controls the signal being sent:

One warning: these menus show what the OS intends to output, not what the panel actually presents. For that, you measure the frames themselves.

Verify what actually reaches the screen

A browser can measure real presented frames because of how animation timing works. Every time the browser finishes drawing and presenting a frame, it fires a requestAnimationFrame callback with a timestamp. Sample those timestamps for a few seconds and you get the true frame delivery rate — which is exactly what the monitor Hz test does, reporting a median Hz, frame time, jitter and missed-frame count.

Settings can lie; presented frames cannot. If Windows says 144Hz but the browser sees 60 callbacks per second, something between the OS and your eyes is capping the signal — usually the display setting itself, a cable limit, or a frame-skipping panel.

The number that actually matters for how a display feels is frame time — the gap between presented frames:

Refresh rateFrame timeReal-world feel
60Hz16.7msBaseline; visible cursor trails in fast motion
120Hz8.3msPhones, tablets and console 120Hz modes
144Hz6.9msThe long-time PC gaming sweet spot
240Hz4.2ms2026 mainstream esports standard
360Hz+2.8msPro-tier monitors up to 540Hz

Two tips for a clean reading: keep the test tab in the foreground (browsers throttle hidden tabs to save power) and close heavy apps so the compositor is not dropping frames for unrelated reasons.

Cable and port limits: the silent refresh rate killer

If the OS offers 144Hz but you cannot select it — or you select it and get a black screen or flicker — the cable is the prime suspect. Every link in the chain (GPU port, cable, monitor input) runs at the speed of the weakest one:

Connection1080p1440p4K
HDMI 1.4144Hz75Hz30Hz
HDMI 2.0240Hz144Hz60Hz
HDMI 2.1240Hz+240Hz+120-144Hz+
DisplayPort 1.2240Hz165Hz75Hz
DisplayPort 1.4 (DSC)240Hz+240Hz+144-240Hz
DisplayPort 2.1540Hz+480Hz+240Hz+

The classic failure: a 1440p 165Hz monitor on an old HDMI 1.4 cable from a drawer. Panel works, GPU works, cable caps you near 75Hz. When in doubt, use the DisplayPort cable from the monitor's box — it is the one rated for the advertised specs.

Frame skipping: when the number lies the other way

Sometimes the OS and the monitor's menu both claim a high refresh rate, yet the panel quietly throws frames away. This is frame skipping: the display accepts, say, a 120Hz signal but only has the electronics to draw 96 of those frames per second, dropping the rest.

The trick became infamous with overclocked Korean 1440p monitors — Qnix and X-Star panels budget gamers pushed from 60Hz to 96-120Hz a decade ago, many of which skipped frames at the top of the range. It still appears in no-name '165Hz' budget panels that are really 144Hz hardware with a hopeful scaler.

Detection is straightforward: run the browser Hz test, compare the median against the claimed mode, and watch the motion track. Skipped frames show up as uneven, stuttering motion even when the average looks fine — high jitter plus missed frames is the fingerprint.

Consoles and TVs: the HDMI 2.1 120Hz trap

The same story plays out in the living room. A PS5 or Xbox Series X can output 4K at 120Hz, but only through an HDMI 2.1 port with enough bandwidth — and many TVs only have HDMI 2.1 on one or two of their four ports. Plug into the wrong one and the console silently falls back to 60Hz.

In 2026, 120Hz panels are standard on mid-range TVs, but 'supports 120Hz' on the spec sheet and 'delivers 120Hz from your console' remain two different things.

What refresh rate actually changes in games

The math is simple and brutal. At 60Hz, each frame lives on screen for 16.7ms. At 144Hz that drops to 6.9ms — you are seeing game state nearly 10ms sooner, every single frame. At 240Hz it is 4.2ms. High refresh does not just look smoother; it cuts the delay between what happens in the game and what you see. Our reaction time benchmarks show how much those milliseconds matter.

Notice the diminishing returns, though: 60→144Hz saves about 9.7ms per frame, while 144→240Hz saves only 2.7ms. Both are real; one is transformative, the other is a competitive edge. That is why 144Hz owned the last decade and 240Hz is the new mainstream.

Want proof the market has moved? Walk into an internet cafe in Seoul, Shanghai or Bangkok in 2026. PC bangs and esports cafes now advertise 240Hz as the standard seat, with 360-540Hz rows for the regulars — the same way cafes once advertised fiber internet. High refresh stopped being an enthusiast flex years ago.

One last habit: any time you change drivers, cables, docks or displays, re-check the setting — driver updates love silently resetting it to 60Hz. A quick pass through the monitor test checklist after any hardware change catches it.

The bottom line

Your monitor runs as fast as the slowest link: OS setting, cable, port, panel. Set the highest refresh rate, use a cable that supports it, then verify with real presented frames in the browser test. Two minutes of work — and a shocking number of 144Hz owners will discover they have been gaming at 60Hz the whole time.

Ready to check your own gear?

Monitor Hz Test

Frequently asked questions

Why is my 144Hz monitor stuck at 60Hz?

Windows defaults to a conservative 60Hz mode on many displays. Go to Settings → System → Display → Advanced display and manually select 144Hz. If 144Hz is missing from the list, your cable or port is the bottleneck — switch to DisplayPort or HDMI 2.0+ and check your GPU's output port spec.

Can HDMI run 144Hz?

Yes, but the version matters. HDMI 1.4 handles 1080p at 144Hz, HDMI 2.0 handles 1440p at 144Hz, and HDMI 2.1 handles 4K at 120Hz and beyond. The GPU port, the cable and the monitor input all have to support the same version — the weakest link wins.

Why does the browser test show 60Hz when Windows says 144Hz?

Three usual suspects: the test tab is in the background (browsers throttle hidden tabs), the browser window is on a different monitor than the one you configured, or a power-saving mode is capping frame delivery. Keep the tab focused, move it to the correct screen, and disable battery saver.

Is 240Hz worth it over 144Hz?

For competitive play, yes — frame time drops from 6.9ms to 4.2ms, and the motion clarity gain is visible in fast flicks and tracking. For casual gaming and desktop work, 144Hz remains the value sweet spot. The jump from 60Hz to 144Hz is still the biggest single upgrade you can feel.

Does refresh rate affect FPS?

No — your GPU renders as many frames per second as it can regardless of refresh rate. But a 60Hz monitor can only show 60 of them per second, so extra frames are discarded or cause tearing. Refresh rate caps visible frames; it does not cap rendered frames.

MENU