Flash Player was switched off on 31 December 2020, and a large number of obituaries for browser gaming were filed that week.
They were about nine years late. WebGL 1.0 had shipped in 2011, WebAssembly reached every major browser in 2017, and by the time Adobe pulled the plug the replacement stack had been running in production for most of a decade.
What actually happened is more interesting than a death. The category lost its name, kept its audience, and got substantially more capable while nobody was paying attention.
The Timeline Nobody Lines Up Properly
Put the dates next to each other and the narrative rearranges itself.
2007: the first iPhone ships without Flash support, which is the moment the platform’s long-term position becomes untenable regardless of anything Adobe subsequently did.
2011: the WebGL 1.0 specification is released, giving browsers direct access to the graphics hardware without a plugin.
2013: asm.js demonstrates that JavaScript can run compiled code at close to native speed, which nobody had seriously expected.
2017: WebAssembly ships in all four major browsers. The same year Adobe announces the end of Flash.
2020: Flash Player is discontinued.
The replacement arrived before the incumbent was deprecated, which is the opposite of how platform transitions usually feel from the outside. Developers had a working alternative for years before the deadline, and the studios that moved early simply continued operating.
What Was Genuinely Lost
Worth being honest, because the transition was not free and something real disappeared.
An enormous archive of Flash content became unplayable overnight. Not commercially significant titles, mostly, but a decade and a half of experimental work, student projects and the kind of strange one-off game that existed because the barrier to publishing was a single file upload.
Preservation efforts have recovered a meaningful portion through emulation, and the work is ongoing, but the casual discoverability is gone. You cannot stumble across those games the way people did in 2008.
The authoring tool disappeared too. Flash was a drawing program that happened to export interactive content, which meant animators could ship games without being programmers. Nothing in the current stack replicates that, and the modern equivalent requires a game engine and more technical commitment.
So the tooling got worse for beginners while the runtime got dramatically better for everyone else.
The Portals That Survived Did One Thing Differently
Most Flash portals were aggregators. Anyone could submit, the catalogue grew without limit, and discovery was a search box over an undifferentiated pile.
That model did not survive, partly because the content stopped working and partly because it was never much good. A catalogue of fifty thousand games with no filtering is a worse product than a catalogue of five hundred with judgement applied.
The portals still operating made the opposite choice. Titles reviewed by online game experts on SilverGames sit in catalogues that have been curated continuously across the Flash transition and rebuilt on the current stack, which is a different proposition from hosting whatever arrives. Curation is expensive and it is the only defensible position once storage and bandwidth stop being scarce.
Which is broadly what happened to every media category that went through the same shift. Abundance made selection the valuable service rather than access.
What the Modern Stack Can Actually Do
The capability gap between 2010 and now is larger than most people assume, and it changed what the category can contain.
Hardware-accelerated 3D through WebGL and now WebGPU, with performance adequate for genuinely ambitious titles rather than novelty demos.
Compiled code via WebAssembly, which means existing C and C++ engines can target the browser rather than requiring a rewrite.
Real multiplayer through WebSockets and WebRTC, at latencies that make competitive play viable.
Persistent storage and offline capability, so a browser game can hold a save file and run without a connection.
Every major engine now exports to web. The constraint on browser gaming is no longer technical, which is why the interesting question moved to distribution and discovery rather than capability.
Why Console Players Should Care
Two reasons, and neither is about replacing anything.
The zero-install proposition is genuinely valuable for a specific slice of time. Waiting for a download, sitting in matchmaking, deciding whether a session is worth starting. A browser tab fills that gap without competing for the evening, which is a different market from the one console titles serve.
And browser titles remain the best available laboratory for mechanics. A five-minute game that has to teach itself in thirty seconds produces design discipline that a forty-hour title can afford to skip, and ideas tested there regularly surface in larger productions later. More on where those ideas end up in the PlayStation news archive.
The category was never dying. It was being rebuilt in public, on a slower schedule than the obituaries assumed, and by developers who had already moved on before the deadline arrived.