xAPI vs SCORM: Differences and Which to Use

Last updated August 2026.

xAPI and SCORM are both standards for packaging e-learning and tracking what learners do, but they work differently. SCORM tracks a course while it runs inside a web browser and reports completion, score and time back to the LMS. xAPI (the Experience API, once called Tin Can) records learning experiences anywhere, including mobile apps, simulations, offline and on the job, by sending statements to a Learning Record Store. For most companies delivering browser-based courses, SCORM is still the safe default; choose xAPI, usually through the cmi5 profile, when you need to track learning that happens outside the LMS.

If you are buying an LMS or building courses, this is one of those decisions that sounds deeply technical and turns out to be practical. The standard your content uses affects what you can track, which authoring tools you can use, and how much of your learning data you actually capture. Here is what each standard does, where they differ, and how to pick without overthinking it.

What SCORM is

SCORM stands for Sharable Content Object Reference Model. It has been the default e-learning standard since the early 2000s, with SCORM 1.2 (2001) and SCORM 2004 the two versions still in wide use. A SCORM course is a zip package of web files that an authoring tool exports and an LMS imports. When a learner opens it, the course talks to the LMS through JavaScript in the browser and reports a fixed set of data: completion status, pass or fail, a score, time spent, and a bookmark so the learner can resume where they left off.

SCORM's strength is compatibility. Nearly every corporate LMS and every major authoring tool supports it, so a SCORM package you build today will run almost anywhere. Its limits come from how it works. Tracking only happens while the course is open in a browser and connected to the LMS, the data model is narrow, and it was never designed for mobile apps, offline use or anything that happens away from a course window.

What xAPI is

xAPI, the Experience API, was released in 2013 and was originally nicknamed Tin Can. Instead of a course reporting a handful of fields to the LMS, xAPI records learning as statements in a simple actor, verb, object form: "Maria completed the forklift safety simulation," "James passed the HIPAA quiz," "the team attended the live workshop." Those statements are sent to a Learning Record Store (LRS), a database built to collect them.

Because statements can come from anywhere, xAPI captures learning that SCORM cannot see: a mobile app used on the warehouse floor, a virtual reality simulation, a PDF read offline, a task signed off by a supervisor, or an external system. That makes the data far richer, but it also means you need an LRS to store it and a plan for what you will actually do with all those statements. xAPI gives you more; it also asks more of you.

The xAPI profile that keeps the LMS in charge

Raw xAPI on its own does not tell an LMS how to launch a course or when to call it complete, which is why most companies moving off SCORM end up using a profile rather than xAPI directly. That profile adds the launch rules, the completion and pass or fail logic, and the LMS control that SCORM had. If that is the decision in front of you, the full breakdown is in cmi5 vs SCORM, which covers the launch and reporting differences properly.

SCORM vs xAPI at a glance

xAPI vs cmi5: the profile question most buyers hit next

cmi5 is not a competitor to xAPI. It is a profile built on top of it, which is why comparing xAPI vs cmi5 as if they were rivals leads people in circles. xAPI defines the statement format and the Learning Record Store that stores it. cmi5 adds the rules xAPI deliberately left out: how an LMS launches a course, how it passes a session identifier, what counts as satisfied, and how the LMS learns that a learner passed.

Put plainly, raw xAPI without a profile is a data-collection standard. Pair it with cmi5 and you get something an LMS can assign, launch, gate and report on the way it does with SCORM, while still capturing the richer statement data. That is why most companies moving off SCORM in 2026 end up publishing cmi5 rather than raw xAPI.

What makes an LMS xAPI compliant, and how to check

An LMS is xAPI compliant when it can send xAPI statements, receive them, or both, and when it can talk to a Learning Record Store. That sounds like one capability. In practice vendors mean at least three different things by it, and the difference decides whether your data actually lands anywhere useful.

• Built-in LRS. The platform stores xAPI statements itself and reports on them. Least work for you, but check whether the reporting goes beyond a raw statement list.
• Sends statements to an external LRS. The LMS emits xAPI about its own activity to an LRS you own. Useful when learning data has to sit alongside other systems.
• Launches xAPI or cmi5 packages. The platform can import and launch a package published as xAPI or cmi5 rather than SCORM. This is the one that matters if you are changing what your authoring tool exports.

Ask a vendor which of those three they do, not whether they support xAPI. And note the vocabulary trap that runs through this whole category: compliant is self-declared, conformant means tested against the ADL test suite, and certified means formal ADL certification, which is rare. Most marketing pages say compliant. Our SCORM compliant LMS page compares platforms on standards support alone, and the wider LMS comparison includes a version-by-version support table across twelve platforms.

One planning note worth having before you shortlist anything: TalentLMS supports SCORM 1.2, xAPI and cmi5 but not SCORM 2004, and Moodle implements SCORM 2004 only partially, having never implemented sequencing. If your existing library was published as SCORM 2004, that single line is the difference between importing packages and republishing every course.

Is xAPI compatible with SCORM?

Not directly. They are separate specifications with different data models, so a SCORM package does not become an xAPI package and an LRS does not read SCORM runtime calls. What is true is that they coexist comfortably. Nearly every corporate LMS that supports xAPI also still supports SCORM, so you can run a legacy SCORM library and publish new content as xAPI or cmi5 in the same platform without migrating anything on day one.

