# Internationalization > Source: https://docs.strapi.io/cms/features/internationalization Internationalization manages content in multiple locales directly from the admin panel. This documentation explains how to add locales, translate entries, and control locale-specific permissions. The Internationalization feature allows to manage content in different languages, called "locales". **Plan** Free feature **Role & permission** None **Activation** Available but disabled by default **Environment** Available in both Development & Production environment ## Configuration Before being usable in the Content Manager, the Internationalization feature must be configured from *Settings*, and it should be enabled on your content types from the _Content-type Builder_. ### Content-type Builder **Path to configure the feature:** _Content-type Builder_ For your content types to be translatable with Internationalization in the Content Manager, the feature must be enabled through the Content-type Builder. Internationalization can be configured for each content type and/or field. 1. Either edit the already created content type/field of your choice, or create a new content type/field. 2. Go to the **Advanced settings** tab. 3. Tick the option named "Internationalization" at content-type level, and "Enable localization for this field" at field level. ### Settings **Path to configure the feature:** *Settings > Global Settings > Internationalization* The *Internationalization* interface displays a table listing all locales available for the Strapi application. By default, only the English locale is configured and set as the default locale. For each locale, the table displays the default ISO code of the locale, its optional display name and indicates if the locale is set as the default one. From the table, administrators can also: - Click on the edit button to edit a locale - Click on the delete button to delete a locale #### Adding a new locale Administrators can add and manage as many locales as they want. There can however only be one locale set as the default one for the whole Strapi application. :::note It is not possible to create custom locales. Locales can only be created based on [the 500+ pre-created list of locales](https://github.com/strapi/strapi/blob/main/packages/plugins/i18n/server/src/constants/iso-locales.json) set by Strapi. ::: 1. Click on the **Add new locale** button. 2. In the locale addition window, choose your new locale among the *Locales* drop-down list. The latter lists alphabetically all locales, displayed as their ISO code, that can be added to your Strapi application. 3. (optional) In the *Locale display name* textbox, write a new display name for your new locale. 4. (optional) In the Advanced settings tab, tick the *Set as default locale* setting to make your new locale the default one for your Strapi application. 5. Click on the **Save** button to confirm the addition of your new locale. #### Enabling AI-powered internationalization AI-Powered Internationalization enables automatic translations for all the locales in a project when the content in the default locale is updated. This enables content editors to have their content translated into multiple languages within a few seconds. AI-powered Internationalization is disabled by default. To enable it, go to *Settings > Global Settings > Internationalization* and set _AI Translations_ to _Enabled_. ### Code-based configuration A `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE` [environment variable](/cms/configurations/environment#strapi) can be configured to set the default locale for your environment. The value used for this variable should be an ISO country code from [the 500+ pre-created list of locales](https://github.com/strapi/strapi/blob/main/packages/plugins/i18n/server/src/constants/iso-locales.json). ## Usage **Path to use the feature:** Content Manager, edit view of your content type In the [Content Manager](/cms/features/content-manager), when the Internationalization feature is enabled for the content-type, a locale drop-down list is added to the top right of the edit view and allows to switch locales. :::info The selected locale persists when navigating between content types. For instance, if you select the Spanish locale while editing a content-type, switching to another content type will keep the Spanish locale selected, even if that content type does not have Internationalization enabled. This makes it easier to work in a specific locale across your content. ::: The Internationalization feature also allows dynamic zones and components to differ from one locale to another. Depending on the locale, dynamic zones can indeed have different structures depending on the locale, and repeatable components can have different entries and be organized differently as well. :::caution Content can only be managed one locale at the time. It is not possible to edit or publish content for several locales at the same time (e.g. Clicking on the **Publish** button will only publish the content for the locale you are currently working on). ::: To translate content in another locale: 1. On the top right of the edit view, click on the locale drop-down list. 2. Choose the locale in which you want to translate your content. 3. Translate your content by filling up your content-type's fields. :::tip Click on the *Fill in from another locale* button, in the top right corner, for all fields (including relations) to be filled up with the values of another chosen locale. It can be useful if you do not remember what was the exact content in another locale. This button is not visible if you've enabled [AI-powered internationalization](#ai-powered-internationalization) since translations are automatically handled by Strapi AI. The latest version of the source document is retrieved by this feature. For localizable relations, Strapi automatically fetch the corresponding entry in the target locale if it exists. If the target locale does not exist for that relation, it will not be filled in. For non-localizable relations, the exact same entry is used. ::: ### AI-powered internationalization [When enabled](#enabling-ai-powered-internationalization), AI-powered internationalization enables automatic translations for all the locales in a project when the source content is updated. This enables content editors to have their content translated into multiple languages within a few seconds. The idea behind the feature is to ensure users only manually fill in content in the default locale, and Strapi AI translates it for all other existing locales. Once enabled, whenever you edit a content-type in the default locale and click **Save**, all other locales for the content-type should be translated automatically, which will be confirmed by an _All locales have been translated_ notification. Using this feature consumes Strapi AI credits. :::caution AI-powered internationalization only works one way, keeping the default locale content as the unique source of truth. Consequently, once the feature is enabled: - Editing and saving content for any locale other than the default one will not trigger automatic translations. - When editing the content for the default locale, the manual modifications made to other locales will be overwritten. ::: :::note Strapi AI credits Strapi AI includes 1,000 credits per month on the plan, and 10 free credits during the free trial. Strapi AI is not available on Enterprise plans. Lightweight actions use fewer credits, while more complex ones use more. You can check your credit usage in the [Settings Overview](http://localhost:1337/admin/settings/application-infos) of the admin panel. Notifications are sent when your usage reaches 80%, 90%, and 100% of your monthly allowance. Overages apply. Credits are shared across all users within the same project instance. When your credits run out, you can keep using Strapi AI, with overages billed monthly. For more information about Strapi AI, please refer to the [dedicated support article](https://support.strapi.io/articles/1821143913-understanding-strapi-ai). ::: ### Usage with APIs Localized content can be requested, created, updated, and deleted for a given locale through the various front-end APIs accessible from [Strapi's Content API](/cms/api/content-api): - [REST API](/cms/api/rest/locale): Learn how to use the locale parameter with the REST API. - [GraphQL API](/cms/api/graphql#locale): Learn how to use the locale parameter with GraphQL API. On the back-end server of Strapi, the Document Service API can also be used to interact with localized content: - [Document Service API](/cms/api/document-service/locale): Learn how to use the locale parameter with the Document Service API.