Remove Google Forms branding: what you can and can't change

We loaded two public Google Forms on 28 September 2026, one from a personal Gmail account and one from a Google Workspace organization, and read the footer text directly. Below the Submit and Clear form buttons, both show the line "Never submit passwords through Google Forms." Then the two differ. The personal-account form says "This content is neither created nor endorsed by Google", with links to Google's Terms of Service and Privacy Policy. The Workspace form says "This form was created inside" followed by the organization's name.

Both then show "Does this form look suspicious? Report", the Google Forms wordmark, and a small help menu with options such as contacting the form owner. That whole block is what people mean by the footer.

Two other things carry Google's name. The address is docs.google.com/forms/..., or forms.gle if you shortened it, and anyone can see it before the page loads. The confirmation screen after submitting is also a Google page. Your message appears on it, but the footer and styling are Google's.

Google doesn't publish a reason, but the text explains itself. "Never submit passwords" and the Report link are anti-phishing measures. Google Forms is free, anyone can publish one, and a form that copies a bank or university login page is an obvious risk. The footer tells every respondent that the page belongs to whoever made the form, not to Google, and gives them a way to report it.

That is also why it isn't sold as a premium feature. Most form builders treat their badge as marketing and charge you to remove it. Google's footer is a safety notice, so no price removes it. Expect it to stay.

No. On a Workspace form, "neither created nor endorsed by Google" becomes "This form was created inside [organization]". Some people find that more professional because your company name is in the footer. The password warning, Report link and Forms wordmark stay, and there is no admin setting to remove them.

Workspace forms can also be restricted to people in the organization, which asks respondents to sign in with a Google account. That adds more Google interface, not less. Workspace's custom service URLs (such as mail.yourcompany.com) cover services like Gmail, Calendar, Drive and Groups. They send visitors on to the normal Google address and can't give an individual form a branded address. Our guide to a Google Forms custom domain covers that in detail.

This is the most common advice in forums, and it rests on a misunderstanding of how browsers isolate pages. Each workaround is covered below.

When you embed a Google Form, your page holds an iframe, and the form inside it is served from docs.google.com. Browsers enforce the same-origin policy. A page on yoursite.com can't read or restyle the contents of a frame from another origin. A rule like .footer { display: none } on your site stops at the iframe's edge. It is a browser security rule, not a Google setting, and you can't opt out of it.

Stylus-type extensions and injected user scripts do hide the footer, but only in the browser that runs them. Your respondents load the unmodified form. This trick makes screenshots look clean and changes nothing for anyone else.

Some tutorials suggest making the iframe exactly tall enough to cut the footer off. It breaks quickly. The form's height changes with screen width, validation messages, long answers and each new section, so a fixed crop either cuts off questions or lets the footer back in. On a phone the iframe usually scrolls inside itself, so respondents can still reach the footer. The result is an unreliable form that hides a phishing warning, and we wouldn't recommend it.

An older trick copies the form's field names and posts answers from your own HTML form to Google's response endpoint. Google doesn't document this. You lose Google's validation, sections, file uploads and sign-in handling, and one change to the form's fields quietly breaks submissions. Once you have built and hosted your own form, the only Google piece left is the spreadsheet, and a form builder with a Google Sheets integration handles that properly.

For many forms, nobody notices. Internal surveys, class quizzes, team retros, volunteer rosters and RSVP lists go to people who already know who sent them. The form is free with unlimited responses, and a footer is easy to ignore. Paying to remove branding from a form only your colleagues see isn't worth it.

The footer starts to matter when the form is someone's first impression of you: a client intake on a proposal, lead capture on a landing page, a paid registration or an order form. There, "Never submit passwords" and a Google disclaimer sit right under the button you want pressed, and the form looks improvised. That is a conversion reason to switch, and the right reason to pay for branding removal.

Zunoform removes its own badge on Pro ($14.99/month or $149.99/year), and there is no Google-style safety footer. Ending screens are pages you write, and redirect after submit works on every plan. If you also need the form on your own address, a custom domain is Business-only ($24.99/month). The Google Forms importer rebuilds an existing form's questions, so you don't have to retype them.

Where it doesn't fit: Zunoform's Free plan still shows a small "Powered by" badge and caps you at 500 responses a month. Google Forms, Tally and Youform have unlimited free responses. If your form is internal and the footer doesn't bother anyone, Google Forms is the cheaper, simpler choice. Stay on it.