Fixing 'imsmanifest.xml is missing' and Other SCORM Upload Errors

You export a course, drag the .zip into your LMS, and get a flat rejection: "imsmanifest.xml is missing or invalid." The file is right there inside the zip — so why does the LMS say it is gone? This is one of the most common SCORM upload errors, and almost always it is a packaging problem, not a content problem. Here is the field guide.

Error 1: "imsmanifest.xml is missing" — when it is actually there

The SCORM spec requires imsmanifest.xml to sit at the root of the archive. The LMS looks for it at the top level of the zip and nowhere else. The number one cause of this error is zipping the wrong thing: you selected the course folder and zipped it, so inside the archive the manifest lives at CourseName/imsmanifest.xml instead of imsmanifest.xml at the root.

The fix is to repackage from inside the course folder so the manifest lands at the top level:

# Run from INSIDE the course folder (where imsmanifest.xml lives):
zip -r ../course.zip . -x '.DS_Store' -x '**/.DS_Store'

Other causes of the same error: the manifest filename is wrong (it must be exactly imsmanifest.xml, lowercase), the file is genuinely missing, or it is malformed XML the parser cannot read.

Error 2: Invalid or malformed manifest

If the manifest is at the root but still rejected, the XML itself may be invalid: an unclosed tag, a bad character, a missing required element, or a stripped UTF-8 byte-order mark that some parsers expect. SCORM manifests are validated against published schemas (the ADL/IMS XSD files), so a structurally wrong manifest fails even if it "looks fine."

Error 3: References to files that are not in the package

The manifest declares every file the package contains. If it lists a file that was not actually included in the zip — a deleted media asset, a renamed page — strict LMSes reject the package, and lenient ones accept it but throw 404s at runtime. The reverse (files present but not declared) is usually tolerated but is still a packaging smell.

Error 4: The course uploads but will not launch

A package that imports cleanly but shows a blank screen or spinner usually has a launch-href problem: the resource’s href points at a page that does not exist, points at the wrong entry page, or the entry page tries to load assets by absolute path that breaks once the LMS hosts it from a different URL. Confirm the launch file in the manifest actually exists and that asset paths are relative.

Error 5: It launches but never reports completion

This one is not a packaging error — it is a runtime one — but it gets reported as "the package is broken." The course runs, the learner finishes, and the LMS still shows incomplete. Common causes: the course never calls the finish/commit step, it sets the wrong lesson status, or it cannot find the LMS API object. We cover completion failures in depth in a separate article; for upload-time triage, first rule out the packaging errors above.

A quick triage checklist

1. Open the zip and confirm imsmanifest.xml is at the very top, not inside a subfolder.
2. Confirm the filename is exactly imsmanifest.xml (lowercase) and the XML is well-formed.
3. Confirm the launch page named in the manifest actually exists in the package.
4. Spot-check that asset paths are relative, not absolute or machine-specific.
5. Upload to SCORM Cloud or a test LMS and watch the browser console for 404s.

Most "broken SCORM package" tickets are not broken content — they are a manifest in the wrong place or a path that points somewhere the LMS cannot follow.

Validate and repair without unzipping anything

ScormEdit includes a free validator: upload a package and it checks the manifest location and validity, flags declared-but-missing files, verifies the launch entry point, and warns about common pitfalls — then offers one-click fixes like moving the manifest to the root and repackaging correctly. You can confirm a package is LMS-ready before you ever touch the upload button, and fix the usual suspects without editing a single line of XML.