Human Eye Can Only See At 60 Fps
Also known as: "30 FPS Is All You Need · " "The Human Eye Can't See Past 30 FPS · " "Eyes Can Only See 30 FPS"
"Human Eye Can Only See at 60 FPS" is an internet myth and gaming community meme based on the false claim that the human eye cannot perceive more than a certain number of frames per second, usually 30 or 60. The debate traces back to forum discussions in the late 1990s and early 2000s, with the myth likely born from the technical limitations of film and television rather than any actual biological constraint. The claim became a running joke in the PC gaming community, where it's often mockingly attributed to console gamers trying to justify lower frame rates.
Overview
The "Human Eye Can Only See at 60 FPS" meme centers on a persistent misconception that the human visual system has a hard cap on the number of frames per second it can process. The number in question shifts depending on who's making the claim. Some say 24 FPS (matching cinema standards), others say 30 (matching TV), and the most common version settles on 60. None of these are accurate. The human eye doesn't process vision in discrete frames at all, instead receiving visual information as a continuous stream1.
The meme works on two levels. First, it's a genuinely debunked myth that keeps resurfacing in online discussions. Second, it's a punchline in the PC gaming community, used to mock console gamers who supposedly cite this "fact" to defend hardware that can't push high frame rates. PC enthusiasts treat belief in the myth as a litmus test for gaming ignorance3.
Online arguments about the limits of human vision and frame rates go back to the earliest days of gaming forums. The oldest known thread on the topic appeared on Hardware Central on April 25, 1999, where users debated whether anything above 30 FPS was visually meaningful3. Some posters in that thread claimed the eye interprets anything above 30 FPS as fluid motion, while others suggested younger people might perceive up to 55 or 60 FPS.
The misconception likely grew out of real technical standards. Film has run at 24 FPS for nearly a century, and NTSC television operates at roughly 30 FPS (60Hz refresh rate divided by interlaced scanning)1. Because movies and TV looked smooth at these frame rates, people assumed these numbers represented biological limits rather than engineering choices. The critical difference, as technical writers pointed out, is that film and TV use motion blur. Each frame in a movie contains blurred movement, which the brain fills in as smooth motion. Computer games render each frame with sharp, distinct edges, so the same frame rate looks noticeably choppier2.
Origin & Background
How It Spread
How to Use This Meme
This meme typically appears in one of two contexts:
As a sarcastic statement: Someone posts "the human eye can only see 30 FPS" in a gaming thread, usually in response to console players defending a game's performance. The statement is almost always ironic, used to mock the claim rather than support it.
As an image macro punchline: Popular meme templates get adapted to include the FPS myth. The setup usually involves searching for something unlikely (intelligence, good takes, reasonable opinions) and the punchline involves someone who unironically believes the eye can't see past 60 FPS.
Cultural Impact
Fun Facts
The "220 FPS" figure attributed to the US Air Force comes from a study where pilots could correctly identify an aircraft image flashed on screen for just 1/220th of a second.
Film runs at 24 FPS and looks smooth because each frame contains natural motion blur from the camera shutter. Game frames are razor-sharp, which is why 24 FPS in a game looks terrible.
You can actually see your computer monitor's refresh lines being drawn if you look at it through your peripheral vision. Try it.
The FPS Compare utility that Overclock.net users shared to debunk the myth was only 11KB in size.
Microsoft's DirectX introduced variable frame rate handling specifically because game FPS fluctuates, unlike the locked rates of film and TV.
Frequently Asked Questions
References (3)
- 1
- 2
- 3