> 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/troubleshooting/translation-issues.md).

# Translation Issues

This page helps you fix problems that come up when you translate files.

## "My PDF, XLIFF, or SRT won't translate with my language"

These formats only work with **Best Accuracy** language pairs, so choosing a **Good Accuracy** language leaves them stuck.

1. Pick a **Best Accuracy** language for these files.
2. Or convert the PDF to DOCX first, then translate.
3. When prompted, remove or convert the files that don't fit the chosen language.

## "I can't find my language"

The language list is long and split into two accuracy tiers, so your language may be in a tier you didn't check.

1. Type the language name into the **search** box in the language dropdown.
2. Look in both **Best Accuracy** and **Good Accuracy** — some languages appear in only one tier.

For the full list, see [Supported languages](/ailyze-docs/reference/supported-languages.md).

## "My source language isn't detected"

Translation does not auto-detect the language, so you have to set both languages yourself.

1. Set the **"Origin"** to the language your file is in.
2. Set the **"Destination"** to the language you want.
3. Make sure the two are not the same.

## "The project is taking a while / there's no progress bar"

Translation runs in the background without a live percentage, so a wait with no bar is normal.

1. Watch the **Status** move from **In Progress** to **Translating** to **Completed**.
2. Wait for the **email** you get when it's done — only **Completed** projects will open.

## "I was charged"

The first 1,000 words are free, and beyond that the app charges from your wallet after you confirm.

1. Confirm the charge shown on the **"Create Project"** button before you submit.
2. If your wallet is short, top it up when you see the insufficient-balance prompt.

For the rate, see [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md).

## "Where's my translated file?"

Translated files are ready only once the project shows **Completed**, and they keep the original format.

1. Click the row to download a single file.
2. Or open the project and use **Download** per file, or **"Download Selected"** for a ZIP.
3. Note there is no in-app preview — download the file to read it.

## "Terms or brand names translated wrong"

The translator doesn't know your preferred wording unless you tell it, so specific terms can come out wrong.

1. Open the **"Optional Instructions"** accordion.
2. Add a custom dictionary that maps each original term to the translation you want.
3. Set a **Formality** level if the tone is off.
4. Run the translation again.

## "The screen says 'Analysis Starting' or the project is named 'New Project'"

The success screen may show wording like "Analysis Starting" or a default project name, but the project is still translating.

1. Ignore the wording and wait for the **email**.
2. Open the project once its **Status** reads **Completed**.

## Next steps

To analyze translated content, open the project detail page and use the **"Analyze"** button (DOCX or PDF goes to document analysis; XLSX or CSV goes to spreadsheet analysis).

* [Analyze multilingual data](/ailyze-docs/common-research-workflows/analyze-multilingual-data.md)
* [Translate files](/ailyze-docs/prepare-research-data/translate-files.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/troubleshooting/translation-issues.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.