Translating a Recorded Session

Translation is something a reviewer does while watching, not something you configure in the SDK. Nothing in your page or app changes, and nothing is translated until someone asks.

In the player

1. Open a session

   From Sessions, open any recording — web or React Native.

2. Choose a language

   Select Translate to… beside the player and pick a language from the list.

3. Wait for the progress bar

   The control shows Translating… with a percentage while the strings are processed. The first translation of a session takes longest; strings already translated in your organisation come back straight away.

4. Watch it translated

   The replay rebuilds with the interface in the chosen language. Show original switches back; Show translation returns to it.

The dashboard itself — menus and settings — is available in English, Turkish, German, Spanish and French, chosen under account settings. That setting only affects the dashboard; the language a session is translated into is chosen per recording.

What is translated

The strings are taken from the recording itself — the first snapshot and every change after it — translated, and put back before the player rebuilds the page. Each string is sent with its context, so a button label is translated as a button label:

• Headings, buttons, labels, links and ordinary text.
• Attributes a reader would see: placeholder, title, alt and aria-label.
• Text in React Native recordings, which are already text and structure rather than images.

Never translated: the contents of script, style, code, pre and svg elements, and masked values — those were asterisks before they left the visitor's browser. If a string cannot be translated it stays in its original language rather than breaking the replay.

Caching

Translations are cached across your organisation by the content of each string and the target language. A navigation bar that appears in ten thousand sessions is translated once, and the next reviewer to open any of those sessions in the same language gets it instantly. Nothing is translated speculatively. Cached strings that have not been used for longer than your retention period are deleted; corrected strings are kept until the organisation is deleted, because they work like a glossary.

Glossary and corrections

• Glossary. Under Translations, add terms the translator must never guess at — product, feature and plan names — with a preferred translation, or leave it empty to keep the term exactly as written. Every session translated in your organisation follows the glossary first. It is included on the Team, Business and Enterprise plans; see pricing.
• Corrections. Members with the moderator role or above can correct a translation. Corrections are recorded in the audit log.

Who can translate

Members can watch sessions and request translations; moderators can also correct translations and delete recordings. See Team in the dashboard for each role.

Self-hosted installs

A self-hosted deployment needs a translation provider configured. Without one the player shows "Translation is not configured for this workspace". See self-hosting configuration.