Free SCORM Validator
Upload a SCORM package and check for common manifest, packaging, metadata, and LMS compatibility issues.
Launch SCORM ValidatorOpens in a new tab. No account required.
What this SCORM validator checks
Manifest structure
Validates that imsmanifest.xml exists, is well-formed XML, and declares the correct SCORM version and metadata.
Packaging & file references
Checks for required files, correct folder structure, and that every referenced asset is actually present in the package.
Metadata completeness
Flags missing or invalid title, description, identifier, and lifecycle fields that LMSs need for cataloging.
LMS compatibility signals
Detects common patterns that cause import failures or incomplete progress tracking in SCORM 1.2 and SCORM 2004 players.
Sequencing & navigation rules
For SCORM 2004 packages, inspects sequencing rules for dead ends, missing prerequisites, and inconsistent control modes.
Cross-domain & API hints
Surfaces potential issues with API discovery, cmi model usage, and cross-frame communication that break runtime behavior.
SCORM 1.2 vs SCORM 2004 support
SCORM 1.2
- imsmanifest.xml with 1.2 schema reference
- Runtime API: LMSInitialize, LMSFinish, LMSSetValue, LMSGetValue
- Core data model: cmi.core.lesson_status, cmi.core.score.raw
- Limited sequencing — mostly next/previous navigation
- Widest LMS compatibility, but stricter data model rules
SCORM 2004 (4th Edition)
- imsmanifest.xml with 2004 schema reference
- Runtime API: Initialize, Terminate, SetValue, GetValue
- Expanded data model: cmi.completion_status, cmi.success_status, cmi.score.scaled
- Rich sequencing & navigation rules (CAM & SN specifications)
- Better progress and completion reporting, but more complex packaging
Common SCORM errors
Missing or malformed imsmanifest.xml
Every SCORM package must have a valid manifest at the root. A missing file, bad XML, or wrong schema reference usually blocks the import entirely.
Broken relative file paths
Resources in the manifest must point to files that exist inside the package. Moved or renamed assets create 404s during launch.
Version mismatch between manifest and API calls
A package claiming SCORM 2004 but calling the old 1.2 API (LMSInitialize) will fail or record incomplete data in modern players.
Invalid cmi field names or values
Writing to unsupported data model elements or sending non-numeric values to score fields can cause LMS errors and lost progress.
Sequencing dead ends or loops
SCORM 2004 packages with badly defined sequencing rules can leave learners stuck, skip required content, or repeat indefinitely.
Missing launch page or index.html
If the manifest's launch resource is not present or misnamed, the course won't start after the learner clicks it in the LMS.
How to test a SCORM package before uploading to an LMS
Upload the validator
Drop your .zip SCORM package into the free SCORM Validator. It scans the manifest, packaging, and metadata without needing an LMS.
Read the report
Review every failed or warning-level check. The validator explains why each issue matters and where to look inside the package.
Inspect the manifest manually
Unzip the package and open imsmanifest.xml in a text editor. Confirm the schema version, identifier, resource hrefs, and metadata all match.
Test in a SCORM player
Upload the package to SCORM Cloud or a staging LMS. Launch the course, complete a few interactions, and check that progress and completion report correctly.
Fix and re-validate
Correct the flagged issues, repackage the course, then re-run the validator and SCORM player tests before releasing to production.
Monitor for drift over time
Product changes, pricing updates, and policy revisions can make correct SCORM content factually stale. Continuity Intelligence watches the source for you.
FAQ
Need deeper LMS and course audits?
A manifest check catches packaging issues. Continuity Intelligence monitors every slide, video, and PDF for drift against the live sources your content depends on.
Talk to Sales