Keeping a Flash work was two jobs: saving the .swf file, and saving a way to run it. Most people did the first and skipped the second; the browser brought the player along. That stopped being true as 2020 turned into 2021, and thousands of saved files suddenly had no runtime to call home.
A file without a runtime
A .swf is not a self-contained movie. It is shapes, timelines, audio, and ActionScript written for Adobe Flash Player, and without that player it is inert. An MP4 plays in whatever you have; a .swf plays almost nowhere. Adobe stopped supporting Flash Player on December 31, 2020 and began blocking Flash content from running in the player in January 2021. Browser support had already been shrinking for years.
Browsers removed the player
The removals were staggered across browsers and operating systems, which is how the file-versus-player confusion set in. By early 2021, the major browsers had removed Flash playback. A modern browser will not run a .swf simply because the file still exists. The file survived fine. The thing that interpreted it disappeared from the normal browsing environment.
Files outlived their players
Homestar Runner is the cleanest documented case. The animated site ran on Flash for two decades, and when the plug-in died the .swf files went nowhere: the old Flash version stayed online at old.homestarrunner.com, while the main site was rebuilt around the Ruffle emulator. Its post-Flash update page is honest about the seams. The cartoons and many games play again, but games made after about 2007 “will probably be pretty janky,” and toons built on embedded video just show a blank box. The files lived on. The runtime they were written for had left the browser.
Emulation recovers most, not everything
Recovery works because emulation replaces the missing runtime. Ruffle, a Flash emulator written in Rust and compiled to WebAssembly, mimics enough of Flash’s behavior that the Internet Archive began playing archived Flash items in the browser with it in 2020. Flashpoint uses additional preservation techniques and standalone projectors for works that need more than a simple browser emulator. Both approaches hit the same hard limit: anything a work expected from a live server, an external file, or a multiplayer backend must be preserved separately or reconstructed.
Save more than the file: the .swf, the .fla if it exists, the author, the original site, and whether the work reached beyond itself. Files are easier to keep than works. A .swf that outlives Flash Player is a relic that proves something existed — not a guarantee that it can be watched. Keep a runtime or an emulator, and plenty of it can be.