> 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/getting-started/translate-your-first-document.md).

# Translate Your First Document

This page shows you how to translate your first file, using the **"Translate docx/pdf/xlsx/pptx/etc"** workflow. For the full set of options, see [Translate Files](/ailyze-docs/prepare-research-data/translate-files.md).

{% hint style="info" %}
**What you need:** an Evidano account and a file to translate — **DOCX, PPTX, XLSX, HTML, or TXT** (all languages), or **PDF, XLIFF, or SRT** (Best Accuracy language pairs only). Your **first 1,000 words are free**.

**What you will have at the end:** a downloadable translated file in the same format as the original.
{% endhint %}

## Step 1: Start a translation

From your account page, click **"Translate docx/pdf/xlsx/pptx/etc"**. Review the **Supported File Types** panel, then upload your file (or pick a previous one).

<figure><img src="/files/46GgtKjDSY5kltmyRY1v" alt="New Translation Project page with the Supported File Types panel"><figcaption></figcaption></figure>

## Step 2: Choose languages

Once a file is selected, the **"Configure Translation"** card appears. Set two language selectors:

* **"Origin"** — the current language of your documents. (You must pick this; it isn't auto-detected.)
* **"Destination"** — the language you want the documents translated into.

Languages are grouped by quality: **Best Accuracy** and **Good Accuracy**. Search to find yours.

<figure><img src="/files/vUuHsNeSSNvsGrnqpUXq" alt="Choosing Origin and Destination languages on the Configure Translation card"><figcaption></figcaption></figure>

{% hint style="warning" %}
PDF, XLIFF, and SRT files only translate with **Best Accuracy** language pairs. If you pick a Good Accuracy language with those files, Evidano will prompt you to remove or convert them.
{% endhint %}

## Step 3: Refine the translation (optional)

Open the **"Optional Instructions"** accordion to:

* Add a **custom dictionary** — force specific translations for brand names, product names, or jargon.
* Set **formality** — choose **Default**, **More Formal**, **Less Formal**, **Prefer More**, or **Prefer Less** (available for some languages).

For details on these options, see [Translate Files](/ailyze-docs/prepare-research-data/translate-files.md).

## Step 4: Submit

Click **"Create Project"** (the button shows the cost, like **"Create Project (USD X)"**, if you're over the free word limit). You'll see a confirmation — "You’ll receive an email when the translation completes." — then land on the **Document Translation** list.

{% hint style="info" %}
**Costs credits:** Beyond your free words, translation draws from your wallet, and you'll confirm any charge first. See [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md) for exact pricing.
{% endhint %}

<figure><img src="/files/qMy4L4GaXCxMDQ4BCvXS" alt="Document Translation list showing the new project and its status"><figcaption></figcaption></figure>

## Step 5: Download your translated file

When the status shows **Completed**, open the project (or click the row). On the detail page:

* Click the **Download** icon on a row to get a single translated file, or
* Select multiple files and click **"Download Selected"** to get them as a ZIP.

The translated file keeps the **same format** as the original.

<figure><img src="/files/GkO48ScIYYKLeZRyU5EU" alt="Project detail page with per-file download and the Download Selected button"><figcaption></figcaption></figure>

Want to analyze the translated content? The detail page has an **"Analyze"** button that sends DOCX and PDF files to document analysis, and XLSX and CSV files to spreadsheet analysis.

## Next steps

* Explore every option — [Translate Files](/ailyze-docs/prepare-research-data/translate-files.md)
* Working across several languages at once? [Analyze Multilingual Data](/ailyze-docs/common-research-workflows/analyze-multilingual-data.md)
* Check which languages are available — [Supported Languages](/ailyze-docs/reference/supported-languages.md)
* Something not working? [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/getting-started/translate-your-first-document.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.