SCORM vs xAPI vs cmi5: The Definitive Comparison (2026)
Side-by-side technical evaluation of SCORM 1.2, SCORM 2004, Experience API (Tin Can), and cmi5 standards.
Executive Overview: The Four Major Standards
E-learning technology has evolved across four distinct generations over the past 25 years. Despite newer standards entering the market, industry telemetry shows that over 90% of global corporate training launches still run on SCORM 1.2 and 2004 due to deep enterprise LMS inertia.
1. SCORM 1.2 (Published 2001)
The universal baseline. Every Learning Management System in existence supports SCORM 1.2. It relies on a JavaScript API adapter (API) living in the browser window to exchange a simple data model. Limited to 4,096 characters for suspend data, but unmatched in global compatibility.
2. SCORM 2004 (4th Edition)
Introduced the Content Aggregation Model (CAM), expanded suspend data to 64,000 characters, separated completion from success status, and added sophisticated Sequencing and Navigation (SN) rules allowing branched learning paths.
3. xAPI / Experience API / Tin Can (Published 2013)
Broke learning free of the browser window. Uses RESTful HTTP requests passing JSON statements formatted as Actor-Verb-Object to a Learning Record Store (LRS).
4. cmi5 (Published 2016)
Known as "the best of both worlds." cmi5 uses xAPI as its messaging protocol but adds strict rules for LMS launching, package structure, session authorization, and reporting.
Stop Sending Raw SCORM Files to Clients
Deploy ultra-thin 4.2KB cryptographic proxies into any enterprise LMS. Maintain instant remote revocation, seat quotas, and zero-PII compliance.