← All SCORM guides

· SCORM Packager team · LMS testing and troubleshooting

How to fix common SCORM upload errors

Short answer: Most SCORM upload errors come down to the zip, not the LMS. imsmanifest.xml must sit at the root of the zip, the course must be published for an LMS (not for the web), and the file must fit under the LMS upload limit. If the upload succeeds but the course never completes, check the completion settings, the SCORM version the LMS supports, and resume data limits.

1. "imsmanifest.xml not found" or "not a valid SCORM package"

This is the most common error by far. The LMS looks for imsmanifest.xml at the root of the zip, and it is not there. Usual causes:

  • The folder was zipped instead of its contents. Right-click → Compress on a folder puts everything one level down, so the zip contains course-folder/imsmanifest.xml. Open the folder, select everything inside it, and zip that.
  • A zip inside a zip. Some tools and file-sharing services wrap the delivery in another archive. Unzip once and upload the inner zip.
  • The course was published for the web, not for an LMS. Storyline's Web output and Rise's Web export have no manifest. Republish with the LMS option and choose SCORM.
  • macOS added a __MACOSX folder and .DS_Store files. They are usually harmless, but strict LMSs can choke on them. Zip from the command line, or remove them.
  • The manifest file name has different casing. Servers are case-sensitive; use exactly imsmanifest.xml.

SCORM Packager validates every upload the same way an LMS would: a package without a manifest at the root is flagged with "No imsmanifest.xml or tincan.xml found in the package", and a damaged archive with "Invalid ZIP file". That makes it a quick pre-flight check before you open a ticket with the LMS admin.

2. The file is too large

Courses with video easily pass a few hundred megabytes. LMSs cap uploads at several levels: Moodle, for example, applies its own site and course limits on top of the web server's and PHP's upload_max_filesize and post_max_size. Ask the admin which limit applies, or reduce the package: compress video to a sensible bitrate, remove unused media from the authoring project, and republish.

3. The manifest is invalid

If someone hand-edited imsmanifest.xml, a single unclosed tag or an unescaped ampersand (&) in the course title makes the XML invalid. Open the file in a browser or an XML validator to see the exact line. The reliable fix is to restore the manifest from the original export and change titles in the LMS instead.

4. The LMS does not support that SCORM version

Most LMSs handle SCORM 1.2 well. SCORM 2004 support varies: Moodle's own documentation states that SCORM 2004 is not supported, although some packages partly work. If a SCORM 2004 course uploads but misbehaves, republish it as SCORM 1.2 and compare. The differences are explained in SCORM 1.2 vs SCORM 2004.

5. It uploads, but never shows as complete

  • Completion settings do not match the course. If the LMS requires "passed" but the course reports "completed" (or the reverse), the status never changes. Align the authoring tool's reporting option with the LMS completion rule.
  • The learner closes the window before the course commits. Courses that only save on exit lose data when the browser is closed abruptly. Test by finishing the course and using its own exit button.
  • Resume data is too long. SCORM 1.2 allows 4,096 characters of suspend data. Long Storyline courses can exceed it, which breaks resume and sometimes status. Publish as SCORM 2004 if the LMS supports it.
  • Pop-up or third-party cookie blocking. When the course opens in a new window or is served from another domain, browser privacy settings can cut the link to the LMS API.

6. Broken pages or missing media after upload

A course that worked on Windows but shows missing images on the LMS usually has file names that differ only in casing (Image.PNG vs image.png), or special characters and very long paths in file names. Linux servers treat those differently. Republishing from the authoring tool normally fixes it; renaming files by hand also requires updating every reference.

Frequently asked questions

Why does my LMS say the SCORM package is invalid?

Almost always because imsmanifest.xml is not at the root of the zip: the parent folder was zipped, the zip is nested in another zip, or the course was published for the web instead of an LMS.

How do I zip a SCORM package correctly?

Open the published folder, select everything inside it, including imsmanifest.xml, and compress the selection. The manifest must be at the top level of the zip, not inside a folder.

Why does my SCORM course not save progress?

The most common causes are a SCORM 1.2 suspend data limit of 4,096 characters, closing the window before the course commits, or browser settings blocking the connection to the LMS. Test with the course's own exit button and try SCORM 2004.

How can I test a SCORM package before uploading it to the LMS?

Preview it in the browser with a simulated SCORM runtime, then test tracking in a sandbox LMS. See how to open a SCORM file without an LMS.

Sources

Product page: Multilingual SCORM package

Check a SCORM zip before the LMS does

Upload a package to a free project: it is validated on upload and you can preview it in the browser before it goes anywhere near the LMS.

Free to try and preview · Download on any paid plan · No credit card required