> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/screeners/translate-a-screener.md).

# Translate a screener

Screener translations let you offer the same screener in more than one language, so respondents can answer in the language they are most comfortable with. When building a screener, you choose which languages to offer, then manually provide the necessary copy for each of your selected languages.

**In Private Panels screeners, you can translate:**

* Question labels
* Question descriptions
* Answer option text
* Slider start and end labels
* Headers, paragraphs, and other text elements you have added to the screener

Translations are available on both **study screeners** and **panel sign-up forms**. The steps are the same for both.

{% hint style="warning" %}
**Warning:** Private Panels does not translate anything for you. There is no machine or automatic translation, so every language you add starts out empty and must be filled in by you or a member of your team.
{% endhint %}

### Enable languages

A screener will always have a **Default** language, which is the language in which you write your questions, answer choices, and more originally. You can enable additional languages in the screener builder, which then unlocks additional fields where you can enter translations for your default copy.

**To enable languages in a Private Panels screener:**

{% stepper %}
{% step %}
On the **Screener builder** tab, click **Languages**. A modal is displayed.

<div align="left"><figure><img src="https://1440167164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT7fhyut5rrQHwe5QRGot%2Fuploads%2FuHDIWhxZfRB7lvXs1hXy%2FPanels_translation%20(2).jpg?alt=media&amp;token=ed40dc69-ce0b-4985-8b56-9e0085ac3702" alt=""><figcaption></figcaption></figure></div>

{% hint style="success" %}
**Tip:** Your default language is not automatically tied to a specific language. That's so you can write your screener copy in whichever language you want without Private Panels assuming you're writing in English. However, you can assign your default language in the modal manually. If you do, you'll see that language in place of **Default** throughout the UI.
{% endhint %}
{% endstep %}

{% step %}
Click **+ Add language**, then search for and select the language you want to offer. Repeat until you've added all languages you want to offer. If you close the search without choosing a language, nothing is added.

<div align="left"><figure><img src="https://1440167164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT7fhyut5rrQHwe5QRGot%2Fuploads%2FlJITxQ4fxi1QEtcmh2Z6%2FPanels_translation.jpg?alt=media&amp;token=c55c911e-cf62-4f43-95ea-1e2b7c207675" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Done**.
{% endstep %}
{% endstepper %}

Now, a language drop-down appears at the top of the screener builder. Use this to toggle between your screener's languages and enter your translated text.

<figure><img src="https://1440167164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT7fhyut5rrQHwe5QRGot%2Fuploads%2Fpl4HYAQmGfzyaE85df5f%2FTranslations_default.jpg?alt=media&amp;token=baa47d8a-beba-460e-84d8-9d9786c2bd9d" alt=""><figcaption></figcaption></figure>

When viewing your other languages, your original Default wording appears underneath each field so you can see what you are translating without leaving the page.

<figure><img src="https://1440167164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT7fhyut5rrQHwe5QRGot%2Fuploads%2FGNrrjpM2nNQ4YcpIlmIQ%2FPanels_translation%20(4).jpg?alt=media&amp;token=df0095d9-02bc-45d1-aac9-218b406064f7" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Translations do not fall back to your Default language.** Respondents get the Default only when their language isn't one you offer. If you add a language and leave a question untranslated, respondents on that language see that question blank rather than the original wording. A language you add but never fill in will show an entirely empty screener. Finish a translation before sharing the screener, and re-check it whenever you add or reword a question.
{% endhint %}

### Modify questions in a translated screener

When adding or modifying questions in a translated screener, keep in mind that your changes affect all of your enabled languages. Only the text itself is managed on a per-language basis.

If you add a question while a language is selected, the text you type becomes both the Default wording and that language's translation. Switch to your **Default** language afterward to set the default wording properly, then switch back to each language to translate it.

### Buttons, confirmation, and disqualification text

The screener's **Next**, **Submit**, **Cancel**, and validation text, along with your confirmation and disqualification page wording, are set separately in the screener's redirects and language settings. For more information, see [Survey redirects and language](https://help.dscout.com/private-panels/screeners/survey-redirects-and-language.md).

{% hint style="info" %}
These settings are not per-language. You set one version that every respondent sees, no matter which language they take the screener in.
{% endhint %}

### Panelist experience

When a screener is offered in more than one language, Private Panels picks the language from the respondent's browser settings. A browser set to a regional variant is matched to the closest language you offer, so a respondent set to Arabic (Qatar) is served your Arabic translation. If the browser's language is not one you offer, the respondent sees the Default language.

{% hint style="info" %}
**Note:** Languages written right to left, such as Arabic, Hebrew, Farsi, and Urdu, automatically flip the screener's layout to read right to left.
{% endhint %}

If a respondent wishes to manually change their language, they can use the **Language** drop-down above the screener whenever more than one language is available. Each language is listed under its own name, so a respondent can recognize their language without reading English. Switching languages reloads the questions in the new language.

<figure><img src="https://1440167164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT7fhyut5rrQHwe5QRGot%2Fuploads%2Fc6G13MiUkEsPn0DPArG0%2FPanels_translation%20(5).jpg?alt=media&amp;token=1384357f-126c-48d3-a15c-a1950fb8ec41" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
**Tip:** To share a link in a specific language, add `?lang=` and the language code to the end of your screener link to open it directly in that language. For example, add `?lang=es` for Spanish. This overrides browser detection, which is useful when you are sending a link to a specific group or checking a translation yourself.
{% endhint %}

### View responses

Responses from every language come back together in one place. There is no separate report or export per language.

In **Study Overview** you will see all respondents in a single table regardless of the language they answered in.

* **Multiple choice, checkbox, and other option-based answers** are recorded against the same answer option no matter which language the respondent used. A respondent who selects the Spanish wording of an option and one who selects the English wording land on the same option, so your counts, filters, segments, and quotas stay accurate across languages.
* **Open-text answers** are saved exactly as the respondent typed them, which means they come back in whatever language the respondent was using. You will need to translate these yourself for analysis.

To pull responses out of Private Panels, follow the [Export survey responses](https://help.dscout.com/private-panels/studies/export-survey-responses.md) guide. The export has the same columns it always does.

{% hint style="info" %}
**Note:** There is currently no column, filter, or export field that tells you which language each respondent used. If you need to know, a practical workaround is to send each language group a link with its own `?lang=` parameter plus a hidden value you can filter on. For more information, see [Hidden values](https://help.dscout.com/private-panels/screeners/hidden-values.md).
{% endhint %}

### Frequently asked questions

<details>

<summary>Respondents are seeing a blank question. What happened?</summary>

This is almost always an unfinished translation. Translations do not fall back to your Default wording, so any field you have not translated shows up empty for respondents on that language.

Switch the builder's language drop-down to the affected language and look for empty fields. If the whole screener is blank, the language was added but never translated. Either finish the translation or remove the language until it is ready.

</details>

<details>

<summary>I added a new question and now it is untranslated in every language.</summary>

This is expected. Structure is shared across languages but wording is not, so a new question arrives with no translations. Switch to each language and translate the new question. The same applies when you reword an existing question: the old translation stays in place and will no longer match, so review it.

</details>

<details>

<summary>Can I show a different confirmation page or different button labels per language?</summary>

Not currently. Button labels, validation text, and your confirmation and disqualification page wording are set once for the whole screener and are shown to every respondent regardless of language. If you need language-specific confirmation wording, the usual workaround is a separate screener per language.

</details>

<details>

<summary>Do quotas, logic, and branching still work across languages?</summary>

Yes. Logic and quotas are evaluated against the underlying answer option rather than the words a respondent saw, so a translated option behaves identically to its Default equivalent. You configure quotas and logic once, in your Default language, and they apply to every language.

</details>

<details>

<summary>Can I translate my screener into a language that is not in the list?</summary>

The language list is generated from the respondent's browser and covers the standard set of world languages, so most languages you need will be there. Search by the English name of the language. If a language you need is genuinely missing, contact <support@dscout.com>.

</details>

<details>

<summary>What happens if I remove a language?</summary>

Removing a language deletes the translations stored for it and stops offering it to respondents. Responses already collected are not affected. Your Default content and all other languages are untouched.

</details>

<details>

<summary>How do I preview a translation the way a respondent will see it?</summary>

Open your screener's public link with `?lang=` and the language code added to the end, for example `?lang=de` for German. That bypasses browser detection and loads the screener in that language, including right-to-left layout where it applies.

</details>

<details>

<summary>Does this work on panel sign-up forms too?</summary>

Yes. Panel sign-up forms use the same Default-plus-languages model and the same **Languages** button. See [Panel sign-up forms](https://help.dscout.com/private-panels/panel-management/panel-sign-up-forms.md).

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/private-panels/screeners/translate-a-screener.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
