Google Forms multiple pages: it is called a section

Last updated September 2026 · ~10 minute read

Short answer: Google Forms does support multiple pages, but nothing in the product is called that. The control is Add section, and a section is a page — Google's own developer reference calls the same object a PageBreakItem, “a layout item that marks the start of a page.” If you have been searching the help centre for “pages” and finding nothing, that vocabulary mismatch is the whole reason.

This page is the translation between the two words, and then the part almost nobody writes down: what a page break actually costs you once your form has more than one of them.

One feature, two names

Google documents this thing twice, in two vocabularies, and never introduces them to each other.

In the Google Docs Editors Help centre, the word is section. The steps are three lines long — “In Google Forms, open a form,” “Click Add Section,” “Name the new section” — under the promise that “sections can make your form easier to read and complete.” Nothing there says the word page.

In the Apps Script reference, the same object is a PageBreakItem: “A layout item that marks the start of a page.” The method that creates one, addPageBreakItem(), “adds a new layout item that marks the start of a page.” Not a metaphor, not an implementation detail leaking out — that is Google's own name for what the Add section button inserts.

So: section = page = page break. One object, three labels depending on which Google property you are reading. Everything below is true of all three, and the mechanics of inserting, naming, moving and deleting one live on our section headers guide rather than here.

What a page break does to the person filling in your form

Three things change the moment you insert your first one.

• One section per screen. Everything between one section header and the next is a page, shown on its own. A respondent cannot see what is coming next, and cannot skim the whole form before starting.
• A Next button replaces Submit at the foot of every page except the last. Your five-question form is now a five-question form plus a click.
• The boundary becomes a decision point. Google's wording, from Show questions based on answers: “At the bottom of each section, you can choose which section people go to next.”

That third one is the reason pagination matters beyond looks. Branching in Google Forms is not attached to a question and it is not attached to a screen — it is attached to a section boundary. No page breaks means no places to branch. If you want a form that behaves differently for different people, the sections come first and the logic follows; see conditional logic in Google Forms for how the per-answer version works.

What splitting a form across pages costs you

Most guides stop at “sections make long forms less intimidating.” True, and incomplete. Here are the five costs, each one grounded in something Google actually publishes — or, twice, in something Google conspicuously does not.

1. Two ceilings, and they are not the same ceiling

Google's Edit your form page states both: “To organize your form by topic, you can add up to 75 sections,” and “you can add and edit up to 300 pieces of content, like questions, descriptions, images, and videos.”

The second is the one that bites. Sections are not free of the content budget — a section header carries a title and a description, and those are pieces of content. Paginate a 200-question form aggressively and you can arrive at the 300 ceiling well before you arrive at the 75-section one, having spent a chunk of your budget on furniture rather than questions.

2. Section navigation can be silently overruled

You can set where a page sends everyone next. You can also set where a particular answer sends one person next. When both exist, one loses, 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 language: a per-answer branch on a multiple choice or dropdown question beats the end-of-section destination set on the page it leads to. This is the single most common “my Google Form logic is broken” report, and it is not a bug. If you set a section to end at Submit form and people keep sailing into later questions, stop re-checking that setting — it is being overruled, not ignored. Go back one page and look for a multiple choice or dropdown question carrying its own destination.

Note the direction, too: the overrule flows forward from the previous page. The more pages you add, the more previous-page settings exist that can quietly beat the one you are currently editing. Section navigation takes the two layers apart, including the one page where neither destination does anything.

3. Shuffle and sections: Google's help centre never says

If you turn on Shuffle question order, the obvious question on a paginated form is whether questions can cross a page break. Google's help centre does not answer it. The only thing that page says on the subject is a warning: “If you want your questions to appear in a specific order, you should not shuffle your questions.”

There is a statement of scope, and — fittingly for this page — it is in the other vocabulary. The Apps Script Form reference describes setShuffleQuestions(shuffle) as “Sets whether the order of the questions on each page of the form is randomized.” Read literally, that confines the shuffle to within a page. It is the closest Google comes to answering the question, and you will only ever find it if you already know that “page” means “section.”

