Summary

  • Adobe stopped supporting Flash Player on 31 December 2020, then blocked Flash content from running in its player beginning 12 January 2021. The two dates governed different things.
  • Safari had already dropped Flash; Firefox 85 removed support on 26 January 2021. Microsoft put its Windows component on yet another removal schedule. The ordinary web lost a chain of execution, not the bytes of every old file at once.

The file was still there

The Flash file could still be there. The visitor could still reach the page. The browser might even still contain a place where a plugin once went. On 12 January 2021, Adobe's own player supplied the missing refusal: it began blocking Flash content from running. A date written into a product's retirement plan now sat between an archived work and its audience.

Adobe had announced the larger decision in July 2017. It would stop updating and distributing Flash Player at the end of 2020, and it urged creators to move existing work to open formats. The notice gave developers more than three years to plan. It did not move an animation, game, lesson or business form for them. HTML5, WebGL and WebAssembly could provide many of the capabilities once delivered by a plugin; they were technologies for making a replacement, not a command that made every existing Flash file run.

The retirement came in stages. Adobe's end-of-life notice, updated on 13 January 2021, identifies 31 December 2020 as the end of support. From then, Adobe would issue no Flash Player updates or security patches. It separately dates the playback block to 12 January. A site operator who waited for support to stop had twelve calendar days before the ordinary Adobe player would also stop loading the old content. Adobe said the block was intended to protect systems after maintenance ended. Its download pages for Flash Player were removed as well.

That sequence made the dependency unusually visible. A publisher owned the pages and the work in them, but did not control the reader's runtime. Keeping a .swf on a server preserved the file, not a functioning public display. The creator needed a replacement experience; the visitor needed a browser and software that could execute it. The company that maintained the player could close its part of that route without taking down the publisher's web server.

Browsers kept their own clocks

Browser makers were already moving on different clocks. Apple's WebKit team said in its Safari 14 feature notes in June 2020 that Safari 14 would no longer support Flash. Adobe's later notice dates the macOS release to September. A Safari visitor therefore hit a browser-level limit before Adobe's support ended in December. The Flash file did not have to change for the result to change.

Mozilla's November 2020 release notice supplies a more pointed overlap. Firefox 84 would be its last version with Flash support. Firefox 85, scheduled for 26 January 2021, would ship without it and without a setting to turn it back on. Yet Mozilla also warned that Adobe's plugin would stop loading Flash content after 12 January. For that interval, asking whether Firefox had removed support was the wrong practical question. The player could refuse playback first.

Mozilla's Firefox 85 release notes later confirmed the 26 January release and the complete removal of Flash support.

Microsoft described still another pair of removals. Its lifecycle notice, published in September 2020 and updated in April 2021, said new Edge would remove Flash in January 2021. The later update said Microsoft had disabled Flash in its browsers and planned permanent removal of the Windows Flash component through Windows Update in July. Removing browser support and removing a Windows component were separate operations. Neither was the same act as Adobe ending security patches or Adobe blocking playback in its player.

These notices also explain why the dramatic sentence “Flash died on 12 January” gets the machinery wrong. Safari had gone earlier. Firefox's scheduled removal was later. Microsoft maintained a separate component-removal calendar. Adobe itself distinguished the end of updates from the later playback block. The public experience converged toward an unusable plugin, but convergence was built from decisions made at different layers.

There were bounded continuations. Adobe's administrator guide describes managed Flash Player environments, and its April 2021 enterprise update identified licensed support after end of life through an official partner, with a separate distribution arrangement for mainland China. Those arrangements were not a general consumer route back into a current browser. They show why “every Flash workload stopped” is as inaccurate as “nothing changed because the files remained.”

The public record used here gives no count of sites or applications that still depended on the player at the switch. A dated crawl tied to actual player dependencies would establish the reach. The decision itself is plain: Adobe ended maintenance, then made ordinary playback fail; browser and operating-system vendors removed their own support on their own schedules. An open file format is one kind of portability. A running experience also needs someone with authority over the software that opens it.

Sources