Skip to main content

Deliver

Dynamic SCORM packages

For LMS administrators: what a dynamic SCORM package contains, the one request it makes at launch, the hosts to allow, how tracking stays in the LMS, and its limits.

Last reviewed

A dynamic package is a SCORM 1.2 or SCORM 2004 package that is uploaded to an LMS once and loads the course as last published from Scormbusters each time a learner opens it. Republishing the course updates it for every learner, in every LMS it is in, without a new upload. Dynamic packages are part of the Enterprise plan. This page is for LMS administrators and IT teams; the author's guide is Dynamic SCORM.

What is in the zip

FileWhat it is
imsmanifest.xmlOne SCO launching index.html, with the course title and pass mark at the time of download. Its identifiers end in _dynamic, so it never replaces a static package of the same course.
scorm-driver.jsThe same SCORM runtime a static package ships: it finds the LMS API and reports status, score, interactions, bookmark and suspend data.
dynamic-launcher.jsFetches the course content, then starts the course.
index.html, styles.css, course.jsonThe loading and status screens, a fallback stylesheet, and the manifest's course file.

The course itself (pages, questions, the Scenes player) is not in the zip. Everything the package ships is MIT-licensed, as in every Scormbusters export.

What the learner's browser requests

At each launch, one request:

GET https://scormbusters.com/api/dynamic/<package key>/content?p=2

p is the launcher's protocol version. Packages downloaded before the shared-runtime release (November 2026) ask with p=1 and keep working unchanged.

  • No cookies are sent or set; the package key in the URL is the only credential. No learner name, ID, score or progress is sent. As with any web request, our hosting providers (Vercel for scormbusters.com, Cloudflare for media.scormbusters.com) see the browser's IP address and user agent.
  • CORS allows any origin (Access-Control-Allow-Origin: *), because LMS content origins vary.
  • The answer is JSON: the course as last published, with an ETag. It is cached at the edge for about a minute, and browsers revalidate it on every launch, so a republish reaches learners within a minute or two.
  • The page scripts every lesson uses (and, for interactive slides, the slide player) are sent once per launch rather than once per lesson, so the answer grows with the course's content, not its lesson count. In our tests a 40-lesson course with an interactive slide and a custom interaction in every lesson is about 0.85 MB before compression; sent whole it is about 9 MB. p=1 packages still receive every lesson whole and run exactly the same pages.
  • Pictures, audio and video then load from https://media.scormbusters.com.

Allow both hosts over https in any proxy, firewall or content filter, and in an LMS that restricts what launched content may load (a Content Security Policy with connect-src, img-src and media-src).

If the request fails, the learner sees "Can't reach the course content" with a Try again button. If the package has been revoked, the course is unpublished or deleted, or the workspace is no longer on Enterprise, the answer is {"status":"retired"} and the learner sees "This course has been retired — contact your learning administrator". In both cases the package does not initialize the LMS session, so nothing in the learner's record changes.

Tracking

Status, score, interactions, bookmark and suspend data go from the package to the LMS API exactly as from a static package, and are never sent anywhere else. The driver never lowers a status or score the LMS already holds.

Progress is saved by lesson (or slide) position. The package tags the suspend data it writes with the course's lesson order at the time, and on the next launch maps saved positions onto the current order: completed lessons that still exist stay completed, a bookmark on a removed lesson moves to the next lesson that still exists. Courses that draw slides at random per attempt keep their bookmark only while it is still in range.

Limits

  • SCORM 1.2 and SCORM 2004 only; cmi5 and xAPI packages are static.
  • One language per package (the course's own); multi-language packages are static.
  • The LMS keeps the title and pass mark from the downloaded manifest. Download a new package to change them.
  • A package keeps the scorm-driver.js it was downloaded with. If a future release ever needs a newer driver, older packages show "This course package needs replacing" instead of a broken course.