Remove This Application Was Created By A Google Apps Script User Free Verified · Popular
There is no direct "free" button or setting to remove the "This application was created by a Google Apps Script user" banner within the Google Apps Script editor. This banner is a security feature automatically applied to web apps and deployments that are not formally verified.
However, you can use several workarounds to hide or bypass this warning: Professional & Official Methods
Embed in Google Sites or External Webpages: The banner is often hidden when you embed the script's URL as an within a Google Site or your own website.
Google Workspace Accounts: If you are part of a Google Workspace organization, users within your same domain generally will not see this banner when accessing your scripts.
Create an Add-on: Converting your script into a verified Google Workspace Add-on removes the banner entirely for all users, though this requires a more formal development and review process. Technical Workarounds
Host the HTML Yourself: You can host your app's frontend HTML/JS on a service like GitHub Pages and call your Google Apps Script as a backend API. This prevents the banner from appearing because users are not viewing a script.google.com URL directly.
Browser Extensions (Developer Only): For personal use or public displays, you can use browser extensions like uBlock Origin or custom CSS injectors to set the banner's container (often with an ID like warning) to display: none;. Note that this only hides the banner for you, not other users.
The light-blue warning banner stating "This application was created by a Google Apps Script user" is a security feature automatically added by Google to all web apps deployed via Apps Script
. There is no official "button" to turn it off for free consumer accounts, but you can bypass or hide it using these methods: Google Issue Tracker 1. Embed in a Website or Google Site The most common legitimate way to remove the banner is by your web app URL into another page. Google Sites: When you embed a script into a Google Site , the banner is typically suppressed for users. External Iframe: You can host a simple HTML page on a platform like GitHub Pages and use an
to load your Apps Script URL. This often hides the banner, though it may not work if your app requires a Google Account login. 2. Google Workspace (Business/Education) If you are part of a Google Workspace organization: The banner is to other users within the same domain.
For external users, the only way to remove it is by publishing the script as a verified Google Workspace Add-on , which requires a more complex review process. 3. Use a Browser Extension (Personal Use Only)
If you only want to remove the banner for yourself or on a specific display (like a public kiosk), you can use a browser extension to hide the element: Custom CSS/JS Extensions: Use tools like uBlock Origin
or a custom JavaScript injector to set the banner's display style to Example Script:
The banner often uses a specific ID or class that can be targeted with: document.getElementById('warning').style.display = 'none'; 4. Technical Workarounds Self-Hosting Content: Instead of using HtmlService.createHtmlOutput()
, you can host your front-end content (HTML/CSS/JS) on a standard web host and use the Apps Script only as a back-end API (receiving requests). This avoids the Google-hosted UI entirely. Important Note:
Google includes this banner as a security precaution to warn users that the script is not an official Google product and may access their data. iframe embed to bypass this banner?
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."
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?
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
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.
Removing "This application was created by a Google Apps Script user" from a Google Apps Script Project
When you create a Google Apps Script project, it automatically adds a message to the project's UI, stating "This application was created by a Google Apps Script user." While this message is a good indication that the project was created using Google Apps Script, you might want to remove it for aesthetic or professional reasons. In this report, we'll explore how to remove this message from your Google Apps Script project.
Understanding the Message
The message "This application was created by a Google Apps Script user" is a default message added by Google Apps Script to all projects created using the platform. This message is displayed at the top of the project's UI and serves as a indicator that the project was built using Google Apps Script.
Removing the Message
To remove the message, you need to use the setTitle method of the HtmlService class. Here's an example code snippet that removes the message:
function doGet()
var html = HtmlService.createHtmlOutputFromFile('index');
html.setTitle('Your Application Title'); // Set your application title here
return html;
In the code snippet above, replace 'Your Application Title' with your desired application title. By setting a custom title using the setTitle method, the default message "This application was created by a Google Apps Script user" will be replaced with your custom title.
Additional Steps
If you want to completely remove the message and not replace it with a custom title, you can use the following approach:
- Open your Google Apps Script project.
- Click on the "Deploy" button in the top right corner of the editor.
- Select "New deployment".
- Choose "Web App" as the deployment type.
- In the "Web App" settings, uncheck the box next to "Display a 'This application was created by a Google Apps Script user' message".
By following these steps, you can remove the message from your Google Apps Script project.
Conclusion
Removing the "This application was created by a Google Apps Script user" message from a Google Apps Script project is a straightforward process. By using the setTitle method or adjusting the deployment settings, you can easily remove or replace the message with a custom title. This report provides a step-by-step guide on how to remove the message, giving you more control over the UI of your Google Apps Script projects.
Recommendations
- Use a custom title that reflects your application's name or purpose.
- Consider adding a custom logo or branding to your application to give it a more professional look.
- If you're deploying your application to a wider audience, consider removing the message to provide a more seamless user experience.
Troubleshooting
- If you've followed the steps above and the message still appears, ensure that you've saved your changes and redeployed your application.
- If you're using a custom domain or URL for your application, ensure that the message is not being cached by your browser or server.
How to Remove the "Created by a Google Apps Script User" Banner for Free
When you deploy a Google Apps Script as a web app, Google automatically inserts a grey header banner that reads: "This application was created by another user, not by Google." This is a security measure to inform users they are interacting with third-party code rather than an official Google product.
While there is no "off" switch in the settings for free consumer accounts, there are several effective workarounds to hide or remove this banner.
1. Embed the App in a Google Site (Most Effective Free Method)
The most reliable way to hide the banner for free is to embed your script's URL into a Google Site. When the web app is viewed through an iframe on a Google-hosted site, the warning banner is typically suppressed.
Step 1: In your Apps Script editor, click Deploy > New deployment.
Step 2: Select Web app and set "Execute as" to your account and "Who has access" to "Anyone". Step 3: Copy the Web App URL.
Step 4: Go to your Google Sites project, click Embed, paste the URL, and publish the site. 2. Self-Host with a GitHub Pages Wrapper
If you want to host the app on your own domain or a custom site for free, you can use a "wrapper" approach.
Create a simple HTML file (hosted on GitHub Pages) that contains an pointing to your Apps Script URL.
Ensure your Apps Script deployment is set to XFrameOptionsMode.ALLOWALL in your doGet function to allow it to be framed by external sites. 3. Use Browser Extensions (Internal/Personal Use)
If the app is only for your personal use or a small internal team, you can use a browser extension to hide the banner locally.
Install an extension like Custom JavaScript for websites or uBlock Origin.
Note: This only works for users who have the extension installed. 4. Professional Alternatives (Verification)
For a permanent solution that doesn't involve workarounds, you can link your script to a verified Google Cloud Project (GCP).
Once your app is verified by Google, the banner disappears for all users.
This process is free but requires a detailed security review if your script uses sensitive data.
For a walkthrough on how to properly deploy and access your web app URL:
The message " This application was created by a Google Apps Script user
" is a mandatory security banner added by Google to identify that a web app was not developed by Google itself. While there is no official "free" button to toggle it off, you can bypass or hide it using the following methods: 1. Embed as an iFrame
The most common way to hide the banner is by embedding your Apps Script web app into another website using an : In your Apps Script code ( ), ensure your HtmlOutput allows iframing by adding: javascript HtmlService.createHtmlOutputFromFile(
) .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); Use code with caution. Copied to clipboard
: When viewed directly via the script URL, the banner remains, but when viewed through your external site's iframe, the banner is typically hidden. 2. Embed in a Google Site
If you don't have a personal website, you can embed the web app into a Google Sites : Open a Google Site, use the tool, and paste your web app's "Exec" URL.
: This often strips the grey header/footer branding for users within the same organization or domain. 3. Use Workspace Internal Deployment If you are part of a Google Workspace
(formerly G Suite) organization, the banner is often automatically removed for other users within your same domain
: Deploy the web app and set access to "Anyone within [Your Domain]" instead of "Anyone" or "Anyone with a Google Account". 4. Browser-Side Hiding (For Personal Use)
If you only want to remove the banner for yourself (e.g., for a public kiosk or personal dashboard), you can use a browser extension to hide the element. : Use an extension like uBlock Origin or a custom CSS injector (like ) to set the banner's container to display: none;
: This only works on the browser where the extension is installed; other users will still see the banner. Summary of Limitations No Script-Level Removal : There is no
you can write inside the script itself to delete the banner because it is injected by Google's servers outside of your HTML body. Security Purpose
: Google maintains this banner to prevent phishing, so complete removal for anonymous public users is intentionally difficult. Further Exploration View community discussions on Stack Overflow regarding the X-Frame-Options workaround. Read more about web app deployment configurations on the official Google for Developers exact HTML code to create the iframe for your own website?
Conclusion: Remove the Warning for Free – Choose Your Path
The message “This application was created by a Google Apps Script user” is removable for free in many legitimate scenarios:
- For personal use: Simply run the script as yourself.
- For small teams on Workspace: Publish internally.
- For developers: Use libraries instead of web apps.
- For public distribution: You will eventually need to pay the one-time verification fee.
Do not fall for scams promising “permanent free removal” through hacking methods. Stick to Google’s official paths, and you can achieve a clean, professional app without monthly costs.
Next Steps:
- Identify if your users are internal or external.
- Try Method 2 (Workspace internal publishing) or Method 3 (library).
- If public, budget $25 for OAuth verification.
By following this guide, you can confidently remove the “Google Apps Script user” warning for free and deliver a seamless user experience.
Last updated: 2025 – The OAuth verification fee was $5 until 2023, then increased to $25–$100. Always check the latest Google Cloud documentation for current pricing.
The blue banner stating "This application was created by a Google Apps Script user" is a built-in security warning designed to protect users from unverified or potentially malicious scripts. While there is no official "one-click" button to disable it for free on public web apps, there are several effective workarounds to hide or bypass it. 1. Embed the Web App in an IFrame
The most common and effective way to hide the banner from your users is to embed your Google Apps Script (GAS) URL within another webpage using an tag.
How to do it: Host a simple HTML file on a free platform like GitHub Pages or your own website.
The Code: Use a basic iframe structure: .
Permissions: Ensure you set HtmlService.XFrameOptionsMode.ALLOWALL in your script's doGet() function to allow it to be framed by external sites. 2. Deploy Within a Google Site
If you don't want to manage external hosting, embedding the web app directly into a Google Site can often suppress the warning for users within your organization or those viewing the site. This is because Google considers its own ecosystem a "safe" container for the script. 3. Use a Google Workspace Account There is no direct "free" button or setting
If you are building an application for internal use, the banner is automatically hidden for users who are in the same Google Workspace domain as the script owner.
Benefit: This removes the banner without any extra coding or embedding.
Free Alternative: If you are using a standard @gmail.com account, you will still see the banner unless you use the iframe method mentioned above. 4. Browser-Side Hiding (For Personal Use)
If you only want to remove the banner for yourself or a small team, you can use browser extensions to hide the CSS element of the banner. In the code snippet above, replace 'Your Application
Chrome Extensions: Tools like Custom JavaScript for Websites allow you to run a script that sets the banner's display to "none".
Script Snippet: document.getElementById('warning').style.display = 'none';. 5. Official Verification (Long-Term Solution)
To remove all "Unverified App" warnings and the banner officially, you must link your script to a Google Cloud Project (GCP) and complete the OAuth verification process. Is there any way to remove the banner? : r/GoogleAppsScript
The banner "This application was created by a Google Apps Script user" is a security feature implemented by Google to inform users that the web app they are accessing was created by a third party and not by Google itself. Open your Google Apps Script project
While there is no direct "off" switch in the script settings for free accounts, you can remove or bypass it using the following methods: 1. Using a Google Workspace Account
If you are part of a Google Workspace organization, the banner will not be displayed to other users within your same domain.
Limitations: External users outside your domain will still see the banner.
Verification: For the banner to be removed for all users (including those outside your domain), the script must typically be published as a verified Google Workspace Add-on or associated with a verified Google Cloud project. 2. Embedding in a Website (iframe)
You can hide the banner by embedding your Google Apps Script web app into another webpage using an .
How it works: Host a simple HTML file on a service like GitHub Pages and use an iframe to display your script.
Constraint: This method primarily works if the web app is deployed with the access setting "Anyone" (anonymous access). If it is set to "Anyone with a Google account," the login prompt may fail to load inside the iframe due to security restrictions. 3. Deploying via Google Sites
Embedding the script directly into a Google Site can often suppress the standard Apps Script header, as Google Sites handles the integration more seamlessly for users. Summary of Options User Account Type Effectiveness Workspace Internal Hidden for members of your own domain. GCP Verification Workspace/Paid Hidden for all users once verified. iframe Embedding Free/Workspace Hidden but may break login for non-anonymous apps. Google Sites Free/Workspace Hidden in many embedded contexts. Remove web app warning for Anyone with Google Account
What if you just want to hide the text in the UI?
That’s not possible from the user side. The message is part of Google’s OAuth permission dialog, which cannot be modified or removed by CSS, JavaScript, or any script trick. You must go through verification.
Final Verdict: Can You Really Remove This Warning for Free?
Yes, absolutely. But the method depends on your role:
- If you are an end-user: Remove the application via your Google permissions page (free, immediate).
- If you are a developer: Submit your app for Google verification (free, takes a few days).
- If the app is unwanted: Revoke access and delete script files from Drive (free, instant).
What you cannot do is magically delete the warning from a script you don’t own. Google designed the warning to be non-removable by third parties to protect you.
Step-by-Step: Removing the Banner
If you already have a Google Workspace account (or are willing to get one for $6–$12/month), here’s what to do:
-
Create or migrate your script to a Workspace account.
(You can copy your existing script from your personal Gmail.) -
Deploy as a web app (or add-on) from that Workspace account.
-
Set execution permissions to “Execute as me” and “Who has access” to “Anyone within [Your Domain]” – or “Anyone” if you want public access.
-
Redeploy – the “Free / created by a user” text will be gone.
For internal company apps, you can also use Cloud Identity Free (no email inbox) to get rid of the banner without paying for full Gmail.
Part 7: Frequently Asked Questions
Method 1: Remove the Warning as an End-User (Revoke Access)
If you do not trust the application or simply want the pop-up to stop appearing, you do not need to “remove” the message itself—you need to remove the app’s access to your account.
Here is how to do that for free:
Step 1: Open your Google Account settings. Go to myaccount.google.com and sign in.
Step 2: Navigate to “Security” on the left sidebar.
Step 3: Scroll down to “Third-party apps with account access” and click “Manage third-party access.”
Step 4: Look for the app name that matches the one showing the warning. It may be listed as an “Unverified app” or “Apps Script” project.
Step 5: Click on the app name, then select “REMOVE ACCESS” .
Once you remove access, the next time you try to use that specific script, Google may ask you to re-authorize it. But the pop-up will no longer appear automatically.
Important: This removes the application, not the warning per se. The warning will only appear again if you re-authorize a script.