lokalizeit.ai
SCORM translation

Translate SCORM courses without rebuilding them.

Upload the SCORM zip your authoring tool already exports. Lokalizeit translates the text in place, patches the manifest, and hands back an LMS-ready package in any of 13 languages — with a fidelity score for every file.

What is inside

A SCORM package is a small website in a zip.

Under the hood, a SCORM course is HTML pages, JavaScript, styles, media files, and an imsmanifest.xml that tells the LMS how to launch it and report progress. The words a learner reads — screen copy, quiz questions, feedback, navigation labels — are scattered across those files, interleaved with the code that makes the course run.

Translating a SCORM course therefore means two jobs at once: replacing every learner-facing string, and leaving everything else byte-for-byte alone. Get the second part wrong and the course stops launching, stops tracking, or both.

What has to survive a translation, untouched:

  • The imsmanifest.xml structure and launch settings
  • The JavaScript runtime that reports completion
  • Quiz logic, triggers, and branching rules
  • Media files, fonts, and stylesheets
  • The exact folder layout inside the zip
The usual failure modes

Why typical SCORM translation workflows break.

Manual rebuilds

The common workaround is rebuilding the course from scratch in the target language: duplicate the project, paste translations screen by screen, republish, and hope nothing drifted. Weeks of work per language.

A broken imsmanifest

The imsmanifest.xml tells your LMS what the package is and how to launch it. Hand-editing it, or zipping the folder at the wrong depth, produces a package the LMS silently rejects or mislabels.

Lost interactivity

Quizzes, triggers, and branching live in JavaScript and JSON, not in neat text files. Workflows that extract text into a document and paste it back tend to break the code around it.

Spreadsheet round-trips

Exporting strings to a spreadsheet, mailing it around, and importing it back loses context, mangles markup, and turns every language into a coordination project.

The Lokalizeit way

Translate in place. Re-export with a patched manifest.

Upload the SCORM zip

The exported package from your authoring tool is all you need. Lokalizeit walks the archive and pulls translatable text out of the HTML and course data files, leaving code, styles, and media untouched.

Translate in place

Every segment is translated where it lives, so quiz feedback, navigation labels, and screen copy keep their exact position and markup. You review segments in the browser before you export.

Re-export, LMS-ready

The package is re-zipped with its original structure and a manifest patched to the target language. Assets are copied verbatim, so the runtime that talks to your LMS ships unchanged.

Publishing from Articulate Storyline or Rise 360? The same flow applies — see the dedicated guides for Storyline and Rise 360, or read the step-by-step walkthrough.

Proof, not promises

A 0–100 fidelity score per file.

Every translated file gets a fidelity score from 0 to 100. It measures whether the structure survived: completeness, formatting markers, number and link integrity, length sanity, and untranslated-segment detection — weighted into one number, with a warning list naming exactly what to review. High scores mean spot-check and ship; low scores point you at the segments that need attention.

Read the full methodology
FAQ

SCORM translation questions.

Will the translated package still track completion in my LMS?
The runtime code that reports progress and completion to your LMS is copied unchanged — only human-readable text is replaced, and the manifest is patched, not rewritten. As with any new package, we recommend a quick test import before rolling it out to learners.
Do I need the original authoring files?
No. The exported SCORM zip is enough. You do not need the source project file from your authoring tool — upload the package your LMS already uses and download a translated one.
Which languages are supported?
Thirteen target languages: Spanish, French, German, Italian, Portuguese, Russian, Hindi, Chinese, Japanese, Korean, Arabic, Turkish, and Swahili. The source language is English. Arabic is exported with proper right-to-left rendering.
Which SCORM versions work?
Lokalizeit works with SCORM course packages exported as a zip — the kind Articulate Storyline and Rise 360 publish. If your tool exports a standard SCORM zip with an imsmanifest.xml, you can upload it.
What does it cost?
Pricing is per word, per quality tier, and you see the exact quote before you confirm. Repeated segments cost 10% of the per-word rate and fuzzy matches 70%, which matters in courses full of recurring labels. Signup includes 2,000 free credits.
What about text baked into images?
Text inside images is not translated automatically — no zip-in, zip-out tool can repaint your graphics. Lokalizeit surfaces embedded images with AI-written descriptions so you can find the ones that need a designer, instead of discovering them after launch.
Keep reading

Your next language is one upload away.

Upload a SCORM zip, see the exact quote, and download an LMS-ready translated package. No card required.