> For the complete documentation index, see [llms.txt](https://docs.cstplus.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cstplus.org/documentation/feature-reference/interface-languages.md).

# Interface Languages

The admin panel is fully localised. You can run it in English, Ukrainian, Russian or Hindi, and every screen follows: navigation, buttons, field labels, hints, empty states, status messages and the CG Studio property panel.

***

### Changing the language

Go to **Settings > General** and pick a language under **Interface language**. The panel reloads in the chosen language. The setting is per browser, so different operators can use the panel in different languages on the same server.

| Code | Language   |
| ---- | ---------- |
| en   | English    |
| uk   | Українська |
| ru   | Русский    |
| hi   | हिन्दी     |

***

### What is translated

{% hint style="success" %}
Navigation, buttons, form labels, tooltips, empty states, toast notifications and the CG editor are translated in all four languages.
{% endhint %}

{% hint style="info" %}
Example values (sample URLs, file paths, `e.g.` samples) and technical codes (codec names, protocol names) are intentionally left as-is. If a phrase has no translation yet, it falls back to English and never breaks the layout.
{% endhint %}

***

### Notes

* The language applies to the **admin panel** only. Public watch pages are branded separately.
* Adding a translation is a matter of extending the dictionary; if you need another language, it can be added without a code change to any page.


---

# 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.cstplus.org/documentation/feature-reference/interface-languages.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.