The Flash Shutdown of 2020

The announcement

In 2017, Adobe announced, jointly with Apple, Google, Microsoft, and Mozilla, the companies that made the major browsers Flash Player ran inside, that it would end support for Flash Player at the end of 2020. That joint announcement mattered as much as Adobe's own decision: it meant every major browser vendor had agreed on the same end date, rather than one browser dropping support while others kept it alive.

The three-year runway was meant to give the huge amount of Flash-dependent content on the web, see Adobe Flash / SWF for what that content actually was, time to migrate to other technologies, or at least time to be archived, before support actually ended.

What happened on the date

Adobe formally stopped supporting Flash Player at the end of 2020. That alone would have been serious but survivable — plenty of unsupported software keeps running for years. What made this different was what came immediately after: starting in January of the following year, Flash Player was built to actively block Flash content from running at all, rather than simply going unpatched. Major browsers removed or disabled their Flash support around the same time. The effect was not a slow fade but a hard, deliberate cutoff.

Why it went this way

Flash Player's long history of security vulnerabilities made it an unusually attractive target for attackers for years, and browser vendors had already been walking away from plugin architectures in general, the old-style plugin systems Flash and other browser plugins relied on, well before 2020. Leaving an unsupported, unpatched, but still-functioning Flash Player installed on hundreds of millions of machines would have meant leaving a known, actively exploited security hole in place indefinitely. Adobe and the browser vendors chose a hard kill switch instead of a slow, silent decline specifically to close that hole cleanly.

The immediate fallout

Because so much of the interactive web had been built in Flash over more than two decades, the shutdown didn't just retire an old plugin, it made a huge amount of existing creative and commercial work instantly unplayable at the same moment, everywhere, regardless of whether the site hosting it still existed or still cared. Games, animations, educational tools, and whole sites built around embedded Flash content all went dark on the same schedule, whether or not anyone had gotten around to migrating or archiving them. Flash game portals, many of which had already been shrinking for years, lost the ability to run most of what remained of their libraries in a single stroke.

What came after

The shutdown is the direct reason preservation and emulation projects matter as much as they do for this era of the web. Ruffle exists to run SWF content again without the now-blocked original plugin, and archives such as Flashpoint exist to make sure the files themselves, not just the ability to play them, survive. Sites like this one, cataloguing Flash-era games and reviving the ones whose files can still be found, are only possible because of that after-the-fact preservation work; without it, the 2020 shutdown would simply have been the end of the story for almost everything it affected.