SCORM Package Validator

Check a SCORM course ZIP for manifest, resource and launch-path errors before you import it into your LMS.

Drop your SCORM ZIP

Choose ZIP file

or drop it anywhere in this box

One course ZIP · SCORM 1.2 or a supported SCORM 2004 manifest
The course code is read, never executed

Free: 3 checks a day, ZIP up to 10 MB, no account neededPro: ZIP up to 128 MB, up to 200 checks a day

See a sample report Open the validator Plans and prices

WHAT YOU GETSample data

Sample report: two package defects block a clean LMS import

Resources: 64
Manifest issues: 2
Static API refs: 18

Error
Manifest resource missingimsmanifest.xml · res-17 points to media/intro.mp4, which the ZIP does not contain
Error
Launch file path invalidSCO-4 resolves outside the normalized package root
Limit
Runtime behaviour not testedLMS API calls are listed from the files, not run

Download package

HTML report
Resource inventory CSV
Manifest summary
Static API-call inventory
JSON
Hash manifest

Fictional course data. Your own ZIP is uploaded only when you start a check in the validator.

What the validator checks

ManifestReads imsmanifest.xml for SCORM 1.2 or a supported SCORM 2004 version.
ResourcesEvery file the manifest references must exist in the ZIP.
Launch pathsEach SCO launch file must resolve inside the package root.
LMS API referencesLists the runtime API calls found in the course files, as a static inventory.

A clean result means the packaging and linkage pass the pinned rule set. It does not prove that tracking works at runtime or that every LMS will accept the course, because each LMS importer adds its own requirements.

Clear answers

SCORM Package Validator FAQ

Which packages are supported?

A single course ZIP up to 128 MB, using SCORM 1.2 or a supported SCORM 2004 manifest. The archive is expanded within limits of 10,000 entries and 1 GB.

Is the course run during the check?

No. Course JavaScript is never executed. The manifest, the resource list and the launch paths are read statically.

What kind of defect does it catch?

Broken linkage, for example a resource in imsmanifest.xml pointing at media/intro.mp4 that the ZIP does not contain, or an SCO launch file resolving outside the normalized package root.

What is the static API-call inventory?

A list of the LMS runtime API references found in the course files. It is evidence that those strings exist, not proof that tracking works once the course runs.

Does a clean result mean every LMS will accept the course?

No. Packaging and linkage are checked against the pinned rule set. Individual LMS importers add their own requirements and runtime behaviour, which this report does not cover.

Details: limits, file handling and how a job runs

Limits

Input: 1 ZIP file
Free tier: 3 checks a day, ZIP up to 10 MB. Failed jobs are never counted.
Largest ZIP: 128 MB (Pro)
Archive: 10,000 entries · 1 GB expanded · 128 MB per member
File handling: Unfinished draft kept 2 hours · encrypted result kept 24 hours
Engine: scorm-package-validator-v4
Rule set: scorm-ims-adl-package-linkage-authentication-2026-08-31

How a job runs

Confirm the job. The file name and settings stay visible before the SHA-256 hash of your ZIP is accepted.
Isolated processing. A one-job sandbox without network access receives only this job. It cannot reach accounts, queues, encryption keys or other customers' storage.
Static reading. The manifest, resources and launch paths are read. Uploaded course code is not executed.
Download. Every output file's hash is listed in the manifest that comes with the result.

Who it is for

Instructional designers, LMS teams and e-learning vendors.

Security model Access and pricing

Available now

Check your SCORM ZIP before the LMS import.

3 free checks a day for ZIP files up to 10 MB, no account needed. Pro handles up to 128 MB and up to 200 checks a day.

Open the validator Find another tool