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

# Supported Languages

This page gives an overview of the languages you can transcribe, translate, and analyze in. The exact lists live in the app's dropdowns.

## Transcription languages

* Choose your recording's language from the **Language of Audio** dropdown, grouped by accuracy: **Best**, **Better**, and **Good**.
* A **Multilingual** option handles recordings that contain **two or more languages**.
* Evidano warns you when a more accurate option exists for your choice.
* The full list is long and loads inside the app; search the dropdown to find yours (around 100 languages).

{% hint style="info" %}
**Tip:** Picking the most specific language or accent improves accuracy a lot. Add **Custom Vocabulary** for names and jargon. See [Transcribe audio and video](/ailyze-docs/prepare-research-data/transcribe-audio-and-video.md).
{% endhint %}

## Translation languages

* Pick your **Origin** (source) and **Destination** (target) languages in the translation setup.
* The full list loads inside the app. Which target languages you can choose can depend on your file format: some formats (`docx`, `pptx`, `xlsx`, `html`, `txt`) support every language, while others (`pdf`, `xliff`, `srt`) support only the higher-accuracy set. See [Supported File Types](/ailyze-docs/reference/supported-file-types.md).

## Analysis response language (documents)

In document analysis, **Optional Settings → "Specify your preferred language of response"** offers **100+ languages**. This sets the language of the **report** ([themes](/ailyze-docs/reference/glossary.md#theme), summaries, insights), separately from your data's language — so you can analyze data in one language and read the findings in another.

* Quotes are usually kept in their **original** language for accuracy.
* The default is **English**.

## Multilingual study and survey building

* **Create AI Avatar Interviewer + Survey** and **Create Survey** let you build in several languages, and can **auto-translate** survey content between the languages you add.

## Choosing a multilingual approach

| Situation                                    | Approach                                                         |
| -------------------------------------------- | ---------------------------------------------------------------- |
| Report in language X from data in language Y | Set the **response language** (documents)                        |
| Unify mixed-language data before coding      | **Translate first**, then analyze                                |
| Non-English audio                            | **Transcribe** (pick the language or Multilingual), then analyze |

## Next steps

* [Analyze multilingual data](/ailyze-docs/common-research-workflows/analyze-multilingual-data.md) — a full walkthrough for mixed-language projects.
* [Supported File Types](/ailyze-docs/reference/supported-file-types.md) — which formats work with which languages.
* [Transcribe audio and video](/ailyze-docs/prepare-research-data/transcribe-audio-and-video.md) — set the language for a recording.


---

# 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://ailyze.gitbook.io/ailyze-docs/reference/supported-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.