SCORM package validator
Your LMS rejects a package without saying why? Drop the ZIP: the tool compares what the manifest declares with what the archive actually contains, and names the problem.
Local analysis — your file never leaves your browser
What is checked
Nine checks, and why they matter
The tool does not validate against the XSD schema, and that is deliberate: a perfectly schema-compliant manifest still fails if a resource is missing. What matters is the consistency between the declaration and what the archive really contains.
| Check | What happens if it fails |
|---|---|
| The manifest is at the root of the zip | The LMS rejects the package on import, usually without a useful message. Cause number one. |
| The manifest is well-formed XML | Import refused. One unclosed tag or one unescaped “&” is enough. |
| The SCORM version can be identified | The LMS does not know which runtime to serve and refuses the upload. |
| The default organization exists | The package imports, but the table of contents stays empty. |
Every identifierref points to a resource | The learner clicks in the table of contents and nothing launches. |
| Every declared file exists in the archive | Blank screen, missing image or video not found mid-module. |
At least one resource is of type sco | The module displays but reports neither progress nor score: unusable. |
| File name case matches | Works on your Windows machine, breaks on the LMS's Linux server. |
| No resource is loaded from an external site | The package is not self-contained and breaks as soon as the remote site changes. |
The most common case
“My LMS rejects my SCORM package”
Nine times out of ten, the manifest is not at the root of the archive. It is a compression mistake, not a design one: you right-click the course folder and choose “Send to → Compressed folder”. The zip then contains the folder, and the LMS, which looks for imsmanifest.xml at the top level, finds nothing.
The right move: open the folder, select its contents — the manifest and the course files — and compress that selection. The manifest must sit at the top level of the zip, next to the other files, not in a subfolder.
Next, in order of frequency: files declared in the manifest that the export left out, identifierref references to resources deleted between two versions, and resources declared as asset when they should be sco — in which case the module displays perfectly but never reports a single result.
If your package passes this check and the LMS still rejects it, the problem lies elsewhere: maximum upload size, MIME type restrictions, or a requirement specific to the platform. And if it imports but tracks nothing, the SCORM tester shows what the package actually does at runtime.
FAQ
About this tool
No. The archive is opened and analysed by your browser, on your machine. No data is transmitted — you can check confidential content without any special precaution. You can even go offline once the page has loaded: the tool keeps working.
No, and that is a choice. Schema compliance does not guarantee that a package works: a flawless manifest still fails if a declared resource is missing. The tool checks the consistency between what the manifest announces and what the archive contains — which is what decides whether the package will work.
SCORM 1.2 and SCORM 2004, all editions. The version is inferred from the ADL namespaces in the manifest and from the schemaversion element. If neither settles it, the tool says so: that is a defect in itself, since the LMS will have the same problem.
Check the “resource of type sco” line. An asset displays without ever talking to the platform: no progress, no score, no time spent. It is a common mix-up in hand-made exports. The tester will show you exactly what the content sends.
Gladly. Write to contact@cvbsp.fr describing the case you ran into, ideally with the manifest involved.
Because Geduk is a French LMS, built for French training organizations. These two tools are universal, so they have an English version; the product pages do not, at least for now.
Who makes this
Free tools from
a French LMS
These two tools are made by Geduk, a learning management system published by CVBSP on Reunion Island, France. They are free, need no account, and keep no record of what you test.
The rest of the site is in French. Geduk is built for French training organizations, so its product pages, pricing and documentation are in French only. The SCORM tester and validator are universal, which is why they come in English too. Questions in English are welcome at contact@cvbsp.fr.