---
title: PingOne Localization
description: These PingOne services use or support language localization:
component: pingone-api
page_id: pingone-api:platform:reference/localization
canonical_url: https://developer.pingidentity.com/pingone-api/platform/reference/localization.html
section_ids:
  browser-settings-and-localization: Browser settings and localization
  davinci-flows-and-localization: DaVinci flows and localization
---

# PingOne Localization

These PingOne services use or support language localization:

* [Agreements](localization/agreements.html)

  * The agreements service uses a `locale` property on agreement language resources to identify an enabled language in which content can be presented to end users.

  * Agreement languages must be enabled through the PingOne language management service.

* [Forms](localization/forms.html)

  * The forms service uses a `languageBundle` property that provides a map of i18n keys to their translations.

  * Language support associated with the language bundle must be enabled through the PingOne language management service.

* [Language Management](localization/languages.html)

  * An environment default language must be specified and enabled.

  * Languages that support localization of PingOne agreements, forms, and notifications content must be enabled.

* [Notifications](localization/notifications.html)

  * Notifications template resources use a `locale` property to identify an enabled language in which notification content can be presented to end users.

  * Notifications languages must be enabled through the PingOne language management service.

* [Users](localization/users.html)

  * Users resources use a `locale` property to localize such items as currency, date time format, or numerical representations.

  * Users resources use a `preferredLanguage` property to specify an end user's preferred written or spoken language. This property can be a factor in determining the language shown to end users for agreement and notification content.

## Browser settings and localization

The following PingOne services use the end user's browser settings as a factor to determine which language to present to users.

* The Forms service translates i18n keys based on the end user's browser settings for preferred languages. For more information, refer to [Localization of forms](localization/forms.html).

* The Agreements service uses the browser's `locale` setting as a factor to present localized content to users. For information about the conditions needed to use the browser's settings, refer to [Localization of agreements](localization/agreements.html).

* PingOne sign-on screens, the PingOne self-service app, and the PingOne app portal also use the end user's browser settings to determine the language to present at runtime.

## DaVinci flows and localization

DaVinci flows use the PingOne forms service to create the sign-on screens presented to end users. These screens follow the same localization runtime logic described in the forms service. For detailed information about DaVinci flows and language support, refer to [Localizing flows with PingOne](https://docs.pingidentity.com/davinci/use_cases/davinci_use_cases_localizing_flows.html).