FPS Test — Check Your Frame Rate Online
This free FPS test starts automatically and measures your real frame rate from actual frame timestamps: current and average FPS, 1% and 0.1% lows, frame time, dropped frames, stutters and your display's true refresh rate. No download, no sign-up.
The meter starts automatically — no button needed. Keep this tab in front for a clean reading.
Your system (read locally, never uploaded)
Benchmark history
What this frame rate test measures
A frame rate test answers a simple question — how many new images does your screen actually show each second — and a harder one: how evenly do they arrive? A system that averages 120 FPS but spikes to a 40-millisecond frame every second feels worse than one locked at a steady 90, and a test that only shows an average would hide that completely. That is why the meter above reports the lows and the frame-time graph alongside the headline number. The slowest 1% of frames, the 1% low, is the figure reviewers trust, because those are the hitches you feel as stutter in a game or a judder in a video.
The comparison lanes under the graph show the same disc moving at 15, 30, 60, 120 and 240 FPS next to a lane running at your own display's full rate. On a 60Hz screen the faster lanes will look identical to the 60 FPS lane, because the display physically cannot show more — that is an honest result, not a bug. On a working 144Hz monitor the difference between the 60 lane and your own lane is obvious at a glance, which makes the lanes the fastest sanity check that a high-refresh display is set up correctly.
How this test measures frame rate
Your browser draws a new frame in sync with your display, a rhythm called VSYNC, and it tells the page the exact timestamp of every frame through the requestAnimationFrame API. This tool records the gap between every pair of timestamps. Frame rate is simply 1,000 divided by the average gap in milliseconds, so the numbers here are measured, not estimated. The refresh rate is detected from the median gap, snapped to the nearest standard rate such as 60, 120 or 144 Hz. Gaps caused by switching to another tab are excluded, because browsers throttle background tabs to roughly one frame per second and that would poison the reading.
That method also defines the limit of any browser test: a page can never draw faster than your screen refreshes, so a perfect score equals your display's Hz, not an unlimited number like an in-game benchmark can report. What the browser test tells you — honestly and precisely — is whether your display, operating system settings, cable and browser are actually delivering the smoothness you paid for.
How to run the test
- Close heavy tabs, downloads and screen recorders — they all steal frames from the same budget.
- Watch the live meter for a few seconds while it settles and detects your refresh rate.
- Optionally add a stress load — Canvas particles load the CPU, the WebGL shader loads the GPU — to see how much headroom you have.
- Press Benchmark 10s, 30s or 60s for a graded result, then use Copy Results to save or share it.
- Compare the lanes and check the frame-time graph: red bars are stutters, frames that took more than twice the normal time.
Why does my high-refresh monitor show 60?
This is the single most common problem this test uncovers: someone buys a 144Hz monitor, plugs it in, and Windows quietly keeps it at 60Hz. Work through the checklist in order. First, open your operating system display settings and set the refresh rate to the highest value listed — on Windows that is Settings, System, Display, Advanced display; on macOS it is System Settings, Displays, Refresh Rate. Second, check the cable and port: many older HDMI cables and some laptop docks cap out at 60Hz at higher resolutions, while DisplayPort or a certified high-speed HDMI cable carries the full rate. Third, plug laptops into power and turn off battery-saver mode, which commonly caps rendering at 60 or even 30 frames per second. Fourth, disconnect a second, slower monitor temporarily — mixed refresh rates can drag the compositor to the lowest common rate. Fifth, make sure hardware acceleration is enabled in your browser settings, and test in a second browser to rule out an extension. Run the test again after each change; the detected rate should jump the moment the real bottleneck is gone.
Frame rate guide: what each number feels like
| Frame rate | Frame time | Typical use |
|---|---|---|
| 24 FPS | 41.67 ms | Cinema — the familiar filmic look |
| 30 FPS | 33.33 ms | Broadcast TV, online video, visuals-first console games |
| 60 FPS | 16.67 ms | The everyday standard for desktops, phones and most games |
| 90 FPS | 11.11 ms | VR headsets, where low delay prevents discomfort |
| 120 FPS | 8.33 ms | High-refresh phones, current consoles, fast-paced games |
| 144 FPS | 6.94 ms | The most common gaming-monitor target |
| 240 FPS | 4.17 ms | Competitive esports displays |
Returns diminish as the numbers climb. Going from 30 to 60 FPS removes about 16.7 milliseconds from every frame, which is dramatic; going from 144 to 240 removes only about 2.8 milliseconds, which is subtle for most people — though fast competitive players still notice it. A stable rate matters as much as a high one, which is why this test grades your lows, not just your average.
Frequently asked questions
What is an FPS test?
An FPS test measures how many frames per second your browser actually draws on your screen. It counts real frame timestamps, so it shows your current frame rate, your display's refresh rate, and whether frames are being dropped or arriving unevenly.
Why is my FPS capped at my refresh rate?
Browsers synchronise animation to your display's refresh (VSYNC), so the maximum frame rate a web page can show equals your refresh rate in Hz. A result equal to your Hz is a perfect score here — it is not a cap being imposed on your hardware.
What is a good FPS result?
An average at or within a couple of frames of your refresh rate, 1% lows above about 85% of that average, and zero or near-zero stutters. The benchmark grade on this page scores exactly those things, from Flawless down to Struggling.
Does this test measure FPS inside my games?
No. A web page has no view into another application, so this measures your browser's rendering — which reflects your display, settings and system health, but is not identical to in-game FPS. Use your GPU driver's overlay for in-game numbers.
Is anything uploaded or tracked?
No. Every measurement runs locally in your tab. Your benchmark history is stored only in your own browser's local storage, and you can clear it any time from your browser settings.
Why does the test ask me to keep the tab in front?
Browsers throttle or pause animation in background tabs to save power, often to about one frame per second. Those gaps are excluded from the statistics automatically, but a visible tab gives the cleanest, most honest reading.