Scormbee

SCORM inspector · manifest viewer

See what is inside a SCORM package without unzipping it.

Drop a ZIP and read its imsmanifest.xml as a clear tree instead of raw XML: the course structure, what each item launches, the files it needs, the SCORM version, the pass mark and what takes up the space. It also recognizes the authoring tool that made the package.

Free · no account · runs in your browser

How it works

How to inspect a package

  1. Drop the ZIP

    Any SCORM 1.2 or 2004 package from any tool. If the manifest sits in a subfolder because the folder was zipped, the inspector still finds it.

  2. Walk from items to files

    Start with the organization, the outline learners see. Each item leads to the resource it launches, each resource to its files and dependencies.

  3. Decide what to do with it

    Keep it, fix it or convert it. When the inspector recognizes a tool Scormbee imports, turn the package into an editable course straight away.

Reading a manifest

The three parts of imsmanifest.xml

Every SCORM package has one manifest at the root of the ZIP. Here is a single-SCO SCORM 2004 manifest, trimmed to what matters.

metadata names the standard: schemaversion is 1.2, or CAM 1.3, 2004 3rd Edition or 2004 4th Edition.

organizations is the table of contents. An item with an identifierref launches a resource; in SCORM 2004 it can carry sequencing, here a primary objective passed at a scaled score of 0.8.

resources lists what can be launched and its files. adlcp:scormType="sco" marks a SCO, which talks to the LMS; an asset never does.

<manifest identifier="fire-safety" version="1.0"
  xmlns="http://www.imsglobal.org/xsd/imscp_v1p1"
  xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3"
  xmlns:imsss="http://www.imsglobal.org/xsd/imsss">
  <metadata>
    <schema>ADL SCORM</schema>
    <schemaversion>2004 4th Edition</schemaversion>
  </metadata>
  <organizations default="org">
    <organization identifier="org">
      <title>Fire safety basics</title>
      <item identifier="item_1" identifierref="res_1">
        <title>Fire safety basics</title>
        <imsss:sequencing>
          <imsss:objectives>
            <imsss:primaryObjective objectiveID="PASS"
              satisfiedByMeasure="true">
              <imsss:minNormalizedMeasure>0.8</imsss:minNormalizedMeasure>
            </imsss:primaryObjective>
          </imsss:objectives>
        </imsss:sequencing>
      </item>
    </organization>
  </organizations>
  <resources>
    <resource identifier="res_1" type="webcontent"
      adlcp:scormType="sco" href="index.html">
      <file href="index.html"/>
      <file href="player.js"/>
      <file href="media/extinguisher.webp"/>
    </resource>
  </resources>
</manifest>
In SCORM 1.2 the namespaces end in imscp_rootv1p1p2 and adlcp_rootv1p2, the attribute is adlcp:scormtype, schemaversion is 1.2 and the pass mark is <adlcp:masteryscore>80</adlcp:masteryscore> in the item.

What the inspector shows

Every view of the report, explained

  • Overview

    What it shows
    Title, SCORM version and edition, counts of items, SCOs, resources and files, sizes, launch file, pass mark
    Why it matters
    The one-screen answer to "what is this and will my LMS take it".
  • Structure

    What it shows
    Organizations as a tree: items, hidden ones (isvisible="false"), SCO or asset, the default organization
    Why it matters
    The outline the LMS builds. Several SCOs mean the LMS has to move learners between them.
  • Resources

    What it shows
    Each resource with its href, files, missing files and dependencies
    Why it matters
    Shared scripts often sit in a dependency; if it breaks, every SCO using it breaks.
  • Files

    What it shows
    Size by file type and the largest files
    Why it matters
    Where the megabytes go before you hit an upload limit.
  • Manifest

    What it shows
    imsmanifest.xml itself, with syntax colouring
    Why it matters
    What the tree leaves out: full metadata, sequencing, extra attributes.
  • Made with

    What it shows
    The authoring tool the package most likely comes from
    Why it matters
    Where the source probably lives, and whether Scormbee can convert it.

Packages from other tools

You know which tool made it. Now what?

Authoring tools leave fingerprints in their packages: folder names, scripts, data formats. The inspector looks for those of isEazy Author, Articulate Rise 360 and Storyline 360, Adobe Captivate, iSpring, Adapt, H5P, Elucidat, Easygenerator and Scormbee, which helps when you inherit courses with no source files.

isEazy Author packages convert into editable Scormbee courses 1:1, and Adapt keeps its content in an open format, so it converts well too. Rise, Storyline, Captivate and iSpring store content for their own players, so Scormbee rebuilds those courses with AI from their text and images. Some packages hold no course at all, only a launcher that loads it from the vendor's server; then ask for a regular export.

A word on sequencing

SCORM 2004 manifests can carry sequencing rules (imsss:sequencing): which SCO comes next and how results roll up. It is the least consistently supported part of the standard, so one SCO that handles its own navigation is the safe choice for most courses.

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

What is a SCORM manifest?

imsmanifest.xml is the XML file at the root of every SCORM package. It describes the course structure, the files and the SCORM version, and it is the first thing an LMS reads when you upload the ZIP.

How do I view a SCORM manifest without an LMS?

Drop the ZIP into the inspector. You get the manifest as a tree and the XML itself with syntax colouring. Nothing is uploaded.

How can I tell which tool made a SCORM package?

The inspector looks for the files and data formats typical of each authoring tool and names the most likely one. Packages it does not recognize still open in Scormbee, which converts what it can read.

Why does my package have several SCOs?

Some tools export each lesson as its own SCO. The LMS then has to move learners between SCOs and combine their results, which is where platforms differ most. One SCO per course is the simplest setup.

Why is my package so big?

Check the size by file type. Video is usually most of it, then full-resolution images and fonts. Compress video, resize images to their display size or host long videos elsewhere.

From the blog

Further reading

Articulate Rise 360, Articulate Storyline 360, Adobe Captivate, iSpring Suite, isEazy, Easygenerator and Elucidat are trademarks of their respective owners. Scormbee is not affiliated with or endorsed by them.

Found a course you want to change?

Convert it into an editable Scormbee course, change what you need and export SCORM 1.2 or 2004 again. The editor opens without an account.