Standards explained
SCORM 1.2 vs SCORM 2004 vs xAPI vs cmi5: Which Standard Should You Use?
Compare SCORM 1.2, SCORM 2004, xAPI, and cmi5 by compatibility, tracking, sequencing, portability, and practical LMS use cases.
SCORM fundamentals11 min read
SCORM 1.2, SCORM 2004, xAPI, and cmi5 solve related but different interoperability problems. The right choice depends on the systems that must accept the course, the learning activity you need to record, and how much launch and session behavior you want the standard to define.
Most teams can treat the standard as an export decision. Keep the editable source in the authoring tool, publish the format required by the destination, and validate the result in the real LMS.
Key takeaways
- SCORM 1.2 remains the safest choice for the broadest legacy LMS reach.
- SCORM 2004 improves status, interaction data, suspend data, and sequencing.
- xAPI records a wider range of learning experiences but does not define a complete LMS launch workflow by itself.
- cmi5 combines xAPI statements with rules for LMS-launched course sessions.
Compare the standards by delivery model
SCORM packages web content for an LMS and defines a browser-based runtime conversation. xAPI defines statements that can describe learning inside or outside an LMS. cmi5 uses xAPI while adding launch, identity, session, and course-structure rules for LMS delivery.
| Standard | Best fit | Main advantage | Main constraint |
|---|---|---|---|
| SCORM 1.2 | Maximum LMS compatibility | Very widely supported | Limited status, interaction, and suspend data |
| SCORM 2004 | Richer LMS-hosted courses | Sequencing and stronger runtime model | Implementation is more complex |
| xAPI | Learning across apps and contexts | Flexible activity statements | Requires an LRS and launch decisions |
| cmi5 | Modern LMS-launched packages | xAPI data with session rules | Smaller installed base than SCORM |
When to choose SCORM 1.2
Choose SCORM 1.2 when the package must work across the broadest possible set of learning platforms or when the receiving LMS explicitly requests it. It reliably covers the core outcomes most programs need: launch, completion or lesson status, score, time, and resume data.
Its compromises appear in richer courses. SCORM 1.2 combines completion and success in one lesson-status field, provides a smaller suspend-data allowance, and has a less expressive interactions model. Authors should keep runtime state efficient and test exactly how the LMS maps statuses into reports.
When to choose SCORM 2004
SCORM 2004 separates completion from success, increases the defined suspend-data capacity, supports richer interaction information, and adds sequencing and navigation. It is useful when the course needs to report “completed but failed,” preserve more state, or control progression across several SCOs.
Ask which edition the LMS supports and test the sequencing behavior. The later third and fourth editions resolved ambiguities, but the specification is more involved than SCORM 1.2. A simple single-SCO course does not become better merely because it uses the newer label.
When xAPI is the better data model
xAPI can describe experiences beyond a conventional course window: coaching, simulations, mobile activity, real-world practice, content views, or application events. Statements are sent to a Learning Record Store and can use a vocabulary tailored to the activity.
xAPI alone does not prescribe all the packaging and LMS-launch behavior teams associate with SCORM. Before choosing it, define identity, authorization, registration, offline behavior, statement governance, and how the reporting layer will turn statements into decisions.
Where cmi5 fits
cmi5 is designed for assignable units launched by an LMS while using xAPI for data. It specifies rules for launch, authorization, sessions, registration, move-on criteria, and a course structure. Those rules make the LMS workflow around xAPI more predictable.
Choose cmi5 when both authoring tool and LMS support it and you need richer statements without inventing the full launch contract. Keep a fallback export if your course must also reach clients with SCORM-only platforms.
Keep the editable source separate from exports
Keep the editable course in its authoring system and treat SCORM, xAPI, and cmi5 packages as release artifacts. Modern authoring tools such as ScormStack, Rise 360, Storyline, and iSpring can publish more than one standard, although exact options vary by product and plan.
ScormStack publishes SCORM 1.2, SCORM 2004, xAPI, cmi5, HTML, links, and Dynamic SCORM according to its current product information. Eluneo accepts SCORM 1.2 and 2004 as well as xAPI and cmi5 packages. The content source and delivery destination can then evolve independently.
A practical decision sequence
Start with the destination’s supported formats, then choose the least complex option that preserves the data and behavior you need. Confirm the choice with a reference package before publishing the complete course catalog.
- Need the widest LMS reach? Start with SCORM 1.2.
- Need separate completion/success, more state, or sequencing? Test SCORM 2004.
- Need to record activity beyond the LMS course window? Design an xAPI data strategy.
- Need xAPI plus a defined LMS launch and session model? Evaluate cmi5.
- Distributing to several clients? Maintain tested exports for the formats they actually accept.
Avoid a standards migration for its own sake
Do not republish a stable SCORM catalog solely because another standard is newer. Migrate when the current format blocks a required learner experience, reporting question, integration, or maintenance workflow. Every republish can change identifiers, completion logic, and resume state.
Create a compatibility matrix by authoring source, export preset, LMS, and expected outcomes. Use it to record the combinations that pass runtime testing instead of relying on a catalog-wide rule.
Frequently asked questions
Is SCORM 2004 always better than SCORM 1.2?
No. SCORM 2004 has a richer model, but SCORM 1.2 remains very widely supported and may be the safer distribution format. Choose according to LMS compatibility and required behavior.
Does xAPI replace SCORM?
xAPI can record a wider range of experiences, but it does not reproduce every SCORM packaging and launch rule. Some programs use xAPI or cmi5 for new needs while continuing to deliver existing SCORM content.
What is the difference between xAPI and cmi5?
xAPI defines how learning activity statements are expressed and stored. cmi5 is a profile that adds rules for launching and managing LMS-assigned course sessions using xAPI.