---
schema_version: "1"
id: b1c3103f7da3ca7318cce9d5d618d3fb00e95165bee104a5fab670dc485fc05c
title: Considerations for Translating Flows
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/workbench_flow_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.workbench_flow_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: de294d225c6c8bbbe373a4dd1d8838bd8bbe5720fbb53abda1ef537a4340e166
description: When you use Translation Workbench to translate flows, note these considerations.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Considerations for Translating Flows

When you use Translation Workbench to translate flows, note these considerations.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

## Translating Flows

- To check which flow types are translatable, see Flow Types in Salesforce Help.
- A translation can only reference a merge field (like {!myVar}) if the field is referenced in the first 1,000 characters of the primary label.
- Translations for flow definition name and version name each have a maximum limit of 255 characters. Other translations for flow labels have a maximum of 1,000 characters.
- Each use of a merge field in a label reduces the 1,000-character limit by 66 characters. For example, even though `{!Account.Name}` is only 15 characters long, it counts as 66 characters toward the limit.
- Text templates and merge field values aren’t supported for translation.
- Right-to-left languages aren’t supported.
- When a flow label isn’t translated for a language, Salesforce uses the translation for the appropriate fallback language. If the fallback language has no translated label, the primary label is used.

## Updating Flow Translations

When you change a flow that you translated, Salesforce copies as much information as it can when you create a version or save changes to the translated version.

For example, version 1 of the Survey Customers flow has a translation for the WelcomeMessage field. When you save another version of the flow, Salesforce copies all the latest translations from version 1 to version 2. The same happens if you save it as a new flow.

When you remove a label from a flow, translations aren’t copied. Salesforce uses the label’s Unique Name to copy translations to another version. When you change the label’s unique name, Salesforce treats it as a new label.

When you delete a flow, its translations are also deleted.

When you translate a flow from a managed package, the flow’s Master Definition Name doesn’t appear on the Translate page or the Override page. To update the translation for the Master Definition Name, edit the flow label and then update the translation from the Translate page.

## Exporting and Importing Flow Translations

- You can export and import translation files to send to translators or to help you translate lengthy text.
- When you export translations, the primary labels are truncated after 1,000 characters.

#### See Also

- [_Salesforce Help_: Translate Flow Screen Components](https://help.salesforce.com/s/articleView?id=platform.flow_translate.htm&type=5&language=en_US)