cmi5 is a specification built on top of xAPI that defines how an LMS launches content and which statements it should send. It gives xAPI the launch, completion, pass/fail, and scoring structure that SCORM has, so you get SCORM-like LMS behaviour with xAPI flexibility.

xAPI vs SCORM | Differences Explained

Q: What is the difference between xAPI and SCORM?

SCORM tracks a learner working through a course inside an LMS in the browser. xAPI (the Experience API, formerly Tin Can) records learning experiences as statements that can come from anywhere, including mobile apps, simulations, and offline activity, and stores them in a Learning Record Store rather than requiring an LMS session.

Q: Is xAPI replacing SCORM?

Not entirely. xAPI is more flexible and better for tracking learning beyond the browser, but SCORM remains the most widely supported standard for packaged courses. Many organisations use both, and cmi5 bridges the two by bringing LMS launch and tracking structure to xAPI.

Q: What is a Learning Record Store (LRS)?

An LRS is the system that receives and stores xAPI statements. Content sends statements to the LRS over a web API, and reporting tools read them back. An LRS can be built into an LMS or run as a standalone service.

Q: Should I use xAPI or SCORM for my courses?

Use SCORM for traditional packaged courses where broad compatibility matters. Use xAPI or cmi5 when you need to track learning outside the browser, offline activity, or detailed experience data. Hotline LMS supports SCORM 1.2 and 2004 plus xAPI and cmi5 package playback.

In this guide

1. What each standard is

SCORM (Sharable Content Object Reference Model) is the long-standing e-learning standard for packaging a course as a ZIP and tracking it inside an LMS. It runs in the browser and talks to the LMS through a JavaScript API. If you need the basics, see What is SCORM? and the SCORM 1.2 vs 2004 comparison.

xAPI (the Experience API, released in 2013 and originally nicknamed Tin Can) was designed by ADL to remove SCORM's two biggest constraints: that learning had to happen in a browser, and that it had to happen inside an LMS. Instead of a browser-only API, xAPI records statements and sends them to a Learning Record Store over a normal web API.

A statement follows a simple grammar: actor, verb, object. "Jane completed Fire Safety." "Sam scored 92 on Module 3." "Priya attended the onsite workshop." Because a statement is just data sent to an endpoint, it can be produced by a course, a mobile app, a simulator, or a person recording an offline activity.

2. Side-by-side comparison

Aspect	SCORM	xAPI
Released	2001 (1.2), 2004	2013
Where it runs	Browser, inside an LMS	Anywhere (app, web, offline)
How it communicates	JavaScript API in the page	Web API to an LRS
Where data lives	The LMS	A Learning Record Store (LRS)
Internet required during use	Yes	No (statements can sync later)
Tracks non-course activity	No	Yes
Granularity	Course / SCO level	Any individual experience
Adoption	Very high	Growing

3. How tracking works

With SCORM, the course content runs in an iframe inside the LMS and finds the LMS's JavaScript API in the parent window. It reads and writes values such as completion status and score through that API, and the LMS stores them. If the content cannot find the API, it cannot report anything; the dependency on the LMS session is total.

With xAPI, the content (or app, or device) sends statements to a Learning Record Store at a known endpoint, authenticating with a credential. The LRS does not care where the statement came from or whether an LMS is involved. This decoupling is the whole point: the experience and the record of it no longer have to share a browser tab.

4. What xAPI can track that SCORM cannot

smartphone Mobile and offline learning

A field worker completes training on a phone with no signal; statements sync when they reconnect.

view_in_ar Simulations and VR

A simulator records each decision and outcome as individual statements, not just a final score.

groups Real-world activities

On-the-job assessments, workshops, and mentoring sessions can all be recorded as experiences.

insights Fine-grained behaviour

Which video a learner rewatched, which resource they opened, how long they spent: each can be a statement.

5. Where cmi5 fits

xAPI on its own is deliberately open: it says how to record a statement, but not how an LMS should launch content or what counts as "completed". That freedom is powerful for analytics but unhelpful when you just want SCORM-style course behaviour.

cmi5 is a specification built on xAPI that fills that gap. It defines how an LMS launches a piece of content, how the content is told where the LRS is, and which statements (launched, initialized, completed, passed, failed, terminated) it should send. In short, cmi5 gives you the launch-and-track structure of SCORM with the flexibility and reach of xAPI. It is the natural successor for teams who want both.

6. Which should you use?

Stick with SCORM when

Your content is browser-based packaged courses
You need the broadest tool and LMS compatibility
Course-level completion and score are enough
Your authoring tool exports SCORM by default

Reach for xAPI / cmi5 when

You track learning outside the browser or offline
You want detailed, experience-level analytics
You record simulations, apps, or real-world activity
You want LMS structure plus xAPI flexibility (cmi5)

The short version: most teams still ship SCORM for their courses and add xAPI or cmi5 where they need to track experiences the browser cannot see. You do not have to pick one forever. Hotline LMS supports SCORM 1.2 and 2004, and includes a built-in Learning Record Store to launch and track xAPI and cmi5 packages alongside them.

xAPI vs SCORM questions

What is the difference between xAPI and SCORM? expand_more

Is xAPI replacing SCORM? expand_more

What is cmi5? expand_more

What is a Learning Record Store (LRS)? expand_more

Should I use xAPI or SCORM for my courses? expand_more

xAPI vs SCORM.