# Translations Metadata Type in SFDX & Metadata API > The Translations metadata type (translations/.translation-meta.xml) stores org-level translations for Custom Labels, Custom Tabs, Custom Applications, Screen Flows, Einstein Bots, and Prompt Templates. - Source: https://sfdxtalk.com/docs/metadata/translations-metadata-type/ - Category: Metadata - Applies to: Salesforce Winter '27 (API version 68.0) - Level: intermediate - Published: 2026-11-12 - Last updated: 2026-11-12 - Publisher: SFDX Talk Editorial (unofficial; not affiliated with or endorsed by Salesforce) - License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) ## Why the `Translations` Metadata Type Is Essential for Global Orgs While [CustomObjectTranslation](/docs/metadata/custom-object-translation-metadata-type/) handles object-level fields and validation rules, **`Translations`** (`translations/.translation-meta.xml`) is the central translation hub for **org-wide, non-object metadata**. Whenever you localize a Lightning Web Component via `@salesforce/label/c.MyLabel` or localize a multi-language customer Screen Flow, those translations live inside `translations/.translation-meta.xml`. ```mermaid flowchart TD TR["Translations
(translations/fr.translation-meta.xml)"] --> CL["customLabels
(Localizes @salesforce/label/c.* in LWC & Apex)"] TR --> FLOW["flowDefinitions
(Localizes Screen Flows, Screens, Choices & Prompts)"] TR --> APP["customApplications & customTabs
(Localizes App Launcher & Navigation Bar)"] TR --> PROMPT["prompts & botTemplates
(Localizes In-App Guidance & Bots)"] ``` --- ## What Is Stored Inside `translations/.translation-meta.xml`? | Child Element | What It Translates | Related Metadata Type | |---|---|---| | `customLabels` | Custom Labels referenced in LWC, Apex (`System.Label`), and Flows. | [CustomLabels](/docs/metadata/custom-labels-metadata-type/) | | `flowDefinitions` | Screen Flow titles, screen component labels, help text, and choices. | [Flow](/docs/metadata/flow-metadata-type/) | | `customApplications` | App Launcher names and descriptions. | [CustomApplication](/docs/metadata/custom-application-metadata-type/) | | `customTabs` | Custom Tab labels in the Lightning navigation bar. | [CustomTab](/docs/metadata/custom-tab-metadata-type/) | | `quickActions` | Global Quick Action labels (e.g., `NewCase`, `LogACall`). | [QuickAction](/docs/metadata/quick-action-metadata-type/) | | `reportTypes` | Custom Report Type labels, descriptions, and section headers. | [ReportType](/docs/metadata/report-type-metadata-type/) | | `prompts` | In-App Guidance walkthrough and floating prompt titles/bodies. | `Prompt` | --- ## Real-World XML Example (`translations/es.translation-meta.xml`) ```xml Commercial_Operations_Console Approval_Submitted_Toast_Message Billing_Dashboard_Tab Customer_Onboarding_Screen_Flow Company_Tax_ID_Input Número de Identificación Fiscal (NIF) Customer_Details_Screen Customer_Onboarding_Screen_Flow ``` --- ## Querying Translated Custom Labels via Tooling API (`ExternalStringLocalization`) While the `Translations` metadata file bundles everything together in source control, Custom Label translations are stored at the database layer in the Tooling API object **`ExternalStringLocalization`**. ### Query All Spanish and French Translations for a Specific Custom Label ```sql SELECT Id, ExternalStringId, ExternalString.Name, ExternalString.Value, Language, Value, LastModifiedDate FROM ExternalStringLocalization WHERE ExternalString.Name = 'Approval_Submitted_Toast_Message' ORDER BY Language ASC ``` *(Run this query against the **Tooling API** endpoint `/services/data/v68.0/tooling/query/`.)* --- ## Senior Architect Best Practices & Gotchas > [!WARNING] > **Avoid Full-File Overwrites on `translations/.translation-meta.xml`:** When you retrieve `Translations` alongside only a subset of `CustomLabels` in `package.xml`, Salesforce only returns the `` translations matching the labels in your manifest. Keep your `translations/.translation-meta.xml` under modular git control so partial retrieves do not accidentally wipe out existing translations in your repository. - **Flow Version Number Independence:** Starting in recent API versions, `` inside `Translations` supports omitting the hardcoded version suffix (`_1`, `_2`) on `` so translations carry forward cleanly when you activate a new version of a Screen Flow. ## Frequently Asked Questions ### What is the difference between Translations and CustomObjectTranslation? CustomObjectTranslation localizes metadata tied to a specific object (fields, validation rules, record types), whereas Translations (stored in translations/lang.translation-meta.xml) localizes org-wide components like Custom Labels, Custom Tabs, Custom Applications, Flows, and Prompt Templates. ### How do you deploy translated Custom Labels in SFDX? Translated Custom Labels are stored inside force-app/main/default/translations/lang.translation-meta.xml under customLabels blocks containing the CustomLabel developer name and localized label. ### Can Screen Flow labels and input prompts be translated via the Translations metadata type? Yes. The flowDefinitions element inside a .translation-meta.xml file allows you to translate Flow definition labels, Screen field labels, help text, choice labels, and validation error messages across Flow versions. ### What are the three tiers of language support in Salesforce Translation Workbench? Salesforce categorizes languages into Fully Supported languages (full UI and Setup translation), End-User languages (standard objects and end-user pages translated, Setup remains English), and Platform-Only languages (you provide all translations via metadata). ## Official References - https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_translations.htm