The LMS says the course launched, while the learner sees a grey rectangle, a polite message about a missing plugin, or nothing at all. Nobody changed the course. The world around it changed, and Flash e-learning courses were among the first casualties. What actually happens to training built on SWF files after Flash Player's end of life, and how do you get it back in front of learners?
Flash-based courses stopped working because the player they need is gone, not because the files broke. Adobe ended support for Flash Player on December 31, 2020, began blocking Flash content in January 2021, and browsers removed the player. A SWF file without a player is just an archive of media and code. You cannot make it play safely for a general audience again, but you can usually recover its text, audio, video and images, read its logic, and rebuild the course in HTML5. Emulators can help with reference viewing, but they are a bridge, not a fix.
Why Did Flash-Based Courses Stop Working?
Flash courses stopped working because the runtime went away. A SWF file was never meant to stand on its own. The Flash Player plugin read it, drew it, ran its ActionScript and passed tracking calls to the page around it. Adobe's own Flash Player end of life page sets out the dates: support stopped on December 31, 2020, and Flash content was blocked from running in Flash Player starting January 12, 2021.

The browsers had been heading that way for years and finished the job. So a course can be perfectly intact on the LMS, with a valid package and a correct manifest, and still show nothing. The package is fine; the engine that played it is gone.
This also explains a confusing symptom. Some courses half work. The menu loads, the narration plays, and then one slide goes blank. That is often an HTML course with a single Flash interaction buried inside it.
How Can You Tell If a Course Depends on Flash?
The quickest way to tell is to open the package and look. A published course is usually a zip file, so copy it, unzip the copy, and search the folders. You are looking for any of these:
- Files ending in .swf (the compiled Flash movie) or .flv (Flash video).
- A script called swfobject.js, or another loader script for embedding SWF files.
- HTML with
<object>or<embed>tags that mention shockwave-flash. - A fallback message telling the learner to install Flash Player.
- Any .fla file. That is the editable Flash source, and if you find one, celebrate quietly.
On Windows, a quick search from a command prompt inside the unzipped folder finds the text clues for you:
findstr /s /i /m "swf shockwave" *.html *.htm *.js *.xml
Run that across a whole folder of packages and you have a list of suspects in minutes. Do it before anyone opens a ticket, not after.
Then open the imsmanifest.xml file at the root of each package and find the launch file named in the resource entry. If that launch page is a thin HTML wrapper whose main job is to load a single SWF, the whole course is Flash.
If the launch page is a full HTML player and the SWF files sit in a media or interactions folder, you are dealing with a mixed course, and only some screens need replacing. That distinction changes the size of the job considerably, so record it in your list next to each package name.
Can Emulators or Old Browsers Keep Flash Training Alive?
Emulators are sometimes good enough for reference viewing, and rarely good enough for learners. Open-source emulators such as Ruffle can play a good share of older SWF content, especially material written in the older ActionScript versions. Support for newer, heavier ActionScript 3 content has historically been less complete. Results vary file by file, so test the actual course rather than trusting a compatibility list.
The catch for e-learning is tracking. Many Flash courses reported to the LMS by calling out from the SWF to JavaScript in the wrapper page. An emulator may draw the screens and still drop those calls, which means the learner finishes and the LMS never hears about it. That is worse than a blank screen, because nobody notices.
A practical way to use an emulator is as a viewing station for the rebuild team. Load each SWF, record a short screen capture of every screen and branch, and file the recordings with the package. Those recordings become the reference the new version is checked against, long after anyone remembers how the original behaved.
Old browsers in a virtual machine are fine for a developer who needs to see the original behaviour. They should never be handed to learners. An unpatched browser running an unpatched plugin is a security problem with a training course attached.
Think of emulation the way you would think of keeping an old Windows box around to run Authorware courses: useful for checking what the original did, useless as a long-term delivery plan.
What Can You Salvage From a Flash-Era Module?
You can usually salvage more than people expect, because a SWF is a container, and most of what is inside can be pulled back out, provided the content is yours to reuse. Check that first if a vendor built the course.
The usual haul, roughly in order of value:
- Text. Screen copy, quiz questions, answer feedback and button labels.
- Audio. Narration often sits inside as MP3, or as separate files beside the SWF.
- Video. FLV files convert to MP4 with common video tools.
- Images and vector art. Extracted vectors can often be saved as SVG and reused at any size.
- Logic. Decompiled ActionScript is ugly to read, but it tells you exactly how scoring and branching worked.
Free SWF decompilers exist and can export most of this in a few clicks per file. Do not forget the paper trail either. Storyboards, narration scripts and SME review notes often outlived the source files on someone's drive, and they are often more useful than the SWF itself.
Sort everything you recover into a plain folder structure as you go: one folder per course, with subfolders for text, audio, video, images and logic notes. Rename files so they match the screen they came from. It feels fussy on day one, and it saves hours on day ten when someone asks where the narration for screen fourteen went.
If you do find the .fla source, newer Adobe animation tools can open many of those files. That gives you clean timelines and assets, though not a ready HTML5 course.
Should You Rebuild Flash Interactions or Simplify Them?
Rebuild the interactions that teach, and simplify the rest. Flash-era courses loved custom interactions: spinning dials, animated intros, drag-everything games. Some were real practice, while many were decoration that took a developer a week to build.
The test is simple. Does the interaction change what the learner does, decides or sees next? If yes, rebuild it. If it only reveals text in a flashy way, turn it into a standard tabs or accordion interaction and move on.
A made-up example shows the scale. Say a Flash module has 12 interactions. Three are software simulations where learners practise real steps, so they get rebuilt. Five are click-to-reveal panels, which become tabs or an accordion. Four are animated transitions, which become a short video or a static diagram. That turns twelve custom builds into three, and the course loses nothing it needed.
Software simulations deserve a special note. Flash was popular for them because it could fake an application screen convincingly. Before you rebuild one, check that the software it imitates still looks and behaves the same way. A faithful rebuild of a simulation for a version of the software nobody uses any more is effort spent teaching the past.
One more reason to simplify: a lot of Flash interactions only worked with a mouse. If you replace Flash training content, build the new version so it works from the keyboard too. You are rebuilding anyway, so do it properly once.
Turning SWF Files Into Courses Learners Can Open Again
Flash e-learning courses did not break; their player was retired on a published date, and it is not coming back. Once you accept that, the work becomes a straightforward salvage job.
Find every package that touches Flash. Keep one emulator or virtual machine for reference viewing. Pull out the text, media and logic you own. Then rebuild the interactions that earn their place and flatten the ones that only sparkled. SWF course conversion is rarely glamorous, but a course learners can open again beats a beautiful one that shows a grey box.
