> 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/prepare-research-data/translate-files.md).

# Translate Files

Translate whole documents, spreadsheets, and slides into another language while keeping their original layout and formatting.

This page shows you how to translate whole files, not just snippets, into another language, keeping their layout, tables, and slides intact. At the end you will have your files in the new language, in the same format, ready to download or analyze.

For a quick first run, see [Translate Your First Document](/ailyze-docs/getting-started/translate-your-first-document.md). Every control on these screens is listed in [Translation Settings](/ailyze-docs/reference/settings/translation.md).

## Before you start

* The files you want to translate. The file count and size caps are in [Supported File Types](/ailyze-docs/reference/supported-file-types.md).
* Translation is charged per character after a free allowance of characters per account, and every document is billed at a minimum; see [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).

## Supported files

| Tier                                     | Formats                               |
| ---------------------------------------- | ------------------------------------- |
| **All languages** (Good & Best accuracy) | `docx`, `pptx`, `xlsx`, `html`, `txt` |
| **Best-accuracy languages only**         | `pdf`, `xliff`, `srt`                 |

`pdf`, `xliff`, and `srt` translate only when both languages are in **Best Accuracy**. With a **Good Accuracy** language, a red line names the file and asks you to remove it or pick another language.

## Step 1: Pick your files

1. From your account page, click **Translate docx/pdf/xlsx/pptx/etc**.
2. Tick the files in the library, or click **Upload files** to add new ones.

You should see a card open below the library with a chip counting the characters and a yellow price quote.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-f34795f4cacb048d9b408862e2862578a1ad7525%2Fsettings-translation-03-configure.png?alt=media" alt="Translation card with the selected-files counter, a character chip, the yellow price quote and the language selectors"><figcaption><p>Read the quote before you go on: it shows whether the project is free and, if not, what it costs and why.</p></figcaption></figure>

## Step 2: Choose the languages

1. Click **Select Origin Language** and pick the language your files are in. Type to search; languages are grouped as **Best Accuracy** and **Good Accuracy**.
2. Click **Select Destination Language** and pick the language you want.

You should see the helper line change to "You'll receive an email when the translation completes." For the full list, see [Supported Languages](/ailyze-docs/reference/supported-languages.md).

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-2b52eca1b97f1e91fc139e38a16df9cc725a981f%2Fsettings-translation-05-target.png?alt=media" alt="Target language list with the source language greyed out"><figcaption><p>The source language is greyed out in the target list, so you cannot pick the same one twice.</p></figcaption></figure>

## Step 3: Add your terms (optional)

Click **Optional Instructions**:

* Under **Custom dictionary**, map terms to the translation you want, for example "mobile clinic" to "clínica móvil". **Add another term** adds a row.
* Under **Formality**, choose **Default**, **More Formal**, **Less Formal**, **Prefer More**, or **Prefer Less**.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-114f713cb10c3b8753372ff98ed577f1de364622%2Fsettings-translation-06-optional.png?alt=media" alt="Optional Instructions with one custom dictionary row and the Formality options"><figcaption><p>A dictionary row needs both halves; half-empty rows are ignored.</p></figcaption></figure>

## Step 4: Start the translation

Click **Create Project**. The button shows the charge, as **Create Project (USD …)**, or just **Create Project** when the project is free.

{% hint style="warning" %}
**Costs money:** A paid project opens **Confirm charge** with your balance before and after; nothing is charged until you click **Create Project** there. If your wallet is too low, **Insufficient Balance** offers a top-up. See [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).
{% endhint %}

You should see "Analysis Starting", then the project list.

## Step 5: Track and download

The list (**Translate docx/pdf/xlsx/pptx/etc**) shows each project's status (**In Progress**, **Completed**, **Error**, or **Failed**) and its language pair. You get an email when a project is done.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-f068ca5dd3d0689711ebe356f201e4b731fa2d69%2Fsettings-translation-08-list.png?alt=media" alt="Translation project list with status, language pair, date created and the open and delete actions"><figcaption><p>Only Completed projects open.</p></figcaption></figure>

* **One file:** click the row; the file downloads straight away.
* **Several files:** **Open Project**, then download files one by one, or tick several and click **Download Selected (N)** for a ZIP.

Translated files keep the same format as the originals. There is no in-app preview.

## Step 6: Send files to analysis

On a project with several files, tick the files and click **Analyze**. The first ticked file decides the workflow: documents open a new document project, spreadsheets a new spreadsheet project. For a single file, upload the downloaded file to the workflow you want.

For how to plan a multi-language project (translate first, or analyze in each language), see [Analyze Multilingual Data](/ailyze-docs/common-research-workflows/analyze-multilingual-data.md).

<details>

<summary>Optional: a realistic example</summary>

* Files: German interview [transcripts](/ailyze-docs/reference/glossary.md#transcript) you want to merge with English ones.
* Languages: source German, target English; a custom dictionary row for each product name.
* Result: English DOCX files you **Analyze** together with the English transcripts in one [codebook](/ailyze-docs/reference/glossary.md#codebook).

</details>

## Next steps

* [Translate Your First Document](/ailyze-docs/getting-started/translate-your-first-document.md) — the shortest path, step by step.
* [Analyze Multilingual Data](/ailyze-docs/common-research-workflows/analyze-multilingual-data.md) — when to translate before analysis.
* [Translation Issues](/ailyze-docs/troubleshooting/translation-issues.md) — unsupported formats, missing languages, and charges.