Skip to main content
ppt-to-scorm.com
← Home LEARN

What is SCORM?

The file format your LMS expects when you upload a course. Here's what's inside the .zip, what your LMS does with it, and the handful of terms you'll see in admin screens — in plain English, so the conversation with your LMS admin is short.

SCORM in one paragraph

SCORM stands for Sharable Content Object Reference Model. In practice it's a packaging convention: take your course (HTML, JavaScript, images, audio, the lot), wrap it with a small XML file that describes the structure and tracking rules, and zip it. Any LMS that "supports SCORM" knows how to read that zip, host the contents, and exchange a few standardised messages with the course while a learner is using it — completion status, score, time spent, and a small bag of "where did the learner leave off" data.

You don't need to know the spec. You need to know three things: the file your converter produces is a single .zip; your LMS admin uploads that zip into a course slot in the admin UI; once it's live, learner activity flows back into the LMS reports. Everything else is plumbing the LMS handles for you.

THE FLOW

.zip → manifest → LMS.

  1. STEP 1
    .zip

    The single file we deliver. Contains your slides, JS player, images, audio.

  2. STEP 2
    imsmanifest.xml

    Inside the zip. Tells the LMS the entry HTML, structure, and tracking rules.

  3. STEP 3
    Your LMS

    Reads the manifest, hosts the content, records completion and scores.

SCORM 1.2 vs 2004 — does it matter?

You'll see two versions referenced: SCORM 1.2 (2001) and SCORM 2004 (multiple editions). For 95% of courses converted from PowerPoint, SCORM 1.2 is correct: every major LMS supports it, every reporting workflow assumes it, and the small features 2004 adds (sequencing rules, deeper score reporting) aren't ones a slide-based course needs.

SCORM 2004 matters when your LMS admin specifically asks for it, or when your training has branching pathways the LMS itself needs to enforce. If you don't know which to ask for, default to 1.2. We'll flag it if 2004 is the better choice for what you're doing.

Deeper read: SCORM 1.2 vs 2004 for PowerPoint — which to pick and why .

What your LMS admin actually does on upload

  1. Open your LMS admin UI and create a new course (some LMSs call it a module or learning object). Look for an Upload SCORM or Add SCORM package button on that screen.
  2. Drop in the .zip we sent. The LMS reads imsmanifest.xml, unpacks the rest, and registers the course internally — usually a few seconds.
  3. Assign it. Decide who can see it, whether it counts toward a curriculum, and what completion threshold (a score % or just viewed all slides) marks it as passed.

That's it. Most LMS admins do this in under two minutes once they've done it once. If yours hasn't, the sample SCORM zip is a safe thing to practise on — it's a real package, not a placeholder.

LEARNER SEES

A clean course player — slides, navigation, optional quiz, progress bar. They click through, do the quiz if there is one, hit Finish. They never see the manifest, the tracking variables, or the LMS plumbing.

LMS TRACKS

Whether the learner started, whether they completed, their score (if there's a quiz), time spent, and suspend data — a small note the course leaves so the learner can resume mid-course on their next visit.

Glossary

imsmanifest.xml
The spec file inside the SCORM zip. Tells the LMS the course's entry HTML, structure, and tracking rules. Generated automatically — you never edit it by hand.
suspend_data
A small bookmark (capped at ~4KB in SCORM 1.2) the course writes to the LMS so a learner can resume where they left off. If a course doesn't resume properly, suspend_data is usually the suspect.
cmi.core.lesson_status
The variable the course sets to completed, passed, failed, or incomplete. This is what flips Completed badges in your LMS reports.
cmi.core.score.raw
The numeric score the course reports back to the LMS. Your LMS decides what counts as a pass.