SCORM, xAPI, and cmi5 are e-learning standards that control how a course reports learner results. SCORM tracks completion and scores inside a Learning Management System (LMS). xAPI tracks learning anywhere and stores it in a Learning Record Store (LRS). cmi5 is xAPI with rules for launch from an LMS.
Pick SCORM for the widest LMS support, xAPI for learning outside the LMS, and cmi5 when your LMS supports it and you want xAPI data inside a familiar LMS workflow.
Key takeaways
- SCORM is still the default in most LMSs. Nearly 3 out of 4 course launches on Rustici Software’s SCORM Cloud in 2023 used SCORM 1.2 or SCORM 2004 (Rustici Software, 2024).
- xAPI records far more data, but it needs an LRS. Every learning activity becomes a statement, and you need an LRS to store, query, and report on those statements.
- cmi5 gives xAPI the structure that SCORM has. It adds rules for course import, launch, and completion, so xAPI courses behave in a predictable way inside an LMS.
- Your LMS sets the limits of your choice. Check which standards your LMS supports before you pick one, because the best standard on paper fails if your platform can’t play it.
SCORM tracks completion and scores inside your LMS
SCORM is a set of technical standards that tells a course how to package itself and how to talk to an LMS. The name stands for Sharable Content Object Reference Model. You upload a SCORM package (a .zip file) to your LMS, and the LMS records what the learner does.
The Advanced Distributed Learning (ADL) Initiative, a program of the US Department of Defense, created SCORM. SCORM 1.2 came out in October 2001. The last release, SCORM 2004 4th Edition, came out in March 2009 (SCORM.com).
SCORM 1.2 captures completion, score, time, learner satisfaction, and limited interaction data (ADL and Rustici Software, 2021). SCORM 2004 adds sequencing rules, so you can decide the order in which learners move through modules.
The two versions live side by side today. SCORM.com calls SCORM 1.2 the industry workhorse, and it describes the 3rd Edition as the most widely used edition of SCORM 2004. In 2023, over half of the content uploaded to SCORM Cloud on any given day was a SCORM 1.2 package (Rustici Software, 2024).
xAPI tracks learning anywhere and stores it in an LRS
The Experience API (xAPI) records learning as short statements with an actor, a verb, and an object. “Maria completed the forklift safety check” is a valid xAPI statement. Each statement goes to an LRS, a server that receives, stores, and returns learning records.
xAPI started as Project Tin Can, which Rustici Software ran under contract from ADL to build a successor to SCORM. That is why you still see the name “Tin Can API.” Version 1.0 came out on April 26, 2013 (SCORM.com).
In 2023, xAPI 2.0 became an official standard of the Institute of Electrical and Electronics Engineers (IEEE). The IEEE approved it as IEEE 9274.1.1-2023 on March 30, 2023, and ADL confirmed its open-source publication in October 2023 (ADL, 2023).
xAPI can track almost any activity. That includes mobile apps, simulations, virtual reality, games, on-the-job tasks, and offline learning (ADL and Rustici Software, 2021). The content doesn’t need to live in an LMS or a browser.
Access to data is where xAPI delivers most. Ben Clark, Lead Developer for Rustici Engine and author of the first Tin Can draft, writes that this is where xAPI “has been most successful” (xAPI.com, 2023). Organizations collect statements in an LRS and send them on to reporting and analytics tools.
cmi5 adds LMS launch rules to xAPI
cmi5 is an xAPI profile, a set of rules for how an LMS imports, launches, and tracks xAPI content. It uses xAPI to send data and adds the structure SCORM always had. The biggest difference in cmi5 vs xAPI is launch. xAPI on its own has no rules for how an LMS starts a course, and cmi5 does.
The project began at the Aviation Industry Computer-Based Training Committee (AICC), and ADL took it over after AICC dissolved. ADL released the first production version, called Quartz, on June 1, 2016 (SCORM.com). The name no longer stands for anything.
cmi5 defines rules for launch, authentication, session management, reporting, and course structure (ADL and Rustici Software, 2021). It tracks a small core set of data, such as status, score, and time, and it accepts any other xAPI statement on top. Course content can sit on any server, not only on the LMS. For a closer look, read our guide to what cmi5 is and why you need it.
cmi5 is on its way to formal standard status. An IEEE working group (P9274.3.1) has worked on it since February 2023, but it is not yet an approved IEEE standard (IEEE Standards Association).
SCORM vs xAPI vs cmi5 compared side by side
SCORM wins on LMS support, xAPI wins on data, and cmi5 combines the two for LMS-based courses. The table below compares all three on the points that matter most when you choose a standard.
| Feature | SCORM | xAPI | cmi5 |
|---|---|---|---|
| What it tracks | Completion, score, time, and basic interactions | Almost any activity, as actor, verb, and object statements | A core set (status, score, and time) plus any xAPI statement |
| Where data is stored | In the LMS | In an LRS, either standalone or built into an LMS | In the LRS that comes with a cmi5-ready LMS |
| Offline and mobile | Browser only, with no native tracking of mobile apps | Yes, including native apps and offline activity | Yes, after the LMS launches the activity |
| Needs an LMS | Yes | No | Yes |
| Launch and security rules | Defined launch, and content must sit on the same domain as the LMS | No launch rules in the standard | Defined rules for launch, authentication, and sessions |
| LMS support today | Almost every LMS and authoring tool | Common in enterprise LMSs and learning platforms, often through a built-in LRS | Growing, but still limited |
| Best for | Standard LMS courses that report completion and scores | Learning outside the LMS and detailed analytics | LMS courses that need xAPI data |
Sources are the ADL comparison of SCORM, xAPI, and cmi5 (2021) and the SCORM.com overview of standards.
Your use case decides which standard to pick
Most SCORM vs xAPI decisions come down to where the learning happens and how much data you need afterward. Use this table to match your situation to a standard.
| If you need to | Use |
|---|---|
| Report completions and pass or fail scores in almost any LMS | SCORM 1.2 |
| Send one course to the LMSs of many clients or partners | SCORM 1.2 |
| Set rules for the order in which learners move through modules | SCORM 2004 (4th Edition) |
| Track learning in apps, simulations, on the job, or offline | xAPI |
| Combine learning data from several systems in one report | xAPI with an LRS |
| Launch courses from your LMS and still collect xAPI data | cmi5, if your LMS supports it |
Check your LMS first. Your LMS vendor can tell you which versions of SCORM, xAPI, and cmi5 the platform plays, and whether it includes an LRS.
Easygenerator publishes SCORM 1.2, SCORM 2004, and xAPI
Easygenerator exports every course as SCORM 1.2, SCORM 2004, or xAPI. You choose the format when you publish, so the same course works with whichever standard your LMS plays (Easygenerator).
Manual SCORM. You export a SCORM 1.2 or SCORM 2004 package and upload it to any compatible LMS. This option gives you full version control and an offline backup of the course files.
Dynamic SCORM. You upload the package to your LMS once. After that, every update you make in Easygenerator reaches the live course in your LMS without a new upload. Media files stay on Easygenerator, so the package uses less LMS storage. Read more about manual and dynamic SCORM export.
xAPI. You export an xAPI package that connects to the LRS of your LMS on its own, with no LRS setup needed, as long as your LMS includes an LRS. It reports results at question and section level, and it saves learner progress in that LRS (Easygenerator Help Center).
Easygenerator does not publish cmi5 today. If your LMS needs cmi5, check that requirement before you choose an authoring tool. For help with a choice between export formats like SCORM, xAPI, and PDF, see our guide to e-learning export formats.
Each standard has a clear limit to plan around
No standard covers every need. SCORM limits your data, xAPI asks for extra infrastructure, and cmi5 still lacks wide support.
SCORM records a small, fixed set of data
SCORM tracks a defined list of data points and nothing else. It works only in a browser, it can’t track native mobile apps or offline activity, and the content must sit on the same domain as the LMS (ADL and Rustici Software, 2021). ADL has not released a new version since 2009.
xAPI needs an LRS and a shared vocabulary
xAPI data has nowhere to go without an LRS. Many enterprise LMSs include one, but some organizations need to buy a standalone LRS.
The freedom of xAPI brings its own problem. Two tools can describe the same action with different verbs, which makes reports hard to compare. xAPI profiles fix this with shared rules, but your tools need to follow the same profile.
xAPI also has no launch rules of its own. Most “xAPI packages” from authoring tools still use the older Tin Can launch method that Ben Clark drafted as a placeholder, which cmi5 is meant to replace (xAPI.com, 2023).
cmi5 has limited LMS and tool support
cmi5 adoption has been slow. ADL and Rustici Software point to missing conformance test suites and a lack of LMSs and authoring tools that support it (ADL and Rustici Software, 2021). ADL has since released those test suites, but support still varies a lot from one LMS to the next. The current version of cmi5 also works with xAPI 1.0.3, while a version for xAPI 2.0 is still in progress at IEEE.