What Is FPS? A Practical Guide to Frames per Second

Frames per second (FPS) is the number of visual frames a computer produces in one second. It is useful because motion is made from a sequence of frames, but the number is only meaningful when you know what produced it and what the display can show. A browser animation, a game engine, and a video file can all report FPS while measuring different parts of the experience.

What does FPS actually measure?

FPS is a rate, not a quality score. A test that reports 60 FPS means that the measured animation produced about 60 callbacks or frames per second during the sample. It does not prove that a game will render at 60 FPS, that every frame arrived at exactly the right time, or that the display is configured for 60Hz.

Common reference points are useful for orientation:

• 24 FPS is common in cinema and can look natural when motion blur and camera movement are controlled.
• 30 FPS is common in video and console performance modes. It can be playable, but camera movement is less fluid than at 60 FPS.
• 60 FPS is a practical baseline for general desktop animation and many games.
• 120 FPS and above can improve motion clarity and input responsiveness when the display and application both support it.

These are not universal ratings. A stable 60 FPS can feel better than an unstable 90 FPS if the faster result contains repeated long frames.

FPS, Hz, and frame time are different

FPS describes the rate at which an application or browser produces frames. Hertz (Hz) describes how often a display can refresh. A 144Hz monitor can refresh up to 144 times per second, but a browser that is producing 60 FPS cannot provide 144 unique frames to it. Conversely, rendering above the display refresh rate does not make a 60Hz panel show 144 refreshes.

Frame time is the duration of one frame in milliseconds. The basic relationship is:

frame time (ms) = 1000 / FPS

That means 60 FPS is about 16.67ms per frame, 120 FPS is about 8.33ms, and 144 FPS is about 6.94ms. Frame-time consistency matters because a single 100ms frame can be visible as a stutter even when the average FPS looks high.

How a browser FPS test works

The FPS Checker test uses the browser's requestAnimationFrame API. The browser schedules a callback before a repaint, and the tool counts callbacks over time while recording the interval between them. This is appropriate for checking the current browser rendering path: it includes the active display cadence, browser scheduling, hardware acceleration, system load, and the page's animation workload.

The API is intentionally synchronized with the browser's rendering loop. Browsers also pause or throttle animation callbacks in background tabs, so a test must stay visible. The MDN reference for requestAnimationFrame documents that behavior and explains why animation code should use the supplied timestamp.

Run a repeatable check

Use the same procedure whenever you compare a device, browser, or setting:

1. Connect the laptop to power or use the same power mode for every run.
2. Set the operating system display refresh rate before starting the test.
3. Close downloads, video playback, heavy tabs, and applications that are actively using the CPU or GPU.
4. Keep the test tab in the foreground and let it warm up for several seconds.
5. Record the average FPS, minimum FPS, worst frame time, and visible spikes. Repeat at least three times instead of keeping only the highest number.
6. Change one variable, such as hardware acceleration or browser, and repeat the same procedure.

This approach makes the result a useful comparison rather than a one-off claim. If a result changes substantially between runs, report the range and the conditions instead of presenting the best run as a guaranteed capability.

What the result cannot tell you

A browser test is not a substitute for an in-game benchmark. Game engines add their own simulation, asset streaming, shader compilation, resolution scaling, and frame-pacing behavior. A device can score well in a light browser animation while struggling in a demanding game, or score lower because an extension or power mode is affecting the browser.

The test also does not measure end-to-end input latency, panel response time, color accuracy, or GPU performance in isolation. Use an in-game overlay for game FPS, a frame-time capture tool for a specific title, and a calibrated measurement device for display characteristics.

Interpreting common results

• Exactly 60 FPS on a high-refresh monitor: verify the OS setting, cable or adapter, browser hardware acceleration, and whether the browser is throttling the page.
• High average FPS with visible judder: inspect the frame-time graph. Repeated long frames usually point to background work, thermal limits, driver issues, or power saving.
• Different browsers produce different numbers: that is expected. Compare them with the same window size, extensions, power mode, and system workload.
• Mobile results fall after a few minutes: heat and battery management can reduce sustained performance. Note the device temperature and test duration.

For a live reading, run the FPS test. Treat it as a transparent snapshot of the current browser session, not as a promise about every application or game.

Further reading

• MDN: requestAnimationFrame()
• MDN: High precision timing
• W3C High Resolution Time specification