The endless runner did not appear fully formed. It was assembled over about three decades from auto-scrolling arcade games, side-scrolling platformers and a handful of Flash-era experiments, and then a touchscreen made it the dominant shape of mobile gaming almost overnight.
About the history in this article
The games and dates named below are well documented and widely reported. Where the genre's lineage is a matter of interpretation rather than record — which game "started" the endless runner, for example — we say so rather than presenting a tidy answer that does not exist.
Arcade roots: forced forward motion
The oldest ingredient is the auto-scroller. Arcade games of the late 1970s and early 1980s frequently moved the play field without asking, because a scrolling world was cheaper than a player-controlled camera and because it guaranteed a steady flow of play. Vertical and horizontal shooters made the technique routine.
The clearest early ancestor on foot is Moon Patrol (Irem, 1982), which pushed a vehicle continuously to the right over craters that had to be jumped and obstacles that had to be avoided, with parallax scrolling layers behind it. The following year BC's Quest for Tires (Sierra, 1983) put a character on a continuously moving path with jump and duck as the primary verbs — a control scheme a modern runner player would recognise instantly.
What these games lacked was endlessness. They had levels, finish points and designed layouts. The forced motion was there; the procedural, no-end-state structure was not.
The platformer detour
Through the mid-1980s and 1990s, the side-scrolling platformer became the dominant form and moved in the opposite direction: player-controlled cameras, hand-designed levels, exploration and backtracking. Forced-scroll sections survived as set pieces inside larger games — a chase sequence, a collapsing bridge — rather than as a genre of their own.
Those set pieces matter, though, because they established something important: players enjoy the intensity of forced motion in short bursts. The endless runner is, in a sense, the decision to make the chase sequence the whole game.
The browser and Flash era
The late 2000s browser scene is where the modern form actually crystallised, and it did so because of a change in distribution rather than technology. Flash games were free, instant and disposable, which favoured designs with very short sessions and no learning overhead. An endless runner is close to the ideal shape for that: one input, no tutorial, a run lasts a minute, and the score is the only progress.
Canabalt (Adam Saltsman, 2009) is the game most commonly credited with crystallising the modern template. It is one-button, monochrome, procedurally generated, has no end, and accelerates continuously. Its influence is widely acknowledged, and the specific combination it locked in — single input, procedural track, distance as score, speed as the difficulty curve — is still the default.
Robot Unicorn Attack (2010) demonstrated that the same structure could carry a completely different tone, and that a runner's identity could come from presentation rather than mechanics. That lesson is still visible in how varied modern runners look while playing near-identically.
The touchscreen moment
The endless runner and the smartphone fit together unusually well, and the reason is physical. A touchscreen has no buttons, which makes precise multi-input control awkward — but it is excellent at registering a tap and a swipe. A genre whose entire control set is "tap, or swipe in one of four directions" needed no adaptation at all.
The early 2010s produced the genre's commercial peak. Temple Run (Imangi Studios, 2011) established the behind-the-character three-lane view with swipe controls that became the template for countless successors. Jetpack Joyride (Halfbrick, 2011) built an entire game around one-button altitude control plus a mission and upgrade structure, showing that runners could sustain long-term progression. Subway Surfers (SYBO/Kiloo, 2012) refined the three-lane format and went on to become one of the most-downloaded mobile games ever made.
Two structural innovations came out of this period and outlasted it:
- Meta-progression. Persistent upgrades, characters and missions gave players a reason to return across sessions rather than only within one.
- Session shaping. Missions and objectives gave individual runs a purpose beyond distance, which addressed the genre's biggest weakness — that runs are otherwise identical.
The minimalist backlash
Flappy Bird (Dong Nguyen, 2013) is not strictly an endless runner, but its sudden and enormous popularity in early 2014 had a visible effect on the genre. It stripped everything away: one input, no progression, no upgrades, no theme, brutal difficulty and a score that reset instantly.
The takeaway a lot of designers drew was that the genre's appeal was never in the progression systems — it was in the loop itself, and the loop works at almost any level of complexity. The years afterwards produced a wave of deliberately minimal runners alongside the elaborate ones, and both are still healthy.
The HTML5 return
Flash's deprecation — announced in 2017 and completed at the end of 2020 — could have ended browser runners entirely. It did not, because by then HTML5 had the pieces that Flash had provided: the Canvas API for rendering, requestAnimationFrame for a proper loop, the Web Audio API for sound, LocalStorage for persistence, and touch events for mobile.
The modern browser runner is technically simpler than its Flash predecessor and reaches more devices. It needs no plugin, no install and no store approval, and the same build runs on a phone and a desktop. That is the tradition this site sits in: thirty runners in plain HTML, CSS and JavaScript with a Canvas element, no framework and no build step — the approach described in How Endless Runner Games Work.
What actually changed, and what did not
Across forty years, the genre's core has barely moved: forced forward motion, a tiny verb set, hazards that map cleanly onto those verbs, a score that measures how long you lasted. What changed was everything around it.
| Era | Distribution | Typical input | What gave a run meaning |
|---|---|---|---|
| Arcade (1982–85) | Coin-op cabinet | Joystick + button | Reaching the next level |
| Flash (2009–12) | Free web portals | One key | Distance, shared as a number |
| Mobile (2011–15) | App stores | Swipe and tap | Missions, upgrades, friends' scores |
| HTML5 (2015–) | Any browser, any device | Keyboard or touch | Personal bests, instant access |
The pattern is that each era's dominant runner design was shaped less by what was technically possible and more by how the game reached the player. Coin-op wanted levels. Web portals wanted no tutorial. App stores wanted retention. Browsers want instant loading and no account — which is why local high scores, rather than global leaderboards, suit the current era so well.
Key takeaways
- Forced forward motion dates to early 1980s arcade games; Moon Patrol and BC's Quest for Tires are the clearest ancestors.
- Canabalt (2009) is widely credited with crystallising the modern endless runner template during the Flash era.
- Touchscreens suited the genre perfectly because tap and swipe are exactly the inputs a runner needs.
- The mobile era added meta-progression and missions; the minimalist wave that followed showed the loop works without them.
- HTML5 restored browser runners after Flash's end, with wider device reach and no install.
Frequently asked questions
What was the first endless runner game?
There is no single agreed answer. Forced-scrolling arcade games like Moon Patrol (1982) and BC's Quest for Tires (1983) established the movement and verbs, but they had designed levels and endings. Canabalt (2009) is most often credited with combining forced motion, procedural generation and a true no-end structure into the modern form.
Why did endless runners become so popular on mobile?
Because the control set matched the hardware exactly. A runner needs a tap and four swipe directions, which is precisely what a touchscreen does well, so the genre needed no adaptation at all when smartphones arrived.
Did the end of Flash kill browser runners?
No. By the time Flash was discontinued at the end of 2020, HTML5 provided everything it had: Canvas for rendering, requestAnimationFrame for the loop, Web Audio for sound, LocalStorage for saving and touch events for mobile. Browser runners simply moved over.
What did mobile endless runners add to the genre?
Two things that persisted: meta-progression (upgrades and unlockables giving a reason to return between sessions) and mission structures (goals that give an individual run a purpose beyond distance).
Is Flappy Bird an endless runner?
Not strictly — the player controls altitude rather than a running character, and there is no forward movement to manage. But its structure is identical, and its 2014 success visibly pushed the genre toward minimalism.
Has the core of the genre changed much?
Remarkably little. Forced motion, a small verb set, hazards mapped to those verbs and a distance-based score have been constant. What changed each era was distribution — and distribution is what shaped the surrounding design each time.
Next steps
For the design side of what all these games have in common, read Endless Runner Game Mechanics Explained. To play something in the minimalist tradition, try One-Tap Runner; for the elaborate end of the spectrum, Endless Runner Ultimate.