> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/on-premises/configuration/overleaf-toolkit/localization.md).

# Localization

## i18n Languages

Both the Overleaf Community Edition and Server Pro have been translated into multiple languages.

The language can be set via `OVERLEAF_SITE_LANGUAGE` with one of the following options:

* `en` - English (default)
* `es` - Spanish
* `pt` - Portuguese
* `de` - German
* `fr` - French
* `cs` - Czech
* `nl` - Dutch
* `sv` - Swedish
* `it` - Italian
* `tr` - Turkish
* `zh-CN` - Chinese (simplified)
* `no` - Norwegian
* `da` - Danish
* `ru` - Russian
* `ko` - Korean
* `ja` - Japanese
* `pl` - Polish
* `fi` - Finnish

Some of these are more complete than others, we always endeavor to have all supported languages fully translated, if you would like to help with our translations please get in touch!

## Multi-language support

Overleaf can support multiple languages per container. This is done via different domains configured to respond in a set language using the environment variable `OVERLEAF_LANG_DOMAIN_MAPPING` with an escaped JSON string.

```
OVERLEAF_LANG_DOMAIN_MAPPING = '
    {
        "www": {
        "lngCode": "en",
        "url": "https:\/\/www.example.com"
        },
        "fr": {
        "lngCode": "fr",
        "url": "https:\/\/fr.example.com"
        },
        "de": {
        "lngCode": "de",
        "url": "https:\/\/de.example.com"
        },
        "sv": {
        "lngCode": "sv",
        "url": "https:\/\/sv.example.com"
        },
        "zh": {
        "lngCode": "zh-CN",
        "url": "https:\/\/zh.example.com"
        },
        "es": {
        "lngCode": "es",
        "url": "https:\/\/es.example.com"
        }
    }'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.overleaf.com/on-premises/configuration/overleaf-toolkit/localization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.