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

# Languages

{% hint style="info" %}
By default, the interface language matches your **Spoken language**, or you can set your **Interface language** independently in **Settings → Look & Feel**.
{% endhint %}

We currently support the following spoken recognition and interface languages:

* English
* French
* Spanish
* German
* Italian
* Ukrainian
* Portuguese
* Indonesian
* Polish
* Arabic
* Mandarin Simplified / Traditional Chinese

To set your **Spoken language**, **Dialect**, or **Interface language** manually, you can do so by accessing the [Settings page](/settings/changing-settings.md).

{% hint style="success" %}
**Looking to translate your live captions into another language?**

Zip Captions supports real-time, on-device translation into 17 target languages! Check out our [**Live Translation guide**](/translation/introducing-live-translation.md) to learn how to set it up.
{% endhint %}

If you would like to see additional languages added you can [create community translations via GitHub](https://github.com/jptrsn/zip-captions?tab=readme-ov-file#languages)


---

# 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://help.zipcaptions.app/settings/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.