How-to guides
Can you edit a SCORM file? Yes, and here is how
You have a SCORM package, something in it is wrong or out of date, and the person who built it has left. Here is what you can do, starting with the option that works best.
Updated
Why a SCORM file is hard to edit
A SCORM package is a .zip of web files that an authoring tool produced. The tool kept the editable project for itself (a .story file for Storyline, a course in your account for Rise) and wrote out a version made for playing, not for editing.
So when you unzip one, you do not find tidy pages of text. You find compressed scripts and data files that were written by a machine. You can change them, but one wrong character can stop the course loading.
Option 1: edit the source and export again
Best for: any change, if you can get the original project.
- Find the source. Ask the person or agency who built the course for the project file, or for access to the course in their authoring account.
- Open it in the same authoring tool, make the change, and publish to SCORM again with the same settings as before.
- Replace the package in your LMS. Most LMSs have an "update" or "replace" option that keeps learners' records.
This is the only route where every kind of change is possible and nothing is at risk. It is worth an email or two to track the source down before you try anything else.
Option 2: make a small fix inside the zip
Best for: a typo, a swapped image, a new course title.
- CopyKeep the original zip somewhere safe. Work on a copy.
- UnzipExtract the copy into a folder.
- FindSearch the folder for the exact words you want to change. A code editor such as VS Code can search every file at once.
- ChangeEdit only the words. Leave quotes, brackets and commas around them exactly as they are. To swap an image, replace the file with one of the same name, type and size.
- ZipSelect everything inside the folder and zip that. Do not zip the folder itself. The file imsmanifest.xml must sit at the top level of the zip, or the LMS will reject it.
- TestOpen the new zip in our free SCORM viewer and click through before it goes near your LMS.
The course title the LMS shows comes from imsmanifest.xml. Open that file in a text editor and change the text between the <title> tags.
What this cannot do: add a page, reorder sections, change a quiz's pass mark or alter how completion is tracked. Those need the source, or one of the next two options.
Option 3: import it into a tool that can read it
Best for: courses built in Articulate Rise.
A few tools can read a published package and turn it back into something editable. This depends on which tool made the package, because each one stores its content differently.
Recourse does this for Rise 360. On the Pro plan you choose "Import from Rise", drop in the SCORM zip, and get an editable course with its lessons, text, images and quizzes. An import report lists what came across, what needed changing and what could not be brought over. Storyline blocks inside the course keep playing as they did. The import is in beta, and it reads Rise packages only. The steps are in how to export a Rise course as SCORM.
Rise itself cannot do this. It has no way to open a SCORM package, even one it made.
Option 4: rebuild it
Best for: old courses, big changes, or a package no tool will import.
Use the old course as your script and build a new one.
- Open the package in the SCORM viewer and go through it, copying out the text and saving screenshots.
- If it has a quiz worth keeping, our SCORM to quiz tool can draft questions from the package (it needs a free signup).
- Rebuild in an authoring tool. If the course teaches a piece of software, it is often quicker to record the task again than to rescue old screenshots. Recourse turns a screen recording into a lesson and a practice simulation.
Rebuilding sounds like the slow option. For a course more than a few years old it is often the fastest, because the software it shows has changed anyway.
Which option should you use?
| Your situation | Use |
|---|---|
| You have, or can get, the original project | Option 1 |
| One typo or one image, and no source | Option 2 |
| A Rise course, and no access to the Rise account | Option 3 |
| Large changes, an old course, or anything else | Option 4 |
Before you start: three checks
- Do you have the right to change it? A course bought from a supplier is usually licensed, not owned. Check before you alter it.
- What happens to learners' records? Uploading a changed package as a new course starts everyone from zero. Use your LMS's replace option if it has one.
- Which version is it? SCORM 1.2 and 2004 are not interchangeable. The viewer shows which one you have. See SCORM 1.2 vs 2004.
How to avoid this next time
- When someone builds a course for you, ask for the source project as well as the SCORM zip, and put that in the contract.
- Store the source next to the zip, with a note of which tool and version made it.
- If your courses change often, consider a live SCORM package. Recourse offers one on its Pro plan: the zip in the LMS points at the hosted course, so you edit once and every LMS shows the new version, with completion tracked as before.
Key takeaways
- A SCORM file can be changed, but it was not made to be edited.
- Editing the original project and exporting again is always the best route.
- Small text and image fixes can be made inside the zip. Keep imsmanifest.xml at the top level.
- Rise packages can be imported into Recourse as editable courses. Anything else usually means a rebuild.
Questions people ask
Can you edit a SCORM file?
How do I edit a SCORM file without the source?
What software can open and edit SCORM files?
Can I import a SCORM package into Articulate Rise or Storyline to edit it?
Why does my LMS reject the SCORM file after I edited it?
Keep reading
Last reviewed 19 November 2026. Recourse publishes these guides for learning, customer education and change teams. Details drawn from public sources can change.