FPS Test
This FPS test measures the frame rate your browser really delivers, live, in seconds: a meter that starts by itself, a timed benchmark with 1% lows and a frame-time graph, motion lanes that show you what 30, 60 and 144 FPS actually look like, and a stress test that finds out how much load it takes before frames start dropping. One honest limit up front: a web page cannot read a game's FPS — this measures your browser and your display, and the page tells you how to check your games too.
—
Starting the meter…
Average
—
Lowest
—
Highest
—
Frames counted
0
Calibrating — measuring your display's refresh rate from real frame timing.
The meter starts by itself and updates four times a second. A healthy system sits at or very near your display's refresh rate. The graph shows the last 120 frames: the line marks your refresh interval, and bars above twice that interval are stutters.
1 · Timed benchmark
Pick a length, press Start, and keep this tab in front until it ends — a background tab is throttled to about one frame a second, so the result would be meaningless. You get average, lowest and highest FPS, the 1% low, dropped frames and a grade.
No benchmark run yet.
Average FPS
—
1% low
—
Low / High
—
Dropped frames
—
2 · What does each frame rate look like?
The same dot crosses every lane at the same speed — but each lane only redraws it at its own frame rate. The low lanes jump in visible steps while the fast lanes glide. On a 60 Hz screen the 120 and 240 lanes look identical to the 60 lane, and that is the honest result, not a bug: a display cannot show more frames than it refreshes.
15 FPS
30 FPS
60 FPS
120 FPS
240 FPS
Your display
Lanes are stopped.
3 · Stress test — how much load before frames drop?
This animates thousands of particles on a canvas, loading your processor and your browser's compositor. Watch the live meter while it runs: a machine with headroom stays at its refresh rate, and one at its limit starts dropping frames. Run it for a minute if you want to spot a laptop slowing down as it warms up.
Stress test stopped.
4 · Your verdict
Run a benchmark above and the verdict writes itself from your numbers. No benchmark yet? The button below reads the live meter instead.
How this FPS test works
Your browser stamps every frame it shows with an exact time, and this test records the gap between stamps using requestAnimationFrame, the browser's own animation callback, which fires once per display refresh. Count the callbacks over a short window and you have the frames per second your browser is genuinely delivering. FPS is 1,000 divided by the average frame time in milliseconds — so 60 FPS means each frame took 16.67 ms, and 144 FPS means 6.94 ms.
The test first calibrates on your idle frames: it takes the median gap over the first couple of seconds and snaps it to the nearest common refresh rate — 60, 75, 90, 120, 144, 165, 240 or 360 Hz — so it can tell you whether you are getting everything your display offers. Gaps caused by a hidden tab are ignored, because browsers pause animation in background tabs; for the most accurate result, keep this tab in front for the whole run.
FPS vs refresh rate — what each number means
FPS is how many new pictures your device makes each second. Refresh rate, in hertz, is how often your screen replaces the picture. The screen sets the ceiling: a game can make 200 FPS on a 144 Hz monitor, but you only see 144 of them each second. A browser cannot draw faster than the screen refreshes, so a perfect browser score equals your display's Hz — not an unlimited number like an in-game benchmark.
Frame time is the inverse of FPS. The table below is the conversion the benchmark uses:
30 FPS — 33.3 ms per frame: the floor for watchable motion, standard for console story modes. 60 FPS — 16.67 ms: the accepted baseline for smooth motion — standard monitors, most phones, console performance mode. 120 FPS — 8.33 ms: modern phones, high-refresh laptops, console flagships. 144 FPS — 6.94 ms: the classic gaming monitor rate. 240 FPS — 4.17 ms: competitive esports panels. If your average sits a couple of FPS below your refresh rate, that is normal measurement noise; if it sits far below, something is holding the system back.
Why 60 FPS on a 144Hz screen?
This is the single most common result on this page, and it almost always has a boring fix. First, the operating system setting: a new monitor almost never arrives running at its full refresh rate — set it to 144 Hz in Windows Display settings (Advanced display, then Choose a refresh rate) or macOS Displays, and run this test again. Second, the cable: an old HDMI cable can top out at 60 Hz at high resolutions; use DisplayPort or a high-speed HDMI cable for 144 Hz and above. Third, power: battery saver and unplugged laptops cap frame rate — plug in and turn battery saver off. Fourth, the browser: make sure hardware acceleration is enabled in your browser settings, and close heavy tabs and extensions before a benchmark run. If the meter still reads 60 after all four, check the refresh rate test for a dedicated Hz reading.
How to read your benchmark
Average FPS is the headline, but it hides stutter — that is what the 1% low is for. If 99 frames take 7 ms and one takes 60 ms, the average still looks great, but you feel the hitch. A 1% low close to the average means genuinely smooth motion; a 1% low far below it means hitches even on a fast average. Dropped frames count the refreshes that got no new frame at all: near zero is the target. The frame-time graph makes the same story visible — tall bars are late frames, and red bars took more than twice as long as they should. Compare runs by changing one thing at a time: close a heavy tab, plug the laptop in, switch the OS refresh rate, and run the benchmark again.
How to test FPS in games
A web page cannot see inside a game, so for in-game FPS use the counter built for it. Steam: Settings, then In-Game, then turn on the in-game FPS counter — it draws a small counter over any Steam game. NVIDIA: open the NVIDIA App and press Alt+R for the performance overlay. AMD: open AMD Software and press Ctrl+Shift+O. Windows (any game): press Win+G for Xbox Game Bar and pin its performance widget, which shows FPS live. Run the game for a few minutes and watch the same three numbers this page teaches you — average, 1% low and dropped frames — because a high average with terrible lows feels worse than a slightly lower, steady average.
FPS on mobile and Safari
Phones are where refresh rates hide most. iPhones with ProMotion (iPhone 13 Pro and newer) can display up to 120 FPS, but Safari caps frame rate at 60 in low-power mode — turn low-power mode off before judging an iPhone's result. Most Android budget phones are capped at 60 FPS, while flagship models support 90 Hz or 120 Hz; the setting usually lives under display settings as "screen refresh rate" or "smooth display", and it is often set to 60 by default to save battery. Run the benchmark with the phone plugged in and the screen set to its highest rate, and keep the tab in front — switching apps pauses the measurement just like a hidden tab does on desktop.
Frequently asked questions
How do I test my FPS on PC?
Open this page and watch the live meter: it starts by itself and shows your current frame rate, milliseconds per frame and your display's estimated refresh rate. For a graded result, run a 10, 30 or 60-second benchmark. That measures your browser's frame rate. To see FPS inside a game, use the game's own counter or a graphics overlay instead: in Steam, open Settings, then In-Game, and turn on the in-game FPS counter; in the NVIDIA App press Alt+R; in AMD Software press Ctrl+Shift+O; on Windows, Xbox Game Bar (Win+G) has a performance widget with an FPS readout.
What is an FPS test?
An FPS test measures how many frames per second (FPS) your device draws. This page counts the frames your browser paints: the browser stamps every frame it shows, this test records the gap between stamps, and FPS is 1,000 divided by the average gap in milliseconds. It works on any phone, laptop or monitor with nothing to install, and every number is measured in your browser — nothing is uploaded.
How many FPS can the human eye see?
There is no single number. What is settled is that the jump from 30 to 60 FPS is the one almost everyone notices — each frame gets 16.67 ms shorter — while the gains above that get smaller: many people can tell 120 from 60 in fast motion, trained eyes can pick out 144 or 240 in a fast game, and beyond that the difference is subtle. 60 FPS is the accepted baseline for smooth motion, and the motion lanes above let you judge it with your own eyes instead of taking anyone's word for it.
Why is my FPS capped at 60 on a 144Hz monitor?
Work through it in order. First, check the display is actually set to 144 Hz in your operating system — Windows: Display settings, then Advanced display, then Choose a refresh rate; macOS: System Settings, then Displays. A monitor almost never arrives running at its full refresh rate. Second, check the cable: older HDMI cables top out at 60 Hz at high resolutions, while DisplayPort or a high-speed HDMI cable is needed for 144 Hz and above. Third, turn off battery saver and plug a laptop into power, and make sure hardware acceleration is enabled in your browser settings. Safari and some mobile browsers also cap frame rate in low-power mode.
What is a good FPS test result?
Compare your average against your own refresh rate, not against someone else's benchmark: 60 FPS on a 60 Hz laptop is a perfect score, and the same 60 on a 144 Hz monitor means something is capping you. A good result is an average within a couple of FPS of your refresh rate, 1% lows above about 85% of it, a stability score over 90% and few or no dropped frames. The benchmark above grades this for you automatically, from Flawless down to Struggling.
What are 1% lows?
1% lows are the frame rate during your slowest 1% of frames. Average FPS hides stutter: if 99 frames take 7 ms and one takes 60 ms, the average still looks great, but you feel the hitch. The 1% low shows how bad those slowest moments get — the closer your 1% low is to your average, the smoother motion actually feels. That is why the benchmark reports it next to the average instead of burying it.
Can this test measure FPS in my game?
No — and any web page that claims to is not telling the truth. A web page has no view into another application, so it cannot see inside Fortnite, Valorant, Minecraft or any other game. This test measures your browser's rendering, which reflects your display and your system's rendering path but is not a game benchmark. For in-game FPS, use the game's own counter, the Steam in-game FPS counter, your NVIDIA or AMD overlay, or Xbox Game Bar.
Does this FPS test work on mobile and iPhone?
Yes. The test runs in any modern mobile browser — Chrome on Android, Safari on iPhone — with nothing to install. iPhones with ProMotion (iPhone 13 Pro and newer) can display up to 120 FPS; most Android budget phones are capped at 60 FPS while flagship models support 90 Hz or 120 Hz. One honest limit: Safari caps frame rate at 60 in low-power mode, so turn low-power mode off before judging an iPhone's result.
How this test works: every number is measured in your browser from requestAnimationFrame timestamps — the live meter, the timed benchmark, the motion lanes and the particle stress test all run on Canvas 2D with no downloads, no sign-up and nothing uploaded. A web page cannot read a game's FPS; for games, use the game's own counter or a GPU overlay as explained above.
Related tests
Refresh Rate Test
Measure your monitor’s real refresh rate in Hz, frame time and stability — in 5 seconds.
UFOGhosting Test
A UFO glides across your screen while the page reports your real refresh rate — follow it to see motion blur.
dBMicrophone Test
Speak and watch the meter — then hear yourself back.
kHzHearing Test
Tones from 50 Hz to 20 kHz find the highest frequency you can hear.