How to actually host a SCORM file. Without an LMS.

Every freelance instructional designer who has ever sent a SCORM 1.2 package to a client has gotten the same email back: "hey — I downloaded the file but it doesn't open?" A SCORM file isn't a file you open. It's a runtime. It needs a host. And until very recently, the answer to "where do I host it?" was either "buy an LMS" or "give up and send a Loom."

This post is the article we wish we'd had when we started. Four real options, what each costs, how they actually feel in the hands of a non-technical client, and the SCORM-API gotchas no one tells you about until you've broken production.

A SCORM file isn't a file you open. It's a runtime. It needs a host.— the sentence that explains 80% of this

What "hosting SCORM" actually means.

A SCORM package is a .zip with two things in it: your authored course (HTML, JS, images, video) and a manifest file (imsmanifest.xml) that tells the host how to start it. Crucially, the course expects to talk to a runtime — a JavaScript API named API for SCORM 1.2 or API_1484_11 for SCORM 2004 — that it can call to read and write learner state: completion, score, suspend data, location, the whole envelope.

"Hosting SCORM" means: extracting the zip, serving the files over HTTPS, and injecting a working API into the page so the course can call LMSInitialize(), LMSSetValue(), and LMSFinish() and not crash. An LMS does this for you. So does every other option below.

The four real options, ranked.

We tested each of these by uploading the same 240MB Storyline 360 package (a 14-minute AML compliance refresher with branching scenarios, two assessments, and one drag-and-drop). Each platform was rated on: did the SCORM run?, did it look like a portfolio?, and did a non-technical client manage to launch it on the first try?

SCORM API gotchas no one warns you about.

Even on a working host, three things will bite you. Here they are in order of pain.

1. cmi.completion_status vs cmi.core.lesson_status.

If your course was authored as SCORM 2004 and you upload it to a host that only speaks 1.2 (or vice versa), the API names don't match — and your course will silently fail to register as "complete." Storyline lets you publish as either; check the publish dialog before you yell at the host.

2. The "API not found" race condition.

SCORM courses look for the API on the parent window during page load. If the host injects the API after the iframe has started looking, you get a silent "API not found" — the course runs, but no data is recorded. A good host injects the API before the iframe loads.

3. SCO suspend_data length limits.

SCORM 1.2 spec caps cmi.suspend_data at 4,096 characters. SCORM 2004 raised it to 64,000. Storyline encodes a lot of state into this field — and if you have a long branching course, you can hit the limit and have your "resume where you left off" silently break. SCORM 2004 4th Edition is the safe default.

// 1. The course looks for the API on parent.
// If it can't find it within 500 polls, it silently fails.
var API = findAPI(window);

// 2. Initialize the session. Always returns "true" on a good host.
API.LMSInitialize("");

// 3. Read and write learner state.
API.LMSSetValue("cmi.core.lesson_status", "completed");
API.LMSSetValue("cmi.core.score.raw", "87");
var who = API.LMSGetValue("cmi.core.student_name");

// 4. Commit changes + close the session.
API.LMSCommit("");
API.LMSFinish("");

When to choose xAPI instead.

If you're authoring new content from scratch in 2026, consider xAPI ("Tin Can") over SCORM. xAPI is more flexible — you can capture interactions outside a single course session, support offline learning, and store statements in any LRS (Learning Record Store) you want. Most modern authoring tools (Storyline, Rise, Captivate, iSpring) support xAPI alongside SCORM.

The catch: xAPI needs an LRS to talk to. SCORM Cloud bundles one. Training OS logs and exports statements via its own pipeline. If you self-host, you're spinning up something like Learning Locker. For a freelance ID, the practical advice is: author in SCORM 1.2 + xAPI in parallel, host on something that gives you both, and let the client pick.

TL;DR — just tell me what to do.

If you're a freelance ID with a portfolio to show: use a purpose-built hosting service (we obviously like ours, but Rise public links work too). You'll be live in 11 minutes.

If you're dispatching courses to client LMSes: SCORM Cloud, full stop. Their dispatch is unmatched.

If you write code for fun: scorm-again on a small DigitalOcean droplet. You'll learn a lot. You'll also spend a Saturday on it.

If you're sending a Loom: please don't. Just upload it somewhere that runs it.