A Short History of Browser Games

Browser games have a longer history than most players realise. The format predates HTML5; predates Flash; predates many of the platforms that we now think of as essential to browser gaming.

This article walks through the browser-games timeline as someone who has played them across most of it.

The pre-Flash era: 1996-2000

The first browser games were Java applets. Java applets were small Java programs that ran in the browser. They were the only way to do real interactive games in the browser until Flash arrived.

Games of this era were limited. The Java applet sandbox restricted what the games could do. Performance was poor by modern standards. But the games existed, and they established that browsers could host games at all.

The Flash era: 2000-2014

Adobe Flash dominated browser games from 2000 onward. The Flash player gave browsers vector graphics, audio support, and decent performance. The format that we now think of as 'browser games' was largely built on Flash.

Flash had its problems. Security vulnerabilities. Performance variability. Mobile incompatibility. But for fourteen years it was the standard for browser games, and tens of thousands of games shipped on it.

The Flash era produced games we still think of as classics. Stick figure animations. Indie experimental titles. Educational games. Simulation games. Adventure games. The diversity was remarkable.

The HTML5 transition: 2010-2020

HTML5 emerged as the open-standard alternative to Flash. By 2010 it was possible to build browser games in HTML5 with Canvas and Audio APIs. By 2015 the performance had caught up to Flash for most use cases. By 2020 Flash was deprecated and HTML5 was the only option.

The transition was disruptive. Many Flash games could not be ported. Developers had to rewrite for HTML5. Audiences moved to mobile apps during the gap.

The HTML5 era: 2014-present

Modern browser games are HTML5 plus various extensions. Web Audio for sound. WebGL for 3D. WebRTC for peer-to-peer multiplayer. Service Workers for offline support.

The capabilities have expanded continuously. Performance keeps improving. The format that was a Flash-replacement has become more capable than Flash ever was.

What I remember from across the eras

I started playing browser games in primary school on Java applet sites. The Flash era was when I learned what good browser games looked like. The transition to HTML5 was confusing for a few years. The current era feels the strongest the format has been.

Each era had its standout games. Stick figure animations from the Flash early years. Edugames from the late 1990s. Modern indie titles from the HTML5 era. Reading the catalogue on this site, you can see traces of each era in modern games.

Why this history matters

Browser games did not appear from nowhere. They have a thirty-year history. Modern browser games inherit from each era they passed through. Reading them with this history in mind makes them richer.

When you see a modern browser game that feels like a Flash-era throwback, the lineage is direct. When you see one that uses modern web technologies in interesting ways, the lineage is recent. The history is in the games.

What the future might bring

Predicting the future is hard, but some trends seem likely. WebAssembly will let browser games approach native performance. WebGPU will succeed WebGL with better 3D capabilities. The browser will keep adding APIs that close the gap with native.

Browser games are unlikely to fully replace native games. But they will continue to claim larger shares of the small-to-medium game-design space. The history of browser games is far from over.