What Happened to Flash Games

On 31 December 2020, Adobe stopped supporting Flash Player. On 12 January 2021, it began actively blocking Flash content from running. Browsers had already removed the plugin. In the space of a few weeks, something like two decades of browser games stopped being playable in the way they had always been played.

If you have a memory of a specific game from a school computer room and cannot find it now, this is why. It is worth understanding properly, because the reasons Flash died are the same reasons the games that replaced it work the way they do.

What Flash actually was

Flash was a plugin. That word is doing a lot of work.

A browser on its own could not run a Flash game. You installed a separate piece of software from Adobe, and the browser handed control of a rectangle on the page over to it. Inside that rectangle, Adobe's runtime — not the browser — decided what was drawn, what code ran, and what the machine was allowed to do.

That arrangement is what made Flash extraordinary in 2005. The web at the time could barely animate a menu. Flash gave a single developer vector animation, sound, timeline tools, and a real programming language, all with output that ran identically on every computer. An enormous amount of internet culture came out of that gap between what browsers could do and what Flash could.

It is also what killed it.

Why it ended

Three things, in roughly this order of importance.

Security. A plugin that runs code outside the browser's control is a permanent hole in the browser's security model. Flash was, for years, one of the most reliably exploited pieces of software on consumer computers. Every browser vendor wanted it gone, and their reasons were good ones.

Mobile. Flash never worked on iOS. Apple refused it in 2007 and never changed position, and by 2012 Adobe had abandoned Flash for Android too. From that point Flash was a desktop-only technology in a world moving to phones — a fatal position regardless of anything else.

The web caught up. HTML5 gave browsers <canvas> for drawing, WebGL for hardware-accelerated 3D, the Web Audio API for sound, and a JavaScript engine fast enough to run a game loop. Everything Flash was needed for, browsers could now do natively — without a plugin, without an installer, and without Adobe in the middle.

Once that was true, Flash was a security liability providing no capability the browser lacked.

What survived, and how

More than you would expect.

Ruffle is the important one. It is an open-source Flash Player reimplementation written in Rust and compiled to WebAssembly, which means it runs inside the browser's normal security sandbox rather than beside it. It is genuinely good at older ActionScript 1 and 2 content, which covers a large share of the classic era. It is still incomplete for ActionScript 3, so many later games remain broken or partial.

The Internet Archive hosts a large collection of Flash content playable in-page through Ruffle.

Flashpoint, run by a preservation community, takes a different approach: a downloadable archive of tens of thousands of games with the original runtimes bundled. It is the most complete option and the least convenient one, because it is a real installation rather than a web page.

Native ports. A number of the best-known Flash games were rewritten properly in HTML5 by their original developers. These are the only ones that are genuinely future-proof.

What did not survive is everything whose author disappeared, whose source was lost, and whose ActionScript 3 is beyond Ruffle. That is a real, permanent loss, and no amount of emulation fixes it.

How browser games are different now

The games that replaced Flash are not simply Flash games in new clothing. The platform change altered the design.

They are built for touch first, or at least touch-compatible. Flash games assumed a mouse and a full keyboard. A modern browser game that cannot be played on a phone has given up most of its potential audience, so control schemes collapsed toward one input — tap, swipe, drag.

They are smaller. A Flash file bundled its own runtime and assets and could comfortably be several megabytes before anyone considered a mobile connection. HTML5 games load as ordinary web assets, streamed and cached, which pushes developers toward starting fast rather than loading everything up front.

They start immediately. The Flash-era loading bar with a sponsor logo is gone, because the economics changed. Nothing has to be downloaded before play begins, and a game that makes you wait now simply loses to one that does not.

They are harder to lose. A Flash game was a single .swf file that lived wherever it was uploaded, and when that site went down the game went with it. An HTML5 game is ordinary HTML, JavaScript and images — anyone can host it, and a great deal of it is open source. The preservation problem that destroyed the Flash era is much less severe this time, largely by accident.

If you are looking for a specific game

Search the exact title plus "HTML5" or "remake" first — a surprising number of the well-known ones were officially rebuilt and are still maintained. Failing that, try the Internet Archive's Flash collection, which will attempt it through Ruffle in the page. Flashpoint is the last resort and the most likely to work.

And if none of those find it: the genre almost certainly survived even when the game did not. The physics games, the tower defences, the stickman fighters, the idle games — all of them continued straight through the transition. What was lost was specific titles, not the ideas behind them.