Google Forms branching is section-level only
Google Forms does have conditional logic, but only one kind: an answer to a multiple-choice or dropdown question can send a respondent to a different section. There is no way to show or hide an individual question. Plan your form around sections and it works well; try to make three fields on one page appear conditionally and you will end up with a maze.
How branching actually works
The feature is called "Go to section based on answer" and it lives in the three-dot menu at the bottom right of a question. It is available on multiple-choice and dropdown questions only. Once switched on, every option gets its own destination: a named section, "Continue to next section", or "Submit form".
The important thing to understand is that a section in Google Forms is a page, and branching is navigation between pages. It is not visibility. A question you want to be conditional has to live on a page of its own, along with everything else that shares its condition.
The second half of the mechanism is the part people forget. Every section has its own after-section destination, set at the bottom of the section. That is how a branch gets back out. Leave it on the default and a respondent who took branch A will walk straight into branch B's questions after finishing A, because the next page is simply the next page.
Setting it up so it doesn't leak
Three rules cover almost every routing bug people hit in Google Forms.
One deciding question, alone at the end of its section
Routing is evaluated when the respondent leaves the section, not when they answer. Any question placed after the branch question in the same section gets asked no matter what they picked. Give the deciding question its own section, or make it the last item in one.
Give every option a destination
Open the three-dot menu, choose "Go to section based on answer", and set a destination for each option — including the boring ones. Options that should not branch stay on "Continue to next section", but set them explicitly so the intent is visible when you come back to this form in six months.
Set every branch's exit
At the bottom of each branch section, set "After section N" to the section where all paths rejoin, or to "Submit form". This is the single most common cause of respondents seeing questions meant for someone else. Then walk each path end to end in preview — a fall-through is invisible in the editor and obvious the moment you click through it.
Where it stops being enough
None of these are bugs. They are the consequences of routing between pages instead of showing and hiding fields.
Only two question types can branch
Google's own branching documentation limits "go to section based on answer" to multiple choice and dropdown. Checkboxes cannot branch, because a multi-select answer has no single destination. Short answer, paragraph, linear scale, date, time, and file upload cannot branch either. Anything shaped like "if they typed X" or "if they scored below 5" is not expressible.
The smallest unit is a page, not a field
Three optional questions with three independent conditions means three sections plus the routing to rejoin them, on a form that logically has one page of content. Respondents click Next repeatedly through pages holding a single question.
Conditions cannot be combined
One question, one answer, one destination. There is no way to express "show this only if they chose annual and they are in the US". You either pre-compute the combinations as options of a single question, or you duplicate sections per combination.
It grows faster than you expect
Branches multiply. A form with three decision points and three options each is not three sections, it is closer to a dozen, and every edit means re-checking every destination. This is the point at which most people either flatten the form and ask everyone everything, or move it somewhere else.
Getting the most out of section branching
If you are staying on Google Forms — and for an internal survey or a class form you probably should — these habits prevent most of the pain.
- Sketch the paths on paper before building. A five-branch form is far cheaper to fix as a diagram than as sections.
- Name sections after the path they serve ("Branch: existing customer") rather than leaving them as Section 4 of 11.
- Rejoin every path into one closing section, so consent, contact details, and the thank-you exist once instead of once per branch.
- Use response validation — regex, number ranges, required — for anything that is a rule about the answer's format rather than about the path. It is not logic, but it removes the reason you wanted logic.
- Keep the number of decision points to two or three. Past that, splitting into two separate forms is usually cleaner than one branching monster.
- Preview every path from first question to submit after any edit, because a broken destination looks completely normal in the editor.
Section routing versus per-question logic
The same requirements, expressed in both models.
| What you want to do | Google Forms | Zunoform |
|---|---|---|
| Show one question based on one answer | Not supported — the question needs its own section | A show/hide rule on that question |
| Branch on a checkbox, text, or scale answer | Not supported — multiple choice and dropdown only | Any question type can drive a rule |
| Keep everything on one page | Branching requires splitting into sections | Logic works in conversational, single page, and document layouts |
| Route someone to a different ending | Point an option at Submit form | Route to an ending page, with the score or answers interpolated |
| What it costs | Free | Free — 500 responses a month, no card |
Google Forms is free and unlimited, and no table changes that. Logic depth is the trade.
Questions people ask
Can Google Forms show or hide a single question?
No. The only conditional mechanism is "go to section based on answer", which navigates between whole sections. To make one question conditional you have to move it into its own section and route people around it.
Can I branch based on a checkbox question in Google Forms?
No. Branching is limited to multiple-choice and dropdown questions, because a checkbox answer can contain several selections and therefore has no single destination. If you need to branch on a multi-select, restructure it as a single-select question or use a form builder with per-question rules.
Why do respondents see questions from a branch they didn't choose?
Almost always because a branch section has no explicit after-section destination. When a section ends without one, Forms continues to the next section in order — which is usually the next branch. Set "After section" at the bottom of every branch to the rejoin point or to Submit form.
Does conditional logic cost extra in Google Forms?
No. Section branching is free, like everything else in Google Forms. The limitation is capability, not price — and paid Workspace does not extend it.
How many sections is too many?
There is no hard limit, but maintenance is the practical one. Once you pass roughly ten sections, verifying every path after each edit takes longer than the form is worth, and splitting into separate forms or moving to per-question logic saves more time than it costs.
Keep reading
Better forms.
Better data.
Build your first form in under 60 seconds. Free forever for personal use, no credit card required.