Scormbee

SCORM test player

Test a SCORM course without uploading it to an LMS.

The player launches your package against a simulated LMS that checks every call the way a strict platform would. You see each call as it happens, the status, score and saved progress the LMS would store, and the error the moment something goes wrong.

Free · no account · runs in your browser

How it works

How to test a package

  1. Drop the ZIP

    The player reads the manifest and starts the course as SCORM 1.2 or SCORM 2004, whichever the package declares. The pass mark from the manifest applies, as in an LMS.

  2. Take the course like a learner

    Answer, get some questions wrong, stop halfway. The log shows each call, its value, what the LMS answered and any error; next to it you see what is stored.

  3. Relaunch, then start over

    Reopen the lesson in the same attempt to check that it resumes where the learner left off, then start a new attempt with nothing saved.

SCORM 1.2 and 2004 side by side

The calls and data you will see in the log

  • API object

    SCORM 1.2
    window.API
    SCORM 2004
    window.API_1484_11
  • Session

    SCORM 1.2
    LMSInitialize(""), LMSFinish("")
    SCORM 2004
    Initialize(""), Terminate("")
  • Read, write, save

    SCORM 1.2
    LMSGetValue, LMSSetValue, LMSCommit
    SCORM 2004
    GetValue, SetValue, Commit
  • Status

    SCORM 1.2
    cmi.core.lesson_status: passed, completed, failed, incomplete, browsed, not attempted
    SCORM 2004
    cmi.completion_status (completed, incomplete…) and cmi.success_status (passed, failed, unknown)
  • Score

    SCORM 1.2
    cmi.core.score.raw, .min, .max
    SCORM 2004
    cmi.score.scaled (−1 to 1), plus .raw, .min, .max
  • Bookmark

    SCORM 1.2
    cmi.core.lesson_location
    SCORM 2004
    cmi.location
  • Suspend data

    SCORM 1.2
    cmi.suspend_data, up to 4,096 characters
    SCORM 2004
    cmi.suspend_data, up to 64,000 characters (4th edition)
  • Session time

    SCORM 1.2
    cmi.core.session_time as HHHH:MM:SS.SS
    SCORM 2004
    cmi.session_time as an ISO 8601 duration, e.g. PT1H5M30S
  • Leaving

    SCORM 1.2
    cmi.core.exit: suspend, logout, time-out or empty
    SCORM 2004
    cmi.exit: suspend, normal, logout, time-out or empty
  • Answers

    SCORM 1.2
    student_response like 0,2 or 1.a,2.b; result "wrong"
    SCORM 2004
    learner_response like 0[,]2 or 1[.]a[,]2[.]b; result "incorrect"

A healthy session

What a correct SCORM 1.2 session looks like

The order matters as much as the values. This is what a well-behaved course sends when a learner comes back and finishes.

Score before status: with a mastery score, a SCORM 1.2 LMS may set passed or failed itself from the raw score.

Commit after every important change, not only at the end, or a crash or a closed tab loses it.

Always finish. Without LMSFinish or Terminate the attempt often stays open, no time is recorded and the next launch may not resume.

LMSInitialize("")                        // "true"
LMSGetValue("cmi.core.entry")            // "resume"
LMSGetValue("cmi.suspend_data")          // saved state
LMSGetValue("cmi.core.lesson_location")  // "5"
LMSSetValue("cmi.core.lesson_location", "6")
LMSSetValue("cmi.core.score.raw", "80")
LMSSetValue("cmi.core.score.min", "0")
LMSSetValue("cmi.core.score.max", "100")
LMSSetValue("cmi.core.lesson_status", "passed")
LMSCommit("")
LMSSetValue("cmi.core.session_time", "0000:12:30.00")
LMSSetValue("cmi.core.exit", "")
LMSFinish("")
An empty cmi.core.exit ends the attempt normally. "suspend" asks the LMS to keep the data so the next launch resumes.

Common problems

Error codes and runtime problems, and how to fix them

