> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flow-board.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage translations

> Create and maintain multilingual flows in Flowboard Studio.

Translations let you use one flow structure for multiple languages. This is the right approach when the journey stays the same but the text shown to the user needs to change based on locale.

## What translations are made for

Use translations when you want to:

* Launch the same onboarding in more than one market
* Keep messaging consistent across languages
* Avoid duplicating and maintaining separate flows for each locale
* Review localized copy in one place

## How translations work

Flowboard keeps one main flow and lets you add language-specific content on top of it. The structure, order of screens, and actions stay aligned while the translated text changes by language.

## Typical translation workflow

<Steps>
  <Step title="Add a language">
    Open the flow editor and switch to the translation area. Add the language you want to support.
  </Step>

  <Step title="Review translatable fields">
    Flowboard lists the content that can be localized, such as titles, paragraphs, button labels, placeholders, and option labels.
  </Step>

  <Step title="Translate manually or with AI">
    Enter the translated copy yourself or use the AI translation tools to create a first pass.
  </Step>

  <Step title="Lock approved wording">
    Lock specific fields when you want to protect legal copy, product names, or approved messaging from future automated changes.
  </Step>

  <Step title="Check the flow before publishing">
    Review the translated screens carefully to make sure the text still fits the layout and the meaning is correct.
  </Step>
</Steps>

## What should be translated

Translate anything the user reads or selects. In most flows, that includes:

* Headings and body copy
* Button labels
* Input labels and placeholders
* List options and picker values
* Chart labels or structured text content

## What stays shared across languages

These parts usually stay the same:

* Screen order
* Routing logic
* Audience rules
* Experiment setup
* Flow analytics history

## Best practices

* Start from your strongest approved source language.
* Keep product names, brand terms, and legal wording consistent.
* Review text length, especially for buttons and compact mobile layouts.
* Use locale-specific wording instead of direct word-for-word translation when needed.
* Recheck every language after major design or copy changes.

<Tip>
  If a translation needs a different user journey, create a separate flow instead of forcing one structure to serve very different markets.
</Tip>

## Related guides

* [Understand flows](/features/flows-overview)
* [Control actions and transitions](/features/flows-actions-transitions)
* [Target by locale with audiences](/features/audiences)