cmi5 vs SCORM: What Is the Difference and Which to Use

Last updated July 2026.

cmi5 and SCORM are both standards for packaging e-learning so any compliant LMS can launch it and record results. SCORM is the older standard, built for browser-based courses that run inside the LMS and report a completion, a score and time spent. cmi5 is the modern replacement, built on xAPI, that can track learning inside or outside the browser (mobile, simulations, virtual reality, offline) and record far richer data about what the learner actually did. For a new deployment, cmi5 is the more future-proof choice, but SCORM is still the most widely supported and is fine for standard click-through courses.

If you are buying an LMS or authoring courses, this is one of those technical decisions that quietly shapes what your training can do for years. The good news is the choice is simpler than the acronyms suggest. Here is what actually separates cmi5 from SCORM, when each fits, and what to look for when you buy.

What is SCORM?

SCORM (Sharable Content Object Reference Model) is the long-standing e-learning standard that lets a course built in one tool run in any compliant LMS. It packages the course as a zip file the LMS unpacks and launches in the browser, and the course reports back a handful of data points: completion status, a pass or fail, a score and total time. Released in the early 2000s and last updated as SCORM 2004, it is the format nearly every authoring tool and LMS still supports.

SCORM works well for what it was designed for: self-contained, click-through courses that run in a web browser while the learner is logged into the LMS. Its limits show up the moment training moves outside that box.

What is cmi5?

cmi5 is the modern e-learning standard, published by the same body behind SCORM, that pairs the packaging and launch rules SCORM provided with the tracking power of xAPI (Experience API). A cmi5 course does not have to run inside the LMS browser window; it can launch on a mobile app, a simulation, a VR headset or an offline device, and still report results back to the system. Instead of a single completion and score, it can record detailed statements about what the learner did, step by step.

In short, cmi5 keeps the interoperability SCORM gave you (any compliant course runs in any compliant LMS) while removing the browser-only limitation and the thin data. It is designed to be the successor SCORM never formally got.

cmi5 vs SCORM: the key differences

The core difference is that SCORM tracks browser-based courses with limited data, while cmi5 tracks learning anywhere with rich data. SCORM reports completion, score and time from a course running inside the LMS. cmi5 uses xAPI to record detailed activity from content running in or out of the browser, online or offline, on almost any device. Everything else, secure launch, pass/fail, session management, cmi5 also handles, which is why it is treated as SCORM's modern replacement rather than a competing option.

Is SCORM outdated?

SCORM is dated but not obsolete. It has not had a major update since SCORM 2004 and it cannot track learning outside the browser or capture rich data, which is why cmi5 was created. But it remains the most widely supported format across authoring tools and platforms, and for straightforward online courses it still does the job perfectly well. Think of SCORM as reliable and universal but limited, and cmi5 as the modern standard you move toward as your training gets more sophisticated.

How does cmi5 relate to xAPI?

cmi5 is built on top of xAPI; they are complementary, not competing. xAPI is the underlying specification for recording learning activity as statements ("learner did this") in a Learning Record Store, but on its own it does not define how a course is launched, secured or marked complete inside an LMS. cmi5 adds exactly those rules, packaging, launch, authentication, pass/fail and session handling, so xAPI content behaves like a proper, trackable course. In practice, cmi5 is the profile that makes xAPI usable for formal LMS-delivered training.

Which should you choose for your LMS?

Choose based on where your training is heading. If your courses are standard browser-based modules and your authoring tools output SCORM, SCORM is fine and will run everywhere. If you expect mobile learning, simulations, offline field training or you want detailed data on how people learn, buy an LMS that supports cmi5 and xAPI so you are not boxed in later. The safest position is a platform that supports both, which lets you keep your existing SCORM library while building new content to the modern standard.

When you are choosing tools, this is one line on a longer checklist. Our course authoring tool guide covers how courses get built and exported, and the related breakdown of SCORM vs xAPI explains the data layer that cmi5 sits on. If your source material is a pile of existing slide decks and documents, you can turn those into presentation-ready lesson content with an AI presentation maker before you package it to either standard.

The short version: SCORM for universal support and simple courses, cmi5 for modern, multi-device, data-rich training. For a new purchase, insist on cmi5 support so the platform can grow with how your company actually trains, and keep SCORM around for the library you already own.