Browse Articles

Select a Product

null Support Directory

Browse all null articles. (Last Updated )

No articles found.

Search Results

No articles found.

Articulate Localization: Overview

Article Last Updated Sep 10, 2026

Develop high-quality localized courses seamlessly with  Articulate Localization, a localization solution integrated right into Articulate’s unparalleled authoring platform. This overview covers the basics of Articulate Localization and explains how to access it.

What Articulate Localization Does

Articulate Localization helps you upskill your global learners more quickly and efficiently with three primary processes:

One-Click AI Translation

Instantly translate Rise 360 and Storyline 360 training into 80+ languages with fully integrated AI translation. Upload custom glossaries to maintain consistency and incorporate specialized terminology.

In-Context Language Validation

Verify the accuracy of localized content with a new language validation experience in Review 360. Validators can preview their changes in context, and authors can import them directly back into the source project.

Multi-language Workflow Management

Streamline end-to-end localization for your Rise 360 and Storyline 360 training. Manage all your languages in a single project, keep track of the validation process in Review 360, and publish all languages at once to Reach 360 or your LMS.

What Languages Are Available

Translate your content into over 80 languages, including certain regional variations such as Canadian French and Brazilian Portuguese.

  • Afrikaans
  • Albanian
  • Amharic
  • Arabic (Modern Standard Arabic)
  • Armenian
  • Azerbaijani
  • Bangla
  • Bosnian
  • Bulgarian
  • Catalan
  • Chinese, Simplified
  • Chinese, Simplified (China)
  • Chinese, Traditional
  • Chinese, Traditional (Taiwan)
  • Croatian
  • Czech
  • Danish
  • Dari (Afghanistan)
  • Dutch
  • English (UK)
  • English (US)
  • Estonian
  • Filipino (Tagalog)
  • Finnish
  • French (Canada)
  • French (France)
  • Georgian
  • German
  • Greek
  • Gujarati
  • Haitian Creole
  • Hausa
  • Hebrew
  • Hindi
  • Hungarian
  • Icelandic
  • Indonesian (Bahasa Indonesia)
  • Irish
  • Italian
  • Japanese
  • Kannada
  • Kazakh
  • Khmer
  • Korean (Standard South Korean)
  • Lao
  • Latvian
  • Lithuanian
  • Luxembourgish
  • Macedonian
  • Malay
  • Malayalam
  • Maltese
  • Maori
  • Marathi
  • Mongolian
  • Nepali
  • Norwegian
  • Norwegian Bokmål
  • Nyanja
  • Pashto
  • Persian (Iran)
  • Polish
  • Portuguese (Brazil)
  • Portuguese (Portugal)
  • Punjabi
  • Romanian
  • Russian
  • Samoan
  • Serbian*
  • Sinhala
  • Slovak
  • Slovenian
  • Somali
  • Spanish (Latin America)
  • Spanish (Mexico)
  • Spanish (Spain)
  • Swahili
  • Swedish
  • Tamil
  • Telugu
  • Tetum
  • Thai
  • Tigrinya
  • Turkish
  • Ukrainian
  • Urdu
  • Uzbek
  • Vietnamese
  • Welsh

*When Serbian is paired with English, Serbian (Latin) is used. When Serbian is paired with any other supported language, Serbian (Cyrillic) is used.

Language Formality

Many languages have different grammatical forms to express levels of formality or politeness depending on the context, such as the target audience, relationship, purpose, or setting.

Formality adjustments include elements like:

  • Pronouns (example: tú → usted in Spanish)
  • Verb conjugations (example: aprendes → aprende)
  • Possessives (example: tu curso → su curso)
  • Commands (imperatives) (example: haz clic → haga clic)
  • Reflexives (example: te inscribas → se inscriba)
  • Language-specific forms (example: Japanese polite verb endings; Korean honorific suffixes)

The Language formality setting in Localization lets you choose from Formal, Informal, or Automatic if the target language supports grammatical formality. The default Automatic setting chooses a formality level based on your content and applies it.

This setting does not rewrite your translation’s overall writing style. It won’t intentionally make the text more advanced, longer, warmer, or more enthusiastic. In most cases, the main difference between Formal and Informal is the grammatical forms of address, not the underlying message.

Note: Formality adjustments do not apply to English, Haitian Creole, Hebrew, Maltese, Somali, or Swahili.

 

Tool Tip: Use our language lookup tool to see which target languages are supported for your source language and if the language pair supports glossary, formality, and right-to-left. 

Here’s how to use it:

  1. Launch the language lookup tool in a separate browser window.
  2. Select your source language from the Select a Source Language dropdown.
  3. A table displays all the supported target languages for the chosen source language with columns for glossary, formality, and right-to-left. A green checkmark in these columns means the corresponding target language supports it.
 

What Can Be Localized?

Multi-language content sharea the same layout and structure across languages. Use this table to understand which content is translated automatically, which requires manual replacement per language, and which isn't translated.

Content

Rise 360

Rise 360 Custom Block (Beta)*

Storyline 360

Text

Automatically translated

(All block text except code blocks, which can be customized per language, and code snippet blocks)

Automatically translated

Automatically translated

(On-slide text, slide notes, and text variable values)

Text labels in Rise 360 and player text labels in Storyline 360

Default text labels are automatically assigned for each target language.

You can assign custom label sets to individual language versions after translation.

Not applicable

Default text labels are automatically assigned for each target language. 

Question banks

Questions drawn from question banks are translated together with the course.

Not applicable

Questions drawn from question banks are translated together with the course.

Closed captions and transcripts (for video, audio)

Automatically translated

Not translated

Automatically translated

Chapters and checkpoints in interactive videos

Automatically translated

Not applicable

Not applicable

Alternative text/ARIA labels

Automatically translated for customized alternative text

Automatically translated for customized alternative text

Automatically translated for customized alternative text

Text-to-speech narration

Automatically translated for AI text-to-speech

Automatically translated for AI text-to-speech

Automatically translated for legacy and AI text-to-speech

Text in images

Not translated

Not translated

Not translated

 

*Right-to-left translation isn't supported for custom blocks at this time.

The following are not translated automatically but can be customized per language:

  • Recorded narration
  • Imported audio (including text-to-speech created outside of the authoring app)
  • Video/video audio
  • Attachments/Resources
  • Embed blocks in Rise 360
  • Code blocks in Rise 360
  • Images in Rise 360 and Rise 360 Custom Block
  • Images on slides, layers, and slide masters in Storyline 360 

How to Access Localization

All active Articulate 360 AI subscriptions and trials can use credits to translate any training format created in Rise 360 and Storyline 360, provided AI is enabled. Translating with credits also gives you access to in-context language validation, multi-language workflow management, and multilingual training publishing.

If AI is disabled for you or your subscription, translation is limited to Rise 360 courses and microlearning, and Storyline 360 courses. You’ll need a paid, course-based localization plan to publish translated content.

Refer to these user guides as you explore localization features in Rise 360:

  1. Creating Multi-Language Rise 360 Courses
  2. Streamlining Language Validation With Review 360
  3. Importing Suggestions from Language Validators
  4. Publish Multi-Language Rise 360 Courses

For Storyline 360, refer to these user guides for detailed instructions:

  1. Creating Multi-Language Storyline 360 Projects
  2. Streamlining Language Validation With Review 360
  3. Importing Suggestions from Language Validators
  4. Publishing Multi-Language Storyline Projects

Note: 

Translating Storyline 360 projects with credits requires Storyline 360 build 3.125.37980.0 or later.

If you have additional questions about using Articulate Localization or just want to learn more, contact sales@articulate.com.