> For the complete documentation index, see [llms.txt](https://help.reasy.ai/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.reasy.ai/help/getting-started/engines/languages.md).

# Languages

#### What is localization? <a href="#what-is-localization" id="what-is-localization"></a>

**Localization** is adapting your app to a specific region. It helps you to translate your app content to other languages. Making your app regionally relevant puts it in reach of a worldwide audience. Reasy supports almost all the languages across the globe.

#### When to use it? <a href="#when-to-use-it" id="when-to-use-it"></a>

Localize when you want to target the global audience with your app. Localizing your app content makes it more appealing to your audience, which as a result, makes them likely to give a try and buy it.

The **Localization** engine in Reasy lets you translate every character your users see on your app’s interface. To provide you with automatic language translations, Reasy has two inbuilt translators – “Yandtran” and “Google”.


---

# 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://help.reasy.ai/help/getting-started/engines/languages.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.