Localization

Atlas ships its hosted pages, components and messages in a set of built-in languages and picks the right one from the user's browser. When you need wording that's yours — a different translation, your product's terminology, or a language Atlas doesn't ship — you add a localization override.

How overrides work

A localization override is a per-locale set of strings that replaces the built-in text for that language. Atlas keeps the base template underneath, so:

• An override changes only the strings you provide; anything you don't override falls back to the built-in translation.

• You can toggle an override enabled/disabled without deleting it.

• Removing an override makes the base translation render again.

Overrides are validated like the base template — the same checks that protect the built-in strings apply, so a malformed placeholder or a missing required variable is caught at save time.

Add a localization

1. Open Customization → Localization.

2. Choose the locale (for example fr-FR).

3. Provide the strings you want to change. Unspecified strings keep the built-in translation.

4. Enable it and save.

What gets localized

• The hosted sign-in and account pages and SDK components.

• The email and SMS templates — pair localization with templates so a French user gets a French verification email as well as a French sign-in page.

Good practice

• Start by overriding only the strings that carry your product's voice; let Atlas's translations handle the rest.

• Keep placeholders ({{code}}, links) intact in every locale — the validator will stop you if you drop one.

• Localization is per-instance: finish it in Development, then reproduce it in Production.

Next

Lock the experience down → Security overview.