Team Forms supports multilingual forms, allowing people to complete the same form in their preferred language.
We recommend building your form in English as the default language, then adding translations for each additional language. This provides a consistent source for translations, integrations, and generated PDFs.
Multi-language forms are available with paid Team Forms plans.
Add languages to your form
Build and complete your form in English.
Open Actions (the three-dot menu), then select Translations.
Keep English selected as the default language.
Select Add, then choose an additional language.
Team Forms will automatically generate suggested translations from the English form text.
Review and edit the suggestions as required.
Repeat for each additional language, then select Save.
Preview each language using the language selector before publishing.
Team Forms can translate labels, descriptions, placeholders, options, buttons, validation messages, help text, and other common form content.
Always review automatically generated translations before publishing. If a translation is left empty, Team Forms displays the original English text.
If you update the English form after creating translations, reopen Translations and review any new or changed text.
What respondents see
When someone opens the form, Team Forms displays an available language matching their browser preferences. If a matching translation is unavailable, the form is displayed in English.
Respondents can switch between English and the configured languages using the language selector.
Api Property Name
Translations only change the text displayed to respondents. A field’s API property name remains the same across every language, ensuring response data and Power Automate integrations continue to work consistently.
We recommend using clear English API property names. They may contain letters, numbers, underscores, dots, and dashes, but cannot contain spaces, accented characters, or other special characters.
For example, a field displayed as Prénom in French could retain the API property name firstName.
Special Characters in Generated PDF
If the questions in your form’s default language use Chinese, Japanese, or Korean characters, select the matching CJK font in the PDF customisation options:
Simplified Chinese
Traditional Chinese
Japanese
Korean
Always preview the generated PDF before publishing to confirm that all characters display correctly.
