Form-building guide
How to create multilingual forms
Make one form understandable to respondents who do not share a primary language.
Build this form freeMultilingual forms work best when language is planned before distribution. The same field structure should make sense in every language, while instructions and consent copy remain specific enough to avoid ambiguity.
Formius lets you generate a form and localize it into supported languages, so teams can keep one maintained form rather than separate versions with drifting questions.
Choose a single source language
Write and approve the source copy first. Keep labels short, use direct instructions, and avoid idioms that become unclear when translated.
Check options and legal copy in every language
Choice labels, helper text, confirmation screens, and consent language carry meaning just as much as questions do. Review these parts in context before sharing a public link.
Keep one response structure
Use one form instead of per-language clones whenever possible. A shared structure makes reporting, permissions, and later edits easier to manage.
Frequently asked questions
- Should I create a separate form for every language?
- Usually no. A single maintained form with localized content prevents version drift and keeps responses in one place.
- What should I review after translation?
- Review question intent, choice options, instructions, consent text, and the respondent-facing confirmation state.