Frequently Asked Questions
Last updated: May 16, 2026
After I upload my SCORM package to OpenSCORM, does it automatically appear in my LMS, or do I still need to create a course shell in my LMS and link it to the new content?
After a SCORM package is uploaded, it can be used immediately in your LMS. OpenSCORM does not create the course shell automatically in your LMS when a new SCORM package is uploaded, unless we configure this integration for you.
If you’re interested in automating this, please contact us to discuss details. We have lots of experience automating business workflow with integrations between systems.
Do I need to specify a course identifier when I upload a SCORM package?
No. A course identifier is automatically generated from the name of your zip file, so you don’t need to remember this step.
This means the only thing you need to think about when you upload a new SCORM package is the name of your zip file. OpenSCORM simply converts the file name to lower case and replaces non-alphanumeric characters with hyphens (so the file name is URL-friendly) — and that becomes your course ID.
How do I manage multiple versions of the same course?
Whenever you upload a new file with a unique name, the new file becomes a fresh new course. This means you can manage multiple versions of the same course with a simple naming convention.
For example, suppose you have 3 versions of a Ladder Safety course. You can append a version number to the name of each SCORM package, so it’s always clear what version you are referencing:
ladder-safety-v1.zipladder-safety-v2.zipladder-safety-v3.zip
If I replace existing content in OpenSCORM, is the change automatically reflected in my LMS?
Yes. If you upload a SCORM package with a file name that is identical to the name of a package you uploaded previously, then the new content replaces the old content. This change is reflected immediately and automatically in your LMS.
If I replace an existing course with new content, is the old original content still available as a backup?
No. If you upload a SCORM package with a file name that is identical to the name of a package you uploaded previously, then the original content is entirely overwritten, and no backup or archive is made by the system.
In this scenario, if learners have completed the course with the original content, then their certificate of completion remains valid. But if learners have started and not completed the original content, they will have to restart the course from the beginning.
If you want to preserve original content for a course replacement, then adopt a file-naming convention that takes this into account.
For example, you can append a version number or a date to the name of each SCORM package file. File names might look like this:
First Aid v24.zipFirst Aid v25.zipFalling Down Rabbit Holes 2024-12-31.zipFalling Down Rabbit Holes 2025-02-04.zipFalling Down Rabbit Holes 2025-09-12.zip
You aren’t required to use lowercase and hyphens in the file naming convention on your computer. Some customers decide to follow this convention so the file name exactly matches the course identifier that OpenSCORM assigns to it, which makes it easy to match copies on their computer to copies they have uploaded.
What SCORM standards do you support?
SCORM 1.2, SCORM 2004, and Tin Can xAPI. All of them. All plans, including the free Mini tier.
Can I deliver SCORM courses without an LMS?
Yes. OpenSCORM works standalone — upload your SCORM, send a link to learners, and track completions. No LMS required. See the deliver without an LMS page for details.
Is OpenSCORM really open source?
Yes. Released under the GNU AGPL v3 license. The source is on GitHub. You can self-host it, audit it, or contribute. See the license page for details.
How do I migrate from SCORM Cloud?
Re-upload your SCORM zips and update the launch URLs in your LMS (or wherever you embed them). Most customers finish in an afternoon. See the migration guide.
Where do I report a bug or request a feature?
GitHub issues for bugs and feature requests. Or email us — see the contact page.