SCORM vs xAPI vs cmi5: Which Standard Should You Use?

Most course authoring software offers some mix of SCORM 1.2, SCORM 2004, xAPI and cmi5 at publish time without any advice. A wrong pick means exporting and uploading every course again.

The short answer to SCORM vs xAPI vs cmi5 is that your LMS decides most of it. Where it supports every standard, SCORM 2004 beats SCORM 1.2, cmi5 beats standalone xAPI for courses the LMS launches, and the choice between SCORM 2004 and cmi5 comes down to whether you need what cmi5 adds. Across all online learning standards, the format decides what data a course can send, but not whether anyone uses it.

Key takeaways

• Start with what your LMS supports. Where it supports everything, choose SCORM 2004 over SCORM 1.2 and cmi5 over standalone xAPI, and pick cmi5 over SCORM 2004 only when you need what it adds, such as content hosted outside the LMS or delivery in a mobile app.
• If your LMS has no learning record store (LRS), xAPI and cmi5 data needs a separate one.
• Ask your LMS vendor which standards are on by default, which need a request, and whether an LRS is included.
• Learning data becomes business evidence only once someone puts it next to a metric the business already tracks.

What Is the Difference Between SCORM, xAPI and cmi5?

SCORM packages a course for the LMS to launch and keeps its results there, while xAPI records almost any learning activity as statements sent to a learning record store and defines no launch rules. cmi5 restores those launch and completion rules on top of xAPI, so an LMS can run xAPI courses in much the same way it runs SCORM.

The table draws on Rustici Software's comparison, and its last row shows Intellum defaults, which differ between learning platforms.

What Is SCORM?

SCORM, the Sharable Content Object Reference Model, is a set of rules for content packaging that bundles learning content into a zip file any conformant LMS can launch and track. Each SCORM package carries a manifest, imsmanifest.xml, that acts as its table of contents, and the course reports results at runtime through a JavaScript API in the browser.

Each course records course completions, scores, time, and a pass or fail result, and that SCORM data stays in the LMS that hosts the package. The data model came from AICC, which the Aviation Industry Computer Based Training Committee created in 1988. SCORM 1.2 holds completion and pass or fail in one field, while SCORM 2004 gives each its own completion status and success status and adds sequencing rules. Our guide to what SCORM is covers the versions, limits, and common problems in depth. For an existing library, read about migrating SCORM content to Intellum.

What Is xAPI?

The Experience API (xAPI), also known as the Tin Can API, records learning as actor, verb, object statements, such as "Priya completed the forklift safety check," and sends them to a learning record store (LRS). This lets xAPI track learners in real world activities, and apps and simulators can collect data even when the learner is offline.

The catch is that the specification sets no launch rules and gives no shared meaning to complete or passed. One authoring tool might send "completed" for a safety check while another sends "experienced," and someone has to reconcile the two before a report means anything. In November 2023, Advanced Distributed Learning (ADL) announced that xAPI had become a published IEEE technical standard, IEEE 9274.1.1.

What Is cmi5?

cmi5 is xAPI with rules for the most common case, an LMS launching a course. It defines how the LMS starts the content, which statements the course must send, and what counts as passed, failed, or complete. ADL released the first production version of cmi5 in June 2016.

A cmi5 package includes a cmi5.xml file that sets out the course structure as assignable units, each sending defined statements for pass, fail, content completion, and score. The biggest cmi5 vs SCORM difference is how the course finds the LMS. cmi5 passes the LRS endpoint in the launch link instead of searching the browser for a JavaScript API, as the cmi5 project's comparison explains. That means content can sit outside the LMS when distributing learning across platforms.

Which Standard Should You Use?

Settle SCORM vs xAPI vs cmi5 by what your LMS supports first, then by what the content needs to do, not by which format sounds newest. For each type of eLearning content you publish from your authoring tool, the decision comes down to four rules:

• Existing courses: keep them in the version they shipped in, because they already work and exporting them again buys you little.
• New courses your LMS launches: choose SCORM 2004 over SCORM 1.2 wherever your LMS and authoring tool support it, because it separates completion from pass or fail and saves more learner progress. Use SCORM 1.2 only if your LMS accepts nothing newer.
• Courses that need what cmi5 adds: pick cmi5 over SCORM 2004 when the content has to sit outside the LMS, run in a mobile app, or send xAPI data alongside completion, provided both ends support it.
• Simulations, apps, and field learning: use xAPI to track learning in cases such as a sales app that logs practice calls, which SCORM cannot track outside the browser.

In a 2026 r/elearning post on the xAPI vs SCORM tradeoff, a practitioner who builds a SCORM 1.2 tool gave xAPI the edge on captured data and SCORM 1.2 the edge on day one use, adding that "SCORM with xAPI on top is still where most people actually live."

What to Ask Your LMS Before You Publish

Some standards ship switched off and not every LMS includes an LRS, so a format your tool exports may not run until someone enables it. Ask these four questions before you publish, and write the answers into the standards line of your RFP:

1. Which standards does the platform support by default?
2. Which standards need a request to turn on, and who handles it?
3. Is a learning record store included, or do we need a separate LRS?
4. Can learning data move into our own data warehouse?

The Intellum LMS platform runs SCORM 1.2 and AICC by default, and your customer success manager can turn on SCORM 2004, xAPI, and cmi5 on request.

Intellum Evolve publishes into Intellum through Cloud Sync, with no SCORM export step, although SCORM 1.2 also works there if required. For use outside the platform, Evolve exports SCORM 1.2, SCORM 2004, or a Web package. It does not export xAPI or cmi5, so teams that need that output can compare eLearning authoring tools.

Intellum's LMS RFP template covers the rest of your evaluation in nearly 200 questions, including reporting capabilities and data warehouse integration.

How to Turn Learning Data Into Business Evidence

Teams choosing a standard often ask whether they need xAPI just to see if someone watched a video. Usually they do not, because a SCORM course can already mark a video complete when it ends. The harder work comes after the course: deciding which business number the learning data should explain, then putting the two side by side.

Stakeholders who ask for "richer data" often assume xAPI will deliver it. xAPI can send the statements, but someone still has to build the report that sets them beside time to proficiency or support tickets. Whether you run SCORM and xAPI side by side or xAPI alone, the extra data changes nothing without that report. Working backward from the business result keeps the choice simple:

• Name the metric first, such as time to proficiency, support tickets, or partner certifications.
• Capture only the learning data that metric needs. Completion and score usually need nothing beyond SCORM, while behavior inside an app or simulator is where xAPI earns its setup.
• Join learning data and business data in one place, so a report can compare people who finished the training with people who did not.
• Give the report an owner who reviews it on a schedule, or the comparison never happens.

Collecting statements is the easy part, and the guide to LMS data and reporting covers turning them into decisions. Intellum's Data Connector moves learning data into your own warehouse, next to the metrics your business tracks. To see how this works in Intellum, request a demo.