---
title: Localize hosted pages
description: PingOne Advanced Identity Cloud lets you localize hosted pages to support the different languages of your end users. Use ISO-639-1 language codes (for example fr and de) to provide locale specific content in as many locales as you need.
component: pingoneaic
page_id: pingoneaic:end-user:hosted-pages-localize
canonical_url: https://docs.pingidentity.com/pingoneaic/end-user/hosted-pages-localize.html
keywords: ["User Interface", "REST API", "Localization", "Translation", "Authentication"]
page_aliases: ["developer-docs:localizing-enduser-login-uis.adoc", "uis:localize-enduser-login-uis.adoc", "end-user:localize-enduser-login-uis.adoc", "end-user:localize-login-enduser-pages.adoc"]
section_ids:
  localize-at-feature-level: Localize at feature level
  localize-related-features: Localize related features
  localize-journey-authentication-nodes: Localize journey authentication nodes
  localize-at-ui-level: Localize at UI level
  specify-preferred-language-journeys: Specify a preferred language for journey pages
---

# Localize hosted pages

PingOne Advanced Identity Cloud lets you localize hosted pages to support the different languages of your end users. Use [ISO-639-1 language codes](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) (for example `fr` and `de`) to provide locale specific content in as many locales as you need.

## Localize at feature level

### Localize related features

You can localize the following features related to hosted journey and account pages:

| Feature              | Description                                                                                                                                                                                                        |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Hosted pages         | Learn more in [Localize headers and footers](hosted-pages-customize.html#localize-headers-and-footers) and [Localize the favicon and theme logo](hosted-pages-customize.html#localize-the-favicon-and-theme-logo). |
| Security questions   | Learn more in [Security questions](../self-service/self-registration.html#security-questions).                                                                                                                     |
| Terms and conditions | Learn more in [Terms and conditions](../self-service/self-registration.html#terms-conditions).                                                                                                                     |
| Email templates      | Learn more in [Email templates](../tenants/email-templates.html).                                                                                                                                                  |

### Localize journey authentication nodes

You can individually localize authentication nodes that display content in hosted journey pages. For example, the [Page node](https://docs.pingidentity.com/auth-node-ref/latest/page.html) lets you add content to the Page Header property to display an initial journey message to end users. You can define as many localized versions of the message as you need:

![ui journeys page node page header modal](../tenants/_images/ui-journeys-page-node-page-header-modal.png)

## Localize at UI level

You can localize static content and server messages in the hosted pages using translation configuration. Learn more in [Localize tenant admin console and hosted pages](../tenants/tenant-localize.html).

## Specify a preferred language for journey pages

By default, Advanced Identity Cloud localizes the content of journey pages using the value of the `Accept-Language` header, which is typically derived from the language settings in the end-user's browser. You can override this behavior by appending a `locale` query parameter to the journey URL.

For example, to set the language to French, append `locale=fr` to the journey URL:

```bash
https://<tenant-env-fqdn>/am/XUI/?realm=/alpha&locale=fr&authIndexType=service&authIndexValue=Login
```

The language used to localize journey pages is determined in the following order of priority:

1. The `locale` query parameter in the journey URL (for example, `&locale=fr`).

2. The language preference set in the end-user's browser.

3. The default locale for hosted pages (`en`), used when neither a query parameter nor a browser language is provided.