> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Translate a document into partner languages

> Generate language variants of a document with AI so every partner reads it in their own language.

> For partner marketing serving a global partner base in their own language.

Partners engage far more with content they can actually read. Introw can generate language variants of a document with AI, so you localize from the same asset instead of commissioning a translation vendor and managing separate files. This guide covers selecting the target languages, running the translation, and reviewing the result, plus the one dependency to be aware of: automatic translation must be enabled for your workspace.

## What you'll achieve

A single document asset that carries language variants, each held against its locale, so a partner is served the version in their language while you maintain one asset. Translations preserve the document's formatting and fill only the language slots that are still empty.

## Before you start

<Steps>
  <Step title="Have a supported document">
    You need a document asset that supports translation. Very large files are not eligible, so keep the source within the document translation size limit.
  </Step>

  <Step title="Confirm automatic translation is enabled">
    Automatic document translation depends on a translation provider being configured for your workspace. If it is not enabled, the generate action reports that automatic translation is not configured, and you will need it turned on before you can continue.
  </Step>
</Steps>

## Steps

<Steps>
  <Step title="Open the Languages tab">
    Go to [Assets](https://app.introw.io/assets/library), open the document, and select its **Languages** tab. This tab lists the base language and any existing variants, and is where you add or generate more.
  </Step>

  <Step title="Choose the target languages">
    Open the generate translations action and pick the languages you want variants for. Use the select-all control to fill every empty language at once, or check individual languages for a subset. Only languages without an existing variant are offered, since translation fills empty slots rather than overwriting work you already have.
  </Step>

  <Step title="Generate the translations">
    Start the translation. It runs as a background job that preserves the document's formatting, so you can keep working while it completes; large files can take a few minutes. You are notified when the variants are ready.
  </Step>

  <Step title="Review each variant">
    Once the job completes, open each new variant from the **Languages** tab and check it for accuracy before relying on it with partners. If you would rather supply your own translation for a language, you can add a variant manually instead of generating one.
  </Step>
</Steps>

## Verify it worked

The new language variants appear under the asset's **Languages** tab, each tied to its locale. A partner in that language is served the matching variant from the same asset, and the base document and its variants stay together as one item.

## Related

<CardGroup cols={2}>
  <Card title="Build the asset library" icon="book-open" href="./build-the-asset-library">
    Add the documents you localize.
  </Card>

  <Card title="Review asset engagement" icon="book-open" href="./review-asset-engagement">
    See which language variants partners use.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full asset library configuration options.
  </Card>
</CardGroup>