100% Free · Unlimited Local Use

Turn any course folder into a SCORM package

Drag in your course's HTML, CSS, JavaScript, and media files. Choose your SCORM version, and download a ready-to-upload ZIP. Everything is built securely on your device—zero server uploads.

Drag your course folder here, or click to browse
We recommend including an index.html as your launch file.
Loaded Assets 0 files
No index.html found at the root — you can still generate a package, but LMS platforms expect this file.
Package generated
Architecture

What gets built inside your zip?

We combine your custom raw assets with precise structural metadata.

📂 course_package.zip
├──📄 imsmanifest.xml
├──📂 lms
│   └──📄 API_Wrapper.js
├──📄 index.html
├──📂 css
│   └──📄 styles.css
└──📂 media

Structural Manifest

Your ZIP needs an `imsmanifest.xml` sitting perfectly at its root. We auto-generate this exact spec file, mapping every single resource and identifier so platforms like Canvas, Moodle, and Blackboard immediately recognize the architecture upon upload.

Runtime API Stub

A course needs to communicate tracking variables. We seamlessly inject the official standard `API_1484_11.js` (or `API.js` for 1.2) into your folder stream, empowering your content to interface back to the LMS environment flawlessly.

Documentation

Common Questions

What is a SCORM package?
SCORM (Sharable Content Object Reference Model) is a set of technical standards for e-learning software. A package is simply a ZIP file containing your course content alongside a structured imsmanifest.xml file that tells an LMS how to read it.
What's the difference between SCORM 1.2 and SCORM 2004?
SCORM 1.2 is the older, most universally supported standard globally. SCORM 2004 offers more detailed tracking features (like complex mastery scores and interaction logging), but not all legacy corporate LMS platforms support it perfectly.
Do I need an index.html file for my course?
Yes, almost always. While technically you can specify any entry file, an index.html root file acts as the universal launch pad that LMS platforms look for to start displaying your bundled web content structure.
Does SCORM Packager upload my course files anywhere?
No. The entire packaging process utilizes native browser APIs (the local File API and JSZip libraries) running safely in your sandboxed computer tab. Your private training content is never sent to our servers.
Is there a file size limit?
Because everything processes on your computer locally, there are no server-side upload caps. You are only limited by your web browser's available memory, usually supporting courses containing up to a gigabyte of media seamlessly.