Remove This Application Was Created By A Google Apps Script User Free -

Only locally via browser extensions. The server-side security dialog remains.

If you’ve built a Google Apps Script project and shared it with others, you may have noticed an authorization screen that says:

“This application was created by a Google Apps Script user free”

This message appears because your script hasn’t been verified by Google. It’s Google’s way of warning users that the app comes from an unverified developer (you, the free user).

While you cannot remove this message entirely for unverified apps, you can replace it with your own branding and remove the “free user” label by completing Google’s OAuth verification process.

If you don’t want to go through verification, you can:

Yes, you can remove “This application was created by a Google Apps Script user – Free.”
No, there’s no secret code or CSS hack to hide it permanently.
The real solution is a Google Workspace account – and for anyone serious about building tools on Google’s ecosystem, you probably should have one anyway.

Stop looking like a hobbyist. Upgrade, redeploy, and watch that message disappear.

Have you successfully removed the banner? Still stuck? Drop a comment below – I help people migrate scripts to Workspace accounts regularly.

Alex was a freelance developer who lived by a simple rule: automate everything

. One afternoon, while scouring a forum for productivity hacks, he found a legendary "Life Dashboard" script designed to sync tasks, emails, and calendars into one seamless interface [1, 2].

He spent hours customizing the code. It felt perfect—until he hit "Deploy." A glaring, grey banner appeared at the top of his screen:

"This application was created by a Google Apps Script user." Only locally via browser extensions

To a perfectionist like Alex, it was an eyesore. It felt like leaving a price tag on a designer suit [1]. He tried every trick he knew: He dove into the , trying to hide the container [1, 3]. He attempted to use

to mask the source, but the banner just followed him like a shadow [1].

He even tried writing a second script to "delete" the banner from the first one—a digital snake eating its own tail [1, 2].

Deep in a developer thread, he finally found the "secret." The banner wasn't a bug or a mistake; it was Google's security seal

[1, 3]. It existed to let users know the app wasn't an official Google product, preventing phishing and keeping the ecosystem safe [1].

Alex realized that removing it via code was nearly impossible because it was injected at the server level

, far above his script's pay grade [1, 3]. The only way to get a "clean" look was to upgrade to a Google Workspace Enterprise account or deploy the project as a Google Cloud

web app—options that cost money he didn't want to spend [3].

He sat back and looked at the banner again. Instead of a flaw, he started seeing it as a badge of honor

. It was proof that he had built something from scratch using nothing but logic and a free tool [1, 2]. He stopped trying to hide it and shared the dashboard with his friends, banner and all.

As it turns out, no one else cared about the grey bar. They were too busy being amazed that the app actually worked [1, 2]. of Google Apps Script or see the workarounds for creating a custom UI without the banner?

To remove the "This application was created by a Google Apps Script user" banner from your web app, you need to transition the project from a personal account to a professional environment. If you’ve built a Google Apps Script project

Here is a guide on how to get a clean, professional look for your Google Apps Script projects. How to Remove the Google Apps Script Header

The "Free" version of Google Apps Script automatically attaches this banner as a security measure to let users know the script isn't an official Google product. To remove it, you have two primary options: 1. Upgrade to Google Workspace

The most direct way to remove the banner is to use a Google Workspace account (formerly G Suite) instead of a standard @gmail.com account.

The Rule: If you are part of a Google Workspace organization and you deploy the web app to be accessed only by users within your domain, the banner is usually hidden.

External Users: If you share the app with people outside your organization, the banner may still appear to them for security reasons. 2. Use a Custom Frontend (The "Proxy" Method)

If you don't want to pay for Workspace, you can hide the banner by using Google Apps Script as a back-end API rather than the front-end host.

How it works: Host your HTML/CSS on a platform like GitHub Pages, Vercel, or Netlify.

The Connection: Use JavaScript fetch() or google.script.run to send data to your Apps Script (deployed as a Web App).

The Result: Since the user is visiting yourwebsite.com instead of ://google.com, the Google banner never triggers. 3. Embed in a Google Site

In some specific configurations, embedding your Web App within a Google Site (google.com) can mask the header. However, this is less reliable than the previous methods as Google frequently updates their iframe security policies. Important Security Note

Google keeps this banner to prevent "phishing"—where bad actors create fake login pages that look like Google services. If you remove the banner using a custom frontend, ensure you are still following Google's OAuth verification processes if your app handles sensitive user data.

Removing the "This application was created by a Google Apps Script user" banner is a common goal for developers who want to provide a professional, white-labeled experience for their users. While this footer is a security feature designed by Google to prevent phishing, there are several legitimate ways to minimize its visibility or remove it entirely depending on how you deploy your project. Understanding the Banner’s Purpose “This application was created by a Google Apps

Before attempting to remove the notice, it is important to understand why it exists. Google automatically attaches this disclaimer to any Web App or script-based UI that is not part of a verified Google Workspace domain or a published Google Cloud project. It serves as a warning to end-users that the application is third-party and not officially vetted by Google. Method 1: Upgrade to a Google Workspace Account

The most straightforward way to remove the "created by a user" branding is to use a professional Google Workspace (formerly G Suite) account rather than a personal @gmail.com account.

When you deploy a Web App within a Workspace domain and set the access permissions to "Anyone within [Your Domain]," the banner is typically removed for internal users. This is because Google assumes a level of trust within a managed organizational environment. However, if the app is shared with external users outside the domain, the banner may reappear to protect those external parties. Method 2: Link to a Standard Google Cloud Project

By default, Apps Script projects use a "Default" Google Cloud Platform (GCP) project. To gain more control over the branding and consent screens, you can switch to a "Standard" GCP project. Create a project in the Google Cloud Console. Go to "Project Settings" and copy your Project Number.

In your Apps Script editor, go to Project Settings and click "Change Project." Enter your Project Number. Configure your OAuth Consent Screen in the GCP Console.

While this doesn't always instantly vanish the footer, it allows you to submit your application for "Verification." Once Google verifies your app, the "unverified app" warnings disappear, and the footer becomes much less intrusive. Method 3: Use a Custom Domain with an Iframe Wrapper

If you are hosting the script as a Web App, you can embed it into your own professional website using an iframe. This doesn't technically delete the code from the script's source, but it places the application within your own branded environment.

To do this, ensure your script's HtmlService is set to allow embedding:

output.setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL);

By wrapping the script in a container on your own domain (e.g., yourdomain.com), the user’s focus remains on your URL and your website’s header/footer, making the Google disclaimer at the very bottom of the frame feel like a minor technical footnote rather than a primary branding element. Method 4: Transition to AppSheet

If your Apps Script is primarily used for data entry or internal tools, consider migrating the logic to AppSheet, Google’s no-code app building platform. AppSheet provides a significantly more professional interface and does not include the "Apps Script user" footer. Since AppSheet is now included in most Workspace tiers, it offers a more "enterprise-ready" look and feel for your tools without the script-specific baggage. Important Security Note

You should never attempt to use CSS or JavaScript hacks (like DOM manipulation) to hide the Google footer programmatically. Google’s security headers often block such attempts, and more importantly, bypassing security notices can lead to your script being flagged for "Terms of Service" violations, resulting in the permanent suspension of your project or your entire Google account.

For a truly "free" experience that looks professional, focus on clean UI design within your HtmlService files. A well-designed, functional application will often earn the user's trust regardless of the small disclaimer at the bottom of the page.

Here’s a short article explaining how to remove the phrase “This application was created by a Google Apps Script user free” from your Google Apps Script project’s authorization screen.