FPS — frames per second — is the number of unique images your graphics card produces every second. Each image is called a frame. The more frames per second, the smoother the motion appears on screen and the more responsive your inputs feel. FPS is one of the most important numbers in PC gaming, and one of the most misunderstood — so let's clear it up properly.
To understand FPS, you need to understand what a frame actually is. When you play a game, your graphics card is constantly rendering the game world: loading geometry, applying textures, calculating lighting, simulating physics, and finally producing a 2D image that can be sent to your monitor. That 2D image is one frame. The graphics card produces these frames as fast as it can — sometimes 60 per second, sometimes 200 per second, sometimes 30 per second if the GPU is overloaded. The number it manages to produce in one second is your FPS.
Where FPS comes from: the rendering pipeline
A frame goes through several stages before it reaches your screen. Each stage takes time, and the total time per frame is what limits your FPS:
- Game logic — The game updates the world: physics, AI, input processing. Usually 1-5 ms.
- CPU draw calls — The CPU tells the GPU what to render. Usually 2-10 ms depending on scene complexity.
- GPU rendering — The GPU processes geometry, applies shaders, computes lighting. Usually 5-30 ms depending on settings and resolution.
- Post-processing — Anti-aliasing, bloom, depth of field, motion blur. Usually 1-10 ms.
- Display output — The frame is sent to the monitor over DisplayPort or HDMI. Usually 1-5 ms depending on cable and refresh rate.
Add all these together and you get the frame time — the number of milliseconds per frame. Divide 1000 by the frame time and you get FPS. A 16.6 ms frame time gives 60 FPS. A 6.9 ms frame time gives 144 FPS. A 4.2 ms frame time gives 240 FPS.
What each FPS tier actually feels like
Gamers argue endlessly about FPS tiers, but most of the disagreement comes from imprecise definitions. Here is what each tier actually feels like, calibrated against years of monitor and gaming benchmarks:
| FPS tier | Frame time | What it feels like |
|---|---|---|
| 20-30 FPS | 33-50 ms | Cinematic for movies, choppy for games. Camera pans judder. Inputs feel laggy. |
| 30-45 FPS | 22-33 ms | Playable for slow single-player games. Visible judder in fast motion. |
| 45-60 FPS | 16-22 ms | Smooth for most games. Minor judder in fast camera pans. |
| 60-90 FPS | 11-16 ms | The baseline for modern PC gaming. Smooth and responsive for almost everything. |
| 90-120 FPS | 8-11 ms | Noticeably smoother than 60. Aim tracking improves. Cursor feels glassy. |
| 120-144 FPS | 7-8 ms | The competitive sweet spot. Targets stay readable while flicking. |
| 144-200 FPS | 5-7 ms | Marginal improvement over 144 FPS. Most players cannot perceive the difference. |
| 200-240 FPS | 4-5 ms | Top-tier esports territory. Pros benefit; most players do not. |
| 240+ FPS | <4 ms | Diminishing returns. Useful only for the top 1% of competitive players. |
FPS vs frame time — the unit that actually matters
FPS is a misleading unit because it is non-linear. The difference between 30 FPS and 60 FPS is 16.6 ms per frame — a huge improvement. The difference between 144 FPS and 240 FPS is just 2.6 ms per frame — barely noticeable. Going from 240 FPS to 360 FPS is just 1.1 ms — invisible to most humans.
This is why reviewers often talk about frame time (in milliseconds) rather than FPS. Frame time is linear: 10 ms is twice as fast as 20 ms, full stop. When you are optimising a system, target a frame time, not an FPS number. A good target for competitive gaming is under 7 ms (144+ FPS). For casual gaming, under 16 ms (60+ FPS) is fine.
What limits your FPS
FPS is limited by the slowest part of your system. The most common bottlenecks, in order of frequency:
- GPU bottleneck — Your graphics card cannot render frames fast enough. Most common at high resolutions (1440p, 4K) or with high graphics settings. Fix: lower resolution or settings, or upgrade GPU.
- CPU bottleneck — Your CPU cannot feed draw calls to the GPU fast enough. Most common at low resolutions (1080p low) or in CPU-heavy games (RTS, MMO, simulation). Fix: upgrade CPU, or use frame generation tech like DLSS 3.
- RAM bottleneck — Not enough RAM causes swapping, which causes stuttering. Fix: 16 GB is the minimum for modern gaming; 32 GB is comfortable.
- Storage bottleneck — Slow storage causes texture pop-in and loading stutters. Fix: install games on an NVMe SSD, not an HDD.
- Driver/OS bottleneck — Outdated drivers, background processes, or Windows power saving can throttle FPS. Fix: update drivers, close background apps, plug in laptops.
- Refresh rate cap — If VSync is on, FPS is capped at the monitor's refresh rate. Fix: disable VSync, use G-Sync/FreeSync, or accept the cap.
How to measure FPS accurately
There are three ways to measure FPS, each with different trade-offs:
| Method | Accuracy | Where to use |
|---|---|---|
| Browser FPS test (this site) | Good — measures rAF callback interval | Browser games, general system health, monitor sanity check |
| In-game FPS counter | Excellent — directly from the game engine | Real games, with frame-time graphs in modern titles |
| External overlay (Steam, NVIDIA, RivaTuner) | Excellent — captures real frame presentation | Cross-game benchmarking, frame-time analysis |
| Hardware capture (NVIDIA Frame View, OCAT) | Perfect — frame-level presentation timing | Professional reviews, scientific benchmarking |
For most users, the browser FPS test on this page is enough — it tells you whether your system can hit your monitor's refresh rate, and it gives you a histogram of frame time stability over 30 seconds. For game-specific optimisation, use the in-game FPS counter or an overlay like Steam's built-in FPS counter.
The 30 FPS myth — and why it persists
You will sometimes hear that "the human eye cannot see more than 30 FPS". This is completely false, and the persistence of the myth is one of the more frustrating parts of gaming discourse. The human eye does not have a frame rate in the way a camera does; it processes information continuously. What we perceive as smoothness depends on the duration of each stimulus, the brightness, the contrast, and the motion speed.
Studies have shown that pilots can identify aircraft flashed at them for 1/220 second — equivalent to perceiving 220 FPS. Gamers consistently distinguish 60 Hz from 120 Hz from 240 Hz monitors in blind tests. The differences become smaller as FPS rises, but they do not disappear. The "30 FPS" myth probably comes from the cinematic tradition of 24 FPS film, where motion blur in each frame hides the choppiness that would otherwise be visible.