Why does SCORM 2004 have editions?
SCORM 2004 3rd vs 4th Edition is a question about revisions of one standard, not two standards. ADL published SCORM 2004 in editions: 2nd Edition in 2004, 3rd in 2006 and 4th in 2009, the final one. Each clarified the last. 4th Edition is the most complete, but 3rd remains widely used and widely accepted.
The editions exist because SCORM 2004 introduced a large new area, sequencing and navigation, that proved hard to implement consistently. Early LMS implementations disagreed on how the rules should behave, so ADL issued revised editions that tightened the wording, fixed ambiguities and added a few capabilities. The core idea did not change between them: the same API, the same split of completion and success, the same manifest structure.
That matters when you choose an export setting. Picking an edition is a compatibility decision about the destination platform, not a choice between fundamentally different technologies. If you are still deciding between SCORM 1.2 and 2004 at all, start with which SCORM version should I use.
What changed in each edition
The differences are smaller than the edition numbers suggest. The ones that most often affect real courses:
| Edition | Year | What it mainly did |
|---|---|---|
| 2nd Edition | 2004 | Corrected and clarified the original 2004 release. Now rarely targeted; most platforms expect 3rd or 4th. |
| 3rd Edition | 2006 | Substantial clarification of sequencing and navigation behaviour and of the run-time data model, so LMSs would implement them more consistently. |
| 4th Edition | 2009 | Further sequencing clarifications, plus a few additions: a much larger cmi.suspend_data limit, shared data stores, and jump navigation. |
The 4th Edition additions are the ones most likely to change how a course behaves:
- Larger suspend data. The
cmi.suspend_datalimit rose from 4,000 characters in 3rd Edition to 64,000 in 4th. Courses that store a lot of state — long bookmarks, many answers, branching history — can need this. - Shared data stores. 4th Edition added
adl.data, a way for SCOs in the same course to share data buckets declared in the manifest. Earlier editions had no standard way to do this. - Jump navigation. 4th Edition added a navigation request that lets content move the learner to a specific activity, which earlier editions did not provide.
Beyond these, the editions are close. Most single-SCO courses that do not use sequencing behave identically whichever of 3rd or 4th they declare. Where you need a specific edition-level detail, the ADL documentation for that edition is the reference.
How to tell which edition a package is
Open imsmanifest.xml and look in the metadata block near the top. The schemaversion element declares the version and edition:
<metadata> <schema>ADL SCORM</schema> <schemaversion>2004 4th Edition</schemaversion> </metadata>
You will typically see 2004 3rd Edition or 2004 4th Edition. A value of 1.2 means the package is SCORM 1.2, not 2004 at all; older 2004 packages may show CAM 1.3, which refers to the 2nd Edition era. The schema files bundled in the zip (the .xsd files) also differ between editions, which is another quick check if the metadata is missing.
The declared edition is what the LMS uses to decide how to treat the package, so it should match what the content actually does. A course that writes 4th Edition elements while declaring 3rd can fail validation or have those writes rejected.
Will my LMS accept 3rd or 4th?
Most current LMSs that support SCORM 2004 accept both 3rd and 4th Edition. Support for 2nd Edition is patchier, and some platforms treat it as legacy. A few platforms state support for "SCORM 2004" without naming an edition; in practice that usually means 3rd and 4th, but it is worth confirming.
Support also comes in degrees. An LMS can accept a 4th Edition upload and still implement sequencing less completely than the specification describes, which only matters if your course depends on sequencing rules. Ask the vendor which edition they test against, and test a package that uses the features you rely on rather than a single-page sample.
Watch the suspend data limit in particular. A platform that accepts a 4th Edition package but enforces the older 4,000-character limit will truncate long bookmarks without warning. A test that resumes a nearly finished course is the quickest way to find out.
Which edition should you export?
Use this order:
- If the destination names an edition, use it. The platform's requirement beats any general advice.
- Otherwise, export 4th Edition if the platform accepts it. It is the final edition, it has the largest suspend data limit, and it is what most current platforms test against.
- Fall back to 3rd Edition if a platform has trouble with 4th, or if you are matching an existing library of 3rd Edition courses.
- Avoid 2nd Edition for anything new.
And if the platform's SCORM 2004 support turns out to be unreliable, SCORM 1.2 is still the most widely supported option, at the cost of a single combined status and a 4,096-character suspend data limit. The trade-offs are laid out in SCORM 1.2 vs SCORM 2004.
Where SCORM Central fits
SCORM Central converts files you already have — PDF, PowerPoint, Word, or video — into SCORM 1.2, SCORM 2004, cmi5, or xAPI, and shows you the manifest, the full runtime log, and a conformance report on every build, so you can see exactly what a package will report before an LMS does. See how it works, or start with one file.