> For the complete documentation index, see [llms.txt](https://evidano.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://evidano.gitbook.io/ailyze-docs/common-research-workflows/analyze-multilingual-data.md).

# Analyze Multilingual Data

Analyze interviews and surveys in any language, and get your themes, quotes, and report in the language you need.

This page shows you how to analyze research that isn't in English, or that mixes several languages, and still get a clear report in the language you want.

At the end you will have a themed report in the language you choose, with quotes you can trace back to the original wording.

## Before you start

* Interviews, survey responses, or recordings in any supported language; see [Supported Languages](/ailyze-docs/reference/supported-languages.md).
* The Free plan works for analysis. Translation and transcription are pay-as-you-go add-ons with free allowances; see [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).

Evidano handles multilingual research in two ways. Pick the one that fits.

## Option A: Analyze directly and set the response language

For document analysis, you usually don't need to translate first. On your account page, click **New document project**, then:

1. Upload your transcripts, in any supported language.
2. In the draft, under **You will receive a report**, set **Report in** to the language you want the *report* in.

Evidano reads the original text and writes the [themes](/ailyze-docs/reference/glossary.md#theme), summaries, and insights in your chosen language. Your [quotes](/ailyze-docs/reference/glossary.md#quote) usually stay in their original language, so your evidence keeps the original wording while your findings are easy to read.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-d76f7449dacf0c2dddce5d91edff0e3e3776bd43%2Fsettings-document-analysis-30-report.png?alt=media" alt="Report options in the document table builder, with the Report in select set to English"><figcaption><p>Badge 5 is Report in: it changes the language of the report, not of the quotes.</p></figcaption></figure>

## Option B: Translate first, then analyze

Choose this when you want the *underlying data* itself in one language, for example to merge interviews from several languages into a single [codebook](/ailyze-docs/reference/glossary.md#codebook), or to share the raw translated transcripts.

1. Use [Translate Files](/ailyze-docs/prepare-research-data/translate-files.md) to translate your documents or spreadsheets into a common language.
2. On the translation detail page, click **Analyze** to send the translated files straight into a new document or spreadsheet project.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2FUHd9Wx4M6RWQ9f6FNBPs%2FAnalyze%20Multilingual%20data%201.gif?alt=media&amp;token=82671bc6-c3f1-4416-82ed-a94a9295ecb2" alt="Sending translated files into analysis with the Analyze button"><figcaption><p>The Analyze button on a finished translation carries the translated files straight into analysis.</p></figcaption></figure>

## Which option should you choose?

| You want…                                                            | Use                                                                                      |
| -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| A report in language X from data in language Y, quotes kept original | **Option A** (response language)                                                         |
| All data unified into one language before coding                     | **Option B** (translate first)                                                           |
| To share translated source files with collaborators                  | **Option B**                                                                             |
| A survey with responses in many languages themed the same way        | **Option B**, then the spreadsheet analysis                                              |
| Audio or video in another language                                   | Transcribe first (pick the language, or auto-detect for mixed audio), then Option A or B |

## A realistic example

**Scenario:** 30 interviews across English, Spanish, and Portuguese. Translate them all to English (Option B), click **Analyze** to build one shared codebook, then compare themes by a Country segment, with original-language quotes available for checking.

## Next steps

* [Translate Files](/ailyze-docs/prepare-research-data/translate-files.md) — translate first when you want one language throughout.
* [How to read your results](/ailyze-docs/analyze-data/how-to-read-your-results.md) — where the response language shows up in the report.
* [Translation issues](/ailyze-docs/troubleshooting/translation-issues.md) — when a translation fails or looks wrong.