---
schema_version: "1"
id: ccd842e93c048a1f0a43b50f2df8d9d3c418216ec660cf0919558dd537fae914
title: Export Data Translation Files
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/workbench_export_data.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.workbench_export_data.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4ea10831bf0ecec6acaf59ceee7090a3bf5fb305f4701e834df16b627a6ee196
description: If data translation is enabled in your Salesforce org, you can create files for your translators that contain your org’s data translations. Examples of translatable data include B2B Commerce Product names and data stored in custom fields.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Export Data Translation Files

If data translation is enabled in your Salesforce org, you can create files for your translators that contain your org’s data translations. Examples of translatable data include B2B Commerce Product names and data stored in custom fields.

### Required Editions

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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d109450e69">User
              Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d109450e69 ">To export or import translation files</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d109450e69 ">
              <p>Manage Translation</p>
              <p style="margin-bottom:0;">AND</p>
              <p style="margin-bottom:0;">Create Documents</p>
            </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 You need the Manage Translation AND Create Documents user permissions to import or export translation files. If you attempt either operation without both user permissions, it’s possible to navigate to the import or export page, but the operation itself fails.

Before you can export data translation files, you must enable Translation Workbench and data translation.

![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 Each data translation export request is limited to 1 GB of data and 100,000 records. If your requested export exceeds either of those limits, only a partial file is exported. To reduce the amount of data exported, use the language filter, available for the Outdated and translated and Bilingual export types. If your org’s data translations for a single object and language exceed either of those limits, use BULK API or [Data Loader](https://developer.salesforce.com/docs/atlas.en-us.dataLoader.meta/dataLoader/data_loader_intro.htm).

1. From Setup, in the Quick Find box, enter Export, and then select **Export**.
2. Select **Data** as the Translation Type.
3. Select the objects for data translation.
4. Select which labels you want to export.
    - **Source**–Used as the initial source for creating translations.
        
        Creates a set of files by object with all translatable text.
    - **Outdated and untranslated**–Used to make updates.
        
        Creates a set of files, by language and then by object, including text changed after the last translation and text that isn’t yet translated. These files are then compressed into .zip files.
    - **Bilingual**–Used for reference and reviewing all your untranslated and translated customizations.
        
        Creates a set of files, by language and then by object, including all the translatable text in its current translated or untranslated state. These files are then compressed into .zip files.
        
        The content in each file is divided into Untranslated and Translated sections. Each translatable text element is in the Untranslated or the Translated section, according to its translation state. The Translated section includes the out-of-date status for each text element.
5. If you selected the Outdated and untranslated or Bilingual export type, select at least one language.
    
    ![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 Inactive status controls only what users see: it doesn't affect exports or imports. Inactive languages are still included in exported translation files and remain available for translators to work on.
6. Select a file format. Salesforce recommends the XML Localization Interchange File Format (XLIFF) because it contains more information than the .stf format, like the field width.
7. Click **Export**.
    
    A status message tells you that the export is being processed. Wait for it to finish before submitting another export request. When the export is complete, an email is sent to the email address specified in your profile. The email includes a link to a .zip file with your exported 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 When exporting data translation files, individual uncompressed files are limited to 25 MB. If multiple files are required, each file name is date stamped and incremented. For example, Bilingual\_de\_Product2\_2020-10-20 0836\_1.xlf and Bilingual\_de\_Product2\_2020-10-20 0836\_2.xlf.
8. Send the files to your outside translators or translation agency for bulk translation activities, then use **Import** to update your data translations.

#### See Also

- [Enable Data Translation](https://help.salesforce.com/s/articleView?id=platform.data_translation_enable.htm&release=264.0.0&type=5 "Allow translation of data stored in certain objects and fields.")
- [Translation Workbench](https://help.salesforce.com/s/articleView?id=platform.workbench.htm&release=264.0.0&type=5 "Use Translation Workbench to maintain translated values for metadata and data labels in your Salesforce org. Specify languages for translation and assign translators for each language. Manage translated values for any Salesforce supported language. Translators can maintain translations directly through the workbench, or you can export translation files for bulk translation imports.")
- [Salesforce Developer Doc: Translations](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_translations.htm)