How to translate a Google Form

Last updated September 2026 · ~10 minute read

Short answer: Google Forms has no built-in translation feature — no translate command in the editor, and no language, locale or translation field anywhere on a form in the Google Forms API. A form holds exactly the text you typed. So there are three real approaches: one form per language, both languages in every question, or branching to a language section. And whichever you pick, respondents still answer in their own words, so the replies come back in whatever language they were typed.

Form+ builds a translated copy of your form, lets you review it against the original, and saves it to your Drive only when you say so — on your real Google Forms and your own Google account. Get Form+ free on the App Store.

That last point is the one that catches people out, so it is worth separating two things that sound identical and are not: translating the form, and a respondent's browser translating the page.

Browser translation is not form translation

Anyone opening your form in Chrome can hit the translate control in the address bar and read your questions in their own language. Chrome's help documents this as translating a page — the content of the page in front of you, plus the option to translate a highlighted section. That is genuinely useful, and for a lot of forms it is all the multilingual support you need.

But it is a display layer inside one person's browser. Specifically, a browser translation:

• changes nothing in your form. Your Drive copy is untouched; no translated version is stored anywhere.
• helps nobody else. The next respondent gets the original unless they translate it themselves.
• is out of your control. You do not get to review the wording — and machine translation of a question like “Do you consent to…” is exactly the sentence you would want to review.
• does not translate what the respondent writes back. Chrome documents translating page content; it documents nothing about translating text you type into a page, and Google Forms has no translation step between the browser and the stored response.

So browser translation solves comprehension, not data. If your form is a quick internal poll, it may be enough on its own. If the wording is legal, medical, financial or graded, you want a translation you approved — which means one of the approaches below.

Approach 1 — One form per language

The simplest, and the most common. You keep one form per audience, each entirely in that audience's language, and hand out the right link.

1. Open the finished original and, from the three-dot menu, choose Make a copy.
2. Rename the copy so the language is obvious — Enrolment form (Español).
3. Translate the title, the description, every question, every help text, and — the one people forget — every answer option.
4. Repeat per language, then send each group its own link.

The cost is the merge. Three languages means three forms, three response tabs and three spreadsheets. Nothing in Google Forms combines them for you; you copy the sheets together, or point them at one spreadsheet as separate tabs and stack them yourself. If the responses feed a report, decide how that merge works before you send the links, not after 400 replies have arrived.

There is also a quieter cost: any later edit has to be made N times, in N languages, and it is easy for the Spanish copy to drift a question behind the English one.

See how to duplicate a Google Form for the copy step in detail, including what a copy does and does not carry over.

Approach 2 — Both languages in every question

One form, each question written twice. The usual layout puts the primary language in the question title and the second language in the question's description line beneath it, so the pairing is visually obvious and every respondent sees both.

1. Turn on the description field for a question (the three-dot menu on the question, then Description).
2. Put the second language in that description.
3. For choice questions, write both languages into each option — Yes / Sí.
4. Do the same for the form title and the section headers.

What you gain: one link, one response set, one spreadsheet, one form to edit when the wording changes. For a two-language audience in the same room — a school newsletter, a workplace survey — this is usually the right answer despite being the uglier one.

What it costs: a form roughly twice as long to read, and it eats into the size budget. Google's Edit your form help page states: “After you've created a form, you can add and edit up to 300 pieces of content, like questions, descriptions, images, and videos.” Descriptions are content, so a bilingual form spends that budget faster than a monolingual one. Most forms are nowhere near 300 — but a long bilingual survey is the shape that gets there.

Approach 3 — Branch to a language section

The clever one: question one is “Choose your language / Elija su idioma”, and the answer sends each respondent to a section written entirely in that language. One form, one response set, and nobody reads a language they do not speak.

Two constraints shape it, and both come from Google's own documentation. Branching — “Go to section based on answer” — is only available for Multiple choice and Dropdown question types, which is fine here since a language picker is naturally multiple choice. And a form can hold up to 75 sections, which no language picker will ever exhaust. The mechanics, the traps and the way branching interacts with Submit form are covered in conditional logic in Google Forms.

The catch is in the spreadsheet. Each language's questions are different questions, so they get different columns. Your sheet ends up with an English block and a Spanish block, each half empty, rather than one tidy column per topic. You can collapse them afterwards with a formula, but you are back to merging — just inside one sheet instead of across three.

