How to upload a SCORM package to SCORM Cloud
This guide walks an admin through importing, testing and sharing a SCORM package in SCORM Cloud today, using the current menu paths from Rustici's own documentation. SCORM Cloud runs Rustici Software's SCORM Engine — the same engine that adds SCORM playback to many other commercial LMSs — so it fully supports both SCORM 2004 4th Edition and SCORM 1.2; choose SCORM 2004 4th Edition for fuller reporting, and SCORM 1.2 only if you plan to dispatch onward to an older downstream LMS. Every Intle generation gives you both downloads from the same content.
Which SCORM version to use
SCORM Cloud is powered by Rustici Software's SCORM Engine, which documents support for SCORM 1.2 and SCORM 2004 (2nd, 3rd and 4th Editions), as well as AICC, xAPI and cmi5. That vendor support does not by itself prove an Intle package against SCORM Cloud. Prefer SCORM 2004 4th Edition when you need separate completion and success (pass/fail) status, multiple objective results or its larger suspend-data limit; use SCORM 1.2 when dispatching to an older downstream LMS or a configuration that requires it. Intle packages target both standards. Package-level checks were recorded on the dated build shown at /lms-compatibility, while SCORM Cloud remains pending until an executed platform test is recorded.
Uploading a SCORM package to SCORM Cloud
- 1
Sign in to SCORM Cloud
Log in at cloud.scorm.com (the app runs at app.cloud.scorm.com). A free Trial account is enough to import and test — it allows a small number of courses and up to 10 active, resettable registrations, which you can reset as you retest.
- 2
Open Add Content
From the dashboard, click the green Add Content button in the top right and choose 'Import a SCORM, AICC, xAPI or cmi5 package'.
- 3
Confirm the destination App
If you are prompted to choose a destination App, leave it on the default application unless you deliberately keep content in separate Apps within your realm.
- 4
Choose your zipped package
Click Choose File and select the .zip you downloaded from Intle. The zip must contain imsmanifest.xml at its root (not nested inside a sub-folder). Trial accounts cap extracted content at around 100MB; very large packages can also time out during web import, so upload those via FTP (ftp.cloud.scorm.com) instead.
- 5
Import the course
Click Import Course. A progress indicator shows while SCORM Cloud unpacks the zip and parses the manifest; when it finishes, the course appears in your Library.
- 6
Launch and test the course
Open the course from the Library and click Launch to run it in the player. SCORM Cloud records the launch as a registration and reports completion, success (pass/fail), score and time for that attempt.
- 7
Check the debug log if anything looks off
To inspect the run-time calls, either enable the Navigation Bar in the course's properties, launch the course and click View Debug in that bar, or open the course in the Library, select the registration you want and view its debug log. Either way you see every SCORM run-time call — the quickest way to confirm completion, score and suspend-data are being set correctly.
- 8
Share the course
Use the Invitations feature to create a Public Invitation (one link anyone can take, with an optional registration cap and expiry) or a Private Invitation (a unique link emailed to each learner). To deliver into another LMS instead, use Dispatch, which lets you update the content later without re-sending the package.
Settings that affect SCORM behaviour
- Launch Behavior (Course Properties -> Launch Behavior): two settings, SCO Launch Type and Player Launch Type, control windowing. For SCORM content both default to FRAMESET, which keeps the navigation bar and content together in a single window; NEW_WINDOW is the runtime default only for xAPI/cmi5. If a course opens in extra windows or trips a pop-up blocker, confirm both are set to FRAMESET.
- Completion/score override (the course's Configuration settings): one setting controls whether a status derived from the score overrides the status the course reports itself, and another controls whether a lesson status can still change after it has been set to complete — adjust these if a course reports 'complete' but not 'passed', or vice versa.
- Mastery score for SCORM 1.2: when a SCORM 1.2 package carries a mastery score, SCORM Cloud compares the reported raw score against it to derive passed/failed — but only when the SCO has not already set its own success status explicitly. Intle writes adlcp:masteryscore into 1.2 packages.
- Registrations and attempts: each learner launch creates a registration; on a Trial plan you can reset registrations to retest. Course Properties also govern attempt handling, which resets run-time tracking so the course appears fresh on a new attempt.
- Delivery model: decide up front between Invitations (learners take the course inside SCORM Cloud) and Dispatch (SCORM Cloud hands the course to your own LMS as a SCORM 1.2 or LTI shell), because reporting lives in different places for each.
Troubleshooting
Import fails with a manifest error such as 'the manifest cannot be found'.
The imsmanifest.xml must sit at the root of the zip, not inside a folder. Re-zip by opening the extracted package, selecting all files inside it, and compressing the selection — do not zip the parent folder. Intle's downloads are already packaged this way, so this usually only appears after a package has been re-zipped by hand.
The course opens in extra windows, or a launch window is blocked by a pop-up blocker.
That happens when SCO Launch Type or Player Launch Type is set to NEW_WINDOW. Open Course Properties -> Launch Behavior, set both to FRAMESET (the default for SCORM content), Save, then relaunch to run everything in one window.
The course plays fine but never registers as complete or passed.
Launch it and open View Debug to see whether the course is setting completion/success and score. Then check the course's Configuration override settings (status-derived-from-score override, and whether status can change after 'complete'), and for SCORM 1.2 confirm the mastery score. Prefer the SCORM 2004 4th Edition download for cleaner separation of completion and pass/fail.
A large package times out during web import.
The browser importer can time out on very large files. For large packages, upload the zip to the 'default' folder inside your 'uploads' directory using an FTP/FTPS client (host: ftp.cloud.scorm.com, username = your SCORM Cloud account email, plus your password), then import it from that folder. Note that some clients, including FileZilla, are not supported — Rustici suggests Cyberduck instead.
Frequently asked questions
Does SCORM Cloud fully support SCORM 2004 4th Edition, including sequencing?
Yes. SCORM Cloud runs Rustici Software's SCORM Engine and supports SCORM 1.2 and SCORM 2004 2nd, 3rd and 4th Editions, including the full Sequencing and Navigation model — plus AICC, xAPI and cmi5. The same engine is licensed to power SCORM playback inside many other LMSs, so conformant packages behave consistently.
Which Intle download should I upload to SCORM Cloud?
Use the SCORM 2004 4th Edition package for fuller reporting: separate completion and pass/fail status, per-objective results, and a 64,000-character suspend-data limit for reliable resume. Choose SCORM 1.2 only if you'll dispatch onward to an older LMS that requires it. Both come from the same Intle generation, so you can switch without regenerating.
How do I test resume/bookmarking works before rolling out?
Launch the course, move part-way through, exit, then relaunch the same registration and verify that position, answers and score restore. SCORM Cloud's debug log can show the suspend-data being written and read. Intle's staged-compression behaviour has dated local API-stub evidence, but the exact release still needs this platform test before rollout.
Can I use SCORM Cloud to check a package before uploading to my real LMS?
Yes — that is one of its main uses. Import the package, launch it, review completion, score and time, and inspect the debug log to confirm the run-time calls. Because SCORM Cloud runs the widely-licensed Rustici SCORM Engine, a package that behaves correctly here is a strong baseline before you import it into your production LMS.
intle packages target SCORM 2004 4th Edition and SCORM 1.2. Package-structure and local resume evidence was recorded against the dated build shown on the compatibility page; it does not verify a later release or a named LMS. For the current per-platform validation status — including SCORM Cloud — see the LMS compatibility evidence page.
Generate a package to test in SCORM Cloud
Describe what you want to teach, download both standards-targeted SCORM versions, then validate the one your SCORM Cloud configuration accepts. Free to start, no card required.
Generate a package free