Adobe Flash reached permanent end-of-life on 31 December 2020. All major browsers removed Flash support entirely in the months that followed. As of 2026, there is no mainstream browser, operating system, or device that will run Flash content without extraordinary measures — and those measures are disappearing too.
For publishers and educational content providers who invested heavily in Flash-based interactive content during the 2000s and 2010s, this represents an ongoing and worsening crisis. Content that cannot be accessed cannot generate revenue, cannot serve learners, and cannot fulfil the terms of licensing agreements signed before Flash's end-of-life.
How bad is the problem?
Estimates suggest there are still hundreds of millions of SWF files in existence across educational publishers, corporate training libraries, news archives, and cultural institutions. The majority of this content has not been migrated. Publishers are sitting on libraries of interactive educational content — animated lessons, assessment quizzes, science simulations, language learning tools — that is simply inaccessible to modern users.
The financial impact is direct: publishers who licensed this content to schools, universities, and corporate clients on multi-year agreements are delivering a broken product. Renewal rates on Flash-dependent products have collapsed. Some institutions have already pursued refund claims.
Can Flash content actually be migrated to HTML5?
Yes — with caveats. The vast majority of what publishers built in Flash can be faithfully reproduced in HTML5, CSS3, and JavaScript. The web platform has evolved dramatically since Flash's peak years and is now fully capable of implementing everything that Flash could do that publishers actually used.
What migrates well
- Timeline animations: CSS animations and the Web Animations API reproduce Flash timeline sequences with high fidelity. Frame-by-frame animations convert cleanly.
- Multiple choice and fill-in-the-blank quizzes: Straightforward JavaScript implementation. Scoring, feedback, and attempt tracking all transfer cleanly.
- Drag-and-drop interactions: The HTML5 Drag and Drop API handles this natively. Touch support for mobile devices is included automatically.
- SCORM eLearning modules: SCORM 1.2 and SCORM 2004 are both implementable in HTML5. LMS integration and tracking are preserved.
- Audio narration and synchronised highlighting: HTML5 Audio API with JavaScript synchronisation reproduces narrated content cleanly.
What is more complex
- Physics simulations with custom ActionScript engines: These require recreation of the simulation logic in JavaScript — not conversion. The output is equivalent, but the development effort is proportional to the simulation complexity.
- Content that relied on Flash video: If the original SWF streamed video using RTMP, the video assets need to be located, re-encoded, and served through HTML5 video. This requires access to the original video files.
- Content with lost source files: If only the compiled SWF exists and the FLA source is lost, migration is possible through SWF decompilation — but the quality of the decompiled source varies and manual reconstruction may be required.
The single most important thing you can do right now, before any migration work begins, is locate and archive your original FLA source files. If they exist, migration is straightforward. If only the compiled SWF exists, migration is possible but more expensive.
A practical migration strategy
Step 1: Inventory your Flash assets
Before you can plan or budget a migration, you need to know what you have. Catalogue every SWF file — or every piece of content that loads SWF files — with its content type, estimated complexity, business value, and source file availability. This inventory is the foundation of everything that follows.
Step 2: Triage by business value
Not every Flash file is worth migrating. Content that is no longer commercially active, that has been superseded by newer content, or that relates to curricula no longer in use should be archived rather than migrated. Focus migration resources on content that is actively licensed, sold, or used.
Step 3: Run a pilot migration
Select 5–10 files representing the range of complexity in your library and have them migrated to HTML5. Test on target devices (iOS, Android, desktop browsers). Compare the HTML5 output to the original Flash behaviour. Use the pilot to validate your cost and timeline estimates for the full migration programme.
Don't wait for the "right time"
There is no ideal moment to start a Flash migration programme — but there are costs to delay that compound every month. Original source files become harder to locate. Staff who remember the original content requirements move on. Institutional clients who might have accepted a phased migration timeline become less patient as the inaccessibility persists. The right time to start was 2021. The second-best time is now.
Accessibility as part of the migration
Flash content was almost universally inaccessible to users of assistive technology. The WCAG 2.1 Level AA compliance that a properly built HTML5 replacement provides is therefore not just a legal requirement — it's a genuine expansion of the audience for your content, and a commercial differentiator in institutional markets where accessibility compliance is a procurement requirement.
Build WCAG 2.1 compliance into your HTML5 migration specification from the start. Retrofitting it afterwards is significantly more expensive than building it in — and the institutional market increasingly requires it contractually.