It also multiplies the content count: every question exists once per language, against the same 300-item budget as above.

Whichever you choose, the answers come back in the language they were typed

This is the part no approach fixes. Translate the questions however you like — the respondent still types their answer in their own words, and that is exactly what Google stores. There is no translation step anywhere between the respondent's keyboard and your spreadsheet, and no language field on a response in the Forms API.

What that means in practice:

• Short answer and paragraph questions come back mixed. A single column can hold English, Spanish and Portuguese sentences side by side. Any counting, coding or sentiment pass you run over that column has to cope with all of them.
• Choice questions are the well-behaved ones. The stored value is the option that was selected, so it is the option text as you wrote it in that form. If you translated the options, the answers arrive in the translated wording — which is why the same choice means two different strings across two language copies of a form, and why the merge needs a mapping.
• Your spreadsheet does the last mile. Google Sheets documents a GOOGLETRANSLATE(text, [source_language, target_language]) function that “translates text from one language into another”, with the source defaulting to auto-detect. A column beside your free-text answers, and you can read the lot in one language while keeping the originals — which matters, because the original is the record.

Form+ carries the same idea in the app: a Translate answers tool that lets you “read text answers in your language” without altering what was submitted.

Interface language is not form language

These get conflated constantly, and they are unrelated settings.

• The interface language — the menus, the Submit button, the “This content is neither created nor endorsed by Google” footer, the required-question warnings — follows the viewer's Google Account preferred language, which Google's Change your language on the web help page describes changing at your account's language settings. Change yours and the editor chrome changes for you. It does not touch a single word of anyone's form.
• The form's content — your title, questions, help text and options — is just text you typed. It has no language attribute at all, which is why nothing in Google's settings can translate it.

So a respondent in Japan already sees Google's own furniture in Japanese while your questions stay in English. Nothing you can set will change that second half.

One related thing Google has shipped, and it is worth not mistaking for translation: its Gemini “Help me create” form drafting works in a long list of languages, so you can ask it to draft a form in Spanish. That generates a new form from your prompt — it is not a command that translates an existing one. See using Gemini in Google Forms.

Translating a form from your phone

Every route above assumes the desktop web editor. Form+ includes a Translate to a new form tool that does approach 1 for you, on your real Google Forms, from an iPhone or iPad.

It is described in the app as creating “a translated version of this form — review and edit the translation, compare it against the original, and only save it to your Drive when you're happy. Your original stays unchanged.” Ten target languages are offered — Spanish, French, German, Portuguese, Italian, Hindi, Arabic, Chinese (Simplified), Japanese and Korean — and the language sheet notes that “you can review and edit the translation before saving.” A Compare view puts the original and the translation side by side before anything is written.

Be clear about what it produces: a translated duplicate, not a bilingual form. The result is a second, separate form in your Drive — which means a second, separate set of responses, with exactly the same merge problem as approach 1. It saves you the retyping, not the reconciling. If a single response set matters more to you than clean monolingual forms, approach 2 or 3 is still the better shape. Translate answers and Translate to a new form are Form+ PRO tools.

Which approach do you want?

Frequently asked questions

Does Google Forms have a built-in translation feature?

No. There is no translate command in the editor, and the Google Forms API's Form, Info and FormSettings resources carry no language, locale or translation field of any kind. A form holds exactly the text you typed into it.

Can respondents translate a Google Form in their browser?

Yes. Chrome's built-in translation translates the content of the page they are looking at, which includes your questions and answer options. It is a display layer in that one browser: it changes nothing in your form, nothing for the next respondent, and nothing in your responses.

If someone translates the form, what language are the answers stored in?

Whatever language the respondent typed. Chrome documents translating page content and selected text; it says nothing about translating what you type into a page, and Google Forms has no translation step between the browser and the stored response. A short-answer reply typed in Portuguese is stored, and lands in your spreadsheet, in Portuguese.

Can I put two languages in one Google Form?

Yes, by writing both languages into each question — usually the second language in the question's description line. You keep one response set. Google's Edit your form page caps a form at 300 pieces of content, and bilingual questions consume that budget in the same way any other content does.

Can I translate a Google Form on my phone?

Not in Google Forms itself, whose editor assumes the desktop web. Form+ for iPhone and iPad includes a Translate to a new form tool that builds a translated copy of a form you can review, edit and compare against the original before saving it to your Drive.