By Walter Jobs, Technology writer and editor · Published 10 October 2026
The usual answer to this is a ladder: 30 is playable, 60 is the standard, 144 is for competition, 240 is for professionals. That ladder is not wrong so much as it is answering a question nobody asked, because it describes averages, and the research on this subject keeps finding that averages are the wrong measure.
What follows is the evidence rather than the ladder. Three independent academic studies, one vendor study whose results undercut the vendor’s own marketing, and a standards body’s measurements of where human perception actually sits. Then a recommendation built from those rather than from habit.
Start with the finding that reframes the question
In 2023 a team from Worcester Polytechnic Institute, with two co-authors at Intel, ran a 33-person study on how frame rate variation affects players across three games. Their stated conclusion: “Analysis of the results shows average frame rate alone is a poor predictor of QoE, and frame rate variation has a significant impact on player QoE.”
QoE is quality of experience, the researchers’ term for whether people thought the game was good. And the measure that did predict it was not the average: “95% frame rate floor, the bottom 5% of frame rates the player experiences, appears to be an effective predictor of both QoE overall and for the individual games tested.”
The paper states the practical consequence itself: “high frame rates alone are not enough as variations in the frame display times can degrade QoE even as the average frame rate remains high.”
So the question “how many fps do I need” has an average-shaped answer and a floor-shaped answer, and only one of them tracks how a game feels. If you have to choose between a build that averages 100 with regular dips to 40, and one that sits between 70 and 80, take the second. That is not a preference, it is what the measurement says.
What the low end costs you, measured
The clearest work on the bottom of the range is from Worcester Polytechnic again, in 2007, with close to 100 participants across two experiments. Its finding sorts by what you are doing: “In general, the analysis shows that actions that require precise, rapid response, such as shooting, are greatly impacted by degradations in frame rates, while actions with lower precision and response requirements, such as moving, are more tolerant of low frame rates.”
That explains a common experience. A slow-paced game at 35 fps can be entirely fine while a shooter at 35 fps feels broken, and it is not that one engine is better written. The tasks have different tolerance.
For the 30 against 60 question specifically, a McMaster University study in 2014 measured target selection and reported: “Performance with 60 FPS frame rate was 14% higher than 30 FPS, but the difference between 45 and 60 FPS was not significant. Latency alone had lower impact than the corresponding frame rate difference. While both factors impact performance, frame rate had a larger effect than the latency it introduces.” The authors describe it as a pilot study, which is worth knowing before you treat 14% as a precise constant.
Two things come out of that. 30 to 60 is a real, measured performance difference, not a feeling. And the gap between 45 and 60 was already too small to detect, at the bottom of the range, where differences are largest.
The high end, tested by the company selling it
This is the part of the subject where almost everything written is downstream of marketing, so it is worth reading the one study that isolated the variable, especially because all eight of its authors were NVIDIA employees at the time.
Published at SIGGRAPH Asia in 2019, the paper’s title states the result: “Latency of 30 ms Benefits First Person Targeting Tasks More Than Refresh Rate Above 60 Hz.” The method mattered, because high refresh displays reduce latency as a side effect, and separating the two is the whole difficulty: “In this study, we isolate latency and refresh rate by artificially increasing latency when operating at high refresh rates.”
With eight skilled esports players and the latency held constant: “We show that reduced latency has a clear benefit in task completion time while increased refresh rate has relatively minor effects on performance when the inherent latency reduction present at high refresh rates is removed. Additionally, for certain tracking tasks, there is a small, but marginally significant effect from high refresh rates alone.” For the single-target tasks, a figure caption in the paper is blunter: “latency has a significant effect on task completion times while the effect of refresh rate is not statistically significant.”
Eight participants is a small sample and we are not going to pretend otherwise. But the direction is what matters, and it points somewhere specific: most of the competitive benefit people attribute to a high refresh rate is the latency reduction that comes with it, not the refresh rate itself. NVIDIA measured that and published it, which deserves credit, and then built a decade of marketing on the half of the sentence that sells monitors.
The practical reading: a 240 Hz panel is a latency purchase more than a smoothness purchase, and it is one of several latency purchases available to you, most of which are cheaper. Our article on frame rate and input lag covers the alternatives, including a mouse polling setting that NVIDIA’s own figures put at up to 3 ms, more than the entire frame-time gap between 144 and 240 fps.
Where human perception actually sits, from a standards body
Two claims circulate in every thread on this topic. That the eye cannot see past about 60 fps, and that research proved humans perceive 500 Hz. Both misuse the literature, and the reason is that there is no single threshold. Different artefacts have different thresholds.
The ITU’s report on the state of ultra high definition television sets out the taxonomy: “If we take ‘artefact’ to mean any perceptual difference between the real scene and the reproduced image, the major artefacts would be flicker, motion blur, and jerkiness (stroboscopic effect).”
Three separate faults, and the measured numbers for each are different:
- Flicker has a fusion frequency, and it moves with how much of your vision the screen fills. The report’s measurements: “The CFFs of the wide FOV were above 80 Hz and were higher than the CFFs of the narrow FOV (about 65 Hz).” So the familiar 60-ish figure is real, for a small screen, and too low for a large one. The report also states the principle: “The critical flicker frequency increases as FOV becomes wider.”
- Motion blur is a property of how long each frame is held on screen, with the report giving “1.2 pixels/frame and 6 pixels/frame” as the perceptible and acceptable limits.
- Jerkiness outlasts both by a wide margin: “It shows that the stroboscopic effect appears even at a frame frequency of 240 Hz for high-speed objects.”
That last line is the one to keep. Some motion artefacts are still visible at 240 Hz, long after flicker has fused. “The eye has a frame rate” is the error; the artefacts have thresholds, and they do not agree with each other.
As for the 500 Hz study, it exists, it was published in Scientific Reports in 2015, and it is about perceiving flicker artefacts produced by high-frequency spatial edges in display hardware. It is not about game frame rates or motion smoothness, and citing it as “humans can see 500 fps” will not survive anyone reading the abstract.
One more figure gets misused here. VESA’s display certification requires an AdaptiveSync Display to support a maximum refresh “greater than or equal to 144 Hz”. That is a logo requirement for a certification program. VESA publishes no perceptual threshold at all, and the 144 figure says nothing about human vision.
What the console makers target, which is a real-world answer
Console platform holders have to commit to numbers in a way PC advice does not, and Nintendo’s documentation for its current hardware is unusually explicit, including the trade-off: “A maximum frame rate of 120 fps enables even smoother gameplay in supported games”, alongside “4K resolution and HDR are available in supported games, and require a compatible display. Frame rate is fixed to a maximum of 60 fps for 4K output.”
Resolution or frame rate, stated as a hardware limit by the manufacturer. Microsoft publishes its own refresh options for its current consoles, listing output “at 24 Hz, 50 Hz, 60 Hz, or 120 Hz” and noting that the advanced modes “require HDMI 2.1 connection”. Sony documents variable refresh support for its console in terms of what it removes rather than a frame rate, describing it as “minimizing or eliminating visual artifacts, such as frame pacing issues and screen tearing”.
No platform holder publishes a per-game frame rate table, because developers choose those per title. If you see one presented as a platform specification, it was assembled by someone else.
So: how many do you need
Expressed as floors rather than averages, because that is what the research supports.
| What you are playing | Floor to aim for | Why that figure |
|---|---|---|
| Strategy, management, turn-based, point and click | 30 fps, flat | Low precision and response demands tolerate low frame rates. Flatness matters more than height here |
| Single-player action, adventure, RPG | 50 to 60 fps | The 30 to 60 difference is the largest measured step in the literature. Above 60 the measured gains get small fast |
| Multiplayer shooters, casually | 60 fps, with the dips above 50 | Aiming is the task most degraded by low frame rates. The floor is doing the work, not the average |
| Competitive shooters, seriously | 120 fps plus, paired with a latency feature | Worth it for the latency, which is where the measured benefit sits. The refresh rate alone was not statistically significant in NVIDIA’s own test |
| Anything on a variable refresh display | Stay inside the panel’s VRR window | Below the window the sync behaviour changes and the smoothness goes with it. See the VRR article |
Two practical notes on using that table. First, work out what your own hardware actually delivers before deciding what you need, with our fps calculator for parts you do not own yet and an on-screen counter for the machine you have. Second, measure your floor rather than your average, which means looking at 1% lows and knowing which of the two competing definitions of that number you are reading.
Common questions
Is 60 fps still enough in 2026?
For most games played for their own sake, yes, and the measured step from 30 to 60 is far larger than the step from 60 to 120. The case for going higher is strongest in competitive shooters and rests mostly on latency, which has other, cheaper levers.
Does a 144 Hz monitor help if I only get 80 fps?
Yes, for a reason unrelated to the panel’s top speed: a variable refresh display will sync to 80 and remove tearing and pacing stutter without the delay a fixed-refresh VSync setup adds. You are buying the variable range rather than the 144.
Why does my 120 fps feel worse than a friend’s 90?
Most likely your floor. A 120 average with frequent drops to 45 reads as worse than a steady 90, which is exactly what the 2023 study found when it compared average frame rate against the bottom 5%. Also check whether a latency feature is enabled in your game, since that changes feel without changing the frame counter.
Is 30 fps unplayable?
No, and the research is specific about when it is a problem. Precise, rapid actions suffer badly. Movement and low-precision actions do not. A strategy game at a locked 30 is a reasonable experience; a shooter at a wobbling 30 is not.
What about frame generation, does 120 generated frames count?
For smoothness, substantially. For responsiveness, no, because the inserted frames carry no new input. Steam’s own performance monitor treats them as separate quantities, reporting generated and real frame rates apart from each other, which is the correct way to read them.