Scormbee

How to Edit a SCORM Package When You Don't Have the Source File

8 min read Czytaj po polsku

It's a common situation: a course has been running in the LMS for years, a regulation changes or a product gets renamed, and nobody has the file it was built from. The agency that made it is gone, the author left, or the license for the authoring tool expired. What you have is a ZIP. This article explains what you can do with it, from a ten-minute fix to a full rebuild.

What's inside a SCORM package

A SCORM package is a ZIP of a small website plus a manifest that tells the LMS how to launch it. A typical one looks like this:

course.zip
├── imsmanifest.xml          what the LMS reads on upload
├── *.xsd                    schema files for the manifest
├── index.html               the launch file named in the manifest
├── scripts/                 the player and the code that finds the LMS API
├── content/                 slide data: HTML, JSON or JavaScript
└── media/                   images, audio, video, fonts

The manifest names the launch file and, in SCORM 1.2, often the pass mark:

<item identifier="item1" identifierref="res1">
  <title>Customer complaints</title>
  <adlcp:masteryscore>80</adlcp:masteryscore>
</item>
...
<resource identifier="res1" type="webcontent" adlcp:scormtype="sco" href="index.html">

Everything the learner sees comes from the launch file and the files it loads. The SCORM inspector shows the manifest, the file list and the sizes without unzipping anything.

Why most packages can't simply be edited

Authoring tools keep two different things: a project file you edit, and a published package you upload. Publishing is a one-way step, like exporting a PDF from a Word document.

Tool Where the editable source lives
Articulate Storyline 360 A .story project file on the author's computer
Articulate Rise 360 The author's Articulate account
Adobe Captivate Classic A .cptx project file
iSpring Suite The PowerPoint file and its project folder
isEazy Author and other cloud tools The author's account
Scormbee Your Scormbee account; every exported package also opens again in Scormbee for editing

In the published output, the content is turned into whatever the tool's player needs. Some tools write tidy JSON files. Others write minified JavaScript where text, positions and quiz logic are mixed together, and some older outputs render text as images. That's why "open the ZIP in an editor" only works for some packages.

Step 1: Find out what made the package

Before choosing a route, identify the tool. File and folder names usually give it away:

You see Probably made with
story.html, story_content/, html5/ Articulate Storyline
scormcontent/, scormdriver/ Articulate Rise 360
course/en/components.json, blocks.json Adapt Learning
fonts/iseazy-* files, a content/ folder of JSON files isEazy Author
index_scorm.html, assets/js/ Often Adobe Captivate

Then ask for the source, which is often the fastest fix of all. Check the contract with the agency, the shared drives of the team that ordered the course, and the authoring tool account of whoever built it. If the source exists, editing it in the original tool and republishing is almost always the best option.

Step 2: Small fixes by hand

