Google Forms conditional logic, section by section

Google calls the feature "Go to section based on answer". A section in Google Forms is a page: respondents see one section at a time and press Next to move on. Branching is therefore navigation between pages, not visibility of individual questions. A question you want to be conditional has to sit on its own page, together with everything else that shares its condition.

There are two controls. The first is on the question: each option of a multiple-choice or dropdown question gets a destination, which can be any section, "Continue to next section" or "Submit form". The second is at the bottom of every section: "After section N", which decides where people go when that section has no branching question, or when they leave a branch.

Google's Apps Script documentation spells out the timing: page navigation happens after the respondent completes the page that contains the option. So if you put three more questions under the branching question in the same section, everyone answers them before the jump takes effect.

The limits below come from the model itself, not from a missing setting. Paid Google Workspace plans use the same Forms editor and do not add field-level logic.

Google's dedicated branching article says "Go to section based on answer" is only available for multiple-choice and dropdown questions. The logic behind that is sound: a checkbox answer can hold several selections, so there is no single destination. Confusingly, Google's separate question-types article currently says checkboxes can send respondents to a section too. We could not reconcile the two pages, so check the three-dot menu on a checkbox question in your own editor before you plan around it.

Short answer, paragraph, linear scale, rating, date, time, file upload and both grid types have no branching option. You cannot express "if they typed a ZIP code starting with 94", "if their budget is over 5,000" or "if they rated us below 7". Response validation can reject answers that break a rule, but it cannot route anyone.

Each option has exactly one destination, decided by exactly one question. There is no AND or OR. "Show the invoicing questions only to business customers in the EU" needs either a combined question or duplicated sections.

Google Forms has no show-or-hide rule for one question. That is why "google forms conditional questions without sections" is such a common search: the honest answer is that it is not possible natively. Each conditional question needs a section, which is how a one-page form turns into eight pages of one question each.

Natively you cannot, but several workarounds get you close. None of them gives true field-level logic, so pick the one whose cost you can live with.

If you need "business AND in the EU", ask a single multiple-choice question with the combinations as options: "Business, EU", "Business, outside EU", "Personal". Each option routes to its own section. It works well up to about six options and reads badly beyond that.

Replace the 0–10 scale with multiple choice in bands, or add a short categorising question after an open one ("Which best describes your issue?"). You lose some precision in the data, which is often an acceptable trade for routing.

If you already know who the respondent is, skip the branch entirely. Google's pre-fill feature (More, then "Pre-fill form") builds a link with answers already filled in, so you can send customers one link and prospects another. For very different audiences, two short forms feeding the same Google Sheet are easier to maintain than one form with twelve sections.

Apps Script can build or change branches while you edit (for example, creating choices that jump to a page), but it runs in the editor, not in the respondent's browser. It cannot show a question at the moment someone answers. Add-ons that restyle Google Forms work around this by serving their own version of the form, which means respondents are no longer on the Google Forms page you built.

Section branching is the right tool for internal surveys, class forms and most event sign-ups: two or three decision points, routing on a single choice. It stops fitting when one of these is true.

You need to branch on something other than a single choice, such as a number, a score, a text match or a multi-select. You need two conditions at once. You want a short form to stay on one page, or in a one-question-at-a-time layout, instead of splitting into many sections. Or the maintenance has got out of hand: past roughly ten sections, re-checking every destination after each edit takes longer than building the form did.

At that point the choice is a form builder whose logic is attached to questions rather than pages. Several do this, including Typeform, Jotform, Tally and Zunoform. Compare them on the logic details that matter to you (condition operators, AND/OR, what happens on a single-page layout) rather than on the word "logic" in a feature list.

Zunoform's logic rules are attached to questions, on every plan including Free. A rule tests conditions on any answered question with operators such as is, contains, greater than, less than and is empty, combines them with all (AND) or any (OR), and then jumps to a specific question, skips, ends the form or redirects. The same rules run in the conversational, single-page and document layouts. Zunoform can also import an existing Google Form so you don't rebuild it by hand.

Where it doesn't fit: if your branching is two or three single-choice decisions, Google Forms already does it for free with unlimited responses, and there is no reason to move. Zunoform's Free plan is capped at 500 responses a month, and a large internal survey inside Google Workspace is better off staying where your colleagues already sign in.