> 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/prepare-research-data/translate-files.md).
# Translate Files
This page shows you how to translate whole files — not just snippets — into another language, keeping their layout, tables, and slides intact.
For a quick first run, see [Translate your first document](/ailyze-docs/getting-started/translate-your-first-document.md). This page is the full reference.
{% hint style="info" %}
**What you need:** An Evidano account and the files you want to translate (up to 10 per project). Your first 1,000 words are free.
**What you will have at the end:** Your files translated into another language, in the same format, ready to download or analyze.
{% endhint %}
## Supported files
| Tier | Formats |
| ---------------------------------------- | ------------------------------------- |
| **All languages** (Good & Best accuracy) | `docx`, `pptx`, `xlsx`, `html`, `txt` |
| **Best-accuracy languages only** | `pdf`, `xliff`, `srt` |
* Up to **10 files** per project; each under **1,000,000 characters**.
* Your **first 1,000 words are free**.
{% hint style="info" %}
`pdf`, `xliff`, and `srt` only translate with **Best Accuracy** language pairs. If you pair one with a **Good Accuracy** language, Evidano asks you to remove or convert it.
{% endhint %}
## Step 1: Upload your files
From your account page, click **"Translate docx/pdf/xlsx/pptx/etc"**. Review the **Supported File Types** panel, then upload (or reuse) your files. The **"Configure Translation"** card appears once a file is selected.
## Step 2: Choose your languages
In the **"Configure Translation"** card, pick two languages:
* **"Origin"** — the current language of your files. You choose this yourself; it isn't auto-detected.
* **"Destination"** — the language to translate into.
Languages are grouped as **Best Accuracy** and **Good Accuracy**; search to find yours. For the full list, see [Supported languages](/ailyze-docs/reference/supported-languages.md).
### Optional Instructions
Open the **"Optional Instructions"** accordion to fine-tune the result:
* **Custom dictionary** — force specific translations for brand names, product names, or jargon (original word → translated word).
* **Formality** — choose Default, More Formal, Less Formal, Prefer More, or Prefer Less. Formality is available for some languages; see [Supported languages](/ailyze-docs/reference/supported-languages.md) for which.
## Step 3: Start the translation
Click **"Create Project"** (the button shows a cost if you go past the free word limit). Evidano confirms that you'll receive an email when the translation completes, and takes you to the **Document Translation** list.
{% hint style="info" %}
**Costs credits:** Beyond your free words, translation is a pay-as-you-go add-on drawn from your wallet, and you'll confirm any charge first. See [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).
{% endhint %}
## Step 4: Track progress
The **Document Translation** list shows a status for each project (In Progress, Translating, Completed, Downloaded, or Error) and the language pair. There's no live percentage — you'll get an email when it's done. Only **Completed** projects are clickable.
## Step 5: Download your files
When a project is **Completed**:
* **Single file:** click the row to download it right away.
* **Multiple files:** open the project and download files one by one, or select several and click **"Download Selected"** to get a ZIP.
Translated files keep the **same format** as the originals. (There's no in-app preview of the translated content.)
## Step 6: Send files to analysis
The project's detail page has an **"Analyze"** button that sends translated files straight into analysis:
* `docx` and `pdf` → **"Analyze docx/pdf files"**
* `xlsx` and `csv` → **"Analyze xlsx/csv files"**
For how to plan a multi-language study (translate first vs. analyze in each language), see [Analyze multilingual data](/ailyze-docs/common-research-workflows/analyze-multilingual-data.md).
## A realistic example
> **Scenario:** A set of German interview [transcripts](/ailyze-docs/reference/glossary.md#transcript) you want to merge with English ones. Upload the DOCX files, set **"Origin"** to German and **"Destination"** to English, add a custom dictionary for your product names, and submit. When it's done, use **"Download Selected"** for your records and click **"Analyze"** to fold them into one English [codebook](/ailyze-docs/reference/glossary.md#codebook).
## Next steps
* [Translate your first document](/ailyze-docs/getting-started/translate-your-first-document.md)
* [Analyze multilingual data](/ailyze-docs/common-research-workflows/analyze-multilingual-data.md)
* [Translation issues](/ailyze-docs/troubleshooting/translation-issues.md)
---
# 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/prepare-research-data/translate-files.md?ask=&goal=
```
`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.