What Is eLearning Localization? Process and Best Practices
This guide is for L&D, HR, compliance and training teams who need one course to work for employees, distributors or customers in several countries.
It explains what localization covers, how to plan it, the step-by-step process, what to prepare, how to handle voiceover, and the mistakes that cost the most time. Tool details come from the vendors' own documentation, checked in October 2026.
Get a Free Quotation
Scoped proposal delivered within 48 hours
eLearning localization in short
eLearning localization is the process of adapting an online course for learners in a specific language and region. Beyond translating on-screen text, it adjusts audio, video, images, examples, formats, interactions and quizzes, then tests the course in the target language and your LMS so it works and reads as if it was built locally.
What is eLearning localization?
eLearning localization means adapting a course so that learners in another language and culture can use it as easily as the original audience. The W3C, the body that sets web standards, defines localization as "the adaptation of a product, application or document content to meet the language, cultural and other requirements of a specific target market (a locale)".
That definition matters for training because a course is more than words. It has narration, video, screenshots, scenarios, quiz feedback, navigation buttons and tracking data. If only the text changes, learners still meet a US actor, a dollar sign, a month/day date and a "Next" button in English. Localization fixes all of that.
Four terms get mixed up in vendor quotes
| Term | What it means | Example in a course |
|---|---|---|
| Translation | Turning the text and script from one language into another, accurately and completely | The safety module's on-screen text and narration script are translated into Spanish |
| Localization | Translation plus adapting everything else for the locale: visuals, examples, formats, audio, interactions, layout, testing | The Spanish (Mexico) version uses local names, local currency, a local narrator and a mirrored layout check |
| Transcreation | Rewriting a piece creatively so it has the same effect, not the same words | A pun in a course title is replaced with a new phrase that works in Japanese |
| Internationalization | Designing the source course so it is easy to localize later | Text kept out of images, room for longer words, no culture-specific jokes |
The W3C describes internationalization as design and development "that enables easy localization for target audiences that vary in culture, region, or language". In practice, the cheapest localization project is the one where the English course was built with it in mind.
What gets localized in an eLearning course?
Everything a learner sees, hears or clicks can need a change. The W3C's own list of localization items includes numeric, date and time formats, currency, symbols, icons and colors, references that may be misread in another culture, and varying legal requirements. For a course, that translates into the checklist below.
| Course element | What changes | Watch out for |
|---|---|---|
| On-screen text | Translated and fitted to the layout | Longer text overflowing buttons, tabs and text boxes |
| Narration and audio | Script translated, then re-recorded or voiced | Audio running longer than the animation it is synced to |
| Captions and transcripts | New caption files per language | Captions are often a separate file, not part of the text export |
| Video | Subtitles, a new voice track, or re-shooting | On-screen text burned into the video |
| Images and graphics | Text in images replaced; people, gestures, dress and settings checked | Screenshots of English software in a localized course |
| Examples and scenarios | Names, workplaces, situations and humor adapted | A scenario that only makes sense under US law or culture |
| Formats | Dates, times, numbers, currency, units, phone numbers, addresses | 03/04 means March 4 in the US and 3 April in much of the world |
| Interactions and quizzes | Question text, answer options, feedback, drag-and-drop labels | Answer logic tied to the English word order or alphabetical sorting |
| Player and navigation | Menu, buttons, prompts, error messages | Player labels often need translating separately from the slide text |
| LMS details | Course title, description, completion message, certificate | Learners enrolled in the wrong language version |
When is translation enough, and when do you need full localization?
Translation is enough when the content is factual, the audience shares a work culture, and nothing on screen is tied to one country. You need full localization when learners must act on the content (safety, compliance, customer conversations) or when examples, laws, formats or voices only fit one market.
| Content type | Usually enough | Why |
|---|---|---|
| Product knowledge for an internal global team | Translation plus format checks | Facts travel well; examples rarely depend on the country |
| Software training (show-me, try-me, test-me simulations) | Localization | The software interface itself is in another language, so screens must match |
| Safety and operating procedures | Localization | Learners must understand and act on the content correctly |
| Compliance and ethics training | Localization | Laws, reporting lines and examples differ by country |
| Soft skills, leadership, sales conversations | Localization or transcreation | Tone, politeness and conversation style differ most |
Regulators expect training people can actually understand. OSHA's 2010 training policy statement says "an employer must instruct its employees using both a language and vocabulary that the employees can understand". The US Department of Justice, in its guidance on how prosecutors evaluate corporate compliance programs, asks whether training is "offered in the form and language appropriate for the audience". Neither says "localize every course", but both make a weak, English-only or word-for-word version a risk for safety and compliance training.
How to build an eLearning localization strategy
An eLearning localization strategy is a short set of decisions you make before translation starts: which languages, how deep, which tools, who reviews and how updates will work. Settle these seven points first and the rest of the project runs smoothly.
- 01
Choose locales, not just languages.
"Spanish" can mean Spain, Mexico or the US. "French" can mean France or Canada. Name the locale, because vocabulary, formats and narrator accent change.
- 02
Rank languages by learners and risk.
Start with the largest learner groups and the countries where the course carries legal or safety weight. Add the rest in later waves.
- 03
Set the depth per course.
Use the decision table above: translation only, full localization, or transcreation for the parts that need it.
- 04
Decide on audio early.
Full voiceover, subtitles only, or text-only versions change the budget and timeline more than any other choice. See voiceover tips.
- 05
Pick the translation approach.
Professional human translation, machine translation with full human post-editing, or a mix by content type. See machine translation, AI and human translation.
- 06
Name in-country reviewers.
A subject matter expert or manager who works in that market and has time booked to review. This is the step that most often delays projects.
- 07
Plan for updates.
Decide how a change to the English course reaches every language version, and keep the editable source files and translation memory in one place.
The eLearning localization process, step by step
A typical eLearning localization process has nine steps, from preparing the source course to launching each language in the LMS. The order matters: fixing the English source and agreeing terms first is far cheaper than correcting the same issue in ten languages later.
- 01
Prepare and freeze the source course
Course owner and developerFinal English content signed off; text kept live (not inside images); room left for longer text.
- 02
Build a glossary and style guide
Client SMEs with the translation teamKey terms, product names, words that stay in English, tone and formality for each language.
- 03
Export the translatable content
DeveloperOn-screen text, narration scripts, captions, quiz feedback and player labels, in the format the authoring tool supports.
- 04
Translate and adapt
Professional translatorsTranslation, cultural adaptation of examples and images, transcreation where needed.
- 05
In-country review
Your reviewersA reviewer in each market checks meaning, terms and tone in a document before anything is rebuilt.
- 06
Record or generate audio
Voice talent or AI voice, audio editorHuman or AI voiceover from the approved scripts, then new caption files.
- 07
Rebuild each language version
DeveloperImport translations, swap images and audio, fix layout, re-sync timing, mirror layouts for right-to-left languages.
- 08
Test in context
QA team and your reviewersLinguistic review inside the built course, functional testing, and LMS testing for each language: launch, bookmarking, completion and scores.
- 09
Publish and launch
Developer and LMS adminOne SCORM or xAPI package per language (or one multilingual package, if your LMS setup needs it), uploaded and assigned to the right learners.
What your authoring tool does and does not export
Each authoring tool handles translation differently, and the gaps are where projects slip. This is what the vendors' own documentation says (checked October 16, 2026):
| Tool | How translation works | What needs separate handling |
|---|---|---|
| Articulate Storyline 360 | Export the course text to XLIFF (1.2 or 2.0) or Word, translate it, then import it into a copy of the project. Word exports can include slide thumbnails for context. | Articulate notes that "closed captions can't be translated using this process", trigger conditions and player text labels must be translated by hand in Storyline, and variable names cannot be translated. Captions are translated and imported separately; player labels are localized with text labels. |
| Articulate Rise 360 | Articulate Localization translates a course into "80+ languages" and keeps the language versions together as one course "stack". Changes to the source language after the last translation run are detected, so only changed text needs translating. | Glossary terms need a paid Localization plan. Articulate advises avoiding all caps for emphasis (AI may treat it as an acronym), emojis and sentences split across blocks. |
| Adobe Captivate | Adobe's help for Captivate Classic describes exporting project captions and closed captions to a Word file, translating them in a column, and importing them into a copy of the project. | For software simulations, Adobe's steps record the same actions again in the localized version of the website or application, then import the translated captions and check timing. |
The practical lesson: a vendor that quotes "per word" from the exported text may miss captions, player labels and re-recorded simulations. Ask what is included.
Requirements for eLearning translations: what to prepare
The requirements for eLearning translations are mostly files and decisions you already have. Sending them at the start avoids the back-and-forth that stretches timelines.
Files
- Editable source files (for example .story, Rise course access or .cptx), not only the published SCORM package
- Final narration scripts and any video scripts
- Caption files (for example SRT or VTT) if they exist
- Original images, icons and video projects with text on separate layers
- Fonts used in the course, and confirmation they support the target scripts
- Any previous translations, glossary or translation memory
Decisions and people
- Target locales (for example "French, Canada"), in priority order
- Depth per course: translation only or full localization
- Audio choice: human voiceover, AI voiceover, subtitles or text only
- Terms that must stay in English (product names, system names)
- In-country reviewer for each language, with review dates
- LMS name, SCORM or xAPI version, and how language versions will be assigned
Storyline 360 can import captions in SRT, VTT, SBV and SUB formats, so caption files from a captioning service can usually go straight back into the course.
Best practices for eLearning content localization
These eLearning localization tips save the most rework. Most of them are decisions made while building the English course, which is why localization works best when it is planned from day one.
Design for text expansion
Translated text is usually longer than English, and short labels grow the most. IBM guidance quoted by the W3C shows English strings of up to 10 characters averaging 200% to 300% of their original length in European languages, falling to about 130% for text over 70 characters. A five-letter button label can more than double. Leave space in buttons, tabs, menus and text boxes, and avoid fixed-width layouts. The W3C also notes that compound nouns in German, Finnish and Dutch may not wrap, and some scripts, such as Thai, need more line height.
Keep text out of images and video
Every word baked into an image or video has to be recreated by hand. Keep labels, callouts and titles as live text over the image, and keep layered source files for anything that must contain text.
Plan for right-to-left languages
Arabic and Hebrew are written right to left. The W3C advises setting the document direction to right-to-left when the main language is RTL, and says well-written style sheets "will automatically mirror the layout". In a course, check that navigation, progress bars, drag-and-drop targets, timelines and charts still read in the right order, and that numbers and English product names inside RTL sentences display correctly.
Localize formats, not just words
Dates, times, numbers, currency, units, phone numbers and addresses all follow local rules. Decide whether a US course for a German audience should show euros and metric units, or keep US figures with a note. Be consistent across text, images and quiz answers.
Tag the language for accessibility
If your course is built to WCAG 2.1 AA, the language matters for screen readers. WCAG 2.1 Success Criterion 3.1.1 (Level A) requires that "the default human language of each web page can be programmatically determined", and 3.1.2 (Level AA) requires the same for each passage or phrase in another language. Without it, a screen reader may read French text with English pronunciation. Each language version also needs its own captions: WCAG 2.1 SC 1.2.2 (Level A) requires captions for prerecorded audio in synchronized media.
Write a source that translates well
Short sentences, one idea per sentence, no idioms, no wordplay, no culture-specific jokes. Spell out abbreviations once. Avoid splitting a sentence across two text boxes or slides, because translators then work on fragments.
Review in context, not only in a spreadsheet
A translation that is correct in a document can still be wrong on screen: a truncated button, feedback attached to the wrong answer, a caption out of sync. Plan at least one review of the built course in each language.
How to voice eLearning modules in other languages
To voice an eLearning module in another language, translate and approve the script first, record or generate the voice from that approved script, then re-sync animations, captions and slide timings to the new audio. Audio changes length in translation, so timings almost always need adjusting.
Tips for eLearning voiceover
- Lock the script before recording. Every change after recording means a new session or a new AI render, plus re-syncing.
- Send a pronunciation list. Product names, acronyms, people's roles, system names and technical terms, with how each is said in that language.
- Mark what stays in English. Learners often see English system names on their screens, so the narrator should say them the same way.
- Match voice to audience. Accent and locale (Brazilian or European Portuguese), age, formality and gender should fit the learners and the course persona.
- Keep timing flexible. Build animations to cue points rather than fixed seconds, so longer narration does not break them.
- Update captions and transcripts. New audio means new caption files in that language.
- Check audio in the course. Listen to each slide in the built course, not only to the audio files.
Voiceover, subtitles or both?
| Option | Best for | Trade-offs |
|---|---|---|
| Human voiceover | Leadership messages, soft skills, safety stories, customer-facing training | Highest production effort; studio time per language; changes mean new sessions |
| AI voiceover | Procedural, product and software training; frequent updates; many languages | Check pronunciation of names and terms; reviewers must still approve every language |
| Subtitles only | Video-heavy courses on a tight budget; audiences used to subtitles | Learners read and watch at once; harder on mobile and for low-literacy audiences |
| Voiceover plus captions | Most compliance and safety courses | Two assets to keep in sync, but it also covers learners who cannot or prefer not to use audio |
Machine translation, AI and human translation
Machine translation can speed up eLearning localization, but raw machine output should not go to learners. Use it only with full human post-editing and review, and keep professional human translation for content where a wrong word has consequences: safety, compliance, legal, medical and customer-facing material.
Two ISO standards draw this line. ISO 17100:2015 sets requirements for the core processes and resources of a quality translation service, and states that "the use of raw output from machine translation plus post-editing is outside the scope" of that standard. ISO 18587:2017 covers "full, human post-editing of machine translation output" and the competences of post-editors. (ISO lists both as under revision; checked October 16, 2026.)
A practical split many teams use
Machine translation plus full post-editing
High-volume, factual, low-risk text, such as product feature descriptions and system steps.
Professional translation and in-country review
Compliance, safety, legal and medical content, scenarios, marketing tone and anything learners must act on.
Transcreation
Titles, slogans, humor and emotional stories.
For a deeper look at the trade-offs, read our guide to machine translation vs professional translation for eLearning.
Common eLearning translation mistakes
Most eLearning translation mistakes are not translation errors. They are planning gaps that show up late, when every fix has to be repeated in every language.
| Mistake | What happens | How to avoid it |
|---|---|---|
| Translating before the English is final | Every English change triggers changes in every language | Freeze and sign off the source first |
| Sending only the SCORM package | Text must be rebuilt by hand; quality drops | Send the editable source files |
| No glossary | The same term is translated three ways across modules | Agree key terms before translation starts |
| Text inside images | Images must be recreated manually or stay in English | Keep text live; keep layered source files |
| Fixed-size buttons and boxes | Translated text is cut off or overlaps | Leave space; test with longer text |
| Forgetting captions, player labels and quiz feedback | Learners see English inside a "translated" course | Use a full checklist of translatable elements |
| Word-for-word scenarios | Examples feel foreign or are wrong under local rules | Localize names, settings and rules; involve local reviewers |
| Reviewers who are not available | The project waits weeks for sign-off | Book reviewers and dates at kick-off |
| Testing only the English version in the LMS | A language version fails to track completion | Test launch, bookmarking and completion for every language |
Example: what a localization project looks like
IKHYA has delivered eLearning since 2010, with 500+ projects for clients in 40+ countries. Our 500th project was a global onboarding program for a FTSE 100 financial services company, localized into 12 languages. Programs like that are where the planning steps above pay off: one source course, one glossary and one set of review dates, rolled out to every language.
Mining
12 compliance courses localized into 7 Asia-Pacific languages for an Australian mining company
- What we did
- Translation inside Rise and Storyline
- Culturally adapted images and examples
- Voiceover
- Right-to-left checks not needed
- LMS QA per language
- 8 weeks
- Result
- All 7 languages launched on the same day as English.
Before launch, we test every course in your LMS, for example Moodle, TalentLMS, Docebo or Cornerstone, and courses track in SCORM 1.2, SCORM 2004 and xAPI LMSs. You also receive the editable source files (for example Storyline or Captivate files) for future revisions. See our eLearning translation and localization services.
What drives eLearning localization cost?
eLearning localization cost depends on how much content there is and how much has to be rebuilt, not only on the word count. IKHYA quotes every project individually. The main cost drivers are:
Course length and word count
Including narration scripts, captions and quiz feedback.
Number of languages and locales
Depth
Translation only, full localization, or transcreation.
Audio
Human voiceover, AI voiceover, subtitles or none.
Media
Images with text, video with burned-in text, animations to re-sync.
Software simulations
That must be re-recorded in the localized interface.
Authoring tool
And the state of the source files.
Right-to-left languages
And other layout work.
Review rounds
With your in-country reviewers.
LMS testing
For each language version.
For a full breakdown of what moves the budget, read our guide to eLearning localization cost. For a figure for your own courses, send us the course list, languages and source files. A free quote includes a recommended route and a timeline for the project.
Frequently asked questions
Translation converts the course text and script into another language. Localization includes translation and also adapts images, examples, formats, audio, interactions and layout, then tests the course in the target language and LMS.
Yes, for the right content. Machine translation works for factual, low-risk text when a professional fully post-edits it, and AI voiceover suits procedural and frequently updated courses. Keep human translation and review for safety, compliance, legal and medical content.
Use voiceover with captions for most compliance and safety courses, AI voiceover for procedural or frequently updated content, and subtitles only when budget is tight and learners are used to reading while watching.
Record or generate one representative module, or a few key slides, in each language from the approved script, and place it in the built course. Reviewers approve voice, pace and pronunciation before the full course is recorded.
It depends on word count, number of languages, depth of localization, audio, media to rebuild, software simulations, review rounds and LMS testing. IKHYA quotes each project individually; read our eLearning localization cost guide or get a free quote with your course list and languages.
It depends on course length, number of languages, audio and how quickly reviewers sign off. Translation and rebuilding can run in parallel across languages, but in-country review is usually the step that sets the pace, so book reviewers and dates at kick-off. A free quote includes a timeline for your project.
Send the editable source files (not only the SCORM package), final narration scripts, caption files, original images and video projects, fonts, any existing glossary or translations, your target locales and your LMS details.
Usually yes: one SCORM or xAPI package per language is the simplest to track and assign in most LMSs. A single multilingual package can work when learners must switch languages inside one course, but it is harder to build, update and test. Decide this with your LMS admin before the build.
Ready to localize your courses?
Need this built for your team? Tell us which courses, languages and LMS you have, and we will recommend the right mix of translation, localization and voiceover for each one.
