Frame Rate Tester
Measure how many frames per second your browser is actually rendering, in real time. The test starts automatically — leave it running to watch your live FPS and the highs, lows, and average build up on the graph below.
— ms / frame
How it works
This test uses the browser's requestAnimationFrame API, which runs a callback just before each screen repaint. By timing the gap between those callbacks we can tell how many frames your browser is painting each second. The "current" reading is averaged over the last half-second so it stays steady, while min, average, and max accumulate over the whole session. Everything is measured and shown locally — nothing is uploaded.
Why is my FPS capped at 60 (or 120, 144…)?
Your browser won't paint faster than your display can refresh. On a standard 60 Hz monitor the ceiling is about 60 FPS; on a 120 Hz, 144 Hz, or 240 Hz panel you'll see correspondingly higher numbers. The dashed lines on the graph mark those common refresh rates. If your FPS sits well below your refresh rate, the page or your machine is struggling to keep up.
Tips for an accurate reading
- Keep this tab focused — browsers throttle frame rates in background tabs.
- Close other heavy tabs and apps that might be competing for the GPU.
- On a laptop, plug in — battery-saver modes often cap the refresh rate.
- Give it a second or two to settle; the first readings can run low.
Frequently asked questions
What is FPS and why does it matter?
FPS (frames per second) is the number of individual images your device draws on screen each second, and it's a direct measure of how smooth motion looks. Higher FPS means smoother animation and less delay between an action and what you see, which is why it matters most in fast-moving content like games and scrolling. Consistency matters too: a steady frame rate usually feels better than a higher one that fluctuates and causes visible stutter.
What's the difference between FPS and refresh rate?
FPS is how many frames your hardware produces, while refresh rate (measured in Hz) is how many times per second your monitor updates what it shows. The frame rate comes from your GPU and CPU, whereas the refresh rate is a fixed property of the display itself. They work together: smooth motion needs both a high enough frame rate and a display that can refresh often enough to show those frames.
Why is my FPS capped at my monitor's refresh rate?
A monitor can only display as many distinct frames per second as its refresh rate allows, so a 60Hz screen shows at most 60 new frames each second even if more are rendered. V-Sync and similar sync technologies also deliberately limit the render rate to match the refresh rate to prevent screen tearing. In a browser specifically, the timing method used to measure frames (requestAnimationFrame) is synced to the display refresh rate, so the reported FPS will not exceed your screen's Hz.
What limits the FPS I can get in a web browser?
Browsers tie their rendering to the display's refresh rate, so the FPS you measure is effectively capped at your monitor's Hz rather than how many frames a game engine could produce. Other factors can lower it further: disabled hardware acceleration (which can force a 60 FPS software-rendering cap), heavy JavaScript or CPU load, background-tab throttling, and multi-monitor setups that may lock the browser to the lowest-refresh display. Different browsers also handle graphics differently, so results can vary between them on the same machine.
What counts as a good FPS?
There's no single correct number; it depends on the content and your display. As a rough guide, 30 FPS is playable but can look choppy, 60 FPS is widely considered smooth for general use, and 120 or higher feels noticeably more fluid and responsive for fast-paced gaming. Keep in mind that any frame rate above your monitor's refresh rate won't show as extra visible frames, and a stable rate generally feels better than a higher but inconsistent one.
How accurate is a browser-based FPS test?
A browser FPS test is reliable for measuring the frame rate your browser is actually presenting and for spotting stutter or dropped frames, since it times each frame using the browser's animation and high-resolution timers. It is not a GPU or game benchmark, though: results are limited by your screen's refresh rate, the browser engine, and other activity on your system, and native tools are more precise for fine-grained frame-pacing measurements. For a quick check of how smoothly your browser is rendering on your current device, it gives a useful and accurate picture.