> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/native-integrations/overview-1/multi-language.md).

# Multi Language

Translate your app's native screens into your users' languages.

Multi Language translates the native parts of your app — navigation bar titles, onboarding slides, buttons, the no-internet screen — into the languages your customers speak.

## What it does and does not translate

**It translates what Twinr draws:** navigation titles, native screen elements, onboarding, system screens.

**It does not translate your website.** Your pages come from your own server, so they arrive in whatever language your site serves. **Localized URL** is how you connect the two.

## Turn it on

Open **Native Features → Multi Language** and switch it on.

<figure><img src="https://3731994945-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlBy5z08zL1UoCwNqmg%2Fuploads%2Fgit-blob-c1281b68013c53b5c42bf5ef7e34a414f319e27d%2Fnf-multi-language.png?alt=media" alt="The Multi Language screen"><figcaption></figcaption></figure>

| Setting              | What it does                                                                   |
| -------------------- | ------------------------------------------------------------------------------ |
| **Languages**        | Choose from 163.                                                               |
| **Default language** | What to show before a customer chooses. *System language* follows their phone. |
| **Localized URL**    | The address to load per language, per screen.                                  |

Click **Save as draft**.

{% hint style="info" %}
**Standard** plans may select **2** languages; **Premium** may select all **163**. During a free trial you can try them all — but if you then choose Standard, only your **first two** selections are kept and the rest are removed.
{% endhint %}

## Localized URL

If your site serves translated pages at their own addresses, enter them here per screen. When a customer switches to Arabic, the app reloads your screens at the `/ar` address you gave.

Without this, switching language translates the app's own furniture while your pages stay in their original language — which looks half-finished.

## Translations

The **Translation** tab is where the wording lives.

1. Click **Download** for a spreadsheet of every translatable string.
2. Fill in the translations. **Do not change the first column or the first row** — they identify the strings, and editing them breaks the upload.
3. Save, and upload the file back.
4. **Save as draft.**

{% hint style="info" %}
**Premium** translates automatically; you only edit what you want to reword. On **Standard** you supply the translations yourself.

Auto-translation works during a free trial, but moving to Standard afterwards removes the generated words — you will need to fill in the spreadsheet and re-upload.
{% endhint %}

{% hint style="warning" %}
Machine translation is a good start, not a finish. Have a native speaker read your product names and calls to action before you ship — those are the strings that cost you money when they are wrong.
{% endhint %}

## Letting customers switch

Add a **Multi Language** button to a screen's navigation bar so customers can change language themselves — see [Navigation Bar Buttons](https://help.twinr.dev/navigation-bar-buttons/navigation-bar-buttons.md). One per screen.

## Check it

{% hint style="warning" %}
**This cannot be tested in Twinr Preview.** Save, publish to production, take a build, and test it on a real device — an APK on Android, or TestFlight on iOS.
{% endhint %}
