You're comparing LMS platforms or buying an authoring tool, and there it is again: "Supports SCORM 1.2 and SCORM 2004." Great. But which one do you actually need?

Short answer: most organizations should use SCORM 1.2. It's simpler, universally supported, and handles 90% of tracking needs. SCORM 2004 adds LMS-controlled sequencing and more storage, but most teams never use those features. Here's how to decide which you actually need.

SCORM is the standard that lets eLearning courses communicate with learning management systems—tracking completion, scores, and progress. There are two versions in active use today: SCORM 1.2 (from 2001) and SCORM 2004. If you need a non-technical overview first, start with our executive guide to SCORM.

Here's the thing most people won't tell you: this debate is mostly academic. For the vast majority of L&D use cases, you could flip a coin and be fine. But since you're here trying to make an informed decision, let me save you some time and walk through what actually matters.

Quick Comparison: SCORM 1.2 vs SCORM 2004

FeatureSCORM 1.2SCORM 2004
LMS SupportUniversal (every LMS supports it)Widespread but inconsistent implementation
Sequencing & NavigationNone (course handles logic internally)LMS-controlled sequencing rules between SCOs
Completion TrackingSingle status field (lesson_status)Separate completion + success tracking
Suspend Data Limit4,096 characters64,000 characters
Interaction DataWrite-onlyRead-write with full question/answer text
ComplexitySimple, stableMore complex, more edge cases
Best ForMost organizations (70%+ of content)Complex learning paths, detailed compliance tracking