A typo, a wrong phone number or an outdated logo can often be fixed inside the package directly. Unzip it, find the text, change it, zip it again.

  • Search all files for a distinctive phrase near the error, using a code editor that searches whole folders.
  • If the search finds nothing, the text may be escaped. Non-English letters often appear as é or &eacute; in JavaScript and HTML, so search for a nearby English or ASCII word instead.
  • The same text can sit in several places: the visible slide, an accessibility layer, the course menu, the transcript. Change every copy.
  • In JSON and JavaScript, keep quotes escaped (\") and don't break line structure.
  • Replace an image with one of the same file name, format and pixel size.

Before you change anything, keep the original ZIP untouched and give every edited copy a new name, such as complaints-v3-original.zip and complaints-v3-fix1.zip. If the fixed package misbehaves in the LMS, you can go back in a minute, and you can compare the two with a folder diff tool to see exactly what you changed.

Then re-zip with imsmanifest.xml at the root. On macOS or Linux, from inside the unzipped folder:

zip -r -X ../course-fixed.zip . -x ".DS_Store" "__MACOSX/*"

On Windows, open the folder, select all files and folders inside it, and compress the selection, not the folder itself. Run the result through the SCORM validator and click through it in the SCORM player before uploading.

Here is what's realistic by hand:

Change By hand?
Fix a typo or a number Usually yes
Replace an image with one of the same size Usually yes
Change the pass mark in the manifest Yes, but also check the course's internal pass mark
Change a quiz's correct answer Risky: answers may be stored in several places or encoded
Reword whole slides Risky: text may overflow fixed-position layouts
Add or remove slides No
Translate the course No

Step 3: Convert it with an importer

If you need more than a small fix, try converting the package into an editable course. This works best for tools that store content as structured data, because the converter reads the content rather than guessing it from the screen.

In Scormbee, three cases are covered:

  • Packages exported from Scormbee open again for editing. Import the ZIP in the editor and you're back to the full project.
  • isEazy Author packages convert to editable courses through the isEazy importer: text, images, sections and quizzes come across, while decorative effects don't.
  • Packages from other tools can go through the SCORM converter, which tells you what it recognized and what it could convert.

Whatever converter you use, check the result slide by slide against the original running in a SCORM player. Pay most attention to quiz answers and to slides where the original used custom interactions.

Step 4: Rebuild from the text, with or without AI

When conversion isn't possible, rebuild. That's less work than it sounds if you start from the existing content instead of a blank page.

  1. Run the original in the SCORM player, which provides a simulated LMS, so the course behaves as it would for a learner.
  2. Capture the content: copy the text slide by slide into a document and take a screenshot of each slide for layout reference. Note every quiz question with its correct answer, checked by clicking through it.
  3. Collect the media: the images and audio are usually plain files in the package's media folders.
  4. Rebuild: either by hand in your authoring tool, or by giving the text document to an AI course generator as a source file. In Scormbee, the AI wizard accepts TXT, Markdown, DOCX and PDF, shows the credit cost before starting, and proposes an outline you approve before it writes slides.
  5. Improve while you're there. A rebuild is a chance to cut outdated slides, fix the quiz and add the practice the old course lacked.

Correct answers deserve extra care. In compiled packages they are often hard to read reliably from the files, so confirm each one with the subject-matter expert rather than trusting what you extracted.

Re-uploading without losing tracking history

The LMS keeps completions and scores attached to the activity, not to the ZIP file. How you upload the new version decides what happens to that history.

Route History Learners in progress
Replace the package inside the existing activity (Moodle allows this in the activity settings) Kept on the activity May resume with old saved data that the new version doesn't understand
Upload as a new activity and hide the old one Stays on the old activity; reports now span two activities Start the new version from the beginning
Upload as a new activity and delete the old one Lost, unless you exported the reports first Start from the beginning

For a hand-fixed typo, replacing the package in place is usually the right call. For a converted or rebuilt course, saved progress from the old player is meaningless to the new one, so upload a new activity, hide the old one rather than deleting it, and export its completion report to a file for the records. Test either route on a copy of the course before touching the live one.

Avoiding this next time

Ask for source files as a named deliverable whenever someone builds a course for you. Store them where the team can find them, together with fonts and media licences. And prefer tools whose packages can be opened again: every package you export from Scormbee opens again in Scormbee for editing, and the project keeps a version history, so the next update doesn't start with a search for a missing file. You can try the editor without an account.

Frequently asked questions

Can I open a published SCORM package in Storyline, Captivate or Rise?

No. Those tools open their own project files or cloud projects, not published packages. Without the original .story or .cptx file, or access to the Rise account the course was built in, you need a converter or a rebuild.

Will editing files inside a SCORM package break tracking?

Not if you leave the manifest, the launch file and the scripts that talk to the LMS alone, and change only text or same-size media. Re-zip with imsmanifest.xml at the root and test in a SCORM player before uploading.

Is there a SCORM editor that opens any package?

Not one that works for every tool. Packages from tools that store content as structured data, such as Adapt or isEazy, convert well. Packages that compile slides into JavaScript are much harder, and for those, rebuilding from the extracted text is often faster.

Who owns the source file of a course made by an agency?

Whatever your contract says. Many agencies deliver only the published package unless the source files are named as a deliverable. Ask for them at handover, together with fonts and media licences.

Can I edit a SCORM course made in Scormbee without the project?

Yes. Every package you export opens again in Scormbee for editing: import the ZIP into the editor and the course comes back with its images and fonts.

More articles

12 November 2026 · 4 min read

How to Update a Dynamic SCORM Course

Publish a change to a Dynamic SCORM course in three steps: edit it, click Publish update, and every LMS shows the new version at the next launch.

Read →