How HTML Export Works

An HTML export creates a standalone version of your content that can be opened in a web browser. The export typically includes:

• HTML files (structure of the content)

• JavaScript files (interactivity and logic)

• CSS files (styling)

• Media assets such as images or small videos

All of these files are bundled together so the content can run locally in a browser or be uploaded to a web server.

How SCORM Export Works

A SCORM export is essentially the same HTML package, but with an additional SCORM wrapper added around it.

This wrapper allows the content to communicate with a Learning Management System (LMS). The wrapper provides functionality such as:

• Tracking learner progress

• Reporting completion status

• Storing scores

• Saving learner interactions

Technically, the SCORM package contains:

1. The same HTML content as a normal HTML export

2. Additional SCORM JavaScript APIs

3. A imsmanifest.xml file describing the package structure for the LMS

In other words:

SCORM = HTML Export + SCORM communication layer

Because of this, most limitations that apply to HTML export also apply to SCORM export.

Known Limitations of HTML / SCORM Export

Timeline Components

Timeline components cannot be exported as HTML.

The timeline feature requires a web server backend to provide the necessary data and functionality. Since an HTML export is designed to run as a static package, this server-side functionality is not available.

As a result, timeline activities will not work in HTML or SCORM exports.

Large Videos

Large videos cannot always be embedded directly inside an HTML export.

Embedding very large media files inside the exported package can lead to:

• Extremely large package sizes

• Slow loading times

• Compatibility issues in some LMS platforms

For this reason, large videos should be provided as separate media files and referenced externally instead of being bundled directly into the HTML/SCORM package.