Quick take: Speedrunning — completing video games as fast as possible — looks like a party trick to outsiders but is one of the most demanding forms of game mastery that exists. It requires deep technical knowledge of game code, precise physical execution under pressure, and the kind of sustained analytical effort normally associated with scientific research.
When someone watches a speedrun for the first time, the usual reaction is confusion. Why would anyone want to finish a game as fast as possible? Isn’t the point to experience the game? And why are they doing that — jumping into a wall in a specific way, clipping through a floor, taking damage from an enemy on purpose? The behavior looks deliberately counterproductive.
What’s actually happening is a complete reframing of the game as an object of study rather than a story to experience. A speedrunner isn’t playing the game the way a developer intended — they’re treating the game code as a physical system to understand and exploit, with rules that emerge from implementation details rather than design intent. The result can look bizarre, but it represents one of the deepest possible forms of engagement with a game.
What Speedrunners Actually Know
Top speedrunners in any given game possess technical knowledge about it that no one else on earth has. They know which memory addresses the game reads for movement calculations. They know which graphical glitches indicate a memory corruption that can be exploited for faster progression. They know the exact frame timing of every input that affects their run. They know how the random number generator works and which seeds produce favorable outcomes.
This knowledge isn’t absorbed passively — it’s actively researched. Communities spend hundreds of person-hours reverse-engineering game code, testing hypotheses about glitch behavior, and building models of game mechanics that are often more precise than any documentation the developer ever produced. Speedrunning communities are, in a very real sense, doing applied computer science. The “laboratory” is just a video game.
Many speedrunning discoveries have revealed genuine bugs in games that were never fixed in official patches. The Ocarina of Time speedrunning community discovered arbitrary code execution vulnerabilities that allow runners to essentially program the game from within itself, running custom code through in-game actions. This required knowledge of the N64 memory architecture that Nintendo’s own documentation never made public.
The Physical Execution Demand
Beyond technical knowledge, speedrunning requires an extraordinary level of precise physical execution. A world record run in a well-developed category might require hundreds of specific inputs executed within tight frame windows — a frame being 1/60th of a second. Missing a single input can cost seconds or cause a run to fail entirely, forcing a reset and starting over from scratch.
Top runners practice specific sections of their runs thousands of times to build the muscle memory required to execute consistently under pressure. The pressure matters: world record attempts are often streamed live to audiences of thousands, adding performance anxiety to an already demanding cognitive and physical task. Maintaining technique under these conditions requires the same kind of psychological preparation that competitive athletes use.
Games Done Quick, the charity speedrunning marathon held twice yearly, has raised over $50 million for various charities since 2010. The events attract audiences in the hundreds of thousands who watch live speedruns of games across every genre and era. The combination of extreme technical skill, live performance pressure, and comedic commentary has made it one of gaming’s most beloved community institutions.
Categories and the Taxonomy of Mastery
Speedrunning has developed a sophisticated taxonomy of run categories that reflect different philosophies about what constitutes mastery. “Any%” runs reach the end credits as fast as possible, with no restrictions on glitches or skips — the result is often barely recognizable as the original game. “100%” runs require completing every significant collectible or achievement. “Glitchless” runs prohibit unintended mechanics, measuring skill at the game as designed. “Low%” runs complete the game with as few items or upgrades as possible.
Each category is essentially a different question about the game, with different answers. Any% asks: what is the minimum execution required to trigger the end sequence? 100% asks: what is the most efficient path through all content? Glitchless asks: how well can a player master the game’s intended mechanics? The same player can hold records in multiple categories, but each requires different knowledge and skills.
A speedrunner doesn’t just play a game — they reverse-engineer it. The world record holder in a speedrun category often knows the game’s code better than most of the people who wrote it, because they had reason to study specific behaviors in exhaustive detail that no developer had time for during production.
Community and the Collaborative Nature of Records
Speedrunning records are rarely individual achievements. They emerge from community research. Individual runners bring different strengths — technical analysis, execution skill, creative route-finding — and discoveries propagate through communities rapidly. A glitch found by one runner becomes available to all. A routing improvement discovered in community discussion gets tested by multiple runners. World records are often built on dozens of individual contributors’ work.
This collaborative structure means that speedrunning records represent a collective intelligence about a game rather than one person’s achievement. The record holder is the person who executed the current optimal route best under current conditions — but the route itself, the glitches that make it possible, and the techniques for executing it reliably were assembled by a community over years or decades of research.
The best way to appreciate speedrunning is to watch a highly developed category in a game you know well — then watch someone play the same game normally afterward. The contrast between the speedrun’s precise, technical execution and normal play makes the depth of knowledge visible in a way that’s impossible to fully appreciate without the comparison.
Why Speedrunning Matters Beyond Gaming
Speedrunning is interesting beyond gaming because it represents a model of expertise development that is unusually transparent and documentable. The knowledge that speedrunners accumulate is shared publicly, the practice methods are explicitly discussed, and improvement is measurable in objective units of time. This makes speedrunning communities unusually good subjects for studying how human expertise develops in complex domains.
Researchers in learning science and human performance have used speedrunning communities as case studies for understanding deliberate practice, knowledge sharing, and creative problem-solving under constraint. The findings align with broader research: expertise in complex domains requires deep conceptual understanding, deliberate practice of specific difficult components, and community knowledge structures that allow individuals to build on collective discoveries.
- Speedrunners treat games as technical systems to research and exploit, not stories to experience — a fundamentally different relationship to the game.
- Top runners possess technical knowledge about games — memory addresses, glitch mechanics, frame timing — that rivals or exceeds the original developers’.
- Physical execution demands are comparable to competitive athletics: precise inputs at 1/60th-second windows, practiced thousands of times under performance pressure.
- Run categories (any%, 100%, glitchless) ask different questions about the game and require different knowledge and skills.
- Records are collective achievements built on community research — the record holder executes the current optimal route, assembled by many contributors.
- Speedrunning communities have discovered actual security vulnerabilities and code execution exploits that had real-world implications.
Frequently Asked Questions
Is speedrunning cheating?
No — within defined category rules, everything is legitimate. Categories explicitly define what is and isn’t allowed. Using an emulator with memory editing would be cheating; using a glitch that the game’s own code allows when certain inputs are given is not. The distinction between intended and unintended mechanics is the foundation of speedrunning category design.
How do speedrunners get started?
Usually by watching runs of games they already know well, then finding the community hub (usually speedrun.com) for that game. Most games have beginner guides and tutorial videos. Starting in a beginner-friendly category — often one without many complex glitches — lets new runners develop basic skills before attempting more technical routes.
What games have the most active speedrunning communities?
Super Mario series games, The Legend of Zelda games, classic platformers like Mega Man, RPGs like Final Fantasy, and modern indie games like Celeste have extremely active communities. Celeste’s speedrunning scene is particularly notable for welcoming newcomers and having well-documented technique guides.
How long does it take to get a competitive time in a speedrun category?
Highly variable. Some shorter games with simple categories can be run competitively within a few weeks of practice. Highly optimized long-form categories can take months or years to develop the consistency needed for competitive times. The initial learning curve is usually steep but becomes more gradual as technique solidifies.
speedrunning explained beginners, any% versus 100% speedrun, Games Done Quick GDQ, how speedrunners find glitches, Ocarina of Time speedrun, speedrunning records community, arbitrary code execution games, speedrun category rules