Free SCORM package checker
Find out why a SCORM package won’t upload, load or track in Moodle: the manifest, missing files, capitalisation mismatches, Flash, insecure links and every web link inside.
The usual reasons SCORM fails in Moodle
The manifest
imsmanifest.xml present, at the top of the zip, valid, with its SCORM version and launch file.
Missing and miscapitalised files
Files the manifest and pages refer to that are missing, or whose capitals don’t match.
Links
Every web link in the package, and insecure http:// links that browsers block inside Moodle.
Outdated content
Leftover Flash files, very large files and file names that break on some servers.
About SCORM in Moodle
Is my SCORM package uploaded anywhere?
No. The package is opened and checked entirely in your browser. Nothing is sent to any server, so you can safely check confidential courses.
Why does Moodle say my file is not a valid SCORM package?
Most often the package was zipped with its folder, so imsmanifest.xml is not at the top of the zip. Zip the contents of the folder instead, or export the course again as SCORM 1.2 or 2004.
Why does a course work on my computer but not in Moodle?
A common cause is file names whose capitals don't match the references in the course: Windows and macOS ignore the difference, but Moodle's file storage does not. The checker lists these.
Can the checker test web links in the course?
It lists every web link it finds. Browsers cannot test other websites from a web page, so open them to check, or use Broken Link Scanner, which checks every link in every course and SCORM package in Moodle automatically.
Which authoring tools are supported?
Any SCORM 1.2 or SCORM 2004 package, including Articulate Storyline, Rise 360, Adobe Captivate and iSpring.
Check every package, automatically
Broken Link Scanner checks every course and SCORM package on your Moodle site, including links inside Storyline, Rise and Captivate, on a schedule.