Google Forms sections: how to add a section header

Last updated September 2026 · ~7 minute read

Short answer: Google's three steps are “In Google Forms, open a form,” “Click Add Section,” and “Name the new section.” The ceiling is documented too — “To organize your form by topic, you can add up to 75 sections.” The part Google's help page never spells out is the important one: a section is not a heading in a long scroll. It is a page, and everyone filling in your form will see it on its own.

That single fact decides whether sections help you or annoy people. Get it straight first, then the rest of this page is mechanical.

Add a section

1. Open the form in the editor.
2. Click Add section in the toolbar that sits beside the questions.
3. Name the new section.
4. Drag your questions above or below the break so each one lands in the right section.

The break is inserted after whichever question is selected, which is the step people skip. If you click Add section with the first question highlighted, you get a one-question opening page and everything else behind it — not the split you meant. Select the last question of the group you want to keep together, then add the break.

Sections count against the same budget as everything else you put on the form. Google's limit is stated plainly: “After you've created a form, you can add and edit up to 300 pieces of content, like questions, descriptions, images, and videos.”

Title and describe the section

A section has two text fields, and both are optional. Google's help page only tells you to name the section, but its Forms API reference is more explicit about what the two fields do: a page break is “a page break. The title and description of this item are shown at the top of the new page.”

So the description is not a footnote — it is the first thing a respondent reads on that page, before any question. Use it for the context that only applies here: “Answer these as the parent, not the child,” or “You will need your policy number for this part.” Instructions you bury under a question get skimmed; instructions in a section description sit alone at the top of a page.

A section is a page

Google's Apps Script reference is unambiguous about what a section is under the hood. The object is called a PageBreakItem, described as “a layout item that marks the start of a page,” and the method that creates one “adds a new layout item that marks the start of a page.”

For the person filling in your form, that means:

• They see one section at a time and move on with Next.
• They can go Back to a previous page and change an answer before submitting.
• Nothing in a later section is visible until they get there — which is exactly why sections are the right tool for a long form and the wrong tool for a three-question one.

Two honest gaps. Google's help documentation does not say anything about how sections affect the progress bar — the bar is a separate form setting, and Google never states how it counts sections, so don't design around an assumption there. And nothing in Google's help pages describes the Back behaviour as a documented guarantee; it is simply what a paged form does.

Where each section sends people next

At the foot of every section there is a destination control. Google's wording: “At the bottom of each section, you can choose which section people go to next.” The options are to continue to the next section, jump to a specific section, or submit the form there and then.

This is not branching. The section destination applies to everyone who reaches the bottom of that page, regardless of what they answered. Sending different people to different places based on an answer is a separate, per-question setting — see conditional logic in Google Forms for that.

When both exist, one wins, and Google says which. From the PageBreakItem reference: “If the previous page contained a MultipleChoiceItem or ListItem with a navigation option, that navigation overrules this navigation.” In plain terms, a per-answer branch beats the section's own destination. If you have set a section to end at “Submit form” and people are sailing past it into later questions, look for a multiple choice or dropdown question on that page with its own destination — that is your culprit.

Moving, duplicating and deleting

Google documents three operations on an existing section, all reached the same way — click the section header, click More, then pick one:

• Duplicate section — copies the section and its questions; what the copy inherits, and what Google never says it inherits, is in duplicate a section in Google Forms.
• Move section — “If you have more than one section, you can change the order,” then “To move a section, click Up or Down.”
• Delete section — three clicks, no warning documented.

That last one is the one people hover over and don't click, and Google's help page is silent on the question everybody has: does deleting the section delete the questions inside it? Google does not say. There is also a fourth operation — merging a section into the one above it, keeping its questions and removing only the break — which Google's help page does not document at all.

On iPhone and iPad, Forms+ answers both. Tap the ⋯ button on a section header and you get Move section, Duplicate section, Merge with above and Delete section. Choose Delete and the confirmation says it in words: “Deleting a section also deletes the questions and responses it contains,” with Merge section up offered right there as the alternative that keeps them. Same real Google Form, same account — the app just refuses to let you find out the hard way.

Forms+ also has a read-only Branching map — “the form's sections and branching logic” — which is the fastest way to see the shape of a sectioned form once it has more pages than you can hold in your head.

How many sections is too many?

Seventy-five is Google's ceiling. It is not advice. Our own view, from watching people fill in forms built this way: the useful range is far lower, and the failure mode is not hitting a limit — it is abandonment.

A section earns its place when it changes something for the respondent: a genuinely new topic, a different person answering, a natural stopping point, or a branch destination that other questions need to jump to. A section that exists only to put a bold heading above three related questions costs a page load and a Next tap and buys nothing; a question description or a title-and-description block does that job without paging. Roughly: if you cannot say what the respondent gains from the page break, delete it and merge the questions up.

Which control do you actually want?

Frequently asked questions

How do I add a section header in Google Forms?

Google's steps are: “In Google Forms, open a form,” “Click Add Section,” “Name the new section.” The title you type becomes the heading at the top of the new page.

How many sections can a Google Form have?

Google documents a ceiling of 75: “To organize your form by topic, you can add up to 75 sections.” The same page notes you can “add and edit up to 300 pieces of content, like questions, descriptions, images, and videos.”

Does deleting a section delete the questions inside it?

Google's help page lists the steps for Delete section but does not say what happens to the questions inside it. Forms+ answers it at the moment you tap: it warns that deleting a section also deletes the questions and responses it contains, and offers Merge section up as the alternative that keeps them.

Is each Google Forms section a separate page?

Yes. Google's developer documentation calls a section a page break — “a layout item that marks the start of a page,” whose “title and description … are shown at the top of the new page.” Respondents see one section at a time with a Next button.

What is the difference between a section destination and branching?

A section destination applies to everyone who reaches the end of that section. Branching applies per answer, on a multiple choice or dropdown question. Where both exist, Google states that “if the previous page contained a MultipleChoiceItem or ListItem with a navigation option, that navigation overrules this navigation.”