What Is SCORM? The Complete Guide for L&D Teams

What is SCORM? Is it a file type? A standard? Something you just upload into an LMS and hope for the best?

If you're like most L&D practitioners, you accepted SCORM as part of the workflow a long time ago, no questions asked. That's fine.

But if you're now being asked to make decisions about it: which version, whether it's still the right choice, how to actually create a package, this is what you need to know. The good, the bad, and the (weird) parts nobody talks about.

What is SCORM? 

SCORM stands for Sharable Content Object Reference Model. It is a technical standard: a set of rules that defines how eLearning content and LMS platforms talk to each other.

Imagine you handed a kid a DVD and asked them to play it. The kid grabs a CD player, thinking hey, this looks like the right shape. But we know CD ≠ DVD.

So what happens? The kid hits play and nothing happens. That's a compatibility problem.

The same issue existed before SCORM. Someone might upload a course into an LMS only to find the animations didn't play, the buttons didn't work, or the progress didn't save. SCORM fixes that. It's a set of rules that defines how a course is packaged, how it launches inside an LMS, and how learner data like completion, score, and time spent gets recorded.

Any course built to SCORM standards can be uploaded to any SCORM-compliant LMS and work the same way, regardless of which tool made it.

🤔 Did you know? The U.S. Department of Defense developed SCORM because they were tired of building digital training content for the military that only worked in specific systems. They delivered the first version in 2000 (along with the mouthful of an acronym).

How does SCORM work? 

In case someone with a technical background is asking...

SCORM defines a standard way for eLearning courses to interact with a Learning Management System.

It governs three core parts of eLearning delivery:

1. ‍Content packaging
   A SCORM course is packaged as a single ZIP file containing all course assets and a manifest file (imsmanifest.xml). The manifest tells the LMS what the course includes, how it is structured, and which file to launch first. Because every SCORM package follows the same format, LMS platforms can import courses without custom setup.‍
2. Course launch and communication
   When a learner opens a SCORM course, the LMS launches it in a browser window or embedded frame. While the course is running, it communicates with the LMS through a standardized JavaScript interface. The course sends updates to the LMS including completion status, progress, quiz results, and pass/fail data.‍
3. Tracking and reporting
   SCORM defines how learner data is recorded inside the LMS. At its core, it captures completion status, pass/fail results, quiz scores, time spent, and basic interaction data like question responses. Because this data follows a shared standard, reports stay consistent even when courses are built in different authoring tools or managed across different teams.

SCORM 1.2 vs SCORM 2004

SCORM exists in multiple versions, but most organizations today choose between SCORM 1.2 (released in 2001) and SCORM 2004. No, the naming convention does not make sense.

Both follow the same core principles: standardized packaging, LMS communication, and learner tracking. Where they differ is in reporting depth and data limits.

SCORM 1.2 covers the fundamentals: whether a learner completed a course, whether they passed, and how long it took. It offers the broadest LMS compatibility and covers most basic tracking scenarios.

SCORM 2004 goes further, separating completion status from success status and supporting more detailed interaction data at the question level. That distinction matters in regulated industries like pharmaceuticals or finance where audit trails require separate records of course completion and assessment results.

Because this data follows a shared standard regardless of version, reports stay consistent even when courses are built in different authoring tools or managed across different teams.

Which version should you choose?

Default to SCORM 1.2 unless you have a specific reason to upgrade. It works in virtually every LMS and covers the vast majority of training scenarios most teams actually run into.

Choose SCORM 2004 if you need separate completion and success tracking or detailed interaction data. One caveat: SCORM 2004's sequencing features are inconsistently supported across LMS platforms, so take that into consideration.

Where does SCORM fall short?

SCORM solves a specific problem well: packaging a course so it runs reliably in any LMS and reports back foundational metrics. For many training programs that's enough.

But the way organizations think about learning has shifted since 2000 (I mean, we all survived Y2K). The expectation now is that L&D supports performance in the flow of work, ties learning to measurable outcomes, and keeps content agile enough to update as the business changes.

SCORM was designed in an era of click-through modules, and those expectations expose its limits quickly:

• Thin analytics
  ‍SCORM tracks completion, score, and time spent. What it can't capture is nuanced behavior like drop-off points, rewatch patterns, or practice performance.
• LMS-bound by design
  ‍SCORM assumes the learner is inside an LMS and that the course can communicate back in real time. As learning moves into Slack, mobile apps, and on-the-job workflows, SCORM data doesn't follow.
• Limited learning design flexibility
  ‍SCORM maps cleanly to linear course structures. Adaptive paths, scenario-based practice, and just-in-time experiences sit outside its scope.
• Inconsistent implementation
  ‍LMS vendors implement SCORM with their own quirks. A package that works in one LMS can behave differently in another.
• High maintenance overhead
  ‍Every content update requires re-exporting and re-uploading a new ZIP. If you're working in an AI-native authoring platform, existing SCORM packages often can't be edited inside those tools at all.

