What is the difference between xAPI and SCORM?

SCORM packages a course for an LMS and reports a fixed set of results. xAPI records granular statements about experiences in actor-verb-object form and can capture learning outside an LMS entirely.

Do I need a Learning Record Store for xAPI?

Yes. xAPI statements must be sent to an LRS, which is separate infrastructure some LMS platforms include and many do not. This is the cost usually left out of the comparison.

Is SCORM 1.2 too old to use?

No. Its age is why it is safe — it is implemented consistently by every major platform. SCORM 2004 is technically superior and less consistently implemented, which is why 1.2 remains the practical default.

When should I choose xAPI over SCORM?

When learning happens outside the LMS, such as on mobile, in simulations or on the job, or when you have a specific analytical question completion data cannot answer and someone able to answer it.

Does CourseConverter export xAPI?

No. It exports SCORM 1.2 and standalone HTML. If xAPI is a firm requirement, that is worth establishing before investing time.

Course Creation

xAPI vs SCORM: Which Do You Actually Need?

November 5, 2026

Anyone researching e-learning standards runs into the same framing: SCORM is old, xAPI is modern, therefore xAPI. It is a poor way to choose, because the two are solving overlapping but different problems and only one of them works without additional infrastructure.

What is SCORM?

A packaging and tracking standard from around 2000, in two versions still in use: SCORM 1.2 and SCORM 2004. It defines how a course is bundled into a ZIP file that any conforming LMS can import, and how that course reports a small set of things back — completion, pass or fail, a score, time spent, and where the learner got to.

Its defining characteristic is that it works inside an LMS, in a browser, in a single session. Its other defining characteristic is that essentially every LMS supports it.

What is xAPI?

A later specification, sometimes called Tin Can, that records statements about learning experiences in an actor-verb-object form: "Leigh completed the fire safety course", "Leigh watched 80% of the induction video".

Two things make it more capable. Statements can describe almost anything, at any granularity, rather than a fixed set of fields. And they do not have to come from inside an LMS — a mobile app, a simulator, a piece of equipment or a manual sign-off can all send them.

What is the catch?

xAPI statements have to go somewhere, and that somewhere is a Learning Record Store. An LRS is a separate piece of infrastructure that receives, stores and lets you query statements. Some LMS platforms include one; many do not.

This is the part usually left out of the comparison. Choosing xAPI is not choosing a file format. It is choosing to run, buy or configure an LRS, and to have someone who can query it — because xAPI gives you a firehose of detailed statements rather than a tidy completion column, and without analysis that data does nothing.

So which should I use?

SCORM 1.2, for most people, most of the time. Specifically:

Use SCORM if your training is delivered in an LMS, and what you need to know is who completed what, when, and with what score. That is the overwhelming majority of workplace training.
Use xAPI if learning happens outside the LMS — on mobile, in simulations, on the job — or if you have a specific analytical question that completion data cannot answer and someone with the time to answer it.
Consider cmi5 if you want both. It is a specification that uses xAPI underneath while keeping the LMS-launched, packaged structure SCORM users expect. Support is growing but is nowhere near universal.

Is SCORM 1.2 too old to rely on?

No, and its age is the reason to trust it. A standard that has not changed in two decades and is implemented by every major platform is a safe place to put content you need to still work in five years. SCORM 2004 is technically superior and less consistently implemented, which is why 1.2 remains the practical default.

The genuine limitations are real but narrow: a coarse data model, awkward handling of anything longer than a browser session, and no way to record learning that happens elsewhere. If none of those describe your problem, the age of the standard is not a problem either.

What does CourseConverter export?

SCORM 1.2 and standalone HTML. There is no xAPI export at present, which is a deliberate scoping decision rather than an oversight — the audience building courses from Word documents is overwhelmingly deploying them into an LMS that speaks SCORM.

If you need xAPI specifically, that is worth knowing before you invest time here. If you are unsure whether you need it, the honest test is whether you can name the question you would ask of the data. If you cannot, you need SCORM.

The decision in one line

Choose based on what you will do with the data, not on which standard is newer. Most organisations need to know who completed the training, they already have a system that records exactly that, and adding an LRS to answer a question nobody has asked is a project without a purpose.

If the question does arrive later, nothing is lost. A course delivered as SCORM today can be rebuilt or re-exported against a different standard when there is a reason to, and the content — which is the expensive part — is unaffected by the choice.