Skip navigation

Localization in Kontent

Localization lets project managers set up additional languages for a project so that content contributors can create multilingual content items.

Table of contents

    Project localization

    To manage language variants available in your project:

    1. From the app menu, choose .
    2. Under Project settings, choose Localization.
    Screenshot showing where to find localization settings.

    Each of your projects has a default language that you can't delete. We recommend that you rename the default language and give it a more descriptive name that reflects the actual language of your existing content.

    Supported features

    Kentico Kontent currently supports localization of content items and asset descriptions. Check out our RoadmapOpens in a new window and let us know if you'd like to see something that we don't have immediate plans for.

    Understanding language fallbacks

    A fallback language is the language used when requested content items don't exist in the specified language. Every language in your project has a fallback language with the exception of the default language.

    For example, when you request a Spanish version of a content item that isn't translated into Spanish, the Delivery API checks whether the content item is translated into the fallback language of Spanish. Learn more about getting localized content and ignoring language fallbacks.

    Consider the following when setting up fallback languages for your projects:

    • You can create fallback chains. For example, fr-CH (Swiss French) with a fallback to fr-FR (French French) and fr-FR with a fallback to a default language is a valid scenario.
    • Your fallback chains can contain cycles. For example, when fr-CH (Swiss French) fallbacks to fr-BE (Belgian French) and fr-BE fallbacks to fr-CH. If no content is present in any of the language variants specified in the fallback chain, the Delivery API returns content in the default language.
    • The Delivery API will use the fallback language only if the requested language variant is not present in the content item.
    • Every language must have a fallback language.

    Exceptions to language fallbacks

    When the Delivery API evaluates language fallbacks for content items, it makes exceptions in the following cases:

    • Links to content items in Rich text elements follow language fallbacks independently.
    • Content items used in Rich text and Linked items elements do NOT follow language fallbacks. This means that whenever linked items are not translated to the requested language, they are not included in the response.

    To retrieve content items in a specific language only, see ignoring language fallbacks.

    What's next?