# StandardValueSetTranslation Metadata Type in SFDX

> StandardValueSetTranslation localizes custom and overridden picklist values on standard Salesforce fields (standardValueSetTranslations/<Name>-<lang>.standardValueSetTranslation-meta.xml).

- Source: https://sfdxtalk.com/docs/metadata/standard-value-set-translation-metadata-type/
- Category: Metadata
- Applies to: Salesforce Winter '27 (API version 68.0)
- Level: beginner
- 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 `StandardValueSetTranslation` Metadata Type Matters

Salesforce automatically translates out-of-the-box standard picklist values (`New`, `Working`, `Closed` on `Case.Status`). However, as soon as you add custom business values to a [StandardValueSet](/docs/metadata/standard-value-set-metadata-type/)—such as `Awaiting Vendor RMA` on `CaseStatus` or `Partner Referral - Tier 1` on `LeadSource`—those custom values appear in English to international users unless you deploy a **`StandardValueSetTranslation`**.

```mermaid
flowchart LR
    SVS["StandardValueSet<br/>(standardValueSets/CaseStatus.standardValueSet-meta.xml)"] --> ES["StandardValueSetTranslation (Spanish)<br/>(CaseStatus-es.standardValueSetTranslation-meta.xml)"]
    SVS --> DE["StandardValueSetTranslation (German)<br/>(CaseStatus-de.standardValueSetTranslation-meta.xml)"]
    ES --> CASE["Localizes Case.Status in Service Console<br/>and Experience Cloud"]
    DE --> CASE
```

---

## SFDX Source Format & File Naming

Files reside in `force-app/main/default/standardValueSetTranslations/` and combine the official [StandardValueSet](/docs/metadata/standard-value-set-metadata-type/) name with a hyphen and the language code:

- `CaseStatus-es.standardValueSetTranslation-meta.xml`
- `OpportunityStage-fr.standardValueSetTranslation-meta.xml`
- `LeadSource-ja.standardValueSetTranslation-meta.xml`
- `AccountRating-de.standardValueSetTranslation-meta.xml`

---

## Key Metadata Fields

| Field | Type | Required | Description |
|---|---|---|---|
| `valueTranslation` | `ValueTranslation[]` | No | List of translated standard picklist values. |
| `valueTranslation.masterLabel` | `string` | Yes | The exact **Master Label** of the value in the `StandardValueSet`. |
| `valueTranslation.translation` | `string` | Yes | The localized text for the target language. Leave empty string if untranslated. |

---

## Real-World XML Example (`standardValueSetTranslations/CaseStatus-es.standardValueSetTranslation-meta.xml`)

```xml
<?xml version="1.0" encoding="UTF-8"?>
<StandardValueSetTranslation xmlns="http://soap.sforce.com/2006/04/metadata">
    <valueTranslation>
        <masterLabel>Awaiting Customer Logs</masterLabel>
        <translation>Esperando registros del cliente</translation>
    </valueTranslation>
    <valueTranslation>
        <masterLabel>Escalated to Tier 3 Engineering</masterLabel>
        <translation>Escalado a Ingeniería Nivel 3</translation>
    </valueTranslation>
    <valueTranslation>
        <masterLabel>Resolved - Pending Verification</masterLabel>
        <translation>Resuelto - Pendiente de verificación</translation>
    </valueTranslation>
</StandardValueSetTranslation>
```

---

## Senior Architect Best Practices

> [!TIP]
> **Always Pair `StandardValueSet` and `StandardValueSetTranslation` in PRs:** Whenever a developer adds a new stage or status to `OpportunityStage.standardValueSet-meta.xml` or `CaseStatus.standardValueSet-meta.xml`, enforce a pull-request check ensuring the corresponding `StandardValueSetTranslation` files are updated in the same commit.

- **Deploy the `StandardValueSet` First (or Together):** If a `StandardValueSetTranslation` file contains a `<masterLabel>` that does not yet exist in the target org's `StandardValueSet`, the translation entry will fail or be dropped during deployment.

## Frequently Asked Questions

### Why do you need StandardValueSetTranslation if Salesforce already translates standard fields?

While Salesforce provides out-of-the-box translations for default standard picklist values, any custom picklist values you add to standard fields like CaseStatus, LeadSource, OpportunityStage, or AccountType require StandardValueSetTranslation to appear localized.

### How are StandardValueSetTranslation files named in SFDX?

Files are stored in force-app/main/default/standardValueSetTranslations/ using the format StandardValueSetName-lang.standardValueSetTranslation-meta.xml, such as CaseStatus-es.standardValueSetTranslation-meta.xml.

### Does a wildcard (*) in package.xml retrieve all StandardValueSetTranslation files?

Depending on the API version, wildcard retrieval can skip standard value sets unless explicitly named. Best practice is to explicitly list customized sets like CaseStatus-es, LeadStatus-es, and OpportunityStage-es in package.xml.

## Official References

- https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_standardvaluesettranslation.htm