Add locale in Flow Builder

Localizing your flows makes them available in multiple languages. In the Flow Builder, localization is organized by screen, each showing a completion percentage to track translation progress.

Finish setting up your flow in the default locale before adding other languages.

Add and set up localization

In the left panel, click . Then, click Add locale. Select the languages to add.

Each added locale appears as a column in the localization table, pre-filled with the default language values.
To focus only on what’s missing, turn on the Missing only toggle in the left panel. The table will filter to show only untranslated rows.

Set the default locale

The default locale holds your source content, and serves as fallback for any missing translations. Every flow starts with English as its default and only locale.

The pin icon marks the default locale. You cannot delete the default locale, unless another locale is made the default first.

To change the default locale, open the context menu in the column header of the target locale, and select Set as default.

Locale column menu with Set as default selected

Export and import for external translation

You can export the localization file to share with translators and import the translated results.

In the top toolbar, click Import / Export.

Export file format

Exporting produces a .tsv (tab-separated) file with one row per translatable element. The columns are:

Column	Description
`Screen`	The screen the element belongs to (e.g., `Welcome`, `Quiz`)
`Element`	Auto-generated element identifier within that screen. You can change it in Interactions > Element ID.
`Property`	The property type (e.g., `content`)
`[default_locale]`	The default language code (e.g., `en`)
`[locale]`	One column per added locale (e.g., `fr`, `es`)

Example:

Screen	Element	Property	en	fr	es
Welcome	title	content	Turn words into art	Transformez les mots en art
Welcome	subtitle	content	Create stunning images in seconds with AI	Créez des images en quelques secondes
Quiz	quiz-title	content	What will you create?

Leave locale columns blank for untranslated lines — Adapty will treat them as missing.

Import file requirements

Format: .tsv (tab-separated values)
Headers: must include Screen, Element, Property, and at least one locale column
Locale column names: must match the locale codes of locales already added to the flow. Importing a file with locale codes not present in the flow results in an error.
Partial import: you can include only a subset of rows; rows not in the file keep their current values

Limitations

The export process strips variables from strings. If you import this data back, you’ll need to manually add the variables back.
The exported file only includes strings — to localize media, see Localize images and videos.

Translate manually

You can also type translations directly into any cell in the localization table.

To manage a specific row, open its context menu :

Reset to default: Reverts the row’s translation to the default language values.

Localize images and videos

Images and videos can be localized by uploading different files for each locale.

Activate the target locale — below the canvas or in the localization panel.
Select the image / video element.
Upload the localized file in the property panel.

Media elements without localized files will display the default locale’s file.

Canvas image changing as the active locale changes

Preview the localization

To check your translations, switch the active locale in the Flow Builder and review each screen.