---
schema_version: "1"
id: c736afa8572e1df5024be49d4f34af46edec589ca55fa31f5e1ff2ecef6a0317
title: Source Translation Files
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/workbench_translation_file_source.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.workbench_translation_file_source.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ad134f36826b607b4f3a3380f0f7afa45cfdabe5b6ab41a1ccfae7318e192d08
description: Use the Source file to translate an organization's labels or data for the first time. The Source file contains labels for all of a Salesforce org's translatable metadata or data in the org's default language.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Source Translation Files

Use the Source file to translate an organization's labels or data for the first time. The Source file contains labels for all of a Salesforce org's translatable metadata or data in the org's default language.

### 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;">Metadata translation available in: Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Data translation available in: 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><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Data translation applies to: B2B Commerce</td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_note.png)

Note Salesforce recommends the XML Localization Interchange File Format (.xlf) for translation files. See Considerations for Working with Translation Files for tips on editing translation files and how to translate rich text field content.

To prepare the translation file for your translators:

- Create one copy of the Source file for each language you’re translating into.
- In the header of each Source file, change the language code from the organization's default language to the translation language. For example, replace `en_US` for English (US) with `es` for Spanish.
- Ensure that the headers are in the organization’s default language. To confirm, export a translation file and copy the headers.

## XML Localization Interchange File Format (.xlf) Source Translation Files

Source .xlf translation file content is organized into translation units. Translation units for translated labels contain a `target` tag with the translated value. Untranslated labels have a `source` tag, but no `target` tag.

Tell your translators:

- After each `source` tag, add a `target` tag that contains the translated value.
- If a `target` tag exists and the translation is out of date, replace the text in the target tag. Outdated labels have a value of `outOfDate="true"` within the trans-unit tag.
- When translating text in a rich text area field, include all HTML tags such as `<p></p>` and `<b></b>`.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_important.png)

Important A translated value for the data in the record’s Name field is required to translate data in other fields for that record. For example, you must provide a German translation for the name of a Product before you can translate its description into German.

  
| Tag | Description | Edit Options |
| --- | --- | --- |
| `trans-unit` | Translation unit. Contains unique identifiers for the label, including the label’s id, maximum width, and out-of-date indicator. | Do not edit. |
| `source` | Label or text in the org’s default language. | Do not edit. |
| `target` | The current translation that’s visible to end users selecting the target language as their personal language. | Enter the translated value. Add a target tag if needed. |
| `note` | Description of the metadata label, if defined in the source language. | Do not edit. Translatable field descriptions each have a separate `trans-unit` tag. |

For example, if you build a custom Nickname field on the Account object, the original file contains this `trans-unit` tag in the exported Source .xlf file.

```markup
<trans-unit id="CustomField.Account.Nickname.FieldLabel" maxwidth="40" size-unit="char">
    <source>Nickname</source>
    <note>The person’s nickname, or what they prefer to be called.</note>
</trans-unit>
```

To translate this label, add a `target` tag containing the translated value to the corresponding `trans-unit` tag after the `source` tag.

```markup
<trans-unit id="CustomField.Account.Nickname.FieldLabel" maxwidth="40" size-unit="char">
    <source>Nickname</source>
    <target>Apodo</target>
    <note>The person’s nickname, or what they prefer to be called.</note>
</trans-unit>
```

## Salesforce Translation Format (.stf) Source Translation Files

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_note.png)

Note Salesforce doesn’t recommend the STF format for translation files. If you choose to use this format, we don’t recommend editing the file with Microsoft Excel. For more information and restrictions, see Considerations for Working with Translation Files.

Tell your translators to replace the untranslated values in the LABEL column with translated values.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_important.png)

Important A translated value for the data in the record’s Name field is required to translate data in other fields for that record. For example, you must provide a German translation for the name of a Product before you can translate its description into German.

  
| Column | Description | Edit Options |
| --- | --- | --- |
| KEY | Unique identifier for the label. | Do not edit. |
| LABEL | Label or text in the org’s default language. | Replace untranslated values with translated values. |

For example, if you build a custom Nickname field on the Account object, the original file contains this row in the exported Source .stf file.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small "><colgroup><col style="width:50%"> <col style="width:50%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><code># KEY</code></td><td class="slds-cell-wrap" style="vertical-align:top;"><code>LABEL</code></td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><code>CustomField.Account.Nickname.FieldLabel</code></td><td class="slds-cell-wrap" style="vertical-align:top;"><code>Nickname</code></td></tr></tbody></table>

To translate this label, replace the LABEL text in that row with the translated value.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small "><colgroup><col style="width:50%"> <col style="width:50%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><code># KEY</code></td><td class="slds-cell-wrap" style="vertical-align:top;"><code>LABEL</code></td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><code>CustomField.Account.Nickname.FieldLabel</code></td><td class="slds-cell-wrap" style="vertical-align:top;"><code>Apodo</code></td></tr></tbody></table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_important.png)

Important Don't add columns to or remove columns from the .stf translation file.

#### See Also

- [Considerations for Working with Translation Files](https://help.salesforce.com/s/articleView?id=platform.workbench_translation_file_considerations.htm&release=264.0.0&type=5 "Review some important considerations to ensure that your edited translation file can be successfully imported.")
- [Supported Languages](https://help.salesforce.com/s/articleView?id=xcloud.faq_getstart_what_languages_does.htm&type=5&language=en_US)