SCORM vs xAPI vs cmi5: The Definitive 2026 Comparison

TL;DR. In 2026, SCORM 1.2 still dominates with ~71% of new e-learning packages, despite being 25 years old. SCORM 2004 4th Edition holds ~18%, xAPI / cmi5 together ~6%, and proprietary HTML5 ~5%. The right standard depends on your LMS, content complexity, and AI integration goals. This guide compares all four side-by-side with concrete decision criteria.

The four standards at a glance

SCORM 1.2: the workhorse

Released in 2001 by ADL (Advanced Distributed Learning Initiative), SCORM 1.2 was the first widely-adopted standard for portable e-learning. It defines: a content package format (ZIP with imsmanifest.xml), a runtime API (JavaScript bridge between the SCO and the LMS via API.LMSGetValueetc.), and a data model (cmi.core.lesson_status, cmi.core.score.raw, etc.).

Why it survived 25 years: SCORM 1.2 is simple. Every LMS on the planet supports it. Every authoring tool exports to it. The data model is small enough to be memorable. If you want maximum compatibility and zero deployment surprises, SCORM 1.2 is the default choice in 2026.

Limitations:no sequencing rules (the content decides its own navigation), no rich verb vocabulary (just "completed" / "passed" / "failed" with score), no offline support, no mobile-native concepts, no support for multi-activity progress aggregation.

SCORM 2004: more power, more complexity

SCORM 2004 introduced sequencing and navigation rules (IMS Simple Sequencing), allowing course authors to define prerequisites, conditional branching, and mastery thresholds at the manifest level. The data model expanded to cmi.completion_status and cmi.success_status (decoupling completion from passing), plus richer interaction tracking.

Editions: 2nd (2004), 3rd (2006), and 4th (2009). Most modern tools target 4th Edition, which fixed several sequencing bugs from earlier editions. In our corpus, 4th Edition accounts for ~18% of all SCORM uploads in 2026 — and effectively all SCORM 2004 in active use.

Limitations:sequencing rules are notoriously hard to debug. Many LMSes implemented IMS Simple Sequencing inconsistently. If your course doesn't need branching, sticking with SCORM 1.2 saves headaches.

xAPI (Tin Can): the rebellion

xAPI was Rustici Software's response to two SCORM limitations: it required an LMS (no offline / mobile learning) and it had a fixed data model that couldn't track non-traditional learning (simulations, social, microlearning).

xAPI introduces the concept of statements: tuples of actor / verb / object("Maria completed the fire drill module") sent to a Learning Record Store (LRS) over HTTP. Verbs and objects are extensible (you can define your own vocabulary). This makes xAPI a great fit for tracking field training, simulations, social learning, and informal knowledge.

Why adoption is slow:xAPI doesn't define a content packaging format. There's no equivalent of imsmanifest.xml. Most LMSes still don't embed an LRS. Authoring tools have to choose between generating xAPI (no clear LMS target) or SCORM (guaranteed compatibility). Result: in 2026, pure xAPI is still <5% of new e-learning packages.

cmi5: xAPI inside SCORM's wrapper

cmi5 (2016) is ADL's attempt to fix the xAPI adoption problem. It marries xAPI's flexible statement model with SCORM-style content packaging: a ZIP with a cmi5.xmlmanifest, an Assignable Unit (AU) launch URL, and a defined set of verbs ("launched", "completed", "passed", "failed", "abandoned", "waived", "terminated") plus extensions.

The case for cmi5: if your LMS supports it, cmi5 gives you the best of both worlds — proper LMS launching, modern data model, mobile-friendly, offline-capable. Tools like PandaSuite have natively adopted cmi5. Major LMSes (Cornerstone, Workday Learning, Moodle 4.x) added cmi5 support 2023-2025.

2026 reality:still <3% market share. Most LMSes process cmi5 but tools don't generate it by default. We expect 12-15% by end-2027 as LXP adoption pushes content vendors toward xAPI-native formats.

Decision criteria

Use this decision tree to pick your standard:

• Need maximum LMS compatibility? → SCORM 1.2 (default, still safest in 2026)
• Need conditional branching / mastery sequencing? → SCORM 2004 4th Edition
• Need to track learning outside an LMS (mobile field work, simulation)? → xAPI to an LRS
• Modern LXP + proper LMS launch + xAPI flexibility? → cmi5 (only if your LMS supports it — confirm before committing)
• Building for AI / RAG pipelines? → SCORM 1.2 + dedicated extraction (the format is irrelevant; what matters is the extractor quality)

Conversion paths

Most authoring tools can export the same content to multiple standards:

• Articulate Rise 360 → SCORM 1.2, SCORM 2004, xAPI, cmi5, HTML5
• Articulate Storyline 360 → SCORM 1.2, SCORM 2004, xAPI, AICC
• iSpring Suite → SCORM 1.2, SCORM 2004, xAPI
• Adobe Captivate → SCORM 1.2, SCORM 2004, xAPI

If you already have a SCORM library and want to migrate to xAPI / cmi5, your first step is extracting the content out of SCORM. SCORM Converter exports SCORM packages to clean Markdown / Word / PDF, which can then be re-imported into any authoring tool that exports cmi5.

References

• SCORM Explained — Rustici Software
• cmi5 Specification
• xAPI Specification (ADL)
• The State of SCORM 2026 Report
• SCORM 1.2 vs SCORM 2004: Key Differences