SCORM 1.2 vs SCORM 2004: Which Should You Use in 2026?

Every authoring tool asks the same question at publish time: SCORM 1.2 or SCORM 2004? It is easy to assume "newer is better," but in the real world the answer depends entirely on your LMS and what you actually need to track. Here is the practical comparison for 2026.

The short version

• SCORM 1.2 — older (2001), simpler, supported almost everywhere. The safe default when you just need reliable completion and score reporting.
• SCORM 2004 — newer, more capable (richer status model, far larger bookmarking data, optional sequencing), but support across LMSes is uneven. Choose it deliberately, for specific needs.

Where SCORM 2004 genuinely wins

Bigger bookmarking / resume data

This is the most important practical difference. SCORM 1.2 limits the suspend_data field — the place a course stores resume state — to 4096 characters. Long, branching, or quiz-heavy courses blow past that and learners get kicked back to the start instead of resuming. SCORM 2004 allows roughly 64000 characters, which is why teams with resume problems often migrate. If your learners "keep losing their place," this is likely the cause.

Separate completion and success status

SCORM 1.2 collapses everything into a single lesson_status (passed, completed, failed, incomplete, and so on). SCORM 2004 separates "did they finish it" (completion_status) from "did they pass it" (success_status). For compliance training where finishing and passing are different facts you must report, that separation is valuable.

Sequencing and navigation control

SCORM 2004 can enforce ordering and prerequisites between SCOs. Powerful in theory — but, crucially, many LMSes implement sequencing partially or not at all. Behavior you rely on in one LMS may quietly not happen in another.

Where SCORM 1.2 still wins

• Compatibility — older and corporate LMSes universally support 1.2; some never fully implemented 2004.
• Simplicity — fewer moving parts means fewer ways for tracking to silently break.
• Predictability — what you test is what you get, because there is no optional sequencing layer behaving differently per LMS.

A decision guide

1. Does your LMS officially support SCORM 2004? If not, the decision is made for you — use 1.2.
2. Is your course long, branching, or quiz-heavy enough to overflow 4096 characters of resume data? If yes, lean 2004 to avoid lost progress.
3. Do you need to report "completed" and "passed" as separate facts? If yes, lean 2004.
4. Do you need enforced ordering between modules? Only choose 2004 for this if you have verified your LMS honors sequencing — otherwise prefer a simpler structure.
5. None of the above? Use SCORM 1.2 — it is the lowest-risk, most portable option.

What about xAPI and cmi5?

You will hear that xAPI or cmi5 makes this whole question obsolete. They are more modern and more capable for tracking learning outside a browser, but SCORM remains the most widely deployed standard, and the enormous installed base of SCORM content is not going anywhere soon. For most LMS-hosted courses in 2026, you are still choosing between 1.2 and 2004 — xAPI/cmi5 is a separate decision we cover elsewhere.

Switching versions on an existing package

If you already published in 1.2 and need 2004 (or vice versa) but no longer have the source file, you are changing the manifest and the runtime calls of a build artifact — not something to do casually by hand. The most common real reason to switch is the 4096-character resume limit, which we dig into in our suspend_data article.

Newer is not automatically better. The right SCORM version is the one your LMS fully supports and that tracks exactly what you need — nothing more.

Check and adjust your package without the source

ScormEdit reads your package’s manifest and tells you which SCORM version it targets, whether your LMS-critical fields are set sensibly, and whether you are at risk of the 1.2 resume limit — all in the browser, from the published .zip, with no authoring source required.