Free SCORM Manifest Validator — Catch Compliance Issues Before Upload — free LMS tool

Free Tool

Free SCORM Manifest Validator — Catch Compliance Issues Before Upload

Paste your imsmanifest.xml and get a full SCORM compliance report. No upload — validation runs entirely in your browser.

Last Updated: May 2026

How It Works

1Extract imsmanifest.xml from the root of your SCORM .zip package
2Paste the XML into the validator below
3Get a full report: detected SCORM version, organization/resource/SCO counts, and every structural issue or warning grouped by severity
4Fix the errors flagged before uploading to your LMS — save hours of debugging failed package uploads

Paste your imsmanifest.xml

Extract imsmanifest.xml from the root of your SCORM .zip and paste its contents below. Validation runs entirely in your browser — nothing is uploaded.

Why Use This Tool

100% Client-Side

Validation runs in your browser. Your course content never leaves your machine — important for confidential corporate training.

Cites the Spec

Every error references the IMS CP / SCORM spec section so you can verify the rule and explain it to your team or vendor.

Both SCORM Versions

Auto-detects SCORM 1.2 and SCORM 2004 (2nd, 3rd, 4th edition). Applies the right validation rules for the detected version.

Frequently Asked Questions

What does this validator actually check?

Structural rules from IMS Content Packaging 1.1.4 and the SCORM 1.2/2004 specs: manifest identifier presence, organizations and default org reference, resource identifier uniqueness, adlcp:scormtype validity, SCO href presence, dangling identifierref lookups, file path traversal, absolute URLs, and metadata schema/schemaversion presence.

Why does my SCORM package upload fail to my LMS?

Most upload failures come from: (1) missing or duplicate resource identifiers, (2) <item identifierref> pointing to a resource that doesn't exist, (3) absolute URLs in <file href>, (4) missing adlcp:scormtype on SCO resources, or (5) malformed XML. This validator surfaces all five.

Does this work for cmi5 or xAPI packages?

No — this validator targets SCORM 1.2 and SCORM 2004 manifests specifically. cmi5 has a different course-structure file (cmi5.xml) and xAPI packages don't require a manifest at all.

Why not just upload the whole .zip?

Two reasons: (1) confidentiality — corporate compliance and product training packages are often sensitive, so we keep everything local, and (2) the manifest is where 90% of upload failures originate, so validating it covers the most common pain point without needing zip parsing in your browser.

Ready to level up your training?

Start building your academy today — 14-day free trial, no credit card required