Skip to main content
Plural supports multilingual projects out of the box. You build your flow once in a primary language, then add secondary languages so the same conversation runs for users who speak a different language. The structure of your flow is shared across all languages — only the text content changes per language.

Primary vs. Secondary Languages

When you create a project, the language you choose becomes the primary language (shown with a star ⭐ icon). This is the language where all structural editing happens.
The structure of your flow — which elements exist, how they connect, and their configuration — can only be edited in the primary language. Secondary languages let you change text content only. If you need to add or remove elements, switch back to the primary language first.
When you add a secondary language, Plural copies the entire flow structure into that language. You then fill in (or auto-translate) the text fields for that language without changing anything else.

Adding a Secondary Language

1

Open language settings

Inside the Flow Builder, click the language selector in the top toolbar (it shows your current language flag or name).
2

Add a new language

Click Add Language and choose the language you want to add from the list.
3

Choose translation behavior

Decide whether to copy content with or without existing text. If you choose to copy with content, Plural can optionally auto-translate your primary language text into the new language at this point.
4

Edit secondary language text

Switch to the new language using the language selector. All elements are visible, but only text fields are editable. Update the speech, button labels, and any other text for the new language.
You can delete any secondary language you have added if it is no longer needed. Deleting a secondary language does not affect your primary language flow.

Translations (Auto-Translate)

Plural includes an Auto-Translate feature (Beta) powered by DeepL and Google Translate that can translate your entire flow into secondary languages automatically.
  • The Auto-Translate icon appears in the top-left toolbar of the Flow Builder. Click it to toggle the feature on or off.
  • When enabled, any text you add or change in the primary language is automatically translated into all secondary languages.
  • If you manually edit a text field in a secondary language, Auto-Translate will not overwrite that field again — your manual translation takes precedence.
  • For languages not supported by DeepL, translation falls back to Google Translate. Always review Google-translated content carefully, as quality can vary.
Auto-Translate is in Beta for all users. Beta status and availability are subject to change. Always review automatically translated content before publishing.

Using the Change Language Element

To let users switch languages mid-conversation, add a Change Language element to your flow. This element switches the active language at that point in the conversation, allowing you to build a language-selection menu at the start of your flow.

Language Tips

Design in your primary language first

Build and test the full flow in your primary language before adding any secondary languages. This prevents you from needing to redo structural changes across multiple language copies.

Review auto-translated speech carefully

Machine translation can produce awkward phrasing when spoken aloud by a robot or avatar TTS engine. Always listen to the generated speech after translating to check for unnatural-sounding sentences.