SCORM 1.2 Export: How to Get Your Course Into Any LMS

You've written your course in Word, it reads well, and now your training manager wants it "in the LMS". That last step is where a lot of people get stuck. SCORM sounds technical, the version numbers are confusing, and every LMS seems to have its own upload quirks. The good news: getting a course into almost any system is a short, repeatable process once you know what each piece does.

This guide walks through a SCORM export from start to finish — why SCORM 1.2 is usually the safest choice, how to produce the package, and exactly how to upload it to the LMSs course creators ask about most.

Why SCORM 1.2 instead of a newer version

There are several e-learning standards floating around — SCORM 1.2, SCORM 2004 (in four editions), AICC, xAPI and cmi5. They all solve roughly the same problem: packaging a course so a learning management system can launch it, track completion and record a score.

For most course creators, SCORM 1.2 is the right default, and here's the honest reasoning:

• It's supported everywhere. Moodle, Canvas, TalentLMS, Blackboard, Docebo, LearnDash and almost every other LMS accept SCORM 1.2 without fuss.
• It's simple. It reliably tracks completion, pass/fail and a single score. That covers what the vast majority of courses actually need.
• It avoids edge cases. SCORM 2004 adds sequencing and richer status tracking, but those features are implemented inconsistently across systems, which is where mysterious "course won't mark complete" problems come from.

If your organisation has specifically asked for SCORM 2004 or xAPI, use that. Otherwise, choose 1.2 and save yourself the troubleshooting.

What's actually inside a SCORM package

A SCORM export isn't a special file format — it's just a ZIP file with a particular structure inside. Knowing what's in there helps when something goes wrong.

• Your course content — the HTML pages, styling and any images, audio or video.
• An imsmanifest.xml file — the "table of contents" the LMS reads to understand how to launch and track the course. This is the file an LMS looks for first.
• SCORM runtime files — small JavaScript files that let the course talk to the LMS and report progress.

You never edit these by hand. The point is simply this: if an LMS rejects your upload, it's almost always because it couldn't find a valid imsmanifest.xml — which usually means the ZIP was created the wrong way (more on that below).

Producing your SCORM export in CourseConverter

In CourseConverter, the SCORM export is built to give you a package that's ready to upload, not a pile of files to assemble yourself. The workflow is straightforward:

• Upload or open your Word document and let it convert into a course.
• Check the structure — headings become pages or sections, and your images carry across automatically.
• Choose SCORM 1.2 as your export format.
• Set the completion behaviour you want (for example, mark complete on reaching the final page, or on passing a quiz).
• Export. You'll get a single ZIP file. Do not unzip it — that ZIP is the package the LMS expects.

That last point trips people up constantly. If you unzip the package to "have a look", then re-zip the folder, you often end up with the manifest one level too deep and the LMS can't find it. Keep the file exactly as exported.

Uploading to Moodle

Moodle has first-class SCORM support, so this is one of the smoother experiences.

• Turn editing on in your course and choose Add an activity or resource.
• Select SCORM package.
• Give it a name, then drag your ZIP file into the package file area.
• Under Appearance, decide whether the course opens in the current window or a new one — a new window or pop-up often behaves more predictably for media.
• Save and display, then click through it yourself to confirm tracking works.

If Moodle reports the package is invalid, re-download a fresh export and try again before anything else — a partial upload is a common culprit.

Uploading to Canvas, TalentLMS and others

The pattern is remarkably consistent across systems, even if the menus differ.

• Canvas: Use the Import Course Content tool and choose SCORM Package as the content type, then upload your ZIP. Canvas imports it as an assignment you can place in a module.
• TalentLMS: Inside a course, choose Add, then SCORM | xAPI | cmi5, and upload the ZIP. TalentLMS unpacks and registers it automatically.
• Docebo, LearnUpon, Absorb and similar: Look for an "Add training material" or "Add content" option and pick the SCORM type. Upload the same ZIP.
• LearnDash (WordPress): Use its SCORM upload feature within a lesson or topic and drop the ZIP in.

In every case you upload the same untouched ZIP file. You don't need a different export per platform — one SCORM 1.2 package serves them all. That's the whole point of the standard.

The offline media-bundling option

If your course includes video or audio, you have a decision to make: stream the media from an external host, or bundle it inside the package so everything ships together.

CourseConverter's SCORM export lets you bundle media offline, which means the video and audio files are packaged inside the ZIP rather than linked out to the internet. Here's the honest trade-off:

• Bundling pros: The course works even if a learner has patchy internet or the LMS sits behind a strict firewall. Nothing depends on an external host staying online. It's the most reliable option for corporate environments.
• Bundling cons: The package gets larger. A few short videos are fine; a course stuffed with high-resolution footage can produce a ZIP that exceeds your LMS's upload limit.
• Streaming pros: Smaller package, faster upload.
• Streaming cons: If the host or link breaks, your course breaks with it — and some locked-down networks block external video entirely.

For most internal training, bundling media is the safer choice. If your package ends up too large to upload, compress your videos before converting, or split a very long course into a couple of shorter modules.

Things worth knowing before you ship

A few realities save you from awkward surprises after go-live:

• Test on the real LMS, not just a preview. Previews confirm the content looks right; only the actual LMS confirms completion and scoring are recorded against a learner.
• Watch your upload size limits. Many LMSs cap SCORM uploads somewhere between 100MB and 1GB. Bundled video is the usual reason you'll hit that ceiling.
• Updating means re-uploading. SCORM packages aren't live-editable inside the LMS. When you change the course, you export a fresh package and replace the old one — and you'll need to decide whether existing learners restart.
• Completion settings matter. Decide up front whether "complete" means reaching the end or passing a quiz, and set it before export so you're not chasing it later.
• Pop-up blockers can interfere. If a course launches in a new window and learners report a blank screen, a browser pop-up blocker is often the quiet cause.

The takeaway

A SCORM export is far less intimidating than it sounds. Choose SCORM 1.2 for the widest compatibility, produce a single ZIP in CourseConverter, and upload that exact file to whichever LMS you use — the steps barely change between Moodle, Canvas and TalentLMS. If your course has video, bundle the media for offline reliability unless file size forces your hand. Then do the one thing people skip: launch it on the real system and click all the way through to confirm it marks complete. Do that, and your course will land cleanly in any LMS you point it at.