> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/add-ons/localization.md).

# Localization

## Platform Localization Add-On

This Add-On allows you to translate your IoT app, console and all of the transactional emails to additional languages. Anything can be localized - from system messages to widget and datastream names.

{% hint style="info" %}
One language per add-on, multiple add-ons possible.
{% endhint %}

The process is the following:

1. We share with you a file containing all of the texts present in your mobile app, Console and transactional emails
2. You provide us with a copy translated into your language of choice
3. Your Blynk launch engineer implements the translations
4. The language is than adjusted based on your user’s phone settings, if the corresponding translation is available.

{% hint style="info" %}
The add-on is available to Enterprise plan subscribers only. Contact your launch engineer to unlock and set up.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.blynk.io/en/add-ons/localization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.