SCORM vs xAPI: What's the Difference and Which Does Your LMS Need?

2 hours ago

3 min read

Disclosure: Kaz Software publishes this guide and builds the DTCLMS learning platform. We have tried to keep the advice useful whichever vendor you choose.

The short answer

SCORM tracks what happens inside a course launched from your LMS. xAPI records learning activity wherever it happens and sends it to a learning record store. Most organisations need SCORM support first, because that is how most packaged courses are delivered. xAPI becomes valuable when you want to track learning beyond the course player.

SCORM in plain language

SCORM (Sharable Content Object Reference Model) is a packaging and communication standard from ADL. A SCORM course is a zip file with a manifest that describes its content. When a learner opens it from an LMS, the course talks to the LMS through a JavaScript interface and reports things like completion, score, time spent and where the learner stopped. Two versions are common: SCORM 1.2, and SCORM 2004, which adds sequencing and navigation rules.

xAPI in plain language

xAPI (the Experience API, also called Tin Can) records learning as statements in the form actor, verb, object, for example 'Rahim completed Fire Safety Basics'. Statements are stored in a Learning Record Store (LRS), which can be built into an LMS or run separately. Because statements are sent over the web, xAPI can track activity outside a browser course, such as a simulation, a mobile app or a workshop sign-in. A profile called cmi5 defines how an LMS launches xAPI content.

SCORM and xAPI side by side

Question	SCORM 1.2	SCORM 2004	xAPI
What it is	Packaging and tracking for web courses launched from an LMS	SCORM 1.2 plus sequencing and navigation rules	Statement-based tracking sent to an LRS
Where learning can happen	Inside the LMS-launched course	Inside the LMS-launched course	Anywhere that can send statements
Typical data	Completion, score, time, bookmark	Completion and success status, sequencing state	Any activity you define as a statement
Needs an LMS to launch?	Yes	Yes	Not necessarily; needs an LRS
Tool support	Very widely supported	Widely supported; implementations vary	Growing; cmi5 covers LMS launch

Which do you need?

You buy or build courses in authoring tools: you need SCORM support. Most authoring tools can export SCORM.
You want to track mobile apps, simulations or on-the-job activity: you need xAPI.
You want both packaged courses and wider tracking: look for an LMS with SCORM playback and a built-in LRS.
Your courses are simple web pages: HTML5 import with light tracking may be enough.

Six things to test when a vendor says 'supports SCORM'

Which versions: 1.2, 2004, and which edition of 2004?
Does it honour sequencing rules if your courses use them?
Does resume work, so learners return where they stopped?
Do your own packages play, not just the vendor's demo ones?
Do you get the same result in a test tool such as SCORM Cloud?
Do large, video-heavy packages upload and play reliably?

For how these standards fit into a full platform, see AI-Enabled LMS Explained: SCORM, xAPI, Compliance Training and Certificates in One Platform. To write them into your brief, use our LMS Requirements Checklist: What to Put in Your RFP.

Frequently asked questions

Is SCORM obsolete?

No. It is old, but it is still the most common format for packaged courses, which is why LMS platforms still need to support it.

Can an LMS support both SCORM and xAPI?

Yes. Many modern LMS platforms play SCORM courses and also include an LRS for xAPI statements.

Do I need an LRS?

Only if you want to track activity beyond packaged courses. Many LMS platforms include one.

Our own platform plays SCORM 1.2, SCORM 2004, xAPI and HTML5 content; see custom LMS development in Bangladesh for details.