# Internationalization (i18n)  is now part of the strapi core

> Source: https://docs.strapi.io/cms/migration/v4-to-v5/breaking-changes/i18n-content-manager-locale

Internationalization (i18n) is now part of Strapi core instead of a plugin. The locale parameter sent to Content Manager changes from `plugins[i18n][locale]` in v4 to `locale` in v5.

Internationalization (i18n) is now part of the Strapi core and no longer a plugin, and this impacts how some parameters are sent and accessed. This also means you should not use or depend on the old `@strapi/plugin-i18n` package in your project, it is now natively included.

This page is part of the [breaking changes database](/cms/migration/v4-to-v5/breaking-changes) and provides information about the breaking change and additional instructions to migrate from Strapi v4 to Strapi 5.

- Is this breaking change affecting plugins? Yes
- Is this breaking change automatically handled by a codemod? Yes
  - Codemod: [dependency-remove-strapi-plugin-i18n](https://github.com/strapi/strapi/blob/develop/packages/utils/upgrade/resources/codemods/5.0.0/dependency-remove-strapi-plugin-i18n.json.ts)

## Breaking change description

**In Strapi v4**

Content Manager sends the following parameter when accessing a locale: `plugins[i18n][locale]`.

**In Strapi 5**

The parameter sent to the Content Manager is now just `locale`.