> For the complete documentation index, see [llms.txt](https://support.vlex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.vlex.com/vincent-by-vlex/vincent/core-workflows/translate-documents-into-any-language-using-vincent.md).

# Translate Documents into Any Language Using Vincent

### Summary

Use the **Translate Documents** Vincent workflow to convert uploaded files into the target language of your choice, built for long legal documents that the default chat would otherwise truncate.

### Why This is Important

Legal practice is increasingly cross-border. You may need to review a Brazilian shareholders' agreement, a French employment contract, or a German court decision in a language your team can work with, and you need the *entire* document, not the first few pages. Pasting long content into a standard chat often results in mid-document interruptions or truncated output. **Translate Documents** is purpose-built to handle full-length files: it processes the document section by section behind the scenes and returns a single, polished translation you can immediately use or refine in Legal Pad.

### Step-by-Step Guide

1. Open Vincent and select the **Translate Documents** workflow from the workflow menu.
2. Upload one or more documents using the **Upload** button. Supported file types include PDF, DOCX, and TXT.
3. Vincent will prompt you for the **target language**. Reply with a single language — regional variants are accepted (for example, *English UK*, *Brazilian Portuguese*, *Latin American Spanish*, *Canadian French*).
   * If you provide multiple languages or an unclear response, Vincent will re-prompt you to confirm one specific target language before proceeding.
4. Vincent processes the file section by section in the background. You do not need to confirm continuation or paste content in chunks.
5. Review the complete translation delivered in the chat window.
6. To make edits, send the translation to **Legal Pad** using the **Edit in Legal Pad** option, where you can refine terminology, formatting, or specific clauses before exporting.

<figure><img src="/files/Uvw6QwWxrPcLpaDaA8MJ" alt=""><figcaption><p>Upload, choose your language, and let Vincent handle the rest. Complete, seamless document translation without the hassle.</p></figcaption></figure>

Upload, choose your language, and let Vincent handle the rest. Complete, seamless document translation without the hassle.

{% hint style="info" %}
**Tip:** Vincent preserves the structure of the original document (headings, numbered clauses, defined terms) so the translated output remains usable as a working draft.&#x20;
{% endhint %}

### Best Practices & Pro Tips

* **Specify the regional variant whenever it matters.** For litigation filings or contract drafting, the difference between *English UK* and *English US* (or *European Portuguese* and *Brazilian Portuguese*) is not stylistic, it affects legal terminology, citation conventions, and enforceability language. Always tell Vincent the exact jurisdiction-aligned variant your matter requires.
* **Use Translate Documents for substantive work, not snippets.** For a single sentence or short quote, the default chat is faster. Reserve this workflow for full contracts, judgments, witness statements, and briefs, anywhere a complete, structurally coherent translation is essential.

### Related Articles

* [Supported File Formats for Analysis](/vincent-by-vlex/vincent/support-and-account-administration/supported-file-formats-for-analysis.md)
* [Requesting a Demo or Trial of Vincent](/vincent-by-vlex/vincent/support-and-account-administration/requesting-a-demo-or-trial-of-vincent.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:

```
GET https://support.vlex.com/vincent-by-vlex/vincent/core-workflows/translate-documents-into-any-language-using-vincent.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.