Object IDs stay attached
A <trans-unit> ID tells Storyline where a string belongs. Keep that identity intact, and translated text returns to its original object instead of becoming an unmapped import.
XLIFF translation for e-learning teams
Articulate Storyline 360 AI translation & localization tool.
New language. Same course.
Human-level AI translation for your Storyline .xlf exports, with guaranteed 100% XML tag preservation and exact custom variable protection. Bring translated text back without broken object IDs, renamed variables, or a slide-repair backlog.
THE .XLF ROUND TRIP
EN → ES
100%
XML tag preservation
%LearnerName%
Protected, character for character
100+
Target languages
.xlf → .xlf
Built for Storyline re-import
Articulate Storyline localization
One changed ID.
A whole afternoon gone.
You know the drill. The translation reads well. Then Storyline rejects the import, a text box stays in English, or a learner's name appears as a broken placeholder. Now you're back in the timeline, checking objects and triggers instead of publishing the course.
Storyline connects exported strings to specific objects through <trans-unit> IDs. A general-purpose chat tool treats those IDs as text. Rewrite one, and the object mapping breaks. Translate %LearnerName% into %NombreDelAlumno%, and the course is left with a variable it never defined. A prompt that says “keep the XML” is not a validation system.
Keep the build. Qopywriter.ai separates translatable language from protected structure. No renamed references breaking triggers. No missing text boxes from rewritten IDs. No rebuilding timelines to repair translation damage.
Your existing workflow. Less repair work.
How to translate a Storyline 360 course
Export the text. Translate the .xlf. Bring it back to the same course. You don't need to rebuild a single interaction.
-
Export from Storyline
Save a copy of your
.storyproject. Open Storyline's translation export and select XLIFF. Keep that project version unchanged while its text is being translated. -
Translate your .xlf
Upload the export to Qopywriter.ai and choose a target language. AI reads connected segments for meaning while XML tags, IDs, and custom references stay protected.
-
Import. Preview. Publish.
Download the translated XLIFF and import it into the matching project copy. Preview slides, layers, states, quiz feedback, and learner variables before publishing to your LMS.
Storyline 360 XLIFF translation
Translate “Welcome.”
Never %LearnerName%.
Your variable names are course logic, not copy. We lock custom references before translation and return them exactly as exported, including capitalization and both percent signs.
The greeting becomes Bienvenido. The learner's name still comes from the same Storyline variable. That's how personalization and variable-driven interactions stay connected when the course runs in your LMS.
What about references inside XML tags? Those stay protected too. The model doesn't get to invent a replacement placeholder or “correct” an ID.
CUSTOM VARIABLE GUARD
EN → ES
Same name. Same case. Same percent signs.
Inline markup stays valid
Formatting groups, inline placeholders, and protected attributes are part of the file's structure. Tags such as <g> and <x/> are preserved, not regenerated by a chat response.
Your timeline stays yours
The .story file is not rewritten. Slide coordinates, object dimensions, trigger actions, and layer timing remain in the authoring project you already built and tested.
Language that teaches
Correct XML gets you in.
Good language gets it across.
A course isn't a spreadsheet of unrelated sentences. “Submit” is a button. “State” is a slide-object setting in one module and a geographical region in another. Qopywriter.ai reads across exported segments to follow the meaning, not just swap words. Corporate terminology stays consistent from the opening screen to the last knowledge check, and scenario dialogue keeps its voice as the story branches.
Human-level linguistic accuracy that rivals professional translation agencies. Without the agency production cycle. Your instructional tone, feedback, and narrative flow get the same attention as your short interface labels.
That's the real test of e-learning course localization: does the learner understand what to do next? Compare the output with your approved source, not just a word count.
Context, not word substitution.
Illustrative English → Spanish examples
For e-learning developers
Leave triggers and timelines alone. Import translated text into the build you already tested, then focus QA on the localized experience.
For instructional designers
Keep directions clear, feedback constructive, and terminology consistent across slides, layers, and branching scenarios.
For HR & L&D teams
Localize onboarding, compliance, and role-based training without adding a new slide-repair backlog for every language.
Transparent character-based plans
Storyline translation pricing
Start with a free trial. Choose a character allowance when you're ready for larger courses. Every plan includes XML and custom variable protection.
Lite
For smaller course exports
$9/ month
400,000 charactersper month
- Context-aware AI translation
- XML & custom variable protection
- Layout & formatting preservation
- 100+ target languages
Starter
For a recurring course pipeline
$19/ month
1,000,000 charactersper month
- Context-aware AI translation
- XML & custom variable protection
- Layout & formatting preservation
- 100+ target languages
Business
For shared localization work
$49/ month
3,000,000 charactersper month
- XML & custom variable protection
- 100+ target languages
- Unlimited team members
- Priority support
Yearly
For a year of training rollouts
$169/ year
12,000,000 charactersper year
- XML & custom variable protection
- 100+ target languages
- Unlimited team collaboration
- Priority support
Before your first import
The questions course teams ask.
File formats, custom variables, text fit, and the checks that still belong in your release process.
Have an import error in front of you?
Keep the original export and the exact error message. Send a redacted sample so our team can check the file without learner data.
support@qopywriter.ai ↗How do I translate a Storyline 360 course with AI?
Export an XLIFF (.xlf) file from Storyline 360, upload it to Qopywriter.ai, and choose a target language. Download the translated file and import it into a copy of the same Storyline project. Preview the course before publishing to your LMS.
Will slide positions, triggers, and timelines stay intact?
X/Y coordinates, object dimensions, triggers, and timeline settings live in your .story project. Qopywriter.ai does not edit that project; it preserves the IDs that map translated text back to its objects. Longer translations still need a visual check for wrapping, font support, and right-to-left layout.
Can I use ChatGPT to translate Storyline XLIFF?
A chat model translates text, but a plain chat response does not enforce XLIFF validation or exact token preservation. An altered ID, dropped inline tag, or renamed %LearnerName% breaks object mapping or personalization. Qopywriter.ai treats those elements as protected structure, not language for the model to rewrite.
Are custom variables and inline XML tags protected?
Yes. References such as %LearnerName% and %CourseScore% keep their exact spelling, case, and percent signs. XML inline tags and translation unit IDs are protected too. Only translatable target text and required target-language fields change.
How does the language quality compare with a human agency?
The AI works across exported segments to preserve meaning, terminology, learner voice, and narrative flow, the same essentials a professional agency reviews. This delivers human-level language without a sentence-by-sentence production handoff. Use the trial to compare output against your approved source, and keep qualified human review for regulated content and final language approval.
Which XLIFF formats and languages are supported?
The translator supports XLIFF 1.2 and 2.0 and more than 100 target languages. Keep the XLIFF version exported by Storyline. Do not convert the schema or rename translation units before re-importing.
Does this translate audio, images, or a published SCORM package?
Only text present in the XLIFF export is translated. Audio, video, and text baked into images are not rewritten. Upload the .xlf, not the .story project or a published SCORM ZIP. Review those media assets separately, then publish the localized course from Storyline and test completion and scoring in your LMS.
What should I check if Storyline rejects an imported file?
Confirm that you're importing into a copy of the exact project used for export. Check that the download is an .xlf file and that its IDs and XLIFF version have not been edited. If the project changed during translation, export again from the current version. For a persistent error, send the exact message and a redacted example to our support team.
Is there a free trial for Storyline XLIFF translation?
Yes. The free trial includes a limited character allowance and requires no credit card. Test a short course with a custom variable and quiz feedback, then check the translated import in Storyline before choosing a paid plan.
Put one export to the test
Your next language.
Not your next rebuild.
Start with a short course. Include a learner variable and quiz feedback. Translate the export, bring it back into Storyline, and check the actual build before your next rollout.