The log shows the error code after every failed call. These are the ones you will meet most often.

The log stays empty

What it means: The course looks for window.API or window.API_1484_11 in its parent frames and its opener, finds nothing and runs without reporting. Usually the content loads from another domain, or the manifest declares the other SCORM version.

How to fix it: Keep the content inside the package and make schemaversion match the API the course looks for.

Session order: 301 (1.2), 103, 104, 112, 113, 122, 132, 142 (2004)

What it means: Data read, written or committed before Initialize (301, 122, 132, 142), Initialize called twice (103), calls after Terminate (104) or Terminate out of order (112, 113). Typical when every page sets up SCORM again.

How to fix it: Use one SCORM wrapper for the whole course, initialize first and track whether the session is open.

Unknown element: 201 (1.2), 401 (2004)

What it means: The element does not exist in this version: a typo, cmi.completion_status in SCORM 1.2 or cmi.core.lesson_status in 2004.

How to fix it: Use the names of the version you declare; mixed names mean the course was packaged as the wrong version.

Read only or write only: 403, 404 (1.2), 404, 405 (2004)

What it means: The course wrote an element only the LMS sets, such as cmi.core.student_name or cmi.entry, or read a write-only one, such as cmi.core.session_time or cmi.exit.

How to fix it: Remove the call. The LMS fills read-only elements; write-only ones never come back.

Wrong value: 405 (1.2), 406, 407 (2004)

What it means: Wrong type or out of range: "80%" instead of 80, a scaled score of 80 instead of 0.8, the other version's time format, "complete" instead of "completed".

How to fix it: Send plain decimals, scaled scores from −1 to 1, your version's time format and words from its vocabulary.

Suspend data too long

What it means: SCORM 1.2 allows 4,096 characters in cmi.suspend_data, SCORM 2004 4th edition 64,000. Some LMSs reject longer values, others cut them silently; either way the course loses its place. The player warns when a course goes over.

How to fix it: Store indexes and flags instead of texts, compress the state, or export SCORM 2004.

Status never reaches completed

What it means: The course sets completed on the last slide, but the window closes before a commit or LMSFinish never comes. In SCORM 1.2 with a mastery score, the LMS may also replace completed with passed or failed.

How to fix it: Commit when the status changes, finish when the window closes, and keep the pass mark in one place.

Your files never leave your computer

Files are read in your browser; nothing is uploaded to Scormbee or anyone else, and nothing is kept after you close the tab. That makes it safe to check confidential or client courses.

Questions

Frequently asked questions

Can I test a SCORM package without an LMS?

Yes. The player gives the package a simulated LMS with the SCORM 1.2 and 2004 APIs, checks every call against the data model and shows the results live. No upload, no account.

How is this different from testing in my LMS?

It tells you in seconds whether the course talks to an LMS correctly. Do the final check in your own LMS, because each platform has its own settings for attempts, new versions and how content opens.

It works here but shows incomplete in my LMS. Why?

Compare settings: a mastery score that overrides the status, an LMS that records status only after LMSFinish, or a window closed before the last commit. A new version uploaded over an old one can also keep the old attempt's status.

Can I test resuming a course?

Yes. Relaunch the lesson in the same attempt and the player hands the course its saved cmi.entry, bookmark and suspend data, just as an LMS would. The data lives only in this tab.

Which SCORM version should my course use?

SCORM 1.2 works almost everywhere but has one status field and 4,096 characters of suspend data. SCORM 2004 4th edition separates completion and success and allows 64,000. Scormbee exports both from one course.

From the blog

Further reading

10 November 2026 · 8 min read

What an LMS Actually Records from a SCORM Course

What a SCORM course sends to your LMS: completion, pass/fail, score, time, bookmark, suspend data and interactions, plus why courses get stuck at incomplete.

Read →

Tired of debugging someone else's package?

Convert it into an editable Scormbee course and export a package that initializes, commits and finishes the way LMSs expect. The editor opens without an account.