At a glance

What you will take away

  1. There is no setting that removes Google Forms branding, and Google's terms forbid hiding it yourself.

  2. Every common workaround either breaks those terms, keeps part of the branding, or puts a third party between your visitor and Google.

  3. The clean answer is to stop showing a Google Form. Show your own form, and keep the Google Sheet it fills.

You cannot remove it, and should not try

You cannot remove Google Forms branding from a form on your website. There is no setting for it, and Google's Terms of Service say: "Don't remove, obscure, or alter any of our branding, logos, or legal notices." What you can do is stop showing a Google Form, put your own form on the page, and still send every response to a Google Sheet you own.

That is not the answer most pages on this query give. They offer a CSS trick, an add-on, or a list of form builders. The first breaks Google's terms, and the others change more than the branding. It is worth knowing what each costs before choosing one.

What the branding actually is

Scroll to the bottom of a public Google Form made with a personal account and you will find Google's footer: the Google Forms wordmark, links to Google's terms and privacy policy, a link to report the form, the warning "Never submit passwords through Google Forms." and the line "This content is neither created nor endorsed by Google."

Most of it is not decoration. The disclaimer and the report link exist because anyone can publish a form on Google's domain, including people impersonating a bank or a school. The password warning exists for the same reason. Google is protecting its own name on a page it hosts but did not write, which is also why it will not let you switch it off.

A form created inside a Google Workspace organisation replaces the disclaimer with a line naming the organisation. That is the only official change to the footer, and the Google Forms wordmark and footer links remain.

The workarounds, and what each one costs

Cropping the embed

The most common trick is to wrap the embedded iframe in a container with a fixed height and hidden overflow, so the footer falls outside the visible area. It is exactly what Google's terms mean by obscuring its branding and legal notices. It is also fragile: the frame's height is fixed, so adding a question, a longer confirmation message or a narrower phone screen moves the footer back into view or cuts off your submit button.

Upgrading to Google Workspace

This is legitimate, and it changes one line: the disclaimer becomes your organisation's name. The Google Forms wordmark, the footer links and Google's page layout all stay. If what bothers you is the words "neither created nor endorsed by Google", it helps. If what bothers you is that the form looks like Google rather than like your site, it does not.

Add-ons that redraw the form

Some Workspace add-ons, Formfacade being the best known, redraw your form's questions on a page of their own and advertise replacing Google's branding with yours. That works, and it is within the rules because Google's page is no longer the one being shown. Be clear about what you now depend on: a third party's page sits between your visitor and your form, and your form's appearance, availability and file handling are that product's decisions.

Posting your own HTML to the Google Form

A hand-built HTML form can post its answers directly to a Google Form's response address, using each question's internal entry. ID as the field name. The branding is gone because Google's page never loads. The method is not documented by Google, it gives your page no confirmation that anything was saved, it breaks silently when someone edits a question, and it cannot carry a file, because a file upload question needs the respondent signed in to Google.

What to do instead: show your own form

If the goal is a form that looks like your website and belongs to it, the lasting fix is to make it part of your website. Write the form in HTML, style it with your own stylesheet, and post it to a service that writes each submission into your Google account. Webtzm is one; the response lands as a row in a Google Sheet in your own Drive, exactly where a Google Form would have put it.

<form class="enquiry" action="https://webtzm.com/submit/YOUR_FORM_ID" method="post">
  <label for="name">Name</label>
  <input id="name" name="name" type="text" autocomplete="name" required>

  <label for="email">Email</label>
  <input id="email" name="email" type="email" autocomplete="email" required>

  <label for="message">Message</label>
  <textarea id="message" name="message" rows="5" required></textarea>

  <button type="submit">Send</button>
</form>

<style>
  .enquiry { display: grid; gap: 0.5rem; max-width: 32rem; font: inherit; }
  .enquiry input, .enquiry textarea {
    font: inherit; padding: 0.625rem 0.75rem;
    border: 1px solid #c9ccd1; border-radius: 6px;
  }
  .enquiry button {
    justify-self: start; margin-top: 0.5rem; padding: 0.625rem 1.25rem;
    font: inherit; color: #fff; background: #1f4ed8; border: 0; border-radius: 6px;
  }
</style>

Change the colours and the font to your own and the form is indistinguishable from the rest of the page, because it is the rest of the page. Every field needs a name; that is what the browser sends and what becomes the column header in the Sheet.

The one screen that is not yours

Be precise about this, since branding is the whole point. Webtzm adds no badge, logo or footer to your form. But a plain HTML post like the one above makes the browser leave your page when the form is sent, and it lands on a Webtzm confirmation page. To keep the visitor on your own page from start to finish, add the small handler your setup panel offers: it sends the form in the background and writes a short status line into an element you place inside the form, styled by your own stylesheet.

The form's origin is also yours to control. Each workflow lists the exact hostnames allowed to submit to it, so a copy of your form on somebody else's page is refused. Allowed domains explains which hostname to add on each common platform.

Moving an existing Google Form across

  1. List the questions. Each Google Forms question becomes one HTML field: short answer to an input, paragraph to a textarea, multiple choice to radio buttons sharing a name, checkboxes to checkboxes sharing a name, dropdown to a select.

  2. Build and publish the form on your page, and add that page's hostname to the workflow's allowed domains.

  3. Send one test with made-up values and confirm it arrives as a new row. The contact form tutorial walks through this end to end.

  4. Close the Google Form rather than deleting it. Its responses and linked Sheet stay where they are, and anyone with the old link sees that it no longer accepts responses instead of an error.

The new responses go to a new Sheet, with one column per field name plus a record ID and two timestamps. If you want the old and new responses side by side, copy the old rows across once; do not point both at the same tab.

Stick with Google Forms if…

  • The people answering expect Google. Staff, students and club members filling in an internal form do not mind the footer and often trust it more.

  • Your organisation's name in the footer is enough. A Workspace form already says who made it, which answers the complaint most people actually have.

  • Your site is a Google Site. Sites cannot host a form like the one above, so a Google Form is the right tool there.

  • You do not want to maintain markup. A Google Form needs nothing from you once it is published. Your own form is a file you edit when a question changes.

Replace it when the form is part of your brand: a customer enquiry, an application, a booking. That is where another company's name at the bottom of the page costs you something, and where the fix is not hiding it but no longer showing it.

Try the pattern

Show your own form and keep the Google Sheet behind it.

Publish one form in your own design and see its first submission arrive as a row in a Sheet you own.

Build your first Webtzm delivery  →

Frequently asked questions

Can I remove the Google Forms footer?

No. There is no setting for it, and Google's Terms of Service say not to remove, obscure or alter Google's branding, logos or legal notices. That includes hiding the footer by cropping an embedded form.

Does Google Workspace remove Google Forms branding?

Partly. A form made inside a Workspace organisation replaces the disclaimer line with the organisation's name. The Google Forms wordmark, the footer links and Google's layout stay.

Is it allowed to crop the embedded form so the footer is hidden?

It is the kind of obscuring Google's terms forbid, and it is fragile. The frame has a fixed height, so a new question or a narrow phone screen brings the footer back or cuts off the submit button.

How do I get a form without Google branding that still saves to Google Sheets?

Put your own HTML form on your page and post it to a service that writes each submission into your Google account. The form carries only your design, and each response still arrives as a row in a Sheet you own.

Does Webtzm add its own branding to my form?

No badge, logo or footer is added to your form. A plain HTML post does move the visitor to a Webtzm confirmation page, so use the handler from your setup panel to keep them on your own page.