Translate the registration form
Updated September 8, 2026
Translate labels, placeholders and option labels; the form itself stays one.
What it’s for
The registration form is shared by every language of the page: the same fields, in the same order, with the same steps and required flags. What a visitor reads on it, the labels, the placeholders and the options of a dropdown, is translated per language.
The value a visitor picks in a dropdown is sent to Livestorm as the source option, whatever language its label was shown in, so your registrant data stays consistent.
Open your page on step 2 · Form. The same language pill as on the Design step sits at the top of the panel.
Pick a version: each field says what is left to translate. Fields, their order, steps and required flags are shared by every language; only the texts visitors read are translated here.
Expand a field: its label, its placeholder and, for a dropdown, each option's label get a box of their own, with the source above. The value sent to Livestorm stays the source's.
The live preview on the right renders the form in the language shown.
Good to know
- The Livestorm terms consent and the session picker are translated by Venue in every language: nothing to do.
- Update translations, in the language pill, also fills in the form texts that are missing or outdated.
- A field you add later gets its translations at the next Update translations.
Related articles
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?