How to Check Your Monitor's Real-Time FPS

Buying a 144 Hz monitor doesn’t guarantee you’re running at 144 Hz. A wrong setting in Windows, a cable that can’t carry the bandwidth, or a power-saving mode can quietly hold your screen at 60 Hz while the spec sticker still says otherwise. Checking your monitor’s real-time FPS is how you confirm the refresh rate you’re actually getting right now, live on your own machine. The fastest way to do it is in the browser: a page draws frames as quickly as your display allows and counts how many land each second, so the number on screen reflects reality rather than a datasheet.

What “monitor FPS” really means

A monitor doesn’t produce frames — it displays them. Its refresh rate, measured in hertz (Hz), is how many times per second the panel redraws its image: 60 Hz means 60 refreshes per second, 144 Hz means 144. When a browser reports “FPS” for your display, it’s measuring how often it can paint a new frame in sync with those refreshes. On an idle desktop with nothing throttling it, the browser’s frame rate rises to meet the refresh rate and settles there. That’s why a healthy 120 Hz monitor reads close to 120 FPS in a live test, and a 60 Hz one tops out near 60.

The key idea is the cap. Your display sets a ceiling. Software can’t paint faster than the panel refreshes, so a real-time FPS reading is a practical, in-the-moment measurement of the refresh rate your system negotiated with the monitor — the advertised number only if everything in the chain agrees. If you want the conceptual distinction spelled out, the guide on FPS vs refresh rate covers how the two relate and why they aren’t the same thing.

How the browser reads it live

Browsers expose a function called requestAnimationFrame. When a page asks to be called before every screen repaint, the browser fires that callback in step with the display’s refresh cycle. By recording the timestamp of each callback and looking at the gaps between them, a test page can work out both the frame time (milliseconds between frames) and the frame rate (frames per second) as they happen.

This matters for accuracy. The measurement is tied to the display’s actual paint schedule, not a fixed guess, so it tracks your true refresh rate in real time. Nothing installs, and no data leaves your device — the timing all happens locally in the page. The display FPS test uses exactly this approach: it animates continuously and shows a running FPS figure so you can watch the number stabilise within a second or two.

Two honest limits are worth knowing. First, the reading is a browser-level measurement; it reflects the refresh rate presented to the browser, which normally matches the OS setting but is filtered through the compositor. Second, a single instantaneous FPS value bounces around, which is why a good test also reports frame time and consistency — a steady stream of evenly spaced frames is what “smooth” actually means.

Step by step: check your real-time FPS

1. Close what you don’t need. Heavy background apps or a busy CPU can cause the browser to miss repaint deadlines, dragging the number below your true refresh rate. Start from a quiet system.
2. Open the test in a foreground tab. Launch the display FPS test and keep the tab active and visible. Background tabs are deliberately throttled (more on that below).
3. Let it settle. Watch the FPS readout for a few seconds. It should climb and hold near a round-ish figure — commonly 60, 75, 120, 144, or 165 depending on your panel.
4. Compare against your OS setting. On Windows, check Settings → System → Display → Advanced display. On macOS, System Settings → Displays. The live FPS should match the Hz shown there.
5. Confirm the panel’s rated maximum. If the live number is lower than what the monitor is rated for, the refresh rate is being capped somewhere — that’s the useful finding.

If you want to cross-check purely against the panel’s negotiated mode rather than browser paint timing, the dedicated refresh rate test focuses on that specific reading.

Why the number might be lower than you expect

A real-time FPS that sits below your monitor’s rating is almost always a configuration or hardware-path issue, not a broken panel. The usual culprits:

The OS is set to the wrong Hz

Plugging in a high-refresh monitor doesn’t automatically select its top mode. Windows and macOS frequently default to 60 Hz and leave the higher rate as an option you have to pick manually. This is the single most common reason a 144 Hz monitor behaves like a 60 Hz one.

The cable or port can’t carry the bandwidth

Higher refresh rates at higher resolutions need more bandwidth. An older HDMI cable, a low-spec adapter, or the wrong port can force the display to fall back to a lower refresh rate to fit within what the link supports. Swapping to a cable rated for your resolution-and-refresh combination often unlocks the full rate.

Power saving throttles the display

Laptops especially will drop refresh rate to save battery. On battery power, a machine may run the panel at a reduced rate or enable a variable/adaptive mode that lowers it when the image is mostly static. Plug in and re-check if the number looks low on a portable.

The browser is throttling a background tab

Browsers intentionally slow down requestAnimationFrame in tabs that aren’t visible — often to a crawl — to save power. If you switch away from the test tab, the FPS reading collapses. That’s expected behaviour, not a fault. Always read the number with the test tab in the foreground.

The system is simply busy

If the CPU or GPU is saturated by other work, the browser can miss repaint deadlines and report fewer frames than the display could show. A quiet system gives the cleanest reading.

Reading the result honestly

A live FPS test tells you the effective refresh rate you’re getting through the browser — a genuinely useful real-world check. What it does not do is read your GPU’s temperature, utilisation, VRAM, or power draw; browsers have no access to those figures, and any tool claiming to show them from a web page is guessing. Stick to what the measurement actually is: frames per second, frame time, and how consistent the two are.

It also helps to separate display FPS from game FPS. This test measures how fast your screen is refreshing, capped by the panel. In-game FPS is how many frames your GPU renders, which can be higher than the display can show (wasted) or lower (the display repeats frames). If your concern is smooth media rather than the panel rate, the browser video performance guide walks through diagnosing choppy playback specifically.

Frequently asked questions

Why does my browser FPS max out at 60 when I have a 144 Hz monitor?

Almost always because the operating system is set to 60 Hz, not because the browser is limited. Open your display settings and manually select the higher refresh rate, then re-run the test. If the OS won’t offer the higher rate, suspect the cable, port, or adapter bandwidth next.

Is a browser FPS reading accurate?

For confirming your effective refresh rate, yes — it’s tied to the display’s real repaint schedule via requestAnimationFrame, so it tracks the rate your system actually presents. It’s a measurement of paint timing rather than a hardware register, and it needs the tab in the foreground on a quiet system to be reliable, but within those conditions it’s a trustworthy real-time check.

Does the number depend on which browser I use?

The underlying refresh rate is the same, but throttling behaviour and compositor timing can differ slightly between browsers, and background-tab throttling is universal. For a fair comparison, always test in a foreground tab with the same conditions.

Why does my FPS drop when I move the test to a second tab?

Browsers throttle animation timers in tabs that aren’t visible to save power, so requestAnimationFrame fires far less often. This is intentional. Bring the test tab back to the foreground and the reading recovers.

Can I check my monitor’s FPS without downloading anything?

Yes. That’s the whole point of a browser-based test — it runs on the page, measures locally, and installs nothing. Open the test and read the number directly.

Checking your real-time FPS takes under a minute and settles the one question a spec sheet can’t answer: is your monitor actually running at the rate you paid for? If the live figure comes back below the rating, walk through the OS setting, cable, and power mode before blaming the panel — and re-run the display FPS test after each change to confirm you’ve unlocked the full refresh rate.