ARTICULATE STORYLINE

Translate an Articulate Storyline course from the published zip

A new language should not mean duplicating the .story file, rebuilding every trigger, and hoping the new SCORM export still tracks. Upload the zip Storyline already published.

Short answer: to translate a Storyline course without opening Storyline, upload the published SCORM zip to SCORM Packager and choose a target language, for example Spanish. It translates the slide text, alt text and player labels (Next, Back, Continue), re-voices the narration, and translates text inside images. You review every string, then download a translated SCORM zip that keeps the original structure and LMS tracking.

Ways to translate a Storyline course, compared

QuestionStoryline translation export (XLIFF/Word)Articulate LocalizationTranslation agencySCORM Packager
Needs the .story source file?Yes, plus a Storyline licenceYes, the project in Articulate 360UsuallyNo, only the published zip
ResultA second .story file per language to republishTranslated versions inside Articulate 360Files to import and republishA translated SCORM zip, ready for the LMS
Narration and videoRe-record and re-import yourselfCheck Articulate docsOften a separate voiceover serviceTranscribed, translated and re-voiced automatically
Text inside imagesReplace images by handCheck Articulate docsUsually a separate DTP stepOCR and redraw, or upload your own image
Review before publishingIn your own processBuilt inAgency QAString-by-string review and team review requests
Cost modelYour authoring timeArticulate add-onPer word, plus project feesMonthly word allowance, free tier available

Storyline's translation export and Articulate Localization are Articulate features. Check Articulate's documentation for their current scope and pricing.

What is translated in a Storyline course

  • Slide titles and text boxes, including text on quiz slides and slide layers
  • Alt text on images and objects
  • Player labels from the Storyline string tables: Next, Back, Continue, Start and similar
  • Narration (transcribed, translated and re-voiced) and video voiceover
  • Text inside images, with OCR and redraw, or your own localized replacement

Slide notes are not translated, and the course title in the LMS manifest stays as published.

Stop rebuilding the .story file for language

Storyline is the right place to change interactions and layout. It is a costly place to change language. Duplicating the project for Spanish creates a second source of truth. The next content update has to land twice. A slide trigger that worked in English breaks in the copy. The LMS then reports a different completion pattern than the original course.

The published SCORM zip is already the artifact your LMS trusts. Translate that zip. Review every string. Swap screenshots and narration that still show English. Export a Spanish course without opening Articulate again.

How it works

  1. Export SCORM from Storyline the way you already do for English.
  2. Upload that course zip and choose the target language, for example Spanish.
  3. Run AI translation on the slide data and player strings inside the zip.
  4. Review slide text, player labels and glossary terms, and handle narration and images.
  5. Preview the translated course in the browser, then download the zip and upload it to Moodle, Canvas, or Blackboard.

Spanish, French, German and the rest

Spanish is the request we hear first. The workflow does not change for French, German, Portuguese, Japanese, or any other target language. Pick the language, review the draft, ship the zip. Rise 360 courses follow the same path: translate a Rise course. For every format we support, see the SCORM translation tool.

Frequently asked questions

Can I translate a Storyline course into Spanish without opening Articulate?

Yes. Upload the SCORM zip Storyline already exported. You do not duplicate the .story file or rebuild triggers for Spanish.

Are player buttons like Next and Back translated?

Yes. SCORM Packager reads the Storyline player string tables inside the published zip, so navigation labels such as Next, Back and Continue are translated along with the slide text.

Is the narration translated too?

Yes. Audio is transcribed, translated and re-voiced with a neural text-to-speech voice in the target language. Video voiceover is replaced the same way. You can upload a recorded voiceover instead.

Will SCORM tracking still work after translation?

Yes. The SCORM driver files and folder layout are kept, only the course text and media are replaced, so completion, score and resume data report to the LMS as before.

Does this work for Rise and other authoring tools?

Rise 360 exports are supported the same way; see translate a Rise course. Other HTML-based SCORM packages are translated from their HTML pages. Tools that keep slide text in their own data files, such as Adobe Captivate, are not fully supported yet.

What if I need French or German instead of Spanish?

Choose that language at translation time. Spanish is the example; the review-and-export steps are identical for every supported target language.

Want the long version? How to translate a Storyline course into Spanish · Storyline's XLIFF export vs translating the zip · One multilingual SCORM package

Translate your Storyline course free

Upload the published Storyline zip and review every string. Translate and preview a full course free (up to 10,000 words). Download the LMS-ready package on any paid plan. No credit card needed.

Free to try and preview · Download on any paid plan · No credit card required