Translations

A single survey can run in many languages, so respondents answer in the language they're most comfortable with. You author your survey in a base language, then add translations alongside the original for each language you want to support. This page explains how translating works and how to find and fill any gaps.

How translation works

You build your survey in a base language first — every title, description and option you type is the original. When you're ready, you switch into Translate mode and pick a target language. The translated text sits next to the original so you can work through it field by field.

While you're translating, the original (base) text is read-only — your edits go into the translation for the language you chose, never the original. Each language keeps its own complete set of translations, layered over the base survey.

The supported languages are:

• Bulgarian
• Catalan
• Greek and Greek (formal)
• English and English (US)
• Spanish
• French
• Dutch
• Romanian

What gets translated

Translate mode covers the text respondents read and the references you rely on:

• Group titles and descriptions
• Question titles, descriptions, and their internal display name
• The labels and descriptions of choice options

Anything that doesn't have meaningful original text is skipped, so you only ever work through fields that actually need a translation. A few things are intentionally not translated: the survey's own internal name (respondents never see it), and any content that came from a shared template, which is managed centrally on the master template and stays locked here.

Tracking your progress

Every language shows a progress indicator — the share of translatable fields that are done — so you can see how complete each one is at a glance, and an overall figure across all languages. Inside Translate mode, any field that still has no translation is flagged with a missing-language badge, making gaps easy to spot as you scroll the survey.

When you open the list of fields for a language, you can filter it to show all fields, only translated ones, only untranslated ones, or only the ones filled in by assisted translation — and search within them — so you can zero in on exactly what's left.

Compare view

A compare mode puts the original and its translation side by side, both in the workspace and in the editor, so you can check meaning as you translate. It's the easiest way to make sure a translation says the same thing as the source before you move on.

Adding a language

Assisted translation

To save time, you can auto-translate all the untranslated fields for a language in one go. The designer counts up exactly what's missing, asks you to confirm, then fills those fields in automatically and shows a short summary of how many succeeded when it finishes. Formatting in rich-text content is preserved, so links and styling survive the translation.

Auto-translation only ever fills empty fields — it never overwrites a translation you've already written. Fields it filled in are marked so you can find and review them (that's the "assisted" filter mentioned above), and editing a marked field clears the mark — a simple way to track what you've checked by hand.

Template content

Anything that came from a shared template is locked and isn't translated here — its wording is owned by, and translated on, the master template. See Surveys & templates for how connected surveys relate to their templates. Once respondents answer in their language, results still flow into Insights for analysis.

Related articles