Send us a message and we'll get back to you shortly.
SCORM records completion and a score inside the LMS; xAPI sends statements to a learning record store. What each needs from your LMS, and which to pick.
Short answer (November 17, 2026): an LMS should play SCORM 1.2, SCORM 2004 and xAPI, and have a learning record store (LRS) for xAPI, built in or separate. Cubite LMS plays SCORM 1.2, SCORM 2004 and xAPI with a built-in learning record store in its Growth plan, $290 a month or $2,900 a year with unlimited learners. It does not play cmi5, and it plays one SCO per SCORM package.
Disclosure: Cubite makes Cubite LMS and publishes this guide. The standards facts come from ADL's xAPI specification and the cmi5 project on GitHub and from Rustici Software's SCORM reference, and the LearnDash and Articulate lines from their own documentation, all read on November 17, 2026.
Most buyers meet SCORM and xAPI as export options: an authoring tool asks which standard to publish to, and the LMS has to play what comes out. The two differ in what they record, where the record is kept and what the LMS needs to run them. This guide covers those differences, what Cubite LMS supports and does not, and which export to choose.
SCORM runs inside the LMS. A SCORM package is a zip with a manifest (imsmanifest.xml) that the LMS launches in the learner's browser, and the package then talks to the LMS through a JavaScript API that the LMS provides: Rustici Software's SCORM reference says all SCORM communication happens within a web browser session, and only through that API. What the package can write is a fixed set of fields. In SCORM 1.2, one lesson status carries both completion and pass or fail (passed, completed, failed, incomplete, browsed or not attempted), next to a score, a bookmark and saved state that the standard sizes at 4,096 characters. SCORM 2004 splits that status into a completion status and a success status, adds a progress measure and sizes saved state at 64,000 characters.
xAPI (the Experience API, earlier called Tin Can) records statements: each carries an actor, a verb and an object, with an optional result and context, for example a learner who completed a module, with the score as the result. The package, or any other tool, sends its statements to a learning record store, which the specification defines as a server responsible for receiving, storing and providing access to learning records. Because the record lives in the LRS rather than in one LMS session, xAPI can track activity outside a browser course too: ADL wrote it for formal and informal learning, both on and offline. Version 1.0.3 is on ADL's GitHub, and the current version, xAPI 2.0, became the IEEE 9274.1.1-2023 standard.
cmi5 is, in the words of the cmi5 project, a profile for using the xAPI specification with traditional learning management systems: it adds rules for how the LMS launches xAPI content and how each session is recorded. Storyline 360 and Rise 360 both offer it as an export, next to SCORM 1.2, SCORM 2004, xAPI and AICC.
The last row is Cubite LMS, and Cubite publishes this guide. The release dates and saved-state sizes come from Rustici Software's SCORM reference, the xAPI 2.0 standard number from IEEE's xAPI project, all read on November 17, 2026.
| SCORM 1.2 | SCORM 2004 | xAPI | cmi5 | |
|---|---|---|---|---|
| Released | October 2001 | 4th Edition in March 2009 | April 2013; xAPI 2.0 as IEEE 9274.1.1-2023 | June 2016 |
| What the package records | One lesson status for completion and pass or fail, a score, a bookmark, saved state | Completion and success as two statuses, a score, a progress measure, a bookmark, saved state | Statements: actor, verb and object, with a result and context | xAPI statements, under cmi5's launch and session rules |
| Where the record is kept | In the LMS that launched the package | In the LMS that launched the package | In a learning record store | In a learning record store behind the LMS |
| Saved state | Sized at 4,096 characters | Sized at 64,000 characters | State documents in the LRS | State documents in the LRS |
| What the LMS needs | A SCORM 1.2 runtime | A SCORM 2004 runtime | An LRS, built in or separate | cmi5 launch support and an LRS |
| Cubite LMS ($290 a month or $2,900 a year) | Plays it | Plays it | Plays it, with a built-in LRS | Does not play it |
What Cubite LMS does not do:
Storyline 360 lists cmi5, xAPI (Tin Can API), SCORM 2004, SCORM 1.2 and AICC under Report to an LMS, and Rise 360 offers the same five when you publish for an LMS (Articulate's help pages, read November 17, 2026). For Cubite LMS:
The publish settings step by step, and what Cubite checks when you upload, are in how to upload a Storyline or Rise course to an LMS.
When another option fits better: if your content is packaged as cmi5, choose an LMS that plays cmi5; if another system has to read the raw statements, a standalone LRS that forwards statements fits better than Cubite LMS, whose built-in LRS keeps the statements and does not forward them. The SCORM, xAPI and built-in LRS page compares eleven vendors on pricing model, SCORM, xAPI, a built-in LRS and cmi5, with each vendor's own page as the source.
The standards facts were read in ADL's xAPI specification and the cmi5 project on GitHub, IEEE's xAPI project and Rustici Software's SCORM reference, and the Articulate and LearnDash lines in their own documentation, on November 17, 2026. They may change.
Choosing an export for your courses?
Bring a SCORM or xAPI package, and we will walk through how it plays in Cubite LMS and how its progress counts toward the certificate.
Looking to learn more about cmi5, SCORM vs xAPI, Learning record store, SCORM and xAPI in Cubite LMS and Cubite LMS, xAPI, SCORM, LMS Comparison, Learning Record Store, cmi5? These related articles explore complementary topics, techniques, and strategies.
Two LearnDash add-ons for SCORM and xAPI, compared on price, data storage and reports.
Which export to choose in Storyline 360 and Rise 360, the publish steps from Articulate's help pages, and what happens in the LMS after you upload the zip.
What DOT and OSHA rules ask you to record, how a LearnDash stack keeps it, and how Cubite LMS does.
Where GrassBlade and Tin Canny keep xAPI and SCORM history, and how to export and keep it.