The Google Forms progress bar

Last updated September 2026 · ~8 minute read

There is one switch, and it lives at Settings › Presentation › “Show progress bar”. Turning it on takes five seconds. The part nobody writes about is that Google has never published what the bar measures — not in the help centre, not in the Apps Script reference, not in the Forms API. That silence is the whole reason this page exists, because it changes what you can honestly promise a respondent on a sectioned or branched form.

Most guides to this setting are four lines long: here is the toggle, enjoy your progress bar. That is accurate and not very useful. The interesting question is what the bar is counting, and the honest answer turns out to be that you cannot know from anything Google publishes.

How we checked

We went looking for a definition rather than a toggle. The pages we read: Google Docs Editors Help Edit your form, How to use Google Forms, Create & grade quizzes with Google Forms, Publish & share your form with responders and Use Google Forms with a screen reader; the Google Workspace Learning Center pages Get started with Forms, Create a form and Tips to customize your forms; the Apps Script Class Form reference; and the Google Forms REST API v1 forms reference. Between them they describe where the setting is and what the setter is called. Not one of them says what the bar represents.

Turning it on

Open the form, click Settings at the top, click the Down arrow next to Presentation, and switch on Show progress bar. That is the entire operation — there is no second control, no configuration, nothing to calibrate. The other switches under the same Down arrow are mapped in our guide to the Google Forms presentation settings.

Two footnotes on the label itself. Google's Edit your form page gives you the path in those words (“At the top of the form, click Settings. Next to ‘Presentation,’ click the Down arrow.”) but then lists only Shuffle question order and the autosave option underneath it — the progress bar is not named there. The one Google help page we found that names the control is the screen reader guide, which lists “Show progress bar” first under “Manage presentation” in Settings. So the label is current; it is just barely documented. That help page carries several things no other Google page does, which is why it has a guide of its own here.

If you automate your forms, Apps Script has the switch as well. setProgressBar(enabled) — “Sets whether the form has a progress bar.” — and hasProgressBar() — “Determines whether the form displays a progress bar.” Those two sentences are the most precise thing Google publishes about this feature anywhere, and you have now read all of it.

Worth knowing if you build integrations: the Forms REST API cannot touch it. The v1 FormSettings object carries exactly two fields, quizSettings and emailCollectionType. The word “progress” does not appear in the reference. Apps Script is the only programmatic route Google offers.

What the bar actually measures: Google does not say

We expected to find a sentence like “the bar reflects how many sections remain” somewhere in the help centre. There isn't one. Across all ten references above, Google documents the existence of the setting and never once defines its unit.

Plenty of third-party guides fill the gap confidently — most say the bar tracks sections or pages rather than individual questions. That is a plausible reading and it may well be exactly right. But we cannot point you at a Google page that states it, so we are not going to assert it here, and more to the point your form's copy should not assert it either. An undocumented behaviour is one Google is free to change without a changelog entry, and unlike a colour or a label, this one silently makes your wording wrong rather than ugly.

The same gap covers the adjacent questions. Whether the bar renders at all on a form with a single section, whether it behaves differently once Make this a quiz is on, and whether it appears on the confirmation page after submission are all undocumented. If any of those matter to you, open your own live form link and look — a thirty-second check on the real thing beats any claim on a page like this one.

Why that matters on a sectioned or branched form

On a sectioned form, the practical consequence is that you cannot tell a respondent what “halfway” means. If your section two holds one question and section three holds twenty, a bar at 50% is describing something — but you do not know whether it is describing the work done or the pages turned, and those are wildly different promises. You can show the bar; you just cannot narrate it.

On a branched form — one using “Go to section based on answer” — it gets sharper. Every respondent walks a different length of path. A route through three sections and a route through nine are the same form. A bar that looks perfectly honest when you test the short route can jump forward, stall, or arrive at the end far sooner than the fill suggested for somebody who answered differently. Nothing is broken when that happens; you are simply seeing a single indicator trying to describe several different journeys.

Two things follow, and they are the practical payload of this page:

• Do not promise a number in your copy. “Two more pages to go” and “you're nearly there” are claims you cannot keep on a branched form, and they read as a broken promise rather than a vague one when the bar disagrees.
• Be careful about leaning on it to reduce drop-off. The received wisdom is that progress indicators reduce abandonment. That is a reasonable expectation on a long linear form. On a branched one, an indicator that misrepresents the remaining work can do the opposite, and you will not see which of the two happened in your response data.

Should you turn it on?

This part is our view rather than Google's, and it comes down to the shape of your form.

A long linear form benefits. Six sections, everyone walks the same six, the bar is a truthful signal however it is computed, because every respondent's denominator is the same. Turn it on.

A branched form deserves caution. Not a prohibition — many branched forms show the bar and nobody complains. Just do not build your wording, your instructions, or your abandonment strategy on top of it, and test the longest and shortest routes through your own form before you send it.

A short or single-section form gains little either way. There is no meaningful journey to describe, and the setting is not worth deliberating over.

Setting it from an iPhone

Forms+ is a native iPhone and iPad client for your real Google Forms, and its form settings screen carries the same switch — Show progress bar, alongside Shuffle question order and Show link to submit another response — on the actual form in your Drive, not a copy of it. If your form branches, the app's branching map draws the routes through your sections as a map, which is a faster way to find your shortest and longest paths than clicking through them one answer at a time.

Frequently asked questions

Where is the progress bar setting in Google Forms?

Open the form, click Settings at the top, click the Down arrow next to “Presentation”, and turn on “Show progress bar”. Google's own “Edit your form” help page gives that path to the Presentation section, and the screen reader guide lists “Show progress bar” under “Manage presentation” in Settings.

Does the Google Forms progress bar count questions or sections?

Google does not say. We searched the Google Docs Editors Help pages for editing a form, using Forms, quizzes and screen readers, the Workspace Learning Center customisation pages, the Apps Script Form class reference and the Forms REST API reference. Every one of them documents that the switch exists; none of them documents what the bar measures. Many third-party guides state that it tracks sections rather than questions, and that may well be right, but no Google page we could find says it.

Does the progress bar appear on a one-page form?

Google does not document the behaviour either way. The setting is a plain on/off switch with no stated dependency on how many sections a form has, so the only reliable way to know what your respondents see on a single-section form is to open the live form link yourself and look.

Can I set the progress bar with the Google Forms API?

Not with the Forms REST API. Its FormSettings object carries only quizSettings and emailCollectionType — there is no progress bar field anywhere in the v1 reference. Apps Script is the only Google-published interface that exposes it, through Form.setProgressBar(enabled) and Form.hasProgressBar().

Can I change the colour of the Google Forms progress bar?

There is no documented control for it. Apps Script offers only an on/off setter, the REST API has no progress bar field at all, and the Presentation settings expose a single switch. The bar takes the form's theme rather than a colour you set for it.