Scormbee

Free SCORM validator

Check a SCORM package before your LMS rejects it.

Drop a ZIP and the validator reads it the way an LMS does: where imsmanifest.xml is, which SCORM version it declares, which file the course starts from and whether every listed file is really there. Each finding says what is wrong and how to fix it.

Free · no account · runs in your browser

How it works

How to validate a SCORM package

  1. Drop the ZIP you will upload

    Check the exact file you will send to the LMS, not the export folder. Most packaging errors happen while zipping.

  2. Read the findings by severity

    Errors stop the import or the launch. Warnings pass in some LMSs and fail in others. Notes are worth knowing; passed checks show what is fine.

  3. Fix, zip again, check again

    Fix the export settings or the files, zip the folder's contents again and drop the new ZIP. It takes seconds, so check every package you send out.

What the validator checks

The checks, what they mean and how to fix them

In the order an LMS meets them during an upload: the ZIP, the manifest, the structure, the launch file, the files, the paths and the scoring rules.

imsmanifest.xml at the root of the ZIP

What it means: The LMS looks for imsmanifest.xml at the top level only. Zip the folder instead of its contents and it ends up in course/imsmanifest.xml, so the LMS says "not a SCORM package". IMSManifest.xml fails on servers that compare names exactly.

How to fix it: Select everything inside the folder and zip that selection. Name the file imsmanifest.xml, in lower case.

A ZIP inside the ZIP, and system files

What it means: Some portals wrap the package in a second archive, so the LMS finds a .zip and no manifest. __MACOSX and Thumbs.db are just clutter.

How to fix it: Upload the inner ZIP; the validator names it.

Well-formed XML and the right schema

What it means: One unescaped & or unclosed tag makes the manifest unreadable. The root must be <manifest> in the IMS Content Packaging namespace: imscp_rootv1p1p2.xsd and adlcp_rootv1p2.xsd for SCORM 1.2; imscp_v1p1.xsd, adlcp_v1p3.xsd, adlseq_v1p3.xsd, adlnav_v1p3.xsd and imsss_v1p0.xsd for SCORM 2004.

How to fix it: Write & as &amp;, re-export instead of editing by hand and keep the .xsd files next to the manifest.

SCORM version

What it means: <schemaversion> tells the LMS which runtime to start: 1.2, or CAM 1.3, 2004 3rd Edition or 2004 4th Edition. If it is missing or contradicts the namespaces, the LMS guesses and may hand the course the wrong API.

How to fix it: Make schemaversion and the namespaces agree.

Organizations, items and SCOs

What it means: Items point to resources through identifierref, and at least one resource must be a SCO: adlcp:scormtype="sco" in SCORM 1.2, adlcp:scormType="sco" with a capital T in 2004. Without a SCO the course opens but never reports. Duplicate identifiers break the links.

How to fix it: Use unique identifiers and mark the resource that talks to the LMS as a SCO.

Launch file

What it means: The launch file is the href of the SCO resource. If it is missing, learners get "page not found". Index.html instead of index.html works on Windows and fails on the Linux servers most LMSs run on. A leading / points outside the package.

How to fix it: Match the file name exactly, letter case included, as a path relative to the manifest.

Listed and missing files

What it means: Every <file href> should exist. Missing files become broken images, silent videos or a script error halfway through. Unlisted files are only a note. Paths that leave the package with ../ fail everywhere. xml:base is taken into account.

How to fix it: Re-export instead of deleting files by hand.

Spaces, special characters and backslashes

What it means: "Intro video.mp4" has to be URL-encoded, and servers do not all encode alike. Accented letters, # and ? break URLs. Backslashes are Windows separators some zip tools write into the archive.

How to fix it: Use lower-case letters, digits, hyphens and underscores, and a zip tool that writes forward slashes.

Pass mark and completion rules

What it means: adlcp:masteryscore (0–100) in SCORM 1.2 and imsss:minNormalizedMeasure (−1 to 1) in 2004 let the LMS set passed or failed from the score. Out-of-range values are errors. satisfiedByMeasure="true" without a minNormalizedMeasure means 1.0: learners need 100%.

How to fix it: Set the pass mark in the authoring tool, or leave it out when the course decides pass or fail itself.

Size, and packages that are not SCORM

What it means: The validator lists the largest files and warns above 100 MB, a common upload limit; yours depends on the platform and its settings. It also recognizes xAPI (tincan.xml) and cmi5 (cmi5.xml) packages and checks their basics: a well-formed file, activity IDs that are valid web addresses (IRIs), the launch file and, for cmi5, the completion and pass settings. AICC packages are recognized but not checked.

How to fix it: Compress videos and resize images. Upload xAPI, cmi5 or AICC to an LMS that supports them, or export SCORM.

Decoding LMS messages

What the LMS says and what usually causes it

  • Manifest not found, not a valid package

    Usual cause
    The folder was zipped, or a ZIP inside a ZIP
    Check that finds it
    Manifest at the root
  • Error parsing the manifest

    Usual cause
    An unescaped & in a title, a cut-off file
    Check that finds it
    Well-formed XML
  • Page not found when the course opens

    Usual cause
    Launch file name differs, often only in letter case
    Check that finds it
    Launch file
  • The course opens, nothing is recorded

    Usual cause
    No SCO, or the content cannot find the LMS API
    Check that finds it
    Organizations and SCOs, then the test player
  • Images missing in one LMS only

    Usual cause
    Spaces, special characters or case in paths
    Check that finds it
    Spaces and special characters
  • Learners fail although they did well

    Usual cause
    A pass mark in the manifest higher than intended
    Check that finds it
    Pass mark

The exact wording differs from one LMS to another.

What a validator cannot see

A valid package can still report the wrong thing.

The validator checks what an LMS reads at upload; it does not run the course. Whether the course finds the SCORM API, sends the score before the status and saves its place shows up only when it runs: open the same ZIP in the SCORM test player, then do a last run in your LMS with a test learner.

Packages from Scormbee

Every Scormbee export is built to pass these checks: one SCO, the manifest at the root, every file listed, and a pass mark only when the course has a graded quiz.

Your files never leave your computer

Files are read in your browser; nothing is uploaded to Scormbee or anyone else, and nothing is kept after you close the tab. That makes it safe to check confidential or client courses.

Questions

Frequently asked questions

Is the SCORM validator free?

Yes, with no account and no limit on packages. It runs entirely in your browser, so nothing is uploaded.

Does it check SCORM 1.2 and SCORM 2004?

Yes. It reads both, names the version and edition a package declares and flags a schemaversion that contradicts the namespaces. xAPI and cmi5 packages get basic checks of their own; AICC packages are reported as not SCORM.

Is this the ADL conformance test suite?

No. ADL's suite checks conformance in depth and is meant for tool and LMS vendors. This validator checks what most often breaks an upload or a launch in a real LMS, in seconds.

The package passes, but my LMS still rejects it. Why?

Platforms add their own rules: an upload size limit, one SCORM version only, limited support for several SCOs. Check the LMS documentation.

Can it repair the package for me?

It tells you what to fix and where. Fix the export settings so the next export is right too, or, if the source is gone, convert the package into an editable Scormbee course.

From the blog

Further reading

10 November 2026 · 8 min read

What an LMS Actually Records from a SCORM Course

What a SCORM course sends to your LMS: completion, pass/fail, score, time, bookmark, suspend data and interactions, plus why courses get stuck at incomplete.

Read →

Package beyond repair? Rebuild it.

Convert the course into an editable Scormbee project, fix it in the editor and export a clean SCORM 1.2 or 2004 package. The editor opens without an account.