--- schema_version: "1" id: 5923f5e495766b9730611989f83168b87b0b89d1ccf96591cea2fe73dacba740 title: Work with Translation Files collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/translation_file_description.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.translation_file_description.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: eef15c6227a5890f02c6b011e477cc5bc366a56e014e2f5cd161b435422c15a1 description: Translate metadata labels or data translation text, or review existing translations, with XML Localization Interchange File Format (.xlf) or Salesforce Translation Format (.stf) files. products: - Salesforce Platform - Security release: "264" --- # Work with Translation Files Translate metadata labels or data translation text, or review existing translations, with XML Localization Interchange File Format (.xlf) or Salesforce Translation Format (.stf) files. ### Required Editions
Metadata translation available in: Salesforce Classic and Lightning Experience
Data translation available in: Lightning Experience
Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions
Data translation applies to: B2B Commerce
Translation files can contain metadata translations or data translations. Metadata translations are for customizations that you made to your Salesforce organization, such as custom picklist values and custom field labels. Data translations are for the data stored within fields, such as the text in the Product object’s Name and Description fields. For metadata and data translation files, there are three file types. - Source: Use to translate labels for the first time. - Outdated and untranslated: Use to translate labels after the first translation pass. - Bilingual: Use to review and edit translations. Translation files are identified with either the .xlf or .stf extension. Salesforce recommends the XML Localization Interchange File Format (.xlf) for translation files. - **[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. - **[Source Translation Files](https://help.salesforce.com/s/articleView?id=platform.workbench_translation_file_source.htm&release=264.0.0&type=5)** 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. - **[Outdated and Untranslated Translation Files](https://help.salesforce.com/s/articleView?id=platform.workbench_translation_file_outdated.htm&release=264.0.0&type=5)** Use the Outdated and untranslated file to translate labels or data that need translation. The file includes labels or data changed since the last translation and labels that haven't been translated. One Outdated and untranslated file is generated for each language. When multiple files are generated, they're exported to a .zip file containing a file for each translation language. - **[Bilingual Translation Files](https://help.salesforce.com/s/articleView?id=platform.workbench_translation_file_bilingual.htm&release=264.0.0&type=5)** Use the Bilingual file to review translations, edit existing translations, and add translations for labels or data that haven't been translated. One Bilingual file is generated for each translation language. - **[Translation File IDs and Keys](https://help.salesforce.com/s/articleView?id=platform.workbench_translation_file_keys.htm&release=264.0.0&type=5)** Each translatable item has a unique identifier in the translation file. In .xlf files, it’s the id within a trans-unit tag. In .stf files, it’s the key. The structure of these identifiers differs for metadata and data translation files. - **[Flow Identifiers in Translation Files](https://help.salesforce.com/s/articleView?id=platform.workbench_flow_translation_files.htm&release=264.0.0&type=5)** In a translation file exported from Translation Workbench, a unique key or trans-unit ID attribute identifies a flow metadata label. #### See Also - [Export Metadata Translation Files](https://help.salesforce.com/s/articleView?id=platform.workbench_export.htm&release=264.0.0&type=5 "To easily translate your metadata, create files for your translators that contain your Salesforce org’s translatable metadata. Examples of translatable metadata include custom field labels, report type names, and picklist values.") - [Export Data Translation Files](https://help.salesforce.com/s/articleView?id=platform.workbench_export_data.htm&release=264.0.0&type=5 "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.") - [Import Translated Files](https://help.salesforce.com/s/articleView?id=platform.workbench_import.htm&release=264.0.0&type=5 "Import and update the translations for your Salesforce org’s metadata, such as custom fields, report types, and picklist values. Or import and update data translations, such as Product names. Typically, you export translation files from Salesforce, then send them to outside translators or a translation agency for bulk translation activities. You then import the translated files.")