xAPI vs SCORM and when the difference matters

If your courses launch from an LMS and your reports need what SCORM already records, keep exporting SCORM: it tracks, at minimum, what SCORM.com calls the "Big 4", completion, score, duration and satisfaction¹. xAPI earns its place when the learning happens outside the LMS (an app, a simulation, the job itself) or when you need data that SCORM's fixed set of fields cannot hold²³. xAPI sends that data as statements to a Learning Record Store (LRS), so it pays off only if you have an LRS, which ADL calls "the linchpin of a functional xAPI implementation", and someone reads it²⁴. cmi5 is xAPI with SCORM's launch and completion rules put back for an LMS³, and it is the right export only when your LMS imports cmi5.

ADL, the Defense Department initiative behind both SCORM and xAPI, recommended xAPI and cmi5 for new acquisitions on its page archived 13 December 2025 and said SCORM is still in wide use⁵⁴. If your LMS is Moodle, its developer documentation says core Moodle's xAPI library is not meant to be a full LRS⁶.

What is the difference between xAPI and SCORM?

SCORM governs a course running inside an LMS, and its data is collected and stored within that LMS³. xAPI is a data and interface standard that lets software applications capture and share data on human performance, sending it as statements to an LRS². cmi5 sits between SCORM and xAPI, with xAPI's tracking and SCORM's structure³.

Start with the Launch from an LMS and Where the data goes rows: they decide whether your LMS can run the content and where your results end up.

What does each standard track?

SCORM tracks a fixed list; xAPI tracks whatever a system can describe as a statement³. SCORM 1.2 and SCORM 2004 track at minimum the Big 4¹, and Rustici Software's comparison calls SCORM "constrained to a defined set of data elements"³. SCORM 2004 widens the list with "full question and answer text"¹; SCORM 1.2 vs SCORM 2004 covers the other differences.

When ADL began investigating new experience tracking capabilities in 2010, it envisioned xAPI data that "should provide more than course completions, test scores, or the number of pages viewed by a learner"². ADL's examples include "Watching a training video, stopping and starting it" and "Quiz scores and answer history by question"².

xAPI statements are the structured data about a learning experience. An xAPI statement includes data about the actor (e.g., learner), verb (e.g., watched, passed), and object (e.g., video, quiz) as well as contextual information such as the timestamp and issuing authority, and also optional information such as results, other informational attachments, and context details.

ADL, "Experience API (xAPI) Standard"²

The xAPI specification sums up the verb as the "did" in "I did this"⁴. If your compliance report asks only who finished, who passed and when, the statement model adds nothing you will use.

Some authoring tools keep a SCORM course's bookmark in suspend data¹. If yours does, the xAPI equivalent is the LRS State endpoint, which ADL says stores "bookmark, state of play of the simulation, other state variables"².

Where does the data live, and what is an LRS?

SCORM data stays in the LMS³. xAPI data goes to a Learning Record Store, which ADL defines as a server "responsible for receiving, storing, and providing access to xAPI learning records"². An LRS validates and stores every xAPI statement, and it "may be part of an LMS or other software package," or stand alone².

In the xAPI specification, a Learning Record Provider sends the data, the LRS stores it, and a Learning Record Consumer "accesses data from Learning Record Store(s) with the intent of processing the data"⁴. The specification calls a Consumer an xAPI Client, defined as "any entity that might interact through requests"⁴. Someone on your team still has to open the report.

ADL tells anyone building or buying an LRS to "procure one that meets xAPI conformance standards". The sample wording it gives DoD and other federal buyers for acquisition documents then mixes 2 versions: it asks for conformance to "Version 2.0" but bases acceptance on a test log for the "Experience API Version 1.0.3 LRS-Conformant conformance label"².

The archived page does not explain the mix. Elsewhere, the same page says the first IEEE release of the standard "will be version 2.0"². Part One of the xAPI specification on ADL's GitHub master branch lists 1.0.3, dated 21 September 2016, as its last revision⁴.

If you buy an LRS, ask which version its conformance test covered.

Do you already have an LRS?

Possibly, and "supports xAPI" on a feature list does not tell you. Moodle is the clearest case because its developers wrote it down: "The final objective of Moodle xAPI library is NOT to implement a full LRS inside Moodle"⁶. The library lets a plugin (the worked examples use mod_h5p) send statements that Moodle turns into standard Moodle events, and from Moodle 4.2 it stores xAPI state too⁶.

For xAPI course packages, Moodle's SCORM FAQ says Tin Can "is supported with a number of 3rd party plugins", naming logstore xAPI, which reports logging data to an external LRS, and mod_tincanlaunch, which launches Tin Can packages inside Moodle⁸. Tin Can is xAPI's previous name⁴. The FAQ does not mention cmi5⁸, and Moodle's user documentation returned no xAPI page at docs.moodle.org/503/en/xAPI on 9 October 2026⁶.

If you are staying with SCORM on Moodle, the steps are in how to upload a SCORM package to Moodle.

No other LMS was checked for this page. Ask your vendor 4 things in writing: whether the LMS includes an LRS, which xAPI version that LRS was tested against, whether you can query or export the statements, and whether the LMS imports xAPI or cmi5 packages.

What is cmi5, and is it the answer?

cmi5 is xAPI with rules for a traditional LMS, and it is the answer when you want xAPI's data while your courses still launch from an LMS³. Rustici's comparison says cmi5 "bridges that gap by having xAPI’s tracking flexibility while maintaining the structure of SCORM"³. The xAPI specification lists cmi5 as an example profile, "designed for the traditional single learner, single online learning use case"⁴.

What cmi5 puts back:

