Free tool · nothing uploaded

SCORM Package Checker & Inspector

Drop a SCORM, cmi5, or xAPI .zip to see what’s inside — standard, authoring tool, outline, files, scoring — plus a diagnostic for 40-plus tracking faults. A free SCORM validator and viewer that runs online in your browser; nothing is uploaded.

Drop a SCORM .zip here

or choose a file from your computer

Analyzed in your browser with JavaScript. No upload, no server, no data leaves this page.

What it does

Inspect the package, then diagnose it

It opens the .zip, shows what’s inside, and checks it against 40-plus known SCORM faults — honest about the runtime causes it can’t see.

Identify

  • SCORM 1.2 / 2004, cmi5, xAPI or AICC
  • The authoring tool — Storyline, Rise, Captivate…

See inside

  • Course outline — modules, SCOs vs assets, titles
  • Every file, plus mastery scores, objectives & thresholds

Diagnose

  • 40+ faults — manifest, paths, case, launch, tracking
  • The runtime causes to verify in your LMS — named, not hidden

SCORM checker FAQs

Checking & inspecting SCORM packages

How do I check a SCORM package before uploading it to my LMS?

Drop the .zip onto this page. It opens the package in your browser, reads imsmanifest.xml, and reports the SCORM version, the course outline, the files, the scoring rules, and any defect that would break tracking — in a few seconds, with no LMS and no upload needed.

Is it safe — does my file get uploaded anywhere?

Nothing is uploaded. The analysis runs entirely in your browser with JavaScript; the package never leaves your device, and there is no server to send it to. That means you can safely inspect confidential or client courses.

How can I tell if my package is SCORM 1.2, SCORM 2004, cmi5, or xAPI?

The inspector reads the manifest’s schemaversion and XML namespaces and labels the exact standard — including the 2004 edition (2nd, 3rd, or 4th). A package with a cmi5.xml is cmi5, a tincan.xml is xAPI/Tin Can, and AICC descriptor files (.crs/.au/.des/.cst) are AICC. It flags a package uploaded to the wrong slot, too.

Can I see what’s inside a SCORM file — the course structure and files?

Yes. The Course outline tab shows the full module tree with each item’s title, whether it’s a trackable SCO or a static asset, and its launch file. The Files tab lists every file by type and size and flags anything missing or orphaned. The tool also identifies the authoring tool (Storyline, Rise, Captivate, iSpring, Lectora and more) where it can.

Why won’t my SCORM package upload to Moodle?

The usual causes are all visible in the package: imsmanifest.xml zipped inside a subfolder instead of at the root, a double-zipped archive, a launch file that isn’t actually in the zip, or an xAPI/cmi5 package sent to a SCORM slot. The diagnostics flag each of these and tell you the fix. If it still won’t track after that, it’s usually a runtime cause — see our SCORM tracking repair.

What does “not a valid SCORM package” actually mean?

It means the LMS couldn’t find a usable imsmanifest.xml at the root — because the manifest is nested in a subfolder, the file is double-zipped, the XML is malformed, or it’s really an xAPI/cmi5/plain-web package. The checker tells you which of these it is and how to fix it.

Want the manual method? Read our full walkthrough, Why your SCORM course isn’t tracking completions — the 7 real causes.

Fix what the package shows, then if it still won’t track, we’ll find the runtime cause and prove the fix with logs.

When self-serve isn’t enough

Free SCORM diagnosis, flat-rate repair.

We run your package in SCORM Cloud with full API logging, name the exact cause, and repair it — verified with logs, at a fixed per-package price.

See SCORM tracking repair

Want the full manual method behind this tool? Read Why your SCORM course isn’t tracking completions — the 7 real causes.