---
title: "Scorm Lab"
description: "SCORM Lab is a debugger rather than a player. You drop a SCORM 1.2 or 2004 package onto the page and it runs against a real runtime while showing you the transcript: every Initialize, GetValue, SetValue and Commit the course makes, the current state of the CMI data model, the sequencing decisions being taken, and the moment something returns an error code instead of a value."
canonical_url: "https://scorm-tools.com/tools/scorm-lab"
last_updated: "2026-10-31T10:21:58.743Z"
---

SCORM Lab is a debugger rather than a player. You drop a SCORM 1.2 or 2004 package onto the page and it runs against a real runtime while showing you the transcript: every `Initialize`, `GetValue`, `SetValue` and `Commit` the course makes, the current state of the CMI data model, the sequencing decisions being taken, and the moment something returns an error code instead of a value.

That transcript is the point. Most SCORM failures are discovered late, in a client's LMS, by someone who cannot see what the course was trying to do — the module simply does not record a completion and nobody can say why. Seeing the call sequence usually makes the cause obvious within a minute: a course that never calls `Initialize`, a completion status written to the wrong element, suspend data exceeding what the LMS will store.

Nothing is uploaded. The package is unzipped in the browser and served locally through a service worker, which means unreleased client material stays on your machine — a practical requirement for agency work, and the reason the tool is usable at all under most confidentiality terms.

It is free and needs no account, though an email is requested. There is a native macOS build in preparation with session replay and LMS quirk profiles; it is not listed here until it is actually purchasable.

**Disclosure:** built by LOST END FOUND, which publishes this directory. It is listed under the same rules as everything else, is never an editor's pick, and never occupies a paid slot.