Support

How can we help?

Send us a message and we'll get back to you shortly.

We typically respond within 24 hours

cmi5

SCORM vs xAPI: what your LMS has to support (2026)

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.

Amir Tadrisi
Amir Tadrisi
LMS engineer since 2013
10 min read

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.

What SCORM and xAPI record

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.

What your LMS needs for each

  • For SCORM: a SCORM runtime, the JavaScript API the package looks for in the browser (named API in SCORM 1.2 and API_1484_11 in SCORM 2004), plus storage for each learner's status, score, bookmark and saved state, so the course can resume.
  • For xAPI: a learning record store to receive the statements, built into the LMS or bought separately and connected to it.
  • For cmi5: an LMS that implements cmi5's launch rules and, as the cmi5 specification requires, an xAPI learning record store.
  • On LearnDash: LearnDash's own documentation says SCORM 1.2 and SCORM 2004 are supported through a third-party add-on, GrassBlade xAPI Companion or Tin Canny by Uncanny Owl, and that the xAPI route also needs a learning record store (last updated April 14, 2019, read November 17, 2026). Cubite lists those among the parts a LearnDash site has to assemble to match what Cubite LMS Growth ships in one price: a SCORM or xAPI player plugin, an LRS to keep xAPI completion records, and someone to update WordPress, the theme and every plugin. Dated prices for the add-ons are in LearnDash and SCORM: the add-on tax and Tin Canny vs GrassBlade.

SCORM 1.2, SCORM 2004, xAPI and cmi5 side by side

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.2SCORM 2004xAPIcmi5
ReleasedOctober 20014th Edition in March 2009April 2013; xAPI 2.0 as IEEE 9274.1.1-2023June 2016
What the package recordsOne lesson status for completion and pass or fail, a score, a bookmark, saved stateCompletion and success as two statuses, a score, a progress measure, a bookmark, saved stateStatements: actor, verb and object, with a result and contextxAPI statements, under cmi5's launch and session rules
Where the record is keptIn the LMS that launched the packageIn the LMS that launched the packageIn a learning record storeIn a learning record store behind the LMS
Saved stateSized at 4,096 charactersSized at 64,000 charactersState documents in the LRSState documents in the LRS
What the LMS needsA SCORM 1.2 runtimeA SCORM 2004 runtimeAn LRS, built in or separatecmi5 launch support and an LRS
Cubite LMS ($290 a month or $2,900 a year)Plays itPlays itPlays it, with a built-in LRSDoes not play it

What Cubite LMS ships, and what it does not

  • SCORM 1.2 and SCORM 2004: Cubite LMS reads the package's manifest, detects the version and plays it through a SCORM runtime in the lesson. Each learner's status, score, bookmark and saved state are stored on Cubite's server and loaded again at the next launch, so a SCORM course can resume on any device. Saved state is kept up to 64,000 characters for both versions.
  • xAPI: Cubite LMS plays xAPI packages, such as Storyline and Rise exports, and its built-in learning record store accepts the statements they send (xAPI 1.0.3, one at a time or in batches) and the place they save through the xAPI State Resource, also in the alternate request syntax Rise uses. Nothing needs setting up: the package gets the LRS address and the learner when it launches.
  • Progress and certificates follow the packages: a package that reports completion counts as done in its unit, the course menu unlocks the next unit once that unit's steps are done, course progress moves, and the certificate follows the course's completion rule. When a package completes the course, Cubite LMS can send a course.completed webhook, and its REST API returns each learner's progress and completion date.
  • Uploading: in the course editor, drop the zip on an xAPI / Storyline block or a SCORM block, up to 500 MB per package. Through the REST API, or the package_upload tool of Cubite's MCP server, you can also give Cubite a link to a hosted zip; the API tells SCORM from xAPI by the manifest inside.

What Cubite LMS does not do:

  • It does not play cmi5 or AICC packages. Export SCORM or xAPI instead.
  • It plays one SCO per SCORM package: for a package with several SCOs it launches the first, and SCORM 2004 sequencing between SCOs is not run. Publish each part as its own package instead.
  • It does not forward statements to another LRS or hand raw statements to other tools. Its LRS keeps the statements sent by packages played in Cubite, and it does not import statements from other systems.

Which one to export from Storyline or Rise

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:

  • SCORM 2004 when learners switch devices, or you want completion and pass or fail as two statuses: Cubite keeps SCORM's saved state on its server, so the course can resume on any device.
  • xAPI when you want the statement record in Cubite's built-in LRS. Cubite LMS keeps an xAPI package's resume point for the browser the learner started it in: on another browser or device the package starts again from the beginning, while the progress already recorded stays.
  • SCORM 1.2 when the same zip also has to run in other LMSs: Rustici Software's reference calls SCORM 1.2 the industry workhorse that every e-learning vendor should support. In Cubite LMS it can resume on any device too.
  • Not cmi5 or AICC 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.

SCORM vs xAPI: common questions

01Should my LMS support SCORM or xAPI?
Both, if your courses come from an authoring tool: SCORM 1.2 and SCORM 2004 run inside the LMS that launched them, and xAPI needs a learning record store. Cubite LMS plays SCORM 1.2, SCORM 2004 and xAPI with a built-in learning record store, at $290 a month or $2,900 a year with unlimited learners.
02Does xAPI need a learning record store?
Yes. xAPI packages send their statements to a learning record store (LRS), which keeps them. It can be built into the LMS, as in Cubite LMS, or bought separately and connected. LearnDash's documentation says its xAPI route needs an LRS such as GrassBlade LRS (LearnDash docs last updated April 14, 2019, read November 17, 2026).
03Does Cubite LMS support cmi5?
No. Cubite LMS plays SCORM 1.2, SCORM 2004 and xAPI with a built-in learning record store; it does not play cmi5 or AICC packages.
04Can Cubite LMS send xAPI statements to another LRS?
No. Its built-in LRS keeps the statements sent by packages played in Cubite and does not forward them. When xAPI activity completes a course, Cubite LMS can send a course.completed webhook, and its REST API returns each learner's progress and completion date.
05Is SCORM 2004 better than SCORM 1.2?
It records more: completion and pass or fail as two statuses instead of one, a progress measure, and saved state sized at 64,000 characters instead of 4,096. Rustici Software's SCORM reference calls SCORM 1.2 the industry workhorse (read November 17, 2026), so pick it when the same zip has to run in other LMSs too.

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.