What Is the Localization Tab?
Localization is where you make an app available in multiple languages. Every app has a default language set when it is created. The Localization tab lets you add further languages and translate all of the app's text labels into them — button captions, field labels, headings, messages, and any other text your app surfaces to users.
When no languages have been added yet, the empty state reads "Translate your app" and invites you to make your app accessible worldwide with support for multiple languages. Once you add a language, a workspace opens with the locales and pages on the left and a translation table on the right.
Note: Open your app from the Applications manager and select the Localization tab in the app's tab bar.
Adding a Language
Click + Add next to Locales to expand the locales your app supports. On the empty screen, the button reads Add Language. Each added language becomes a locale you can switch to, preview, and edit independently.
Click + Add: Opens the Add Language dialog.
Select a language: Choose the target language from the Select Language dropdown. You can add as many languages as your audience needs.
(Optional) Enable Auto-translate: If your workspace has AI translation configured, toggle Auto-translate on — described as "AI-powered translation, instantly and effortlessly". The platform will translate all of the app's source labels into the selected language automatically.
Confirm: The language is added to the Localization workspace. It now appears in the locale dropdown alongside any other locales you've added.
The Translation Workspace
Once at least one language has been added, the Localization tab opens as a two-pane workspace:
Left side — under Locales, a dropdown picks the language you are translating. The default language is marked (Default), and the choice applies to all namespaces below it. Under Namespaces, choose Common or one of the app's pages to load its translation table.
Right pane — the translation table. The first column shows each label as it appears in the default language. When you select a locale other than the default, a column for that language holds the translations you type. Location shows where the label comes from on the page (the block and property, for example
typography3 / Value), and Device shows which device it belongs to.
Editing Translations Inline
Click any translation cell to edit it. Type the translated text directly into the cell and press Enter or click away to save. You can search the label list to find specific strings quickly.
Auto-Translating a Page
When Auto-translate is configured in your workspace, an Auto Translate button appears above the translation table whenever a non-default language is selected and you have edit access. Clicking it fills all empty translation cells for the current page with AI-generated translations. You will see the notification "Your app is being translated" while it processes, and a completion notification when it's done. Review the AI translations before publishing — they are a starting point, not a guarantee of accuracy.
Import and Export Labels
For large apps or teams that translate outside the platform (e.g. in a spreadsheet or with a professional translation service), use the bulk import and export features:
| Action | What it does |
| Export All Labels | Downloads all source labels and their existing translations for the selected locale in a structured file. Send to a translator or edit in bulk. |
| Import All Labels | Uploads a translated label file and populates the translation table. Existing translations are overwritten by the imported values. |
Import All Labels and Export All Labels are in the ⋯ menu above the translation table. They appear only when your administrator has set up label import and export, and importing also needs edit or Manage Localization access to the app.
Tip: Export all labels first, translate the file externally, then import. This is faster than editing cell by cell and ensures translators work in a familiar format (e.g. a spreadsheet) without needing platform access.
How Repeated Labels Are Handled
The same source text often appears in multiple places — the same button label on several pages, the same status message across different screens. When you translate one occurrence, the platform asks how to apply it and remembers your choice. When a non-default language is selected and you have edit access, you can change the choice later: click the Auto-apply button above the translation table. It shows the current choice, for example Auto-apply · Ask me each time. The options are:
| Option | Behavior | When to use |
| Ask me each time | Prompts for a propagation choice every time a match is detected. | When you want full control over every occurrence. |
| Auto-apply across pages | "Every matching label syncs" — the translation is applied wherever the same source text appears, across all pages. | For globally consistent terms like "Submit", "Cancel", "Save". |
| Auto-apply on this page | "Same page only" — applies to all matching labels on the current page only. | When the same word means different things on different pages and you only want page-level consistency. |
| Edit each cell manually | "No propagation" — each occurrence is edited independently. | When every occurrence must be individually crafted (e.g. context-dependent phrasing). |
For a value used in many cells, you can also make a one-time per-instance choice:
Apply across all pages — propagates this specific translation everywhere immediately.
Only on this page — applies to matching labels on this page only.
Translate each cell separately — leaves other occurrences untouched.
Example — Translating "Submit" consistently
Your app uses "Submit" on 12 different forms. You translate it to French as "Envoyer". When the propagation dialog appears, choose Apply across all pages. All 12 occurrences are translated at once — no need to touch each form individually.
If one form uses "Submit" in the sense of "submit a request", first set Auto-apply to Edit each cell manually, then edit that cell. While Auto-apply across pages is on, editing one cell also updates every matching cell that still holds the old translation. To reverse that, click Undo on the bar that appears after the edit.
Locale Switching at Runtime
Users of the published app can switch the display language using a language switcher you add to the app's navigation. Supported languages are the ones you add in this tab; the default language is shown as (Default) in the locale list. Add the language switcher as a navigation item in Builder Settings → Development → Navigation so users can change their preferred locale from within the app. You can also add it to the user menu. See Navigation Overview.
Ignore browser language
By default, visitors to public apps (and to the public pages of a private app) see the app in their browser language when it is one of your supported languages. Turn on Ignore browser language in the Localization tab's left nav to always open these pages in the default language instead. Signed-in users are not affected.
The Common Label Set
The Common set in the locale's left nav contains labels that are not specific to a single page — shared messages, generic actions, and platform-level text that appears across the whole app. Translate Common labels to ensure they are consistently localized everywhere, not just on individual pages.
Tips and Best Practices
Enable localization before launch
Add your target languages and create initial translations before publishing. Enabling localization after launch means your app has been live in a single language — users who preferred another locale were not served.
Always review auto-translated content
AI translation is fast but not perfect for specialized vocabulary, product names, or legal language. After auto-translating, review key screens — especially those involving pricing, instructions, or compliance terms.
Set a propagation preference early
If your app has many shared terms, click the Auto-apply button above the translation table and choose Auto-apply across pages before starting translation work. This saves significant time and ensures consistency across a large label set.
Note: Auto-translate requires workspace-level AI translation to be configured by an administrator. If the Auto-translate toggle is absent or disabled, contact your workspace admin to enable it.
Related Pages
Navigation Overview — adding a language switcher to your app's menu.
App Settings & Privacy — configuring your app's general settings.