Designing Articulate Storyline Courses for Translation: Best Practices That Save Time, Money, and Headaches
- Vicky Nothnagle - DTP Services Manager
- Mar 19
- 6 min read
If you've ever clicked "Import" on a translated Storyline file and watched your carefully designed layout fall apart in real time — you're not alone. It's practically a rite of passage in the eLearning industry.
The standard workflow looks deceptively simple:
Articulate Button → Translation → Export
Send the Word or XLIFF file to your translation provider
Receive the translated file back
Articulate Button → Translation → Import
And just like that... new language! Easy, right?
Not quite. What usually follows is overlapping text, broken buttons, mistimed animations, and audio that's completely out of sync with what's happening on screen. At that point, it becomes clear that what you're actually dealing with isn't just translation — it's localization. And there's a meaningful difference between the two.
(Not sure where translation ends and localization begins? Our blog breaks it down clearly.)
It's More Than Swapping Words
Localization means thinking about audio synchronization, interactive elements, cultural adaptation, and multimedia — not just the text on screen. And the more complex your course design, the more complex (and costly) the localization process becomes.
We know instructional designers are often juggling tight deadlines and tighter budgets. So consider this your practical guide to designing Storyline courses with translation in mind — so that when the time comes to go multilingual, the process is smoother, faster, and more affordable.
And if you want the bigger picture first, we'd also recommend checking out our free eBook: The eLearning Content Creator's Guide to Effortless Translation.
1. Design for Text Expansion From Day One
This is the most common — and most preventable — Storyline localization problem.
When you translate from English into languages like German or French, text expands. Significantly. German averages around 20% expansion; French can hit 30% or more. "Plane" becomes "Flugzeug." "We eat cheese" becomes "nous mangeons du fromage." That's not just more letters — in French, it's also an additional word due to grammatical structure.
Storyline won't automatically resize your text boxes, buttons, or fields to accommodate longer translated strings. So if you've designed elements that are perfectly sized for English, you'll find translated text spilling outside the boundaries of buttons, labels, and callouts — breaking your visual layout entirely.
What to do: When designing slides, give every text-bearing element more breathing room than you think you'll need. A good rule of thumb is to build in at least 30% extra space if you know the course will be localized.
2. Simplify Your Timelines — Your Future Self Will Thank You
Storyline's edit mode displays all slide elements simultaneously, regardless of their staggered timing. That makes it genuinely challenging for post-production engineers to realign elements on the timeline after localization — especially when audio is involved.
Here's the wrinkle: just as text expands, audio expands too. "We eat cheese" is three syllables. "Nous mangeons du fromage" is six. And foreign-language voice talent may naturally speak at a different pace than your original narrator, regardless of syllable count.
The more elements that need to be resynced on a complex timeline, the more manual work is required — and the more it costs.
Two approaches that help:
Reduce slide complexity. Fewer animated elements per slide means fewer sync points to adjust after translation. If that means adding a slide or two, it's usually worth it.
Use Slide Layers triggered by Cue Points. Each Slide Layer only shows the elements in its own timeline, dramatically reducing the complexity of any given section. Cue Points on the base layer can trigger each layer in sequence, synced to a master narration track — or each layer can carry its own independent audio track, effectively functioning as a sub-slide. More setup upfront, but far less rework during localization.
3. Think Carefully About Audio vs. Subtitles — and When to Choose Which
Subtitles are a fantastic localization tool: versatile, scalable, and typically less expensive than re-recording voice-over in every target language. But whether they save you money depends heavily on where you're starting from.
If subtitles don't already exist in your source course, your localization provider will need to create an English subtitle master file before any translation can happen. That process involves accounting for slide durations, audience reading speeds, line limits (generally no more than two lines per caption), and making sure subtitles don't visually overlap with other on-screen elements. That's a significant upfront investment.
Here's the math that usually guides the decision:
1–2 target languages: Retrofitting subtitles may cost as much or more than recording localized voice-over. Voice-over might win here.
3+ target languages: The cost of creating the subtitle master file gets spread across multiple languages, making the subtitle approach increasingly cost-effective.
If you're building a course — or a curriculum — that's likely to be localized broadly, building closed captions into your source course from the start is one of the smartest investments you can make.
Articulate 360 supports native closed captioning, including import of industry-standard SRT files, which integrates well with professional localization workflows.
4. A Note on Articulate's Built-In Localization Feature
Articulate recently introduced Articulate Localization, a tool within the Articulate 360 suite that enables automated translation of Rise 360 and Storyline content into 70+ languages with just a few clicks. We took it for a spin and have some honest thoughts.
The functionality is genuinely impressive for certain use cases — fast, accessible, and easy to use. But it's important to understand what it is: machine translation, without human involvement. For internal-only content, early-stage drafts, or situations where near-enough is good enough, it may fit the bill. But for anything learner-facing, regulated, or culturally sensitive, automated-only translation carries real risk.
It's also worth noting that when you factor in cost vs. value, working with a translation partner who uses AI as part of a human-reviewed workflow often delivers a better result at a comparable or lower price point.
5. Write Source Content With Translation in Mind
This is less a Storyline-specific tip and more a golden rule for any eLearning content that will be localized: write clean, neutral, translatable source text.
That means:
Avoiding idioms, metaphors, and regional references ("knocked it out of the park" doesn't translate)
Spelling out acronyms before using them
Keeping sentences direct and avoiding overly complex syntax
Skipping humor or cultural references that don't cross borders well
The cleaner the source content, the more efficiently AI-assisted translation tools can process it — and the less time human linguists need to spend untangling nuance that shouldn't have been there in the first place. It's the kind of thing that pays dividends at scale.
How AI-Assisted Human Translation Changes the Equation
Here's where things have meaningfully evolved since older guidance on this topic was written.
Today, the most effective eLearning localization workflows aren't purely human — and they're definitely not purely machine. They're AI-assisted human translation workflows, where AI handles the speed-and-volume lifting, and experienced human linguists handle cultural accuracy, quality assurance, and the judgment calls that automated tools consistently get wrong.
At Language Intelligence, this is exactly the approach we've built our workflows around. Our AI-assisted translation services combine the efficiency of modern language models with native-speaking subject matter experts who understand the content, the audience, and the stakes.
The result: faster turnaround, lower cost at scale, and quality that holds up — whether you're localizing a single course into two languages or a full curriculum into fifteen.
Our eLearning Engineering team works directly with Storyline, Rise 360, and other major authoring tools, and our proprietary intellireview® platform makes it easy for your subject matter experts to review translated content in context, collaborate with linguists, and approve changes — all in a secure, cloud-based environment.
Setting Realistic Expectations
Storyline's export/import translation feature is a genuinely useful starting point. But it doesn't account for text expansion, timeline resync, audio adaptation, subtitle creation, or cultural localization. Those pieces don't manage themselves — they require expertise, process, and the right technology stack.
The good news is that by designing with localization in mind from the start — extra space in your layouts, simpler timelines, source captions, clean writing — you can dramatically reduce the complexity of what comes after.
And when you're ready to take that next step, we're here to help make it straightforward.
Language Intelligence has been helping organizations communicate across languages since 1988. Today, we operate as a Language Solutions Integrator — combining AI, human expertise, and workflow automation to deliver multilingual content that works. Learn more about us →
