---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Language internationalization support

# Language internationalization support {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The ServiceNow platform supports multiple languages.

Language support is available when at least one language plugin has been activated, as
described in [Activate a language](https://servicenow-prod.fluidtopics.net/JVX9OJGGemU7rGe1QNjBRw "By default, the language supported by the platform is American English. You can activate plugins for other supported languages if you have the admin role.").

When a user logs in, the language for the instance session is determined by the following
logic:

1. If the language selection at login is enabled, that language is used.
2. If not, the language preference selected using the language picker in the header bar is used.
3. If not, the language setting in the User \[sys_user\] table is used.
4. If none of the above are true, the system default language is used.

{#c_LangInternationalizationSupport__ol_k3c_td3_fr}

You can also enable a fallback language to use if a translation isn't available in the preferred language, as described in [Set a fallback language](https://servicenow-prod.fluidtopics.net/POLFU3TS7H6L913zN~SzJg "Set a fallback language to be used when user interface text is not translated in the user's preferred language to accommodate the language needs of your users.").  
Some parts of the system aren't translated and remain in the language used to create them:

* Journal fields
* Report titles
* Any field that stores free-form text
{#c_LangInternationalizationSupport__ul_hjh_bk2_mnb}

Additionally, plugin names and spoke names aren't translated. The English version of plugins and spoke names is always kept, even when they're used in other contexts. Feature names are translated, however.

Beginning in the Washington DC release, new product and application names are localized in all supported languages. Existing product and application names are being localized incrementally.  
{#c_LangInternationalizationSupport__table_o1b_t23_fr__entry__2}

| Question | Answer |
|-|-|
| Will fields that I created or edited myself be translated? | The ServiceNow AI Platform does not perform translations. ServiceNow only provides translations of strings that the company itself has created. When you create a field, a message, or other textual UI content, translate this content manually. |
| I am not seeing journal fields translated. | Translation tables are not provided for user-defined string fields, such as short description, additional comments, and report titles. These fields can appear only in the language they were created in. |
[Table 1. FAQ]

{#c_LangInternationalizationSupport__table_o1b_t23_fr}
**Related concepts**   

* [Locating translatable UI strings](https://servicenow-prod.fluidtopics.net/FiWciIyq0d8JwqSnbSmTQw "Locate individual untranslated strings to provide your own translation of customer-created and customer-edited strings, such as field names and messages.")