> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/platform/languages-and-localization.md).

# Languages & Localization

Using Pylon in different languages for both your team and your customers.

### Your Team

If your team operates across many different languages or English just is not your primary language, you can localize the entire Pylon app to a language of your choice!

You can find these settings on your [Profile](https://app.usepylon.com/settings/profile) page.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FkWfo7pSRvRI4YTygo1aN%2FCleanShot%202026-04-01%20at%2020.52.52.png?alt=media&amp;token=2adef1e1-0e07-4f33-8e28-440ee14782f4" alt=""><figcaption></figcaption></figure>

**Message Language**

If your customers reach out to you in different languages, Pylon can automatically translate those messages into the native language of your users. Your users can then reply in their native language and their response will be translated on-the-fly into the customer's language.

**App Language**

The inside of the Pylon app can be translated into a language of your choice (this can be a different language for different members of your team), allowing you to easily navigate and use the Pylon app.

Set it under **App language** on your Profile page. The app is available in English, Spanish, French, German, Italian, Japanese, Korean, and Brazilian Portuguese.

### Your Customers

Translate your [Knowledge Base](/pylon-docs/getting-started/pylonboarding/knowledge-base.md), [Customer Portal](/pylon-docs/customer-portal/overview.md), [Chat Widget](/pylon-docs/chat-widget/overview.md), and [Ticket Forms](/pylon-docs/support-workflows/ticket-forms.md) so your customers can receive support in any language.

Each modality supports translation - on the [Languages](https://app.usepylon.com/settings/languages?tab=supported-languages) page you can select which languages you want to support. In each of these interfaces your customer will have a language picker to select which language they would like to view content in, and wherever possible we'll default this to their preferred language (for example, their browser language or Pylon's own knowledge of their preferred language based on their past interactions).

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FgFaRBLPZJ9Qhoa9mycKA%2FCleanShot%202026-04-01%20at%2021.03.56.png?alt=media&amp;token=e95b3487-8f1c-4e6f-9458-fdc4101a9700" alt=""><figcaption></figcaption></figure>

From the [Custom Translations](https://app.usepylon.com/settings/languages?tab=custom-translations) tab you also have fined grained control of modifying specific translations in specific languages.

**Knowledge Base**

Within the knowledge base you also have fine grained control of article translations:

* **Auto-translate** articles into each supported language with AI, or turn it off to write and edit a translation by hand.
* When you edit an article, its auto-translated versions are marked **Has changes** and regenerated when you publish them. You can also **Regenerate translation** at any time.
* Publish all translations at once with **Publish translations** on the article list.
* Translate collection names and descriptions and the knowledge base header.
* Terms on the **Custom translations** tab are applied when Pylon translates your knowledge base, so you can control how product names and other terms are translated, or keep them untranslated.
* Each translated page gets its own URL (for example, `/fr/articles/...`) and appears in your sitemap. Visitors switch languages with the language picker. The knowledge base opens in your default language unless the URL specifies another; it doesn't use the visitor's browser language.

AI translation is part of Pylon's AI Assistant features and is available on select plans. You can support up to 20 languages besides your default; unlimited languages are available on the Enterprise plan.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FaU9IrLuqDv9uUD2kolNO%2Fimage.png?alt=media&amp;token=79789041-75e4-4f10-add4-493fb48df840" alt=""><figcaption></figcaption></figure>

For the full guide, see [Knowledge Base Translations](/pylon-docs/knowledge-base/translations.md).


---

# 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.usepylon.com/pylon-docs/platform/languages-and-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.