What HTML5 Replaced - A Short History of Browser Games After Flash

For roughly a decade and a half, “browser game” and “Flash game” meant the same thing. If you played something in a tab between about 2000 and 2015, it was almost certainly a Flash file, running inside a plugin that most people had installed without ever choosing to.

Adobe ended support for Flash Player at the end of 2020, and the browsers removed it. That was announced years in advance, so the shift was gradual rather than sudden, but the end point was absolute: a technology that had carried an entire category of games simply stopped executing.

Why Flash mattered in the first place

Flash was not designed for games. It was a vector animation tool, and the game engine grew out of it more or less by accident, which explains a lot about the era.

What it gave developers was a single runtime that behaved the same everywhere. Write once, and it looked and ran identically on any machine with the plugin, at a time when browsers agreed on almost nothing. It came with a drawing tool built in, a timeline, and a scripting language that a person could learn in a weekend. That combination meant the people making browser games were not only programmers. Animators made games. Teenagers made games. The barrier was low enough that the medium filled up with things nobody would have commissioned.

The other half of the story is distribution. Portals paid for sponsorship, or split advertising revenue, and a single popular game could support the person who made it. That economy is what produced the flood.

What actually replaced it

There is no single successor, which is the important part. Flash was one thing; what replaced it is a stack of separate browser features that had to mature independently.

The canvas element gave JavaScript a rectangle it could draw into directly, which covers most two-dimensional games. WebGL exposed the graphics hardware, which is why a browser game can now be genuinely three-dimensional — the reason something like Space.io can run a 3D dogfight in a tab at all. Web Audio replaced the sound handling, which sounds like a footnote until you remember that a game with broken audio feels broken. And JavaScript itself got enormously faster during the same period, to the point where the language stopped being the bottleneck. WebAssembly later made it practical to compile game engines written in other languages down to something the browser runs.

Engines followed the features. Rather than a single authoring tool, developers now pick from several that export to the web, and the games on this shelf were built with a mix of them. That fragmentation is the main practical difference from the Flash era: there is no longer one way to make a browser game, and no longer one runtime that guarantees identical behaviour.

What got better

Games run without a plugin, which removed a whole category of security problems and a whole category of “please install” pages. They run on phones, which Flash never really did — that incompatibility is a large part of why the platform ended.

Performance ceilings went up. The 3D games on this site, from Prism Match 3D to Car Parking Master 3D, are doing things the plugin era mostly could not. And because the games are ordinary web pages now, they benefit from everything else the web gained — better fonts, better input handling, sensible fullscreen behaviour.

What got worse

Two things, and both are worth being honest about.

The first is preservation. A Flash game was a single file, and when the runtime went away the file stopped running. A great deal of work has gone into emulating the old runtime so those files can execute again, and community archives have collected an enormous number of them, but the default outcome for anything not deliberately rescued was disappearance. That is a real loss, and it happened to a body of work that was mostly made by individuals with no publisher to look after their back catalogue.

The second is a shift in what gets made. Flash’s economics rewarded odd, specific, single-idea games because a sponsorship deal did not require retention. Modern browser game distribution leans toward titles designed for repeat sessions and advertising breaks, which favours certain shapes — endless runners, merge loops, level ladders — and disfavours the twenty-minute experiment. You can still find the experiments. There are just fewer of them per thousand titles.

Where that leaves the browser game now

Better than the pessimistic reading suggests. The technical constraint that made Flash necessary is gone, and what is left is a platform where a game is a link. No install, no store, no account, no platform holder taking a cut or deciding what is allowed. That was always the actual appeal, and it survived the runtime that first delivered it.

The genres carried over more than you might expect. A tile-matching puzzle like Jewel Link, an artillery duel like Fury Tanks, a physics hill climber like Hill Racing — these are all direct descendants of things that ran in the plugin, rebuilt on different plumbing. The medium changed underneath; the games mostly did not.

If you want to see what the current version looks like, the full catalogue is the short answer, and our note on how we choose what to publish explains why it is deliberately small.