The source file is gone. The zip isn't.
Import any SCORM, cmi5, xAPI or AICC package, edit the course, export a new one.
Last reviewed
Import the published SCORM zip into Scormbusters. It recognizes the authoring tool that made it, rebuilds the content as an editable course — text, images, media and, where the package records them, quiz questions with their answer keys — and exports a new SCORM, cmi5 or xAPI package.
Storyline triggers and Captivate Classic actions are rebuilt as working triggers where the slide canvas can run them the same way, about half of them in our test corpus; the import report lists the rest for you to rebuild.
- Captivate, Storyline and iSpring cannot re-open their own published SCORM output; editing needs the source file or a tool that reads the package.
- Scormbusters identifies the authoring tool from a package's contents and reads Captivate, Storyline, Rise 360, Lectora, iSpring, Adapt, H5P, generic SCORM 1.2/2004, AICC, cmi5 and xAPI packages.
- Storyline triggers and Captivate Classic actions are rebuilt as working triggers where the slide canvas runs them the same way: 49% and 40% respectively in our test corpus. Custom JavaScript never is. Flash-era packages recover structure only.
- Exports: SCORM 1.2, SCORM 2004, cmi5 and xAPI.
Packages Scormbusters can read
| Made with | What is read |
|---|---|
| Adobe Captivate | Classic HTML5 publishes (9 to 2019), .cptx projects, and all-new 12/13 publishes |
| Articulate Storyline | HTML5 publishes, including quiz questions with their answer keys |
| Articulate Rise 360 | Published packages |
| Lectora | Published HTML and .awt projects |
| iSpring Suite and QuizMaker | Published packages |
| Generic SCORM 1.2 / 2004 | Any conformant package, including hand-built ones |
| AICC, cmi5, xAPI (Tin Can) | Packages in each standard |
| Adapt / Evolve, H5P | Course and content packages |
| Common Cartridge, QTI | .imscc and QTI 1.2 / 2.x question banks |
| Moodle | Course backups (.mbz), Moodle 1.9 to 4.x — user data is never imported |
| PowerPoint | .pptx decks |
Articulate Studio (Presenter) packages are recognized and their slide text and notes are read, but content inside Flash is not converted — see Articulate Studio end of support.
A small text or image fix: edit the files by hand
A SCORM package is a delivery format — an imsmanifest.xml, a player and the content it shows — and Storyline, Captivate and Rise open only their own project files, not a package. For a one-word fix you can skip the tools:
- Keep a copy of the original zip.
- Unzip it and find the text in the HTML or data files, or the image in its folder.
- Make the change, keeping the file names the same.
- Zip the contents, not the folder, so imsmanifest.xml sits at the top level of the zip.
This works well for hand-built or simple HTML packages. Storyline, Captivate and Rise output is harder: text sits inside compiled JavaScript or JSON, sometimes drawn into images, and one slip breaks the course.
Patching a package versus rebuilding it
Tools that edit a SCORM package in place are good for a typo or a replaced logo. They leave the original player, its fixed slide size and its accessibility problems untouched, and they do not change quiz logic.
Rebuilding gives you a course you can keep maintaining: real, editable text instead of text baked into images, keyboard-operable questions, and answer keys you can change. Slide-based Storyline courses keep their slide layout on Scormbusters’s slide canvas; most other formats become lessons that reflow on any screen. How this compares with ScormEdit.
Step by step
- Download the package from your LMS (most can export the original zip).
- Run the free scan to see its accessibility problems and a screen-reader transcript. No account needed.
- Import it into Scormbusters and review the import report.
- Edit, fix what the accessibility checker flags, and rebuild any interactions.
- Export SCORM 1.2, SCORM 2004, cmi5 or xAPI and replace the old package.
Export with “Replace the original in your LMS” and completions and grades stay attached in the LMS (verified in Moodle; try a test copy in yours). In-course bookmarks start over.
Frequently asked questions
Can you edit a SCORM file directly?
You can unzip a SCORM package and change its HTML, but most authoring tools publish the content as generated JavaScript and images, so small text edits are fiddly and anything structural — adding a question, changing an answer key, reordering screens — is impractical. Rebuilding the package as an editable course avoids that.
How does Scormbusters know which tool made my package?
It looks at the contents, not the file name. Each authoring tool leaves recognizable files in its output, so a Storyline, Captivate or Lectora publish is read by a parser for that tool. Anything else falls back to the generic SCORM reader.
Are quiz questions and answers kept?
Where the package records them, yes: Storyline, Captivate, iSpring, Lectora, QTI and Moodle questions come across as real questions with correct answers. A question the importer cannot read is listed in the import report.
Is anything lost?
Storyline triggers and Captivate Classic actions (jumps, show and hide, variables, conditions, state changes) are rebuilt as working triggers where the slide canvas runs them the same way: in our test corpus, 49% of Storyline trigger actions and 40% of Captivate Classic actions. Custom JavaScript, effects and timeline pauses never are. Flash-era packages recover structure only. The import report lists what did not come across.
What do I get at the end?
An editable course in Scormbusters, and a new SCORM 1.2, SCORM 2004, cmi5 or xAPI package you upload to your LMS. You can also export a portable source file, so the course is never locked in again.
Bring one stuck course. See what comes back.
Upload the published zip and play it rebuilt as an editable course, with the list of anything to rebuild by hand. No account, no card; the private link lasts seven days.