FPS Counter: See Your Real Frame Rate

What this FPS counter actually measures

This counter measures how many frames your browser can render per second on the device you're using right now. It is not a game overlay and it does not read your GPU driver: it reports the frame rate the page itself is achieving, plus frame time and your 1% low.

That distinction matters. A browser FPS counter answers "how much can this device, this browser and this tab sustain" — which is a good proxy for general performance and a fast way to catch a machine that is throttling, running on integrated graphics, or stuck in a power-saving mode. It does not answer "what FPS am I getting in this game" — for that, see the section further down.

How to read your numbers: average FPS, 1% low, frame time

Average FPS is the headline: how many frames per second you get on average. Easy to read, easy to be fooled by.

1% low is the average of your slowest 1% of frames. This is what stutter feels like. A system averaging 120 FPS with a 1% low of 40 will feel worse than one averaging 90 with a 1% low of 75.

Frame time is how long one frame took, in milliseconds. It is the raw signal behind the other two: at 60 FPS each frame has 16.7 ms, at 120 FPS 8.3 ms, at 144 FPS 6.9 ms. Spikes in frame time are what you see as a hitch.

Is your FPS good? What each frame rate tier means

One rule that saves a lot of confusion: your FPS can never look better than your monitor's refresh rate. Getting 200 FPS on a 60 Hz screen still shows you 60 pictures a second. If you suspect your display isn't running at its rated speed, run the refresh rate test — it takes ten seconds and it's a different problem from a low frame rate.

Why your browser FPS is lower than your game FPS

Four usual suspects, in the order worth checking: Hardware acceleration is off in your browser settings, so everything is rendering on the CPU. Power saving is on — laptops and phones drop the frame rate the moment they think you're idle. The tab is in the background or half-covered, and browsers deliberately throttle background tabs. Something else is eating the GPU — a video call, a stream, twenty tabs. Try the counter again with a single tab open, charger plugged in, and you'll usually get a very different number.

How to see FPS inside a game (PC, Xbox, PS5, phone)

If what you actually want is the frame rate inside a game, the browser can't read that — the game renders in its own process. Use the overlay your platform already ships:

Steam — Settings → In-Game → In-game FPS counter, pick a corner.

NVIDIA — GeForce Experience overlay (Alt+R) or the NVIDIA app's performance overlay.

AMD — Adrenalin → Performance → Metrics overlay (Ctrl+Shift+O).

Windows, any game — Xbox Game Bar (Win+G) → Performance widget → FPS.

PS5 / Xbox Series X|S — no built-in counter; most games put one in their display settings, and 120 Hz modes have to be enabled per game.

Android / iOS — FPS overlays need developer tools (GameBench, PerfDog) or the game's own counter. A phone browser can't read another app's frame rate.

What this page is genuinely good for on a phone: telling you how fast the device renders in the browser, which is a decent read on whether it's thermally throttling.

FPS counter vs refresh rate test

Two different questions, two different tools. The FPS counter tells you how many frames your device can produce. The refresh rate test tells you how many times per second your monitor actually updates — the ceiling your FPS can never exceed. If your FPS is capped at exactly 60 no matter what you do, the display is the more likely culprit; run the refresh rate test first. New to all this? Start from the FPS test on the homepage, which pushes your device until it drops frames and shows you the ceiling.

FAQ