Ultimately, the decision around whether to use SCORM is really an exercise in change management. If you have a robust content library that you plan to keep up to date, and it is all SCORM packages, moving away is a significant undertaking.

If, on the other hand, you're looking to reimagine what it means to deliver learning, you may find yourself choosing a different path, one where modern tooling has made the alternatives genuinely viable.

What are alternatives to SCORM? 

SCORM was designed to solve a specific interoperability problem between courses and LMS platforms. As you can imagine, the way we deliver learning has grown considerably more complex since 2001, and the standards have had to keep up.

xAPI (Experience API)

If you identify somewhere on the spectrum between luddite and tech-curious, you may have heard the term API. An API, or application programming interface, is a connection between one piece of software and another. For example, at Synthesia, we have customers who want to create videos from a dataset in a spreadsheet, so we have an API that allows you to generate a video from inside Google Sheets.

xAPI was designed by the same people who created SCORM as a deliberate successor. Released in 2013, it allows any system to send a structured statement to a Learning Record Store (LRS).

(If that sounds like gobbledygook, here's what it means.) Let's say you share a video training with employees via Slack. You can decide what data would be helpful to collect, structured as subject-verb-object statements. For example: "Sarah completed the video." "James stopped watching at minute five." "Maria rewatched the video three times."

Those statements give you a richer picture of how training content is actually being used. With specific structured statements, you can also collect data that gets closer to measuring behavioral change.

cmi5

cmi5 was released in 2016 to bridge SCORM and xAPI. It uses xAPI for data tracking, but adds back the structured course launch and completion rules from SCORM. Essentially, it puts some guardrails on xAPI data.

This was designed as a bit of a patchwork solution to help teams transitioning from SCORM to xAPI. For example, you might use SCORM for compliance tracking, which has regulatory implications. cmi5 gives you a path to transition toward xAPI without losing the structured completion reporting that compliance programs require.

AICC

Truthfully, I've never encountered AICC in the wild. It predates SCORM and passes data to an LMS over HTTP rather than through a JavaScript API. It is a legacy format that is still supported in some LMS platforms, particularly older custom solutions.

Choosing between formats

If your training lives primarily in an LMS and your reporting needs are straightforward, SCORM is still the right default. (Estimates put somewhere between 60 and 80 percent of all corporate training content delivered via SCORM in 2026.) If you're building something more ambitious, or your learning strategy is starting to extend beyond the LMS, xAPI or cmi5 may give you the infrastructure to support it.

How to create a SCORM package

Creating a SCORM package requires two things:

1. An authoring tool that supports SCORM export
2. An LMS that supports SCORM imports

The authoring tool is where you build the course content and define the completion rules, such as a minimum score or time spent. The LMS is where learners access the content and where tracking data gets recorded.

Most authoring tools follow the same general workflow. You build your course content, set your completion criteria, choose your SCORM version, and export. The tool handles the packaging, generating the imsmanifest.xml and zipping everything into a file ready for upload.

💡Tip: If you're evaluating authoring tools, our eLearning authoring tools guide can help you decide.

Does Synthesia support SCORM packages? 

Synthesia supports SCORM packages as a delivery format for video-based training. Videos can be exported as SCORM 1.2 or SCORM 2004 packages and uploaded to any SCORM-compliant LMS.

The workflow looks like this:

What happens when your video content changes?

Traditional SCORM workflows require re-exporting and re-uploading a package every time content changes. Synthesia's SCORM export embeds a dynamic video player, so updates to the video are reflected in the LMS without regenerating or re-importing the package. If you're managing compliance training or product content that changes frequently, that's a lot less re-uploading.

Can one SCORM package support multiple languages?

For global training programs, a single SCORM package can support multiple languages. With Synthesia's multilingual video player, learners can select their preferred language within the same course. Completion is tracked the same way regardless of which language they choose, so your LMS reporting stays consistent across regions.

The future of SCORM

I'm not in the prediction business, and there's plenty written about the death of SCORM that has aged poorly over the past decade. What I will say is this: L&D has historically been stuck with the short end of the technology stick. The tools that other functions take for granted often arrive in learning environments years later, watered down, or bolted onto infrastructure that was never designed for them.

Even a company like Synthesia, which is actively pushing the boundaries of what AI can enable for learning, has to accommodate SCORM. That's not a criticism. That's the reality of where enterprise learning infrastructure is today.

The more interesting question is whether the conversation is even about SCORM anymore. Packaging standards are infrastructure. What they enable, or constrain, is the real debate. As organizations start asking learning to demonstrate behavioral change rather than completion, the standard that tracks it has to keep up with that ambition.

Moving away from SCORM costs time, money, and organizational will. It means managing a change curve around where people go for content, how learning gets tracked, and what the LMS is even for. For most organizations, that's not a 2026 conversation. For some, it already was.

Whether SCORM finds its obsolescence in the next decade or quietly persists for another twenty years, the more important shift is already happening. Less focus on how content is packaged. More focus on what it actually changes.