SCORM wrapper

What is a SCORM wrapper?

A SCORM wrapper is a JavaScript library that acts as an abstraction layer between the content of an e-learning course and the LMS API. Its function is to automatically manage the communication between the two: starting the learning session, recording the learner’s progress, submitting the score, and closing the connection correctly — without the developer having to manually write each call to the SCORM standard.

For L&D and corporate training teams, the SCORM wrapper is the technical component that makes it possible for any course published in SCORM format to work correctly in any compatible LMS, reliably recording the completion status, time spent, and score for each learner. Without it, tracking SCORM activities in the LMS is simply not possible.

How a SCORM wrapper works, step by step

When a learner launches a SCORM course from the LMS, the wrapper executes a four-phase process in the background, completely transparent to the user:

• API location: the wrapper searches for the API object that the LMS exposes in the browser environment (current window, parent window, or opener). This step is critical because different LMS platforms implement the API at different levels of the window tree.
• Session initialization: once the API is located, it calls LMSInitialize("") (SCORM 1.2) or Initialize("") (SCORM 2004) to open communication between the course and the LMS.
• Data exchange: throughout the course, the wrapper sends and receives values from the SCORM data model: completion status, score, session time, and other tracking parameters configured in the package.
• Session close: when the learner exits the course, the wrapper persists all data and terminates communication to ensure the LMS correctly records progress — even if the learner closes the window unexpectedly.

This entire process is handled automatically by the wrapper, freeing the developer from having to manage connection errors, differences between SCORM versions, or LMS incompatibilities.

SCORM wrapper vs. direct API implementation

There are two ways for a course to communicate with the LMS: implementing SCORM API calls manually, or using a wrapper that abstracts that complexity. For technical teams, the difference in development effort and reliability is significant:

Most widely used SCORM wrappers in e-learning

There are several open-source libraries and integrated solutions that act as SCORM wrappers. The most common in corporate training projects are:

• pipwerks SCORM API Wrapper: created in 2008 by Philip Hutchison, it is the reference library for the e-learning development community. Compatible with SCORM 1.2 and SCORM 2004, open source (MIT license), and used in thousands of courses worldwide.
• ADL APIWrapper.js: the original wrapper developed by the ADL (Advanced Distributed Learning Initiative), the organization that created the SCORM standard in 1999. It serves as the technical reference base for many other implementations.
• SCORM Again: a modern open-source library designed to address the limitations of classic wrappers in development environments using modern JavaScript frameworks.
• Built-in wrappers in authoring tools: tools like isEazy Author include their own SCORM communication layer in the exported package. L&D teams that create courses with authoring tools do not need to worry about the technical wrapper implementation: it comes built in, tested, and optimized out of the box.

What the SCORM wrapper means for L&D teams

For a training manager, the SCORM wrapper is the reason a course created in an authoring tool can be published on any LMS without additional technical work. When the LMS correctly displays a “completed” status, the final score, or the time each employee spent on a course, that information has travelled through the wrapper.

A poorly implemented or missing wrapper is the most common cause of the most frequent SCORM tracking problems: courses that do not register completion, scores that are not saved, or sessions that do not resume from the point of exit. In corporate training contexts where traceability is required for auditing or compliance purposes, a wrapper failure can invalidate training records entirely.

When evaluating how to create a SCORM package, it is worth verifying that the chosen tool or wrapper correctly handles both SCORM 1.2 and SCORM 2004, includes error handling for the varying behaviours of different LMS platforms, and has been tested with the major platforms on the market.

SCORM wrapper and SCORM package: two different concepts

These two terms are often confused. The SCORM package is the complete .zip file imported into the LMS: it contains the course content (HTML, images, videos), the imsmanifest.xml manifest file that describes the course structure, and the JavaScript wrapper that manages communication with the LMS. The SCORM wrapper is just that JavaScript component inside the package: the layer that talks to the platform.

In practice: when you download a course from your authoring tool and upload it to the LMS, you are uploading the complete package. The wrapper is already inside it. For more detail on the complete structure and how to download SCORM content correctly, see the linked resource.

SCORM wrapper and xAPI: does the wrapper have a future?

The xAPI standard (Experience API) emerged as an evolution of classic SCORM. Unlike SCORM, xAPI does not require a JavaScript wrapper in the traditional sense: communication is handled via direct HTTP requests to a Learning Record Store (LRS), without depending on the API the LMS exposes in the browser.

However, the SCORM wrapper remains fully relevant because the majority of corporate LMS platforms still operate primarily on SCORM 1.2, particularly in environments with formal compliance or traceability requirements. According to The Learning Guild’s State of the Learning and Development Industry 2024 report, SCORM remains the dominant distribution format in more than 70% of surveyed organizations. The wrapper is therefore a technical component with guaranteed relevance for the foreseeable future.