Attribute translations cover the attribute name, slug, and description. Attribute option translations are separate: each option can translate its label and value. The label is the display text shoppers see in option selectors; the value is the option's URL token (it plays the slug role for options), so translating it localizes filter and variant URLs. Translated values must stay URL-safe: lowercase letters, digits, underscores, and hyphens only.
On the web
- In your store admin, go to Translations.
- Choose the language you want to translate into.
- Select Attributes.
- Enter the translated name and, optionally, a translated slug.
You can also translate attributes with per-language CSV import and export or AI translation jobs. Changing the original attribute name or slug can mark existing translations as outdated.
If a field already has translations in any language, you cannot clear that field on the original attribute until those translations are removed. The same backend rule applies to forms, update imports, and any other source edit path.
Translation CSV imports are row-atomic. If any translated field in a row is invalid, references a missing attribute ID, duplicates a localized unique value, or tries to translate a field whose original value is blank, that row is rejected and none of that row's translated fields are saved. Other valid rows in the same file can still be imported.