Send us a message and we'll get back to you shortly.
SCORM and xAPI in Cubite LMS
Upload an Articulate Storyline or Rise course to an LMS
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.
Amir Tadrisi
LMS engineer since 2013
10 min read
Short answer (November 17, 2026): Cubite LMS, at $290 a month or $2,900 a year, plays Storyline and Rise courses published as SCORM 1.2, SCORM 2004 or xAPI (Tin Can API), with a built-in learning record store for xAPI, in packages of up to 500 MB; it does not play cmi5 or AICC. In Storyline 360, pick the standard under Report to an LMS on the LMS / LRS tab of the Publish window; in Rise 360, click Publish, select LMS and pick it there. Then upload the zip.
Disclosure: Cubite makes Cubite LMS and publishes this guide. The Storyline 360 and Rise 360 steps come from Articulate's own help pages, read on November 17, 2026, and are linked where they are used.
Articulate Storyline 360 and Rise 360 both publish a course as a zip for an LMS. The standard you pick decides what the LMS records and how the course resumes, and one publish detail can decide whether progress is recorded at all. This guide covers which standard to pick, Articulate's publish steps, and what Cubite LMS does with the zip after upload. For the standards themselves, see SCORM vs xAPI: what your LMS has to support.
Which standard to pick
Export option
In Cubite LMS ($290 a month or $2,900 a year)
Pick it when
xAPI (Tin Can API)
Plays it and keeps its statements in the built-in LRS; the package resumes in the browser the learner started it in
You want the statement record and learners finish on the device they started on
SCORM 2004
Plays it; status, score and saved state are stored on Cubite's server, so the course can resume on any device
Learners switch devices, or you want completion and pass or fail as two statuses
On the Home tab of the ribbon, click Publish, then select the LMS / LRS tab on the left.
Enter the Title as you want it to appear in the published output, and a Description. A tip from Cubite, not from Articulate's page: keep each on one line, without double quotes. Storyline writes both into the package's tracking script, and a line break or a double quote there can stop that script from loading (see the upload check below).
The Identifier is the unique string Storyline assigns so your LMS or LRS can identify the course.
Choose the standard in the Report to an LMS drop-down. Storyline 360 supports cmi5, xAPI (Tin Can API), SCORM 2004, SCORM 1.2 and AICC; for Cubite LMS, choose xAPI, SCORM 2004 or SCORM 1.2.
Click Reporting and Tracking to choose when the course counts as complete: when the learner has viewed a number of slides, completes a quiz, or through triggers. Articulate notes that whichever the learner completes first is what gets reported. For SCORM, choose the LMS reporting option there too.
Publish to your computer's own drive (Articulate warns that a network or USB drive can cause problems), choose Zip when publishing finishes, and upload that zip.
Open the course from your Rise 360 dashboard, click Publish in the upper right corner and select LMS.
Choose the LMS standard: xAPI (Tin Can API), SCORM 2004, SCORM 1.2, AICC or cmi5. For Cubite LMS, choose xAPI, SCORM 2004 or SCORM 1.2. If you change the pre-generated identifier of an xAPI export, Articulate says not to use special characters.
Choose Standard package, which you upload again for each new version. A connected package, which Rise updates without a new upload, supports SCORM 2004 and SCORM 1.2 only, and we have not tested connected packages with Cubite LMS.
Choose the tracking: by completion percentage or by a Storyline block, or by quiz result, with a reporting option when you track by course completion or quiz result.
Set the optional settings you need, such as the exit course link or Hide Cover Page. Reset progress after updates is not available for xAPI exports.
Click Publish again to generate the package, then download the zip from the link in Rise's notification email and upload it.
Rise's page says to point an LMS that asks for the launch file at indexapi.html. Cubite LMS reads the launch file from the package's own manifest, so there is nothing to point it to.
Upload the zip to Cubite LMS
Where: in the course editor, add an xAPI / Storyline block or a SCORM block to the unit, then drop the zip on it or click to browse. A new course also offers Import a SCORM package and Import an xAPI / Tin Can package. The block shows the upload's progress.
Size: up to 500 MB per package. A zip that is already online can also be handed to Cubite as a link, through the REST API (POST /api/v1/packages) or the package_upload tool of Cubite's MCP server, with the same limit.
What Cubite checks: that the zip holds tincan.xml (xAPI) or imsmanifest.xml (SCORM) and the launch file it names, and for SCORM which version the manifest declares.
The Storyline tracking-script check: a Storyline package reports to the LMS through a tracking script inside the zip, lms/scormdriver.js. If that script cannot load, the course still plays but nothing is recorded: no resume, no progress and no completion, so the units after it stay locked. Cubite LMS checks the script at upload and refuses a zip whose script will not load, with a message that says why. The cause the check names is a title or description typed on two lines, or a double quote in them. The fix: put them on one line without double quotes in Storyline's Publish window, publish again and upload the new zip.
What learners see
An xAPI package opens from a launch screen with its title, a short description, a What to expect list and a Start module button, then runs in a full-screen player with Exit module, New tab and Fullscreen controls. Opened in a new browser tab, it records progress the same way.
A SCORM package plays inside the lesson page, under a header with its title, a status (Not started, In progress or Completed) and a progress bar. A lesson page runs only one SCORM package of a given SCORM version at a time, so give each package its own unit.
Resume: a SCORM package's status, score and saved state are stored on Cubite's server and loaded at the next launch, so it can resume on any device. An xAPI package saves its place in Cubite's LRS, Rise's saves included (Rise sends them in xAPI's alternate request syntax, which the LRS accepts), for the browser the learner started it in; on another browser or device it starts again from the beginning, and the progress already recorded stays. Storyline offers prompt to resume, always resume or never resume, and Rise always resumes (Articulate's comparison of Storyline 360 and Rise 360 LMS output, last updated January 16, 2026, read November 17, 2026).
What counts as complete, and what happens next
Cubite LMS uses the package's completion, not its score. A SCORM 1.2 package is done when it reports passed or completed, a SCORM 2004 package when it reports completed, and an xAPI package when it sends a completed or passed statement for the course, or when the learner has viewed every module its tincan.xml lists. A finished package counts as done in its unit, and once that unit's steps are done the course menu unlocks the next one and course progress moves. When the course is complete, the course's certificate, if you have set one up, is issued under its completion rule, and the learner gets a Course completed email, which is on by default. Cubite LMS can also send a course.completed webhook, and its REST API returns each learner's progress and completion date.
So in SCORM 2004 and xAPI a package can count as done with a failed quiz inside it: SCORM 2004 reports completion and pass or fail separately, and an xAPI package is done once the learner has viewed every module. In SCORM 1.2, a failed status keeps the package incomplete. When a pass mark must decide the certificate, check how the package reports completion in Storyline or Rise, or put the final test in a Cubite Quiz block, which counts as done only when the learner passes.
On phones
Rise 360 courses are responsive: Articulate says they automatically adapt to every screen and orientation (Rise 360 Courses Use Responsive Design, last updated January 16, 2026). Storyline 360 courses use Articulate's responsive player, which responds to the screen size and orientation of mobile devices while the slide content keeps its aspect ratio, and hides sidebar menus and browser chrome (Articulate 360 FAQs: Responsive Player, last updated October 23, 2026). Both were read on November 17, 2026. Test the published package on the phones your learners use before you launch.
Moving Storyline courses off LearnDash? If GrassBlade LRS or Tin Canny holds your learners' statement history today, keep an export of it as your archive (how to export it): Cubite's LRS stores the statements sent by packages played in Cubite and does not import statements from other systems.
Articulate's steps were read on its help pages on November 17, 2026, and may change. Check the wording in Storyline's Publish window and Rise's Publish menu before you publish.
Uploading Storyline and Rise courses: common questions
01Which Storyline or Rise export should I upload to my LMS?
One your LMS plays. Cubite LMS, at $290 a month or $2,900 a year, plays SCORM 1.2, SCORM 2004 and xAPI (Tin Can API), with a built-in learning record store for xAPI; it does not play cmi5 or AICC. Choose SCORM 2004 when learners switch devices, xAPI when you want the statement record, and SCORM 1.2 when the same zip also has to run in other LMSs.
02Why does my Storyline course play but never record progress?
One cause is a tracking script that does not load: Storyline writes the course title and description from the Publish window into lms/scormdriver.js, and a title typed on two lines or a double quote can break it. Cubite LMS refuses such a zip at upload with a message that says so. Put the title and description on one line without double quotes, publish again and upload the new zip.
03How large can a Storyline or Rise zip be?
Up to 500 MB per package in Cubite LMS, uploaded from the course editor or, for a zip that is already online, handed over as a link through the REST API or Cubite's MCP server.
04Do Storyline and Rise courses resume where the learner left off?
Rise always resumes, and Storyline lets you prompt to resume, always resume or never resume (Articulate's comparison of Storyline 360 and Rise 360 LMS output, last updated January 16, 2026, read November 17, 2026). In Cubite LMS, a SCORM package can resume on any device, and an xAPI package resumes in the browser the learner started it in.
05Do I need to set up an LRS for an xAPI export?
Not in Cubite LMS: its learning record store is built in, and the package gets the LRS address and the learner when it launches. 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).
Have a Storyline or Rise course ready?
Bring the zip, and we will walk through the upload, the launch and how its progress counts toward the certificate in Cubite LMS.
Looking to learn more about SCORM and xAPI in Cubite LMS, Upload Storyline to an LMS, Rise 360 LMS export and Cubite LMS, xAPI, SCORM, Learning Record Store? These related articles explore complementary topics, techniques, and strategies.