Worth remembering
There are two ways to get a SCORM course into your LMS. Manual SCORM means you export a fixed package and upload it yourself. Dynamic SCORM means updates sync automatically without re-uploading. The right choice depends on how often your content changes and how much control your LMS environment requires.
Most e-learning authoring tools export SCORM in one way. You finish a course, download a .zip file, and upload it to your Learning Management System (LMS). If you ever update the course, you start that process again.
Easygenerator supports a second method alongside this: dynamic SCORM. Understanding what each method does and when to use which saves your team significant time and prevents version problems down the line.
This guide covers what exporting a SCORM package actually means, the difference between manual and dynamic SCORM, and a decision framework to help you choose the right method for each course you publish.
What it means to export a course as a SCORM package
A SCORM package is a .zip file that contains everything your LMS needs to launch and track a course. Inside the package you will find the course content files, a manifest file (imsmanifest.xml) that tells the LMS how to launch the course, and the runtime logic that sends completion and score data back to the LMS.
When you export a SCORM package from an authoring tool, you are creating a self-contained bundle. The LMS does not need to communicate with the authoring tool after that point. It reads the package, launches the course, and records learner data independently.
Easygenerator exports as SCORM 1.2, SCORM 2004, and xAPI. You can also convert a PowerPoint, PDF, or Word file into a SCORM-ready course with EasyAI, then export it in whichever format your LMS supports. For a full explanation of the SCORM standard and what the package contains, see our guide on how to create a SCORM file.
The two ways to get a SCORM course into your LMS
Once a course is ready to publish, you have two routes available in Easygenerator.
Manual SCORM. You export the course as a SCORM package (1.2 or 2004), download the .zip file, and upload it to your LMS through the standard import process. The package is fixed at the point of upload. If you update the course later, you export a new package and re-upload it to replace the previous version.
Dynamic SCORM. You publish the course via dynamic SCORM, which creates a live link between Easygenerator and your LMS. When you update the course in Easygenerator, those changes sync automatically. Learners always see the latest version without any re-upload.
Manual SCORM: what it is, how it works, and when to use it
Manual SCORM is the standard publishing method used across the e-learning industry. Every SCORM-compliant authoring tool supports it, and every SCORM-compliant LMS accepts it.
The workflow is straightforward. You complete your course, go to Publish in Easygenerator, select SCORM 1.2 or SCORM 2004, download the .zip file, and upload it to your LMS. The LMS hosts the content and handles all tracking from that point on.
Manual SCORM is the right choice when:
- The course is a compliance module that must be version-locked for audit purposes
- Your LMS environment is air-gapped or operates under strict IT governance policies that require all content to be hosted internally
- The course is unlikely to change after launch
- Your LMS does not support dynamic SCORM and requires a standard package upload
Worth remembering
Manual SCORM remains the dominant publishing method across corporate LMS deployments because of its universal compatibility. SCORM 1.2, the most widely used version, is supported by the vast majority of commercial LMS platforms. (ADL Initiative, SCORM conformance documentation, 2023)
Dynamic SCORM: what it is, how it works, and when to use it
Dynamic SCORM is a publishing method developed by Easygenerator that maintains a live connection between the authoring tool and the LMS, allowing course updates to sync automatically without re-uploading the SCORM package.
Instead of exporting a fixed package, you publish the course in a way that keeps it connected to Easygenerator. The LMS receives the course through a dynamic link rather than a static file.
When you update the course in Easygenerator, like correcting a fact, adding a section, or updating a product name, those changes appear in the LMS automatically. You do not need to re-export, re-download, or re-upload anything. Every learner who opens the course from that point on sees the updated version.
Dynamic SCORM is the right choice when:
- The course content changes regularly, such as product training, onboarding materials, or process guides
- You need every learner to be on the latest version immediately after an update
- The course is translated into multiple languages and one update in Easygenerator syncs across all language versions at once
- Your team wants to reduce the administrative overhead of managing SCORM packages in the LMS
Worth remembering
Manual vs dynamic SCORM: how they compare
Here is a direct comparison of both methods across the factors that matter most to L&D teams.
| Manual SCORM | Dynamic SCORM | |
|---|---|---|
| How it works | Export a fixed .zip package and upload it to your LMS manually | Course updates sync automatically to the LMS |
| Version control | You control exactly which version learners see | Learners always see the latest version instantly |
| Update method | Re-export and re-upload a new package each time | Edit in Easygenerator and changes go live automatically |
| Maintenance effort | Higher: every change requires a manual upload cycle | Lower: one edit updates all published instances |
| Multi-language sync | Each language version must be re-uploaded separately | Updates apply across all language versions at once |
| Best fit | Compliance courses, audited environments, air-gapped LMSs | Onboarding, product training, fast-changing content |
| LMS dependency | Content hosted inside the LMS | Content hosted by Easygenerator, linked to the LMS |
Which method should you use? A decision framework
The right method depends on your content type, update frequency, and LMS environment. Use this table to match your situation to the right approach.
| Scenario | Best method | Reason |
|---|---|---|
| Content changes often (product training, onboarding) | Dynamic SCORM | Updates reach learners without any re-upload work |
| Compliance course that must be version-locked for audit | Manual SCORM | The hosted version stays fixed until you replace it intentionally |
| Air-gapped LMS or strict IT governance | Manual SCORM | Content lives entirely inside the LMS, no external hosting |
| Multi-language course updated regularly | Dynamic SCORM | One edit in Easygenerator syncs across all language versions |
| One-time course with no planned updates | Either | Both methods work; manual is simpler if you never plan to update |
| LMS incompatible with dynamic SCORM | Manual SCORM | Download the .zip package and upload via standard LMS import |
When neither SCORM method is the right choice
SCORM, whether manual or dynamic, is built around LMS delivery. There are situations where neither method serves you well.
If your learning activity happens outside a formal course, like in a mobile app, a simulation, a performance support tool, or informally on the job, xAPI is a better fit. xAPI tracks any learning event and sends the data to a Learning Record Store (LRS), which can sit independently of an LMS entirely. Easygenerator exports in xAPI format alongside SCORM, so you can choose per course.
If you need to share content quickly without LMS infrastructure, Easygenerator’s private URL delivery lets you publish a course as a shareable link. There is no SCORM package involved and no LMS required. Completion tracking is more limited, but for use cases where a link is enough, it removes the setup overhead entirely.
For a full breakdown of all available export formats and when to use each, see SCORM vs xAPI vs PDF: which e-learning export format should you use?
How to export a SCORM package in Easygenerator
The export process is the same whether you choose manual or dynamic SCORM. The difference is in where Easygenerator sends the output.
For manual SCORM:Â open your course, go to Publish, select Download as SCORM. Choose SCORM 1.2 or SCORM 2004 depending on what your LMS supports. Easygenerator generates the .zip package and downloads it to your device. Upload it to your LMS using the standard import process.
For dynamic SCORM:Â open your course, go to Publish, select your LMS integration or the dynamic SCORM option. Easygenerator creates a live connection to your LMS. Any future edits to the course in Easygenerator will sync automatically.
Easygenerator also supports xAPI export for organizations using a Learning Record Store alongside their LMS. The export process follows the same steps. Select xAPI as the format instead of SCORM.
Connecting to your LMS
For organizations using manual SCORM, the .zip package works with any SCORM-compliant LMS. Easygenerator is compatible with 99% of LMSs through standard SCORM export.
For dynamic SCORM, Easygenerator offers native integrations with a set of LMS and LXP platforms. The three most widely used are Cornerstone, LearnUpon, and HowNow. These integrations let you publish directly from Easygenerator into your LMS without any file handling.
For the full list of supported platforms, see the Easygenerator integrations page. For a full guide to LMS compatibility and how to verify your platform supports SCORM, see what is a SCORM-compliant LMS?
