Translate Articulate Storyline courses in place.
Publish your Storyline course to SCORM, upload the zip, and get back an LMS-ready package in any of 13 languages. No source .story file, no rebuild, no spreadsheet round-trip.
The published zip is the course.
When Storyline publishes to SCORM, everything a learner sees — slide text, quiz questions, feedback, button labels — lands in the package alongside the player code that runs it. Lokalizeit reads that package directly: it extracts the learner-facing text, translates it in place, and leaves the player, triggers, and media byte-for-byte alone.
That means the workflow does not depend on who has the .story file, which version of Storyline it opens in, or whether the original author still works with you. If the course runs in your LMS, it can be translated.
What you skip
- Hunting down the original .story project file
- Duplicating the project once per language
- Exporting and re-importing translation spreadsheets
- Repositioning text boxes slide by slide
- Republishing and re-testing each language by hand
Three steps from published to localized.
1. Publish and upload
Publish your Storyline course to SCORM as you normally would for your LMS, then upload the resulting zip to Lokalizeit. That zip is the only input needed.
2. Pick language and tier
Choose one of 13 target languages and a quality tier. You see the word count and the exact credit cost before anything runs, and you can review every translated segment in the browser.
3. Download, LMS-ready
The package is re-zipped with its structure intact and a manifest patched to the target language. Import it into your LMS the same way you imported the original.
Every translated file ships with a 0–100 fidelity score so you know what to review before it reaches learners. For the generic flow behind this, see SCORM translation or the step-by-step walkthrough.
Storyline into Arabic, reading right-to-left.
Arabic is one of the 13 target languages, and it gets real right-to-left treatment: document direction set to RTL in the exported files, punctuation attached where it belongs, and English terms preserved as left-to-right islands inside Arabic sentences. An RTL advisory rides along with the fidelity score so you remember to verify direction-sensitive visuals before launch.
How Lokalizeit handles RTLWorth checking after any Arabic export from a slide-based tool: fixed-position graphics that assume left-to-right flow, and text boxes sized for shorter English strings. The fidelity report flags length anomalies so you know which slides to look at first.
Storyline translation questions.
- Do I need the .story source file?
- No. Lokalizeit works from the published SCORM zip — the same package you already give your LMS. If the original project file is long gone, you can still translate the course.
- Will triggers, branching, and quiz logic survive?
- The JavaScript and course data that drive interactivity are copied unchanged; only learner-facing text is replaced, in place. Slide structure, triggers, and scoring stay wired the way you built them. As with any new package, run a quick test import before launch.
- Which Storyline versions are supported?
- Any version that publishes a standard SCORM zip with an imsmanifest.xml. Lokalizeit reads the published output, not the authoring project, so the Storyline version you authored in does not matter.
- What about text inside images and screenshots?
- Text baked into images is not translated automatically — that is true of any tool working from a published package. Lokalizeit surfaces embedded images with AI-written descriptions so you can find the ones that need a designer before launch.
- Which languages can I translate into?
- Thirteen target languages: Spanish, French, German, Italian, Portuguese, Russian, Hindi, Chinese, Japanese, Korean, Arabic, Turkish, and Swahili. The source language is English.
- Will the translated course still report completion?
- The runtime code that talks to your LMS ships unchanged, and the manifest is patched rather than rewritten. Completion and score reporting work the way the original package did; we still recommend a test import to confirm in your specific LMS.
Publish once. Translate everywhere.
Upload a published Storyline SCORM zip and see the quote before you spend a credit. No card required.