thearchivist.funFlash Player reaches the end of official support
Adobe ended support for Flash Player on 31 December 2020. The company then blocked Flash content from running in Flash Player beginning on 12 January 2021. These were related but separate milestones: the end of support marked the withdrawal of maintenance, while the January change affected playback through the official player. Browser vendors also removed or disabled their Flash integrations. For people who remembered Flash through short cartoons, games or interactive websites, the change made software dependency visible. A saved SWF file could still exist on a disk while the ordinary browser route for experiencing it disappeared. The work's survival as a file did not automatically preserve its behavior. Timing, audio, interaction and scripts were part of what a visitor had originally encountered. Adobe's notice directed users away from the unsupported player, and Microsoft's lifecycle documentation separately described the transition in its browser ecosystem. These primary records are useful because they establish what the vendors actually discontinued. They should not be stretched into the claim that all Flash-authored work vanished, or that every related development tool ended on the same day. Other forms of playback, migration and preservation require their own evidence. The event offers a practical model for documenting any service or format approaching obsolescence. Record the original runtime, preserve available source material, identify external dependencies and test a supported access route. A video recording can preserve one performance of an interactive work, but it cannot reproduce all its branches. A screenshot can document its appearance while missing its sound and timing. The best preservation description states which aspects remain accessible and which have been lost, approximated or left untested.
Context and provenance
Read this record with the Internet Archive's November 2020 adoption of Ruffle. The vendor's retirement and the preservation community's response were different events with different goals. A secure contemporary browser need not keep an obsolete plug-in alive in order for historians to care about the works made for it. That tension appears whenever a platform changes authentication, removes an API or stops supporting an old file type. Treat the announced deadline as the beginning of a dependency audit, and document the experience that an alternative player actually preserves rather than assuming perfect compatibility.
Why it matters
The retirement demonstrated that storing a digital object and retaining a usable way to experience it are separate preservation problems.
Sources and evidence
Editorial review: 2026-09-23. New evidence may change this account.