Is the package valid?
The imsmanifest.xml is checked for the problems that stop an import: a missing launch file, files the manifest lists but the zip doesn't have, a missing version. Errors are in plain English.
Upload a SCORM zip and watch every runtime call it makes — Initialize, SetValue, Commit — with manifest checks alongside. Free, in the browser, no account.
The imsmanifest.xml is checked for the problems that stop an import: a missing launch file, files the manifest lists but the zip doesn't have, a missing version. Errors are in plain English.
Launch the course and see the full call log per attempt: every SetValue, every Commit, in order, with the values the LMS would receive.
Completion, success, score, total time, and the bookmark, exactly as an LMS would have stored them.
A real run of a two-file SCORM 1.2 package through the tester: the attempt state on the left, the full runtime call log on the right — every call, its value, and its return code, in order.
Score written before status, a commit straight after, exit set before LMSFinish — the healthy pattern from the log examples below. Manifest validation runs on upload, before any attempt, and reports in the same place.
Most import failures are manifest failures, and they happen before a learner ever launches the course. The tester reads imsmanifest.xml and checks what an LMS checks first: that it is well-formed XML at the root of the zip, that it declares a SCORM version, that it has an organization, a launchable item and a resource, that the launch file exists, and that every file it lists is in the zip. It reports what is wrong in words rather than XSD error paths. The usual culprits: a resource href that points at a file not in the zip, a manifest nested inside a folder instead of sitting at the root, or a missing schemaversion. Any one of them stops the import cold. The manifest, explained covers the structure in detail.
This is the part no authoring-tool preview shows you. The tester launches the course against a real SCORM runtime and records the conversation: every Initialize, GetValue, SetValue, Commit and Terminate, in order, with the exact string values that would reach an LMS and the return code for each call. A course that never sets cmi.completion_status, or sets it and then never commits, is obvious in ten seconds in a log and invisible everywhere else.
The log answers this if you know what to look for: is score written before status, so a platform that evaluates a mastery score at the moment status arrives has the number it needs; is there a Commit after the status writes, before the fragile exit; is cmi.suspend_data inside the cap for the declared version — 4,096 characters for SCORM 1.2, 64,000 for 2004. The tester shows you the calls and the stored values; automatic checks for these patterns are coming soon.
Two logs from courses that behave identically for the learner. One reports; one does not.
Healthy. Score before status, a commit straight after, exit set before termination:
SetValue("cmi.score.scaled", "0.84") → "true"
SetValue("cmi.success_status", "passed") → "true"
SetValue("cmi.completion_status", "completed") → "true"
Commit("") → "true"
SetValue("cmi.exit", "normal") → "true"
Terminate("") → "true"
Broken. Status written first, no commit before the learner closes the tab, and a final write that lands after the session has already closed:
SetValue("cmi.completion_status", "completed") → "true"
SetValue("cmi.score.scaled", "0.84") → "true"
Terminate("") → "true"
SetValue("cmi.score.raw", "21") → "false" error 133: store after termination
Once you can read the log, the same discipline applies to every package you ship. The SCORM API explained walks through each method and the error codes worth knowing, and testing a SCORM package before upload is the full pre-flight checklist.
| Approach | What it tells you | What it costs you |
|---|---|---|
| Authoring-tool preview | That the content renders | Nothing — but it stubs the SCORM API, so it cannot fail on a missing commit or a late write |
| Upload to the real destination LMS | The truth, for that one platform | You need access, and a failure is often already a customer-visible one |
| A hosted sandbox with an account | Runtime behaviour against a reference player | Signup, and usually a registration or upload allowance |
| Browser developer tools | Whatever you instrument yourself | You have to wrap the API object by hand and know what to look for |
| This tester | Manifest validity plus the full runtime call log | Nothing, and no account — results are not saved between sessions |
None of these replaces testing on the destination platform when you know what it is. What a pre-flight check buys you is that the package is already correct when it gets there, so a failure points at the platform rather than at your zip — and platform quirks are their own subject, covered in runtime behaviour profiles, which the Pro and Business plans can replay a package against.
Most SCORM problems only show up at runtime, in someone else's LMS, after the course has shipped. A five-minute check of the actual call log catches lost completions, missing scores, and bookmark failures while they are still your problem to fix quietly — not a support ticket from a customer.
The tester runs in the guest workspace — nothing to install and no signup. If you want to keep the results, or fix the source file and rebuild the package, that is what the full product does. Replay against saved LMS profiles comes with Pro and Business.
Upload a PowerPoint, PDF, or video you already have, build it as a SCORM package, and run it in the tester to see every call it makes.
→ upload handbook.pdf rendering … 86 pages course … 1 lesson, 86 pages building … SCORM 2004 4th Ed validating … 0 errors ✓ handbook-scorm2004.zip
You will be taken to app.scormcentral.com to sign in.
First month $1 on monthly Starter, once, on your first paid plan. Then $19.99 a month. A card is required at checkout. Cancel any time from Billing > Manage billing. You will be taken to app.scormcentral.com to create your account. Already have one? .