• Launch. "xAPI does not include instructions for launching content in an LMS"; SCORM and cmi5 do³.
• Completion. cmi5 "establishes interoperable rules for determining completion/mastery of learning activities", while "xAPI has no defined satisfaction criteria"³.
• Reporting. Statements carry learner session identifiers, so they can be grouped for normalized reports³.
• Structure. A package can hold several AUs in a hierarchy with criteria for progression, "much as SCORM does with multiple SCOs"³.

cmi5 does not remove the LRS: "The LMS uses a conformant LRS to support both" xAPI and cmi5³, so the 4 vendor questions above still apply to you. ADL recommends cmi5 alongside xAPI⁵ and Storyline 360 exports it⁷. None of the sources read for this page can say whether your LMS imports cmi5.

Know who wrote that comparison. ADL contracted Rustici Software in 2011 for Project Tin Can, the first xAPI designs, before version 1.0 in 2013². Rustici offers its own LRS on the comparison page itself³.

When does xAPI change nothing for you?

When your courses launch from an LMS, your reports stop at the Big 4, and nobody would open an LRS. A SCORM conformant LMS can play any SCORM content³, and core Moodle supports SCORM 1.2⁸. If your client's report relies on a particular status wording, Storyline's LMS Reporting setting picks it, and that setting "isn’t available or necessary for cmi5 or xAPI content"⁷.

When does xAPI matter?

xAPI matters when the learning, the content or the data leaves the LMS:

• Mobile apps. SCORM "cannot track mobile applications natively and is limited to a browser context"; xAPI and cmi5 can³.
• Content hosted elsewhere. SCORM content "must reside on the same server or domain as the LMS"; with cmi5 it can sit anywhere³. Storyline's xAPI settings ask for a Launch URL when you host the content "on a server that’s separate from your LMS"⁷.
• Learning that is not a course. Simulations, video, mentoring and "Real-world performance in an operational context" are all on ADL's list².
• Data that has to move. "With xAPI and cmi5, data can be shared across systems"³, and ADL says xAPI is best run on "many distributed LRSs that can communicate with each other"².

One case comes from the buyer rather than from your learners: ADL and the Defense Department instruction DoDI 1322.26 recommend "xAPI and cmi5 solutions for new e-learning acquisitions and implementations"⁵. If you sell training to a federal buyer, read the contract; this page has not seen yours.

How to do it yourself

You need your LMS documentation or its administrator, your authoring tool and a test LRS. For the test LRS, ADL's xAPI page lists open source tools: a sample LRS with its source code on GitHub, and an xAPI Statement Viewer². Storyline 360 is the worked example because Articulate's documentation was the one saved; other authoring tools were not checked.

Decide in 5 questions

1. Where does the learning happen? If it all happens in courses launched from your LMS, lean toward SCORM. A phone app, a simulation, video outside the LMS or work on the job points to xAPI³².
2. What must the report show beyond the Big 4? If the answer is nothing, stop here and export SCORM¹.
3. Who will read the LRS, how often, and what will they decide from it? Put a name next to it. The xAPI specification's data flow ends at a Learning Record Consumer⁴, and if the name is blank, so is that box.
4. What does your LMS import, in writing? The SCORM version, xAPI packages, cmi5 packages, and whether it has a conformant LRS of its own³⁶.
5. Does a contract or policy name a standard? For Defense Department work, DoDI 1322.26 is the instruction ADL cites⁵.

Then test before you commit

1. Publish 1 short course for the target. In Storyline 360, open Reporting and Tracking, choose the standard from the Report to an LMS drop-down and, for an outside LRS, mark Report to an external LRS on the LRS tab⁷.
2. Choose how the LRS credentials are stored. "Supplied at launch" keeps them out of the project file; "Manual" stores them in it, and you republish if they change⁷.
3. Upload to the real LMS or LRS. Articulate's advice: "it’s best to upload the published course to your LMS/LRS for proper testing"⁷.
4. Read the statements back in the LRS and check that each one carries the actor, verb and object you expected².
5. Build the report your named reader wants, from the test data, before any rollout.

These are working estimates for 1 course, not vendor figures. A course that sends custom statements takes longer, because you have to check every statement type.

The mistakes that cost the most

1. Buying an LRS nobody reads. ADL warns that xAPI's flexibility "makes it difficult for Learning Record Consumers to make sense out of the data" without shared vocabularies, which it calls xAPI Profiles².
2. Reading "supports xAPI" as "has an LRS". Moodle's core xAPI library is, in its developers' words, not a full LRS⁶.
3. Exporting plain xAPI for an LMS launch. xAPI has no LMS launch instructions; cmi5 does³.
4. Changing the course Identifier on a republish. Articulate says not to change it for a course already in your LMS or LRS, and, for xAPI, to avoid special characters and spaces if you must change it⁷. Articulate's article does not say what breaks if you ignore this.

Questions people also ask

Is xAPI replacing SCORM? ADL recommends xAPI and cmi5 for new acquisitions and, in the same paragraph, says SCORM solutions are "still in wide use"⁵.

Is Tin Can the same as xAPI? Yes. The specification calls Tin Can API "The previous name of the API defined in this document"⁴, and Storyline 360's documentation lists the standard as "xAPI (Tin Can API)"⁷.

Do you need an LRS to use xAPI? Yes. ADL says all xAPI statements are validated and stored by an LRS, which can be part of an LMS or a standalone application².

Should you pick xAPI or SCORM 2004? SCORM 2004 adds full question and answer text to SCORM's data¹, but that data still stays in the LMS³. If your report fits inside your LMS, compare SCORM 1.2 vs SCORM 2004; if it does not, the choice is xAPI or cmi5.