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

# Translate and review a demo

> Add languages to one demo, review the translated experience, and test what viewers receive.

A translated demo lets different audiences follow the same story in their own language. The languages belong to one demo; translating does not create a separate copy. Start with a reviewed original so you do not multiply mistakes across languages.

## Add a language

1. In the editor, open **Language** and select **Translate to…**.
2. Choose the languages you need and review the translation estimate before starting. AI translation availability depends on your workspace and plan.
3. Wait for translation to finish. Open **Language** again and select a translated language to review it in the editor.
4. Select **Review all translations…** to compare the original text with each translation and edit the fields that need attention. Changes save as you go and become visible to viewers when you publish.

Review names, product terminology, actions, and the final CTA with a person who knows the language and the product. Generated text can be fluent and still describe the wrong action. Check longer text in context: a guide that fits in one language may cover the target in another.

## Check screens and media

Translated guide text does not automatically make the words inside every captured screenshot accurate. In the translation review, a screenshot step can use a language-specific replacement image; without one, it shows the original image. Check the translated screen and instruction together, and use a suitable localized capture where needed.

Review narration, captions, dates, and any personalization values separately. Keep essential instructions in text even when the demo includes audio. Changes to text in a selected language apply to that language; layout changes apply across languages, so check the original and other translations after adjusting placement.

## Test the published language

Publish the reviewed draft and open the shared experience in a separate browser session. Test the original and each language you intend to share, including the starting step, branches, screenshots, and ending. The player can choose a published translation from the viewer's browser language and offers a language control when translations are available.

A link can request a published language with `?lang=` and its language code—for example, `?lang=fr` for a published French translation. `?lang=original` selects the source language. An unavailable language override is ignored; the player then considers the browser's languages and falls back to the original. When a link already has a query string, add another parameter with `&` rather than a second `?`.

## Removing a language

Removing a language removes its translated text, images, narration, and captions, including manual edits. Read the review before applying the removal. The published demo continues to show its existing version until you publish the changed draft. If you are unsure whether the content is still needed, keep it and review the affected links first.

See [Review a demo before it goes live](https://docs.arcdemo.io/guides/review-and-publish.md) and [Keep a demo current](https://docs.arcdemo.io/guides/maintain-a-demo.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.