From Flash to WebGL: How Browser Games Died and Came Back Better

Browser games have died at least twice. Both times the obituary was premature — and today, the games running quietly in your browser tab are more technically impressive than anything the Flash era ever shipped. This is the short history of how we got here, told through games you can play on this site right now.

The Flash empire (1999–2010)

For a decade, "browser game" meant one thing: Adobe Flash. Sites like Newgrounds, Kongregate, and Miniclip hosted tens of thousands of games built by teenagers, students, and tiny studios; hits like Line Rider — yes, the same Line Rider you can play here, since rebuilt for the modern web — spread through school computer labs like weather. Flash's superpower was a tiny plugin and a forgiving toolchain: anyone with a cracked copy of Flash MX and an idea could reach fifty million players. Its weakness was everything else — security holes, battery drain, and a plugin model the emerging mobile web wanted dead.

The death (2010–2017)

Steve Jobs' 2010 letter Thoughts on Flash was the beginning of the end: the iPhone would never run it. Chrome began sandboxing, then blocking, then removing the plugin. Ad networks that had funded Flash portals collapsed into the mobile app economy. By the mid-2010s the conventional wisdom hardened: real games had left the browser for app stores, and the browser game was a nostalgia artifact. For a while, the conventional wisdom was mostly right.

The quiet rebuild (2011–2018)

While the portals shrank, the web platform was being rebuilt underneath them. Three technologies mattered. The HTML5 <canvas> element gave JavaScript a fast 2D drawing surface — good enough that developers began porting classics; the Flappy Bird and Clumsy Bird clones of 2014 were early proof. WebGL exposed the GPU to the browser, and demos like HexGL (2012, a full anti-gravity racer) and PlayCanvas games like SWOOOP and the multiplayer TANX showed console-feeling 3D running in a tab. And WebAssembly (2017) let developers compile C++ and Rust to near-native browser speed — the technology behind the silky particle physics of Sandspiel.

The same years produced a parallel indie renaissance nobody planned: the incremental game. A Dark Room (2013), Candy Box 2 (2013), and Universal Paperclips (2017) needed no graphics at all — just text, numbers, and ideas — and became cultural events anyway. The browser turned out to be the perfect home for games that live in a background tab.

The competition-sized miracle

One more thread deserves mention: js13kGames, an annual competition to build a complete game in thirteen kilobytes of JavaScript — smaller than this article. Winners like Underrun (playable here) pack lighting, sound, and level design into a file smaller than a single photograph, and the developer behind it, Dominic Szablewski, went on to build browser-native gems like Xibalba and ZType. Constraint, as ever, breeds craft.

Why the browser won after all

App stores won the decade, but they charged for it: 30% fees, install friction, review queues, and a discovery lottery. The browser's counteroffer never changed — click a link, be playing in three seconds. For a certain kind of game, that's unbeatable. It's why Wordle became a global phenomenon as a plain web page, and why the games on this site need no downloads, no accounts, and no permissions. Flash died. The idea it proved — that everyone with a browser is a gamer — turned out to be immortal.