> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/document-processing/translate-documents.md).

# Translate Documents

Translate the text of documents loaded earlier in the workflow. Use this tool to produce text in another language for a later response or file-generation step.

## Use this tool

1. Load the source documents in an earlier workflow step.
2. Set **Source Language** and **Target Language**.
3. Set **Chunk Size** if needed and run the workflow.
4. Review **Translation**, including names, numbers, and specialist terms.

## Behavior and limits

The output is translated text, not a replacement file with the original document layout. Use [Convert Markdown to File](https://docs.stackai.com/stackai-tools/file-creation-and-conversion/convert-markdown-to-file.md) if you need to turn the text into a downloadable document. Documents must be available from an earlier workflow step.

## Inputs

| Field      | Parameter    | Description                                                                   |
| ---------- | ------------ | ----------------------------------------------------------------------------- |
| Chunk Size | `chunk_size` | The size of text chunks to translate at once (in characters) Default: `8000`. |

## Configuration

| Field                      | Parameter         | Description                                |
| -------------------------- | ----------------- | ------------------------------------------ |
| Source Language (required) | `source_language` | The language of the source documents       |
| Target Language (required) | `target_language` | The language to translate the documents to |

## Outputs

| Field       | Parameter     | Description                            |
| ----------- | ------------- | -------------------------------------- |
| Translation | `translation` | The translated text from the documents |

## Related guides

* [Parsing, OCR, and Document Structure](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/parsing-ocr-and-document-structure.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-tools/document-processing/translate-documents.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
