Native Notion forms don’t have a translation setting, so a Notion form in multiple languages means building it yourself. The cleanest setup is one form per language, all writing into the same database, with a Language property so you can tell the responses apart. If you need a single link that switches language, you’ll need a third-party form tool with a translation feature.
Do native Notion forms support multiple languages?
Native Notion forms don’t support translation; the questions appear exactly as you type them. The Notion forms help page covers question types, sharing and the submit screen, but it has no setting for a form language or a translated version.
Notion does have a display language. You set it in Settings → Preferences → Language & Time, per Notion’s language help page, and on mobile it follows your phone’s language ranking. It changes your interface. Your respondents still read the questions you typed.
One piece of fixed text is yours to change: the submit button. The help page says you can set its color and text, so a Spanish form can say “Enviar” instead of “Submit”.
How to set up one form per language
The most reliable setup is a separate form for each language, each connected to the same Notion database. The help page describes adding a form to an existing database by selecting + next to your existing views and choosing Form.
For a bilingual English and Spanish event signup:
- Build the English form first. Finish every question, including required fields and the submit screen text.
- Add a Language property to the database, as a select with English and Español. You’ll sort responses by it later.
- Add a second Form view with the + next to your views. Rewrite each question title and description in Spanish, and change the submit button text.
- Tag each form’s responses. Add a required multiple-choice Language question to each form, offering only that form’s language, so every submission records it.
- Share each form link on the matching language version of your site or email.
Notion’s help page doesn’t say how many forms one database can hold, so try the second form view on a copy of your database first.
Do this on desktop. The help page says you can’t currently create or customize a form on a mobile device. For the basics of the builder, see how to create a form in Notion.
Why translated answer choices cause messy data
Translated answer choices can split your data, because a Notion form question maps directly to a database property. The help page says the question type is the equivalent of the property type.
That means a multiple-choice question writes into a select property. If the English form offers “Vegetarian” and the Spanish form offers “Vegetariano”, your database can end up with two options for the same meal. A filter on “Vegetarian” then misses every Spanish signup.
Two fixes:
- Keep a short shared code in each label, such as “VEG – Vegetarian” and “VEG – Vegetariano”, then group by the code.
- Use one language for the choice values and translate only the question text around them.
Use the second one. Most respondents can read a short English choice like “Yes” or “Large”, and your database stays clean. Shared-code labels work, but they look clumsy on the form. Our guide to mapping form fields to Notion properties explains how each question type lands in the database.
Watch out for browser auto-translate
Browser auto-translate can change a form your respondent already sees in their language. The Fillout help page notes that many Chrome respondents have Google Translate on, which auto-translates websites.
Sometimes that helps: a Spanish speaker opening your English Notion form may get a rough machine translation for free. It can also garble your Spanish form or rewrite a choice label your filters depend on. Native Notion forms have no setting to stop it. Keep the wording plain and short.
Using a form tool with a built-in language setting
Third-party form tools that connect to Notion can switch a single form’s language, but what they translate varies. As of November 2026, two help centers describe this clearly.
NoteForms lets you pick a Form Language in its Design tab, and its help article says this translates forms, including error messages. Error messages only change after you save the form.
Fillout offers translations into many languages and says a form can have up to 2,000 translatable items for auto-translation. The catch, from its help page: changing the form’s language only translates text you can’t edit yourself. Questions, button labels and choice labels stay as written until you translate them.
Translating responses after they arrive
If respondents write free-text answers in different languages, you can translate them after submission. Zapier offers a template to receive new form responses, translate content, and create database entries in Notion.
This fits a support or feedback form, where the questions can stay in one language. For more on automating the step after submission, see our Notion form automation guide.
What a Notion form in multiple languages can’t do
A native Notion form in multiple languages has one real limitation: no single link detects the respondent’s language. Each language is a separate form with its own URL, and sending people to the right one is your job. Get it wrong and a Spanish reader lands on the English form.
Public web forms are also anonymous, per the help page. If you need to know who replied, add a required name or email question to every language version. Our post on sharing a Notion form publicly covers the sharing options in detail.
FAQ
Can Notion forms be translated automatically?
No. Notion’s forms help page has no translation or form-language setting. You write the questions in the language you want respondents to see.
Does changing my Notion display language translate my form?
No. The display language in Settings, Preferences, Language & Time changes your own Notion interface. It doesn’t rewrite the questions you typed into a form.
How do I know which language a respondent used?
Give each language its own form and add a Language property to the database. Set it per form, or ask a required multiple-choice question that records it.
Should I translate the answer choices too?
Only if you accept extra select options in the database. A choice like Yes and its Spanish version Sí can end up as two separate options, so keep a mapping or a shared code in the label.