SCORM authoring tools and course frameworks
Where the course gets made — and where its SCORM output is decided.
Compiled and checked by the scorm-tools.com editor. Last updated .
The authoring tool decides what standard your course speaks, long before anyone uploads it. That makes "which standards does it publish?" the first question worth asking, and the one vendor comparison pages answer least clearly — plenty of tools advertise xAPI support that turns out to mean a statement endpoint rather than a conformant launch.
Three quite different things live in this category. GUI authoring tools are the familiar commercial suites: you assemble slides, interactions and quizzes, then publish a package. Code-first frameworks hand you a build pipeline instead, which is the right shape when courses are versioned in git and reviewed like software. Markdown and document converters sit between the two, turning writing into a package with the least ceremony.
Two practical notes. Publishing SCORM 1.2 remains the safest default for reaching old LMSs, and most tools still offer it alongside 2004 — check which edition. And accessibility varies enormously between tools that claim WCAG conformance; if that matters to your client, test the published output rather than trusting the brochure.
11 tools · 11 open source · 2 support cmi5
Order is editorial and never for sale: standards coverage first, then maintenance state, then popularity, then alphabetical. How we list .
Tools in this category
Filter these tools
Showing 11 of 11
Standards supported: 1.2 · 2004
Licence: GPL-3.0Pricing: Open sourceStandards supported: 1.2 · 2004 · xAPI
Licence: GPL-3.0Pricing: Open sourceStandards supported: 1.2 · 2004 · xAPI · cmi5 · LTI
Licence: MITPricing: Open sourceStandards supported: xAPI
Licence: GPL-3.0Pricing: Open sourceStandards supported: 1.2
Licence: MITPricing: Open sourceStandards supported: 1.2 · 2004 · xAPI · cmi5
Licence: Apache-2.0Pricing: Open sourceStandards supported: 1.2 · 2004 · xAPI
Licence: BSD-3-ClausePricing: Open sourceStandards supported: 1.2
Licence: AGPL-3.0Pricing: Open sourceStandards supported: 2004
Licence: Apache-2.0Pricing: Open sourceQuestions people ask about authoring tools & course frameworks
Which authoring tools publish cmi5?
Far fewer than claim to. cmi5 needs the full AU lifecycle — launch, session identifier, moveOn rules — not just an xAPI endpoint. The standards matrix on each listing shows what we could verify and where the claim came from; the cmi5 hub page lists the tools together.
Do I need a paid authoring tool at all?
Not necessarily. If your courses are text, images and simple assessment, an open-source framework or a markdown-to-SCORM converter produces a perfectly conformant package. Paid suites earn their money on complex interactions, branching simulation, review workflows and support.
What is the difference between SCORM 1.2 and 2004 output?
1.2 is simpler, universally supported, and limited: one completion status, a coarse data model. 2004 adds sequencing and navigation, a separate success/completion distinction, and richer objectives — at the cost of LMSs implementing it inconsistently. Publish 1.2 unless something specific requires 2004.
Can I move a course between authoring tools?
Rarely without rework. Published packages are portable; source projects generally are not. That lock-in is the strongest argument for the code-first frameworks in this category, where the source is plain text you own.