> For the complete documentation index, see [llms.txt](https://docs.scaleflex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleflex.com/portals/portal-settings/translations.md).

# Translations

Translate a Portal's texts, and choose which languages visitors can see.

A Portal is written in its primary language. The **Translations** page is where you add more languages, translate the texts into them, and decide when each one goes in front of visitors.

Open it from the Portal's settings, or from the language menu in the builder's top bar — **Translations**, below the list of languages, where each language also shows how far it is translated. It is open to the project's administrators.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FzJgY6OqNZO4qzAgJeUfT%2Ftranslations-builder-language-menu.png?alt=media" alt="" width="336"><figcaption><p>The builder's language menu: how far each language is translated, and <strong>Translations</strong> at the bottom.</p></figcaption></figure>

{% hint style="info" %}
Translation statuses, the translations sheet, AI translation and CSV import and export are on Portals created since translation tracking arrived. On an older Portal the page lists its languages, and you can add, hide and delete them — the texts are translated in the builder, one language at a time.
{% endhint %}

## Languages

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FmNAnKYt5b0sVi1cVEjms%2Ftranslations-languages.png?alt=media" alt=""><figcaption><p>The Translations page: three live languages, and Greek still hidden with one text left to translate.</p></figcaption></figure>

| Column         | What it shows                                                                                                                       |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Language**   | The language. The Portal's own language is marked **Primary**.                                                                      |
| **Translated** | How much is translated, and what is left: texts **missing**, texts whose **source changed**, and translations that **need review**. |
| **Visibility** | **Live** or **Hidden**. The primary language is **Always live**.                                                                    |

**Add language** adds one or several at once. **New languages start hidden from visitors**, so you can translate before anyone sees a half-done version.

Showing a hidden language asks first, and tells you how far it is translated — wherever a text is missing, visitors see the primary language instead. Hiding is immediate. Each language's menu has **Export** and **Delete**.

## Keep translations up to date

With **Keep translations up to date** on, missing, new and changed texts are translated automatically into the live languages. Only the project's administrators can change it.

If the project's AI budget runs out, or the translation service fails, it stops and says so on the page. Whatever was translated so far is kept.

## Translating in the sheet

The pencil on a language — **Edit translations** — opens the sheet: one row per text, the primary-language source on the left, and a column per language. The language picker beside the filters chooses which columns are shown.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FUKhmr6icM8fcMXBX4ThJ%2Ftranslations-sheet-two-languages.png?alt=media" alt=""><figcaption><p>The translations sheet with Greek and German side by side: Greek translations are by AI and wait for review, German ones are translated.</p></figcaption></figure>

Narrow it down with **Search texts**, the page picker — **All pages**, **Custom pages**, **System pages**, **Datasets** — and the status filter, which reads **Any status** until you pick one.

Click a cell to type a translation. A formatted text opens in its own editor, and **Open side by side** puts the source next to it. **Open in the builder** and **Open the dataset** take you to where the text lives.

| Status                    | Means                                                                    |
| ------------------------- | ------------------------------------------------------------------------ |
| **Missing**               | Not translated yet. Visitors see the primary language.                   |
| **Translated**            | Done.                                                                    |
| **Needs review**          | Translated by AI. Visitors already see it; click its icon to approve it. |
| **Source changed**        | The primary text was edited after this translation was made.             |
| **No translation needed** | Stays as it is in every language — a brand name, an email address.       |

Tick rows to act on several at once: **Translate with AI**, **Mark as reviewed**, **Mark as needing translation**, or **Mark as “no translation needed”**.

## Translating with AI

**Translate missing texts** at the top of the page translates into every language at once. **Translate with AI** on a language, or **Translate all with AI** in the sheet, translates into fewer.

AI translations arrive as **Needs review**, so you can check them before or after visitors do. Only the project's administrators can run AI translation.

## Translating outside the Portal

**Export to CSV**, in the **…** menu at the top of the sheet, downloads the texts, filtered by language, pages and status. It opens in Excel, Google Sheets or Numbers. Fill in the translation column only, then bring the same file back with **Import CSV**, in the same menu.

The import tells you what it saved and what it skipped, and why — for example rows edited in the Portal since the export, rows in the primary language, and formatted texts, which are translated in the sheet instead.

## When visitors see a translation

* **Page texts** are saved to the page drafts and reach visitors with the next [publish](https://docs.scaleflex.com/portals/publishing-a-portal.md). Translations on pages other than the one you publish from go out only when you select **Other pages**.
* **Dataset values** are live straight away.
* **Showing a language** is live straight away, but its page translations still wait for the publish.

If a visible language is not fully translated, or AI translations are waiting for review, the top of the publish dialog says **Translations need attention.** Hover it for the counts, or use **Go to translations** to fix them first. It never stops you from publishing.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2Fik8Mlnmc2DncWTLS4Ls0%2FScreenshot%202026-11-11%20115138.png?alt=media&amp;token=f928e645-9fa5-4a6f-87ae-e797d2729478" alt="The publish dialog with the Translations need attention warning and the Go to translations link" width="375"><figcaption><p>The publish dialog: the translations warning at the top.</p></figcaption></figure>

## Related

* [General](https://docs.scaleflex.com/portals/portal-settings/general.md) — the primary language.
* [Fields](https://docs.scaleflex.com/portals/portal-settings/datasets/fields.md) — which dataset fields are translatable.
* [Navigating a Portal](https://docs.scaleflex.com/portals/viewing-a-portal/navigating-a-portal.md) — the language switcher visitors use.
