> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/features-and-advanced-setup/theme-string-translations.md).

# Theme string translations

Edit the wording that comes from the theme itself — button labels, cart messages, form notices — and add translations for the languages your store sells in.

Every storefront has text that no one typed into a product or a page: **Add to cart**, **Sold out**, **Continue shopping**, the notice under a newsletter form. Those strings live inside the theme, and Shopify lets you change them without touching code — the catch is that there are two different screens for it, and picking the wrong one is the usual reason a translation does not show up.

## Languages included with the theme

Avante ships with five languages out of the box:

| Language          | Locale file       |
| ----------------- | ----------------- |
| English (default) | `en.default.json` |
| German            | `de.json`         |
| Spanish           | `es.json`         |
| French            | `fr.json`         |
| Italian           | `it.json`         |

Each one has a matching `.schema.json` file, which translates the labels you see **inside the theme editor** — not the storefront.

{% hint style="info" %}
Any other language works too. It just does not arrive pre-translated: you add the language in **Settings → Languages**, and then translate the theme strings yourself (or with Shopify's free AI translation in Translate & Adapt).
{% endhint %}

## Which screen to use

<table><thead><tr><th width="220">You want to change…</th><th>Go to</th></tr></thead><tbody><tr><td>Wording in your <strong>default</strong> language</td><td><strong>Online Store → Themes → … → Edit default theme content</strong></td></tr><tr><td>Wording in any <strong>other</strong> language you sell in</td><td>The <strong>Translate &#x26; Adapt</strong> app (Shopify, free)</td></tr></tbody></table>

This split is strict. Editing the German text in Translate & Adapt will never change the English one, and editing the default content will never fill in German.

## Change a theme string

{% stepper %}
{% step %}

### Find the exact wording

Open your storefront and copy the string as it appears, for example `Sold out`. Search is literal, so copy it character for character.
{% endstep %}

{% step %}

### Edit the default language first

Go to **Online Store → Themes**, open the **…** menu on your live theme and choose **Edit default theme content**. Use the search box, change the wording, save.
{% endstep %}

{% step %}

### Add the other languages

Open **Translate & Adapt**, pick the language, switch to the **Theme** tab and fill in the translation for the same string. Shopify can pre-fill it automatically, and you can correct anything that reads oddly.
{% endstep %}

{% step %}

### Check on the storefront

Switch the language on your live storefront, not in the theme editor preview, and reload the page.
{% endstep %}
{% endstepper %}

## Good to know

* Strings are grouped by where they appear — `products`, `cart`, `collections`, `customer`, `newsletter`, `blogs` and so on. If a string is hard to find by wording, look in the group that matches the page it is on.
* Some wording comes from **apps**, not from the theme. App text is translated inside that app (or in the **Apps** tab of Translate & Adapt), and will not appear in the theme content editor.
* Product titles, descriptions, collection names, page content and navigation are **store content**, not theme strings. They are translated in Translate & Adapt under their own tabs.

## Why a string shows as “Translation missing”

A literal `Translation missing` label, or a raw key like `products.product.add_to_cart`, means Shopify could not resolve that string for the language being displayed. The usual causes:

{% hint style="warning" %}

* **The language has no value for that string.** Most common on a secondary language that was added, but never translated. Fill it in via Translate & Adapt.
* **The wrong layer was edited.** The default content was changed while the storefront was displaying another language, or the other way around.
* **The string belongs to custom code.** A snippet added by an agency or an app can call a translation key that does not exist in the theme at all. That key has to be added to the code — or the code changed to output plain text.
* **The theme was updated and old customizations stayed behind.** A custom template or section still calling a key from an earlier version will not find it.
  {% endhint %}

## Related

* [RTL support — Right-to-left languages in Avante](https://staylime.com/docs/avante-themes/features-and-advanced-setup/rtl-support.md) — selling in Arabic, Hebrew or another right-to-left language.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/avante-themes/features-and-advanced-setup/theme-string-translations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