We are flagging rather than asserting, for two reasons: it is a developer reference describing a setter, not a statement about the responder experience, and the help centre — where the setting actually lives — stays silent. If the ordering of a paginated quiz matters to you, duplicate the form, switch shuffling on and open the live link a few times. Thirty seconds of your own evidence beats any sentence on this page. Our shuffle question order guide covers the setting itself.

4. The progress bar becomes a promise you cannot keep

Once a form has pages, people expect a progress indicator, and Google offers one. What Google never publishes is what the bar measures on a sectioned form — pages turned, questions answered, or something else. On a branched form, where different respondents walk paths of different lengths, that gap gets sharper still. We took that one apart separately: the Google Forms progress bar.

5. Editing branching can cost respondents their drafts

A paginated form is a form people leave halfway through and come back to. Google's own warning is that if you make changes to branching logic in a form, “you may lose access to certain pages of a form” — which means the edits you make to a live paginated form are not free for the people mid-way through it. The conditions, and the 30-day draft window they sit inside, are on our autosave and drafts guide.

When to paginate, and when not to

This part is our judgement rather than Google's, so we will be plain about it.

Paginate when the break does work. Three cases qualify. A genuinely long form, where thirty questions in one scroll reads as a wall and six pages of five reads as a sequence. Logically distinct blocks — “about you,” then “about your order,” then “anything else” — where a respondent's frame of mind actually changes between them. And branching, which as above has nowhere to attach without a section boundary.

Do not paginate for tidiness. A page break to put a bold heading over three related questions costs a page load and a Next tap, spends content budget on a title and description, adds a boundary that some previous page's navigation can now overrule, and buys the respondent nothing. A title-and-description block, or a description on the first question of the group, does that job without paging anybody.

The test we would apply to every break in your form: say out loud what the respondent gains from this page turn. If the honest answer is “it looks neater in the editor,” that is a benefit to you, not to them — merge it up.

Which control do you actually want?

Paginating a form on iPhone or iPad

Forms+ is a native client for your real Google Forms, on your own Google account, so the sections you add are page breaks on the same form a respondent is filling in — not a copy. Sections get the same operations you would expect from the web editor, including Move section for reordering pages and Merge with above for removing a break while keeping its questions. The end-of-section destination is edited where you would expect it, under an After section heading offering Continue to next section, a specific section, or Submit form.

The one thing worth calling out for a multi-page form specifically is the read-only Branching map — “Visualize the form's sections and branching logic.” It draws one card per section in form order down a spine, a Submit terminal at the end, and a curved edge for every explicit jump, numbered so that each curve pairs with the rule inside the card that causes it. On a form with more pages than you can hold in your head, that picture is how you find the overruling branch from cost 2 above in seconds rather than by clicking through every section in turn.

Frequently asked questions

Does Google Forms have multiple pages?

Yes, but there is no feature with that name. The help centre calls the control Add section, and each section is a page: respondents see one at a time and move on with Next. Google's Apps Script reference is the place that says so plainly, describing a PageBreakItem as “a layout item that marks the start of a page.”

What is the difference between a section and a page break?

Nothing. They are two names Google uses for the same object. Section is the word in the Google Docs Editors Help centre and in the editor interface; PageBreakItem is the word in the Apps Script reference, where addPageBreakItem “adds a new layout item that marks the start of a page.” If you searched for “multiple pages” and found nothing, this vocabulary gap is why.

How many pages 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 help page also caps total content at 300, stating that you can “add and edit up to 300 pieces of content, like questions, descriptions, images, and videos.” Section titles and descriptions count toward that 300.

Does shuffling questions move them between sections?

Google's help centre never says. Its only statement of scope is in the Apps Script reference, where setShuffleQuestions “sets whether the order of the questions on each page of the form is randomized” — wording that confines the shuffle to a page. The help centre page that carries the setting says only that “if you want your questions to appear in a specific order, you should not shuffle your questions.” On a paginated quiz, test it on a copy of your own form rather than trusting either reading.

Why is my form ignoring the next section I set?

Look for a multiple choice or dropdown question on the page before it that has its own destination. Google's Apps Script reference states that “if the previous page contained a MultipleChoiceItem or ListItem with a navigation option, that navigation overrules this navigation.” A per-answer branch beats the end-of-section destination, so the section setting you edited is being overruled rather than ignored.