Multilingual forms
A form can maintain its text in several languages. People filling it out see it in their own language.
The description in the interface: Enable this feature to support multiple languages for your form.
Included in the top plan
Multilingual support is part of the top plan. → Change plan
Turning it on
In the More tab: Multiple languages. After that, Edit translations takes you to the Form language editor.
Default language
The Default language is the language of the text you entered in the form builder.
This is the language that matches the text already set up in the form builder.
Don't edit the default language in the language editor
Change the default language text in the regular form editor, not in the language editor. So build the form completely in one language first, then translate it.
Adding more languages
Under Additional languages, you can add as many languages as you like:
Here you can add one or more additional languages.
The list covers more than 180 languages, each shown in its own native name.
Use Current language to switch between the languages you're currently editing.
What gets translated
Global form text
| Field | Corresponds to |
|---|---|
| Form title | Form title |
| Form description | Description |
| Submit button | Label of the submit button |
| Success page heading | Title of the success page |
| Success page message | Success page message |
| Success page button | Button text on the success page |
Form fields
Labels and descriptions of all fields.
Text blocks
All inserted text and heading blocks.
What doesn't get translated
Data stays as it is
Only the form's own text is translated — not the content:
- Select options for a single- or multiple-select field stay in whatever language they're stored in on the Grid
- Linked entries appear with their value from the target Grid
- Error messages and system text follow the application's language setting
There's no built-in solution for multilingual select options within a form. With two languages, a bilingual option is sometimes the pragmatic route — e.g. Rechnung / Invoice.
Working with it in practice
Finish first, translate last
Any later change to a field label or text block has to be reapplied in every language. So finalize the form's content first and translate it at the end.
For ongoing changes, it's worth keeping a list of which text is current in which language — the language editor doesn't show what's changed since the translation was made.
Start with a second language
Two languages are manageable. From three or four on, every form change becomes a lot of work. Check whether you really need all the languages — or whether a separate form per language would be more practical.
Alternative: multiple forms
Instead of one multilingual form, you can create a separate form per language on the same Grid and distribute the matching link.
| One multilingual form | Multiple forms | |
|---|---|---|
| Plan | top plan | any plan |
| Maintenance effort | one form, multiple text sets | everything duplicated per language |
| Changing structure | once | in every form |
| Links | one link | one link per language |
When multiple forms are better
If the forms should differ by language anyway — different required fields per country, for example — separate forms are the clearer solution. They're also not tied to a specific plan.