There are also wrapper tools that emit xAPI statements from a SCORM course, and some authoring tools can publish the same source project to either standard. Both are legitimate, and both are usually simpler than a big-bang migration. The pragmatic path most L&D teams take is to leave the existing catalog on SCORM, publish anything new that needs richer tracking as cmi5, and let the old library age out on its natural refresh cycle.

Which should you use?

For most companies, SCORM is still the right starting point. If your training is browser-based courses and quizzes, and you mainly need to know who completed what and how they scored, SCORM does that job, works with every tool, and needs no extra infrastructure. It is the boring, reliable choice, and boring is a virtue in compliance training where an auditor just wants a clean completion record.

Reach for xAPI, and specifically cmi5, when SCORM's blind spots start costing you. That is the case if you deliver learning on mobile devices or offline, run simulations or hands-on assessments, want to record on-the-job performance, or need deeper analytics than completion and score. Plenty of organizations run both: SCORM for the core course library and xAPI for the experiences that live outside it. The one thing to avoid is choosing a standard your LMS or authoring tool does not fully support, so confirm support on both sides before you commit.

The part that matters more than the standard

It is easy to spend a week on SCORM vs xAPI and forget that the standard is plumbing. What actually changes outcomes is whether the right training gets assigned to the right people, completed on time, and recorded in a way you can prove. A modern platform handles the standard for you and puts the attention where it belongs: assigning courses by role, enrolling new hires automatically, tracking completions and certifications, and reminding people before a deadline slips.

You also do not need to be a SCORM expert to build good training. Most companies already have the raw material sitting in documents and slides. Turning those into a course is faster than it used to be: you can lift the key points out of a policy deck, and if you want a polished, on-brand version of the slides themselves, you can even turn a report or PDF into a presentation before you build the lesson around it. From there, a browser-based course authoring tool lets you assemble the course and quiz without touching a packaging spec, and the platform delivers and tracks it whether the underlying content is SCORM or xAPI.

If the standards question came up because you are moving off an old platform, the packaging format is only one line on a longer list, and the LMS migration checklist covers what else travels with your course library. Readers weighing cmi5 specifically will find the launch-and-report differences spelled out in cmi5 vs SCORM.

If your goal is company training rather than a technical project, pick the standard your tools support, then judge the platform on how well it assigns, tracks and proves training. That is where a good employee training platform earns its keep, long after the SCORM vs xAPI question is settled.

For most buyers the standards question never really arises. If you author courses in the browser and deliver them to your own staff, an online training platform for employees handles packaging and tracking invisibly, and SCORM only becomes relevant when you import a library from a previous vendor or buy off-the-shelf compliance content.

Frequently asked questions

What is the main difference between SCORM and xAPI?

SCORM tracks a course while it runs in a web browser connected to the LMS and reports a fixed set of data: completion, pass or fail, score and time. xAPI records learning experiences anywhere, including mobile, offline and on the job, by sending statements to a Learning Record Store. SCORM is narrower but universally supported; xAPI is more flexible but needs an LRS.

Is xAPI replacing SCORM?

Not outright. xAPI is more capable, but SCORM remains the default for browser-based courses because nearly every LMS and authoring tool supports it and it needs no extra infrastructure. Many organizations use both, and the cmi5 profile lets xAPI work with the launch-and-manage structure of an LMS. For most standard course libraries, SCORM is still the practical choice in 2026.

Does xAPI work with an LMS the way SCORM does?

Not on its own. xAPI sends statements to a Learning Record Store, which is a different thing from an LMS launching a course and recording a result. To get xAPI tracking with normal LMS launch and completion behavior you use a profile on top of it, and the trade-offs are set out in cmi5 vs SCORM.

Does xAPI replace SCORM?

Not in practice, and not on any timeline worth planning around. SCORM 1.2 remains supported by essentially every corporate LMS and authoring tool, and it is still what most off-the-shelf compliance libraries ship in. xAPI is replacing SCORM only in the specific cases where SCORM was never adequate: mobile, offline, simulations and on-the-job sign-offs. For a browser-based compliance course, SCORM works fine and will keep working.

What is the difference between an API and xAPI?

An API is any interface one piece of software uses to talk to another. xAPI, the Experience API, is one specific API with a defined vocabulary for learning: an actor, a verb and an object, sent as statements to a Learning Record Store. So xAPI is an API, in the same way a lease is a contract. The name causes real confusion, because a vendor saying it has an API is not saying it supports xAPI.

Which LMS platforms support xAPI and cmi5?

As of August 2026, Docebo, Absorb LMS, iSpring and Cornerstone OnDemand cover SCORM 1.2, SCORM 2004, xAPI and cmi5. TalentLMS supports SCORM 1.2, xAPI and cmi5 but not SCORM 2004. 360Learning covers SCORM 1.2, 2004 and xAPI. Moodle handles SCORM 1.2 well, SCORM 2004 partially, and needs plugins for xAPI. Confirm the version directly with any vendor before you migrate a library.

Do I need to know SCORM or xAPI to build training?

No. A modern LMS handles the standard for you. You build the course in a browser-based authoring tool, assign it by role, and the platform delivers and tracks it whether the content is packaged as SCORM or xAPI. The standard matters when your tools have to talk to each other; day to day, you focus on the training, not the spec.

Where it does matter is at purchase time, because vendors mean different things by "SCORM support" and the version matrix is rarely on the pricing page. Our comparison of SCORM compliant LMS platforms sets out which platforms read SCORM 1.2, SCORM 2004, xAPI and cmi5, and the practical steps in uploading a SCORM file to an LMS cover what to test before you commit.