> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/help-and-faqs/how-to-translate-a-theme-after-adding-a-new-default-language.md).

# How to translate a theme after adding a new default language?

### What you are seeing <a href="#what-you-are-seeing" id="what-you-are-seeing"></a>

You added a new language in your Shopify admin and set it as the default one, but your storefront is still in the old language. Buttons, labels and menus have not changed, and running an auto translation does nothing.

### Why it happens <a href="#why-it-happens" id="why-it-happens"></a>

* **The language you want translated is the default one.** The **Translate & Adapt** app by Shopify does not translate the language that is currently set as default, because it treats it as the source, not the target. This is the usual cause.
* **The translation app is not installed yet.** Adding a language in **Settings > Languages** publishes it, but nothing translates the theme text automatically.
* **The theme text was never translated, only the products were.** Product titles and descriptions are separate content from theme text such as *Add to cart* or *Search*.

The fix is to move the default temporarily to another language, translate the one you want, then set it back as default.

### Step 1: Set a different language as default <a href="#step-1-set-another-default" id="step-1-set-another-default"></a>

{% hint style="success" %}
**Steps:**

1. Install the [Translate & Adapt](https://apps.shopify.com/translate-and-adapt) app by Shopify.
2. Go to **Settings > Languages**.
3. Click **Change default** and pick any other language as the default.
   {% endhint %}

*Result:* the language you want to translate is no longer the default, so the app can now treat it as a target.

{% hint style="info" %}
Changing the default removes your previous language entry from the list. Add the language you want to translate back in **Settings > Languages** and publish it before you continue.
{% endhint %}

<figure><img src="/files/9rMFJokGbYSroIPuxKqw" alt=""><figcaption></figcaption></figure>

### Step 2: Auto translate with Translate & Adapt <a href="#step-2-auto-translate" id="step-2-auto-translate"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Apps** in your Shopify admin and open **Translate & Adapt**.
2. Select the language you want to translate.
3. Click **Auto-translate**.
   {% endhint %}

*Result:* the app fills in the theme text for that language. Larger stores can take several minutes.

<figure><img src="/files/dngSRyTapCsinu5ZNR3M" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/R0x2YPLi8X0nbdN33QMk" alt=""><figcaption></figcaption></figure>

### Step 3: Set the translated language back as default <a href="#step-3-restore-default" id="step-3-restore-default"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Settings > Languages**.
2. Click **Change default**.
3. Select the language you have just translated and save.
   {% endhint %}

*Result:* your storefront now opens in the translated language for every visitor who is not routed to another market.

{% hint style="info" %}
Shopify shows a warning at this point about changing the default language. It is expected here, because you are switching back on purpose. Save your change.
{% endhint %}

<figure><img src="/files/PSQrKtxpFNvezdNlabzm" alt=""><figcaption></figcaption></figure>

### When to contact support <a href="#when-to-contact-support" id="when-to-contact-support"></a>

Contact support if some theme text stays in the old language after a successful auto translation, or if a translated string breaks the layout (text overflowing a button, for example). Translation quality itself is handled by Shopify, not by the theme.

Send this with your first message:

* Your store URL, and the URL of a page where you can see the untranslated text.
* Which language pair is involved, and which language is currently the default.
* A screenshot with the untranslated text circled.
* Theme name and version: **Vélare 1.0.0**, shown under the theme name in **Online Store > Themes**.
* A [staff account](/velare/help-and-faqs/staff-account.md) for the support team if they need to look at the theme content themselves.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Theme translation](/velare/help-and-faqs/theme-translation.md): translating into one language, or selling in several at once
* [Change currency](/velare/help-and-faqs/change-currency.md): the currency side of selling to more than one country
* [Staff account](/velare/help-and-faqs/staff-account.md): how to give the support team access to your store


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://uxsmart.gitbook.io/velare/help-and-faqs/how-to-translate-a-theme-after-adding-a-new-default-language.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