What SCORM 2004 Added (And Whether You'll Use It)

SCORM 2004 came out—you guessed it—in 2004, three years after SCORM 1.2. The folks at ADL wanted to address some limitations, so they added a bunch of features. Here's what changed:

Sequencing and Navigation

This is the headline feature. SCORM 2004 lets you set up complex rules about how learners move through content. You can say things like "don't let them access Module 3 until they've passed the quiz in Module 2" or "if they fail this assessment twice, send them back to the remedial section."

Sounds useful, right? Here's the thing: most authoring tools handle this kind of logic internally, within a single course package. You don't need SCORM 2004's sequencing spec to build a course with branching scenarios or conditional navigation. You just build it in Articulate or whatever tool you're using, and it all gets wrapped up in one SCORM 1.2 package that works fine.

Where SCORM 2004 sequencing actually helps is when you want the LMS itself to control navigation *between* separate course objects. That's a pretty specific use case, and honestly, most organizations don't do this. They just build one course, zip it up, upload it, done.

Separate Completion and Success Tracking

SCORM 1.2 has one status field: cmi.core.lesson_status. It can be things like "completed," "passed," "failed," or "incomplete." The problem? You can't easily distinguish between "they finished the whole course but failed the test" and "they quit halfway through."

SCORM 2004 splits this into two fields: cmi.completion_status (did they complete it?) and cmi.success_status (did they pass?). This is genuinely better for reporting. You can now see exactly who finished but didn't pass, which is useful if you're tracking compliance training.

That said, most SCORM 1.2 courses work around this by just using "passed" and "failed" as the primary statuses. Not perfect, but functional enough for most situations.

More Suspend Data

SCORM 1.2 lets you save up to 4,096 characters of suspend data—that's the stuff that remembers where the learner was when they left. SCORM 2004 bumps this up to 64,000 characters.

Real talk: 4,096 characters is usually plenty unless you're building something really complex with tons of bookmarking and state management. Most courses I've seen don't come close to hitting that limit. But if you're building a big simulation or a really long course with lots of saved interactions, the extra space is nice to have.

Better Interaction Tracking

SCORM 1.2 lets you track interactions (quiz questions, essentially), but it's write-only. The course sends data to the LMS, but it can't read it back. SCORM 2004 makes this read-write, so the course can pull up old answers if needed. It also tracks way more detail—full question text, full answer text, objectives, the works.

This matters if you want to do detailed reporting on which specific questions learners are getting wrong. But again, most organizations just look at overall scores, not granular question-level data.

Minor Naming Changes

SCORM 2004 cleaned up some of the data model naming. Instead of cmi.core.lesson_location, it's just cmi.location. Instead of the API object being called "API" (SCORM 1.2), it's "API_1484_11" (SCORM 2004).

Nobody cares about this except developers, and even they don't care much.

So Why Does Everyone Still Use SCORM 1.2?

Because it works, it's simple, and it's supported everywhere.

According to industry data, SCORM 1.2 is used in the vast majority of e-learning content—some estimates put it at over 70%. It's been around since 2001, and every LMS on the planet supports it. Every authoring tool exports to it. It just works.

SCORM 2004, despite having more features, is significantly more complex to implement correctly. The sequencing rules, in particular, are notorious for being interpreted differently by different LMS platforms. You can build a course that works perfectly in one LMS and completely breaks in another because they implemented the sequencing spec differently.

Plus—and this is the kicker—most of the "advanced" features in SCORM 2004 just don't get used. In our experience working with L&D teams, the vast majority don't use LMS-level sequencing. They don't need read-write interactions. They don't hit the suspend data limit. They just need courses to launch, track completion, record a score, and report it. SCORM 1.2 does all of that.

Here's Who Actually Needs SCORM 2004

Okay, so when should you go with SCORM 2004?

1. You're building complex, multi-SCO courses with LMS-controlled sequencing

If you legitimately need the LMS to manage navigation between multiple course objects—like a big learning path where the LMS decides what comes next based on performance—SCORM 2004's sequencing features are built for this.

Example: A medical training program where learners take a pre-assessment, get routed to different modules based on their weak areas, then loop back for reassessment. If you want the LMS to handle that routing logic (not the course itself), you need SCORM 2004.

Most people don't need this. But if you do, you'll know.

2. You need detailed completion vs. success tracking for compliance

If you're in a regulated industry and auditors want to see the difference between "completed the training" and "passed the assessment," SCORM 2004's separate completion_status and success_status fields make reporting cleaner.

Example: In healthcare compliance training, you might need to show that an employee went through all the HIPAA modules (completion) even though they failed the final quiz (success). SCORM 2004 tracks both separately, making audit reports much cleaner.

You can work around this in SCORM 1.2, but 2004 makes it more straightforward.

3. Your authoring tool defaults to 2004 and you don't have compatibility concerns

Some tools (like Articulate Storyline) can export to either version, but they default to SCORM 2004. If your LMS fully supports 2004 and you don't have legacy content to worry about, there's no real downside to sticking with the default. For tool-level differences, see our SCORM authoring tools comparison.

Just test it first. Make sure bookmarking works, completion tracking works, scores report correctly. If it all works, you're fine.

4. You're building massive simulations with complex state management

If you're creating something like a big branching scenario or a simulation that needs to save a ton of learner data across sessions, the extra suspend data in SCORM 2004 (64,000 characters vs. 4,096) can be a lifesaver.

Example: A sales training simulation where learners make dozens of decisions, interact with multiple virtual clients, and need to resume exactly where they left off across multiple sessions. All those choices and state variables add up fast.

This is rare, but it happens.

Here's My Recommendation

If you're not sure, go with SCORM 1.2.

It's simpler, more compatible, and does everything most organizations actually need. You'll have fewer headaches with LMS compatibility, and you won't be paying for features you don't use.

Use SCORM 2004 only if you have a specific reason—like one of the scenarios I listed above. And if you do go with 2004, make absolutely sure your LMS supports it properly. Don't just trust the marketing page. Upload a test course and actually verify that everything works: launching, tracking, bookmarking, reporting, the whole thing.

I've seen too many teams pick SCORM 2004 because it sounds newer and better, only to run into weird bugs six months later when a course won't bookmark correctly or the LMS interprets sequencing rules differently than the authoring tool expected.

What About Mixing Them?

Yeah, you can totally have some courses in SCORM 1.2 and others in SCORM 2004 in the same LMS. Most modern platforms support both without issues.

This is actually pretty common. You might have a bunch of legacy SCORM 1.2 content you bought from a vendor years ago, and now you're building new stuff in an authoring tool that exports SCORM 2004. That's fine. They'll coexist just fine.

Edaxu, for example, handles both SCORM 1.2 and 2004 content in the same library with unified reporting across both versions. So you don't have to worry about inconsistencies when you're mixing standards.

The only thing to watch out for is reporting—make sure your LMS can give you consistent reports across both versions. Some older systems get weird about this, especially with completion vs. success status.

The Honest Truth

Most of the SCORM 1.2 vs. 2004 debate is academic. In practice, for the vast majority of L&D use cases, you could flip a coin and be fine.

The real problems you'll run into have nothing to do with which version you picked. They're things like:

  • Your LMS timing out before the course finishes saving data
  • Popup blockers breaking the SCORM API connection
  • Users closing the browser window before the course calls LMSFinish()
  • Your authoring tool exporting broken packages

Those issues happen with both versions.

So pick SCORM 1.2 unless you have a clear, specific reason to use 2004. Test your courses thoroughly regardless of which version you pick. And spend your energy on building good content, not worrying about SCORM specs.

That's what actually matters.


Ready to see how simple SCORM management can be? Edaxu handles both SCORM 1.2 and 2004 seamlessly. Start a free trial and test your first SCORM course, upload your courses, track completions, and get the reports you need without wrestling with compatibility issues.


Frequently Asked Questions

Can I use SCORM 1.2 and SCORM 2004 courses in the same LMS?

Yes. Most modern LMS platforms support both versions simultaneously. You can have some courses in SCORM 1.2 and others in SCORM 2004 in your content library without any issues. Just make sure your reporting can handle both versions consistently.

Is SCORM 2004 backwards compatible with SCORM 1.2?

No, they're separate standards. A SCORM 2004 course won't run as a SCORM 1.2 course, and vice versa. However, most authoring tools let you export your course as either version, so you can recreate the same course in whichever format you need.

Which SCORM version does Articulate Storyline use?

Articulate Storyline and Rise 360 can both export to SCORM 1.2 and SCORM 2004 (including 2nd, 3rd, and 4th editions). Storyline defaults to SCORM 2004 3rd Edition, while Rise 360 also defaults to SCORM 2004. You can choose SCORM 1.2 from the publish settings in either tool if your LMS works better with it.

Does SCORM 2004 work on mobile devices?

SCORM itself doesn't dictate mobile compatibility—that's more about how the course is built (responsive design, HTML5 vs Flash, etc.). Both SCORM 1.2 and SCORM 2004 courses can work on mobile devices if the content is designed for it and your LMS has a mobile-friendly player.

Can I convert SCORM 1.2 courses to SCORM 2004?

If you have the source files from your authoring tool, yes—just re-export as SCORM 2004. If you only have the published SCORM 1.2 package (the zip file), it's not really possible to convert it without the source. Some tools claim to do this, but the results are usually messy. Better to rebuild from source if you need to switch versions.

Should I choose SCORM 2004 4th Edition over earlier editions?

SCORM 2004 4th Edition is the most recent and most stable version of SCORM 2004. If you're going with SCORM 2004, choose 4th Edition unless your LMS specifically has issues with it (rare). The differences between 2nd, 3rd, and 4th editions are mostly bug fixes and clarifications, not major feature changes.


Further Reading and Sources

Research for this post drew from the following sources:

ET
Edaxu Team
matt@edaxu.com

Edaxu writes practical guides for teams running SCORM, certification, compliance, and professional training programs.