Course translation is the process of converting an existing course’s on-screen text, narration, captions and graphics into another language while keeping its structure, tracking and layout. Done well, you translate one finished source and import the result into a copy, so you never rebuild the course for each client language.
This guide is for training providers whose corporate clients ask for the same course in German, Spanish or Arabic. Tool details come from vendor documentation as of October 2026. We did not test the exports ourselves.
Key takeaways
- Prepare the source once, then export, translate and import into a copy, never into the master course.
- Plan space by string length, not by language: short labels expand the most.
- Export files carry text only. Captions, audio, text inside images and player labels need their own steps.
- Machine translation is a draft, and regulated content needs full human review.
- Test every language in the client’s LMS before you call it done.
What does a course translation workflow look like from start to finish?
A course translation workflow has ten steps: freeze the source, prepare it, export text, translate, review linguistically, localize non-text assets, import and fix layout, test, package, and maintain versions. Each step needs one named owner, one output and one quality check, as the table shows.
| Step | Owner | Output | QA check |
|---|---|---|---|
| 1. Freeze the source | Instructional designer | Locked course, scripts, quiz bank | Source signed off; no open edits |
| 2. Prepare for translation | Course developer | Source that passes the checklist | Text-in-image count is zero or listed |
| 3. Export text | Course developer | XLIFF or Word file, plus glossary | File opens; segment count looks right |
| 4. Translate | Translator or vendor | Translated file | Glossary used; variables untouched |
| 5. Review linguistically | Native-speaking reviewer | Corrected file | Sign-off on terms, tone and meaning |
| 6. Localize non-text assets | Audio and graphics owner | Narration, captions, images, alt text | Audio matches approved script |
| 7. Import and fix layout | Course developer | Language copy of the course | No overflow; fonts render; player labels translated |
| 8. Test | QA tester | Test log per language | Every slide, layer and quiz path; completion and score in the client LMS |
| 9. Package and publish | Developer, client LMS admin | One SCORM per language, or one multi-language package | Launches in the client’s LMS |
| 10. Version and maintain | Course owner | Language record and change log | Every source change reaches every language |
How do you prepare a course for translation before exporting anything?
Preparing a course for translation means making the source easy to export and easy to fit: put every word in editable text, lock the content, and give translators context. Run this checklist on the source first, before any file leaves your team.
The pre-translation checklist:
- Lock the content. CommLab India’s 2026 guide advises finalizing structure, screen text, assessments and narration scripts first.
- Replace text baked into images and video frames with live text over a clean background.
- Remove idioms, humor and abbreviations that only make text fit.
- Write a glossary of product names, jargon and terms to leave untranslated.
- Flag variables. Storyline does not translate variable names through export.
- Use flexible text boxes with spare space.
- List every asset the export will miss: images, audio, video, captions, attached PDFs.
- Duplicate the course so the source-language master is never overwritten.
If a client sends only a published package, there is no export menu. Our guide to editing a SCORM file without the source files covers that case.
How much extra room does translated text need?
Translated text needs more room than English, and the shorter the English string, the bigger the jump. The W3C, citing IBM guidelines, lists average expansion of 200 to 300 percent for strings up to 10 characters, falling to about 130 percent above 70 characters. Plan button and label space by string length, not by language.
The W3C’s example: “views” grew to 2.8 times its English length in German but only 1.2 times in Chinese. See the W3C’s text size in translation article before you set fixed-width containers.
What changes for right-to-left languages?
Right-to-left languages such as Arabic and Hebrew change reading direction, so layout, navigation and punctuation placement must change with them. The W3C says direction must always be declared with the dir attribute, because a language tag alone does not set it. Check each tool’s support before you quote a client.
Articulate’s manual Rise 360 process covers left-to-right languages only, and its Localization page says right-to-left translation is not supported for custom blocks. If you hand-edit HTML output, read the W3C’s guidance on the dir attribute.
Which authoring tools support course translation export, and in what format?
Storyline 360, Rise 360 and iSpring Suite export course text as XLIFF, and Storyline 360 also exports Word. Adobe’s Captivate Classic documentation describes a Word export of captions only. Every export leaves something out, so check the third column against your course before you promise a client a delivery date.
| Tool | Text export format | Not covered, per vendor documentation | Doc date |
|---|---|---|---|
| Articulate Storyline 360 | XLIFF 1.2 or 2.0, or Word (.docx) | Closed captions, trigger conditions, player labels, variable names | Oct 9, 2026 |
| Articulate Localization (Storyline 360, Rise 360) | Translation inside the tool: AI into 80+ languages, plus human validation in Review 360 | Text in images or videos, outside embedded media, linked files such as PDFs | Sep and Oct 2026 |
| Articulate Rise 360, manual | XLIFF 1.2 | Code blocks, survey blocks, question banks; left-to-right only | Sep 24, 2026 |
| iSpring Suite 10 | XLIFF | Equations, some animated links, SmartArt graphics | No date shown |
| Adobe Captivate Classic | Word (.doc) of captions and closed captions | Import only from a file exported from the same project | Jun 29, 2023 |
The Storyline process is in Articulate’s Storyline 360 translation guide. It calls Word files “great for machine translation” and “even better for human translation.” Choose Word for document-based review, XLIFF for translation tools.
For Rise, Articulate’s manual translation guide has you duplicate the course per language, export XLIFF 1.2 from the Translations tab, import the result, then translate the Labels tab. It says manual translations cannot be distributed as a multi-language package. Check that page’s eligibility note against your courses; we did not test it.
Pro tip: Import Into A Copy. Storyline’s guide says to import into a copy of the project, and iSpring’s guide warns that source text is replaced on import. Treat the source-language course as a read-only master, and name each copy with its language code.
Should you use human translation, machine translation, or both?
Most training providers should use machine translation as a first draft and a human reviewer as the final authority. Machine output is fast, but it can miss terminology, tone and learning intent. Choose review depth by risk: regulated or safety content needs full human review, while internal low-risk content may need only a light edit.
The ISO 18587 standard sets requirements for full human post-editing of machine translation output, plus the competences post-editors need. CommLab India’s 2026 article warns that machine output can keep sentence structure while missing what the learner should take away. A language services author in Training Magazine adds that quality varies by language pair, so test yours.
When to choose each approach:
- Machine draft plus full human review: compliance, safety, legal or assessment content.
- Machine draft plus light review: internal updates and low-risk refreshers.
- Human translation from scratch: scenario-heavy content where tone carries the lesson.
Check the client contract before sending course content to any machine translation service.
What else needs localizing besides the text?
Besides text, course localization covers narration, captions, images, alt text, and cultural references such as dates, currency and workplace scenarios. None of these ride along in a text export. Give each its own owner and checkpoint, because translated slides with English audio are not a translated course.
- Audio: re-record or generate narration from the approved translated script. Articulate’s Localization FAQ says text-to-speech narration in Storyline 360 and Rise 360 is also translated. Recheck timing after import.
- Captions: Storyline’s guide says closed captions cannot be translated through its export process. Translate and import them separately.
- Graphics: Articulate Localization does not translate text inside images, so redraw those images with live text.
- Alt text and language tags: translate alt text and mark passages in another language. WCAG 2.2 success criterion 3.1.2 requires each passage’s language to be programmatically determinable at Level AA.
- Cultural references: have a native reviewer check dates, currency, symbols and scenarios.
How do you re-import and test each language?
To re-import and test a translated course, import the file into a copy of the source, fix layout, then test in three passes: language, visual and functional in the client’s LMS. CommLab India puts it plainly: “Translation is not complete until the localized course functions properly in the learning environment.”
- Import into the copy. If the tool reports that the file does not match the course, re-export before continuing.
- Translate what the export missed. Player labels, captions and trigger conditions.
- Check every slide and layer. Look for overflow, truncated buttons, wrong fonts and mirrored layouts.
- Run the language checks. CommLab India describes translator completion, linguistic editing, then in-country review.
- Test in the client’s LMS. Walk every quiz path; confirm completion, score and resume. Our guide to testing a SCORM package before it reaches a client’s LMS has the checklist.
- Record sign-off with reviewer, date and file version.
Should you ship one SCORM package per language or all languages in one?
Ship one package per language when the client’s LMS assigns courses by language, and one multi-language package when learners should choose at launch. Both work, but LMS handling of language, bookmarks and updates differs, so test the client’s LMS before you pick.
| Option | Choose when | Watch for |
|---|---|---|
| One package per language | The LMS enrolls by language, or languages update on different schedules | More files; updates repeat per package |
| One multi-language package | Learners pick a language at launch and all languages update together | LMS may not record the language; one change republishes everything |
Storyline can publish either way. Articulate’s multi-language publishing guide says the single-package option lets learners pick a language on launch, and reports that choice to the LMS in language preference fields for SCORM 1.2, SCORM 2004, AICC and xAPI. It warns that some LMSs might not support them. Latitude Learning documents that switching language versions in its LMS loses bookmarked progress, so ask each admin how switching works.
How do you keep every course translation in sync with the source?
To keep every course translation in sync, treat the source course as the single master, log each change by slide or segment, and push every change through all language copies. A change that reaches only English leaves international clients training on outdated content, which matters most when regulations change.
- Version the source and each language copy with a shared number plus a language code.
- Re-export after a change and translate only the changed text. Translation memory tools reuse earlier translations of unchanged sentences.
- Keep a one-page record per language: source version, export date, translator, reviewer, sign-off.
Our posts on version control when regulations change and course branding for multiple clients cover the governance side, since each translated or rebranded copy is one more file to update.
Pro tip: Rehearse One Language First. Run one short module through every step in the workflow table before quoting a full course. The pilot shows which assets your export misses and how long review takes.
What should you do next?
Pick the course your international clients ask about most. Run the preparation checklist on it, export one module, and walk it through all ten steps in one target language. That pilot shows your real gaps before you commit to a delivery date.
If you also manage clients, enrollments and delivery in one place, see SimpliTrain’s training management platform for training companies. Its page lists a multi-lingual capability without detail, so ask in a demo what it covers. SimpliTrain and SimpliAuthor are made by the same company that publishes this site.
Frequently asked questions
How do I translate an existing course without rebuilding it?
Export the course text from your authoring tool, translate the file, and import it into a copy of the course. Then handle what the export misses: captions, audio, images and player labels. Fix layout, test in the client’s LMS, and publish one package per language or one multi-language package.
Which file format should I send for translation, XLIFF or Word?
Send XLIFF when a translator or tool will process the file, and Word when a person will read and edit it. Articulate’s Storyline 360 guide says Word suits both machine and human translation, while XLIFF suits translation services and programs. Rise 360’s manual process uses XLIFF 1.2 only.
Is machine translation good enough for corporate training courses?
Machine translation is good enough for a first draft, not for a finished course. It can miss terminology, tone and learning intent. Use full human review for compliance, safety, legal and assessment content, and a lighter edit for low-risk internal material. Test your specific language pair, because quality varies.
Can one SCORM package hold several languages?
Yes, in some tools. Storyline’s single-package option lets learners choose a language at launch, according to Articulate’s documentation. Articulate also says manually translated Rise 360 courses cannot be distributed as a multi-language package. Confirm with the client’s LMS admin that language selection and tracking behave correctly.
What is the difference between course translation and course localization?
Course translation converts the words into another language. Course localization goes further and adapts audio, images, dates, currency, examples and scenarios for the target audience. A course with translated slides but English narration, or American workplace scenarios, is translated but not localized.



