MULTILINGUAL SCORM
One multilingual SCORM package for the LMS
If each language is already a finished course, stop uploading five catalog items. Merge them into a single SCORM package with a launcher learners actually use.
This is not a translation job
Translation starts from one source course and produces a new language. A multilingual SCORM package starts from language versions you already have — a Swedish zip, a German zip, an English zip — each authored, QA’d, and signed off. The LMS problem is catalog clutter: five course objects, five enrollments, five completion reports for what is really one course.
Merging those zips into one export is the fix. Learners pick a language once. The LMS tracks one activity. Admins update one item when you ship a new version.
What the combined package includes
- One zip the LMS imports as a single course object.
- A launcher so the learner chooses a language before the content starts.
- Stable identifiers so completion still belongs to that course.
- Optional branding (logo, colors and footer) so the selector looks like your academy (paid plans). Titles and layout can be set on every plan.
Specifications
- Output format
- SCORM 1.2, SCORM 2004 or xAPI (Tin Can)
- Launcher layout
- Language cards or a dropdown, in a light or dark theme
- Completion rule
- Complete when one language is finished, or only when all are
- Languages per package
- Up to 2 on Free, 5 on Starter, 10 on Growth and 30 on Premium


When to translate first instead
Merge finished artifacts. If you only have an English course and you need Spanish, translate that course first (see the Storyline and Rise workflows). Then merge the language zips if the LMS should expose one catalog item.
Frequently asked questions
How do I make a multilingual SCORM package for the LMS?
Is this the same as translating a course?
What if I only have an English Storyline export?
How is completion reported for a multilingual SCORM package?
How many languages can one package hold?
Step-by-step: How to merge multilingual SCORM courses into one LMS package · Fix common SCORM upload errors