When Adobe formally ended support for Flash Player at the close of 2020, the obituaries were unanimous. Flash was insecure, proprietary, battery-hungry, and had already been pushed out of mobile a decade earlier by Apple. Good riddance, said the industry, and it moved on.
Five years later, something unexpected has happened. Flash content — games in particular — is not only still accessible, it is being played by more people than it was in the plugin’s final years. That comeback did not come from Adobe. It came from the open-source community, and it holds a lesson for any business currently sitting on a pile of software the vendor no longer supports.
The scale of what was at stake
It’s easy to forget how much of the early web was built on Flash. Estimates from preservation groups put the number of Flash games alone in the hundreds of thousands. Beyond games, Flash powered animation portals, interactive news graphics, corporate training modules, banking dashboards, and a generation of e-learning products. When the runtime disappeared, all of that became unreadable data — files that existed but could not be executed.
For most companies, “we’ll just rewrite it” was not realistic. The developers were gone, the source files were often lost, and the business case for rebuilding a 2009 training module in HTML5 was thin.
The technical fix: emulate the runtime, not the content
The solution that emerged is elegant. Rather than converting each piece of content, the community rebuilt the Flash runtime itself as an emulator — most notably Ruffle, written in Rust and compiled to WebAssembly. Instead of a native plugin with system-level access, you get a sandboxed module that any modern browser can run.
This is the same strategy that has kept 1980s console games playable for forty years: preserve the machine, and everything written for it comes along for free. What is new is that WebAssembly lets that machine live inside a web page, so the end user does not have to install anything, and the security problems that killed the original plugin simply do not apply.
The user side: making it accessible
Emulation only matters if ordinary people can use it, and this is where the ecosystem matured quickly. Archive projects like Flashpoint collect and curate the games themselves. Hosted players handle the “how do I run this” problem — for example, Allowflash offers a browser-based Flash player where users can load games and SWF files directly in the tab, on desktop or mobile, without downloads or plugins. The friction that once required a plugin install, a security exception, and a prayer has been reduced to opening a web page.
That combination — a preserved runtime, curated content, and zero-install access — is why Flash games have found a second audience among people who were not even born when the originals were released.
What this means for enterprise legacy software
There are three takeaways for anyone managing ageing systems.
First, content and runtime are separable. Companies often assume that when a platform is discontinued, everything built on it must be rewritten. Flash shows that re-implementing or emulating the runtime can be far cheaper than migrating every artefact — a strategy already used in mainframe emulation and, increasingly, in containerised legacy stacks.
Second, sandboxing changes the security calculus. Flash was killed for security reasons, yet emulated Flash is safe, because the emulator inherits the browser’s sandbox rather than running native code. The lesson generalises: legacy code that was dangerous in its original environment can be acceptable inside a modern isolation boundary.
Third, open source outlives vendors. Adobe had no commercial reason to keep Flash alive. The community did. Businesses that depend on proprietary runtimes should think about whether an open re-implementation exists — or could be sponsored — before the vendor’s end-of-life date arrives.
The bigger picture
The Flash revival is more than a nostalgia story. It is a case study in how digital culture survives platform death, and it arrived just as regulators, archivists, and enterprises are all asking harder questions about software longevity. Two decades of interactive web history were on the verge of becoming a black hole. Instead, they are a click away, running faster than they ever did in the original player.
The plugin is dead. The content, it turns out, was never the problem.
