Mon, Mar 30, 2026

CMI5: The E-Learning Standard That Goes Beyond SCORM

PandaSuite now supports CMI5 export. 🎉

For teams creating interactive e-learning content (field training, gamified modules, rich media experiences), this is a big deal. Your projects can now be deployed in any CMI5-compatible LMS, with full tracking that works reliably on mobile and even offline.

But what is CMI5? Why does it exist? And how does it differ from SCORM, the standard you may have been using for years?

That’s what this article is about. If you’re new to e-learning standards, start with our article on the SCORM format. If you already know SCORM and are wondering what CMI5 adds, you’re in the right place.

What Is CMI5?

CMI5 is a communication standard between e-learning content and an LMS. Its role is the same as SCORM’s: allow a training module to launch from a platform, and transmit progress and completion data.

But CMI5 is built on a different architecture. It was developed by AICC and later adopted by ADL (the organizations behind SCORM and xAPI) to address what SCORM could no longer cover: mobile, offline, rich data, complex content.

Technically, CMI5 is an xAPI profile. It uses xAPI as its data format and adds a precise deployment protocol: how a session initializes, which events are mandatory, how it closes.

xAPI, CMI5, SCORM: Understanding the Three Standards

The confusion between the three is common. Here’s how to tell them apart:

• SCORM is a complete standard: it defines how to package a module (the ZIP file), how to launch it from an LMS, and how to transmit data. It works via a JavaScript API injected into an iframe.

• xAPI (also called Tin Can) is an open specification for describing learning experiences. Each event is expressed as “actor–verb–object”: “Alice completed this module”, “Thomas dropped out of the simulation at step 3”. xAPI can track any experience but doesn’t define how an LMS should launch content.

• CMI5 is the missing link. It uses xAPI as its data format and adds the missing protocol: secure URL launch, structured session, normalized termination. CMI5 combines the richness of xAPI with the reliability of an interoperable standard.

How Does CMI5 Work?

Unlike SCORM, which opens content in an iframe and maintains a permanent JavaScript connection with the LMS, CMI5 works differently.

At launch, the LMS generates a secure session URL and passes it to the content. The content uses it to communicate directly with the LRS (Learning Record Store) via standard HTTP requests, with no iframe and no permanent connection. Data is sent asynchronously, whenever the network allows.

The LRS: The Component That Changes Everything

CMI5 introduces a new element: the LRS (Learning Record Store), a database dedicated solely to storing and retrieving learning data in xAPI format.

In SCORM, the LMS does everything (launch, collection, storage). In CMI5, roles are separated: the LMS handles enrollments, the LRS handles progress. This separation makes it possible to centralize data from multiple sources (your LMS, a mobile app, a kiosk, a standalone simulation) into a single unified report.

CMI5 is not plug-and-play: if your LMS doesn’t have a native LRS, the implementation requires infrastructure work that shouldn’t be underestimated.

The Concrete Benefits of CMI5

Training That Works in the Field, Even Without a Network

For teams training mobile workers, this is the most immediate benefit. A technician on the shop floor, a salesperson in a showroom, a healthcare worker on the move: they don’t always have a network connection. With SCORM, no network means no tracking.

CMI5 is built for these situations: data is sent asynchronously, once the connection comes back.

Precise Reporting

With SCORM, the LMS only knows whether a learner completed a module and with what score.

CMI5 sends every interaction as an xAPI statement. In practice, you can see:

• which question a learner failed (and how many attempts it took)
• how far into a video they got before dropping off
• how much time was spent on each section

This data lets you identify friction points and improve your content based on facts, not intuitions.

Interactive Content Without Rendering Constraints

With SCORM, content runs inside an iframe with dimensions imposed by the LMS, which quickly becomes a problem for gamified modules, full-screen simulations, or complex animations.

CMI5 removes this constraint. Content can be displayed in any context:

• full-screen browser
• native application
• embedded browser

This is particularly useful for no-code content like that created with PandaSuite, where the visual and interactive experience is central. Moodle 4.x, Docebo, TalentLMS, and Cornerstone have all strengthened their CMI5 support over the past two years. The shift is underway.

CMI5 vs SCORM: What Really Changes

SCORM remains relevant in many contexts: if your content consists of standard modules, if your LMS doesn’t yet support CMI5, or if your learners work exclusively on desktop with a stable connection. But as soon as field use, mobile, or data richness comes into play, CMI5 is the standard that delivers.

To go further on designing engaging e-learning experiences, check out our article on how to choose the right SCORM authoring tool for your context.