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

If your app uses sensitive or restricted scopes, you must submit for verification. After verification, Google will stop showing generic “created by a Google Apps Script user” attribution.

If you have ever installed a Google Workspace add-on, a simple script, or a web app built with Google Apps Script, you have likely encountered the following warning message:

"This application was created by a Google Apps Script user and has not been reviewed by Google."

While this message is a standard security feature from Google, it can be frustrating—especially if you are the developer testing your own script, or if you are a user trying to run a trusted tool. Worse, many online guides tell you that you must pay for a Google Workspace account or undergo a costly verification process to remove it.

The good news? You can remove or bypass this message for free in several legitimate ways.

In this comprehensive guide, we will explain:

Avoid any service or script that claims it was "created by a Google Apps Script user" and asks you to pay or click to remove a watermark. This is a red flag for phishing and account abuse. Stay safe and only authorize scripts from trusted, verified developers. If your app uses sensitive or restricted scopes,

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.

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) If you have ever installed a Google Workspace

You can hide the banner by embedding your Google Apps Script web app into another webpage using an </code>. 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 <hr> If you’ve built a Google Apps Script project and shared it with others, you may have noticed an authorization screen that says: <blockquote> “This application was created by a Google Apps Script user free” </blockquote> 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. <hr> The Text: <blockquote> "This application was created by a Google Apps Script user." </blockquote> <hr> How to remove this text: If you are using the <code>MailApp</code> or <code>GmailApp</code> service in your script, Google automatically appends this footer to prevent spamming. You cannot remove it using the standard free tier of Google Apps Script. To remove it, you must switch to using the Gmail API in your script. Here is a basic example of how to send an email without the footer using the API: <pre><code class="language-javascript">function sendEmailWithoutFooter() var recipient = 'example@email.com'; var subject = 'Test Subject'; var body = 'This is the body of the email.'; // Create the raw email content var raw = 'To: ' + recipient + '\r\n' + 'Subject: ' + subject + '\r\n\r\n' + body; // Encode the message var encodedMessage = Utilities.base64EncodeWebSafe(raw); // Send using the Gmail API Gmail.Users.Messages.send( raw: encodedMessage , 'me'); </code></pre> Note: You must enable the Gmail API service in your script project (Services > Gmail API) for this code to work. 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 <a href="https://developers.google.com/apps-script/concepts/deployments">web apps and deployments</a> 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 <code><iframe></code> within a <a href="https://issuetracker.google.com/issues/63521070">Google Site</a> or your own website. Google Workspace Accounts: If you are part of a <a href="https://workspace.google.com/products/apps-script/">Google Workspace</a> 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 <a href="https://github.com/rbbydotdev/someday">GitHub Pages</a> and call your Google Apps Script as a backend API. This prevents the banner from appearing because users are not viewing a <code>script.google.com</code> URL directly. Browser Extensions (Developer Only): For personal use or public displays, you can use browser extensions like <a href="https://stackoverflow.com/questions/59659626/google-apps-script-hide-running-script-notification">uBlock Origin</a> or custom CSS injectors to set the banner's container (often with an ID like <code>warning</code>) to <code>display: none;</code>. Note that this only hides the banner for you, not other users. The message " This application was created by a Google Apps Script user " is a standard security disclaimer automatically added by Google to identify that the web app is third-party and not an official Google product. no official "one-click" way to remove this banner for free on a personal (@gmail.com) account, as it is a fundamental security feature of the platform. However, there are several methods to work around it or minimize its visibility: 1. Embed the App in a Google Site (Recommended) The most common "legitimate" workaround is to embed your Apps Script Web App into a Google Site. : The banner is typically hidden when viewed within the frame of a Google Site or a website. How to do it Google Site , and paste the URL of your deployed web app. 2. Use a Google Workspace Account If you use a paid Google Workspace (formerly G Suite) account, the banner behavior changes: Internal Users : The banner is not shown to users within the same organization domain. External Users : It may still appear unless the script is part of a verified Google Cloud project or published as a Workspace Add-on 3. Browser-Side Hiding (Developer/Private Use Only) If you are only using the app for yourself or on a public display (like a TV), you can hide the banner locally using browser tools. Extensions : Tools like uBlock Origin Custom JavaScript can be used to set the CSS of the banner element to display: none; JavaScript Code javascript document.getElementById( ).style.display = Use code with caution. Copied to clipboard Note: This only hides it for you; other visitors will still see it. 4. Verify Your App with Google For production-level apps, you can follow the official verification process through the Google Cloud Console : Create a standard Google Cloud project, link it to your script, and submit it for review. : While this primarily removes the "Google hasn't verified this app" warning screen, it is the only way to officially identify your developer credentials to Google. Google Site to hide the banner? Is there any way to remove the banner? : r/GoogleAppsScript To remove the message "This application was created by a Google Apps Script user" (or "This application was created by another user, not by Google") from your web app, you should understand that this is a security feature designed to protect users from phishing or malicious scripts . While there is no "free" button to toggle this off, here are the most effective ways to manage or remove it: 1. The Official Professional Route (Verified Publisher) The most "correct" way to remove the banner for all users is to have your application verified by Google. Once verified, the banner typically disappears because the publisher is now trusted . Create a GCP Project: You must associate your Apps Script project with a standard <a href="https://script.google.com/">Google Cloud Platform (GCP)</a> project . Request Verification: Submit your app for OAuth verification through the <a href="https://console.cloud.google.com/">Google Cloud Console</a>. This process can take several weeks and may require identifying yourself (which often requires a paid Workspace account) . 2. The Browser-Side "Fix" (For Personal Use) If you only want to hide the banner for yourself or a small group of users who are willing to install an extension, you can use a browser-based CSS injector . Use a Browser Extension: Install an extension like Custom JavaScript for websites or <a href="https://www.tampermonkey.net/">Tampermonkey</a>. Inject CSS: Use the following code to hide the banner's container: javascript <code>document.getElementById('warning').style.display = 'none'; </code> Use code with caution. Copied to clipboard Note: This only works for users who have the extension active . 3. Alternative Hosting (Avoiding the Apps Script Domain) If you want a professional look without the banner, you can move your front-end away from <code>script.google.com</code>. Embed via iFrame (Partial Success): Some users try embedding the Apps Script URL in another website. However, the banner often remains because it is tied to the Apps Script domain . Use a Front-End Framework: Host your UI on a free platform like GitHub Pages or Netlify and use the Google Apps Script purely as a Backend API (via <code>doGet</code> or <code>doPost</code>). This completely bypasses the Apps Script web app UI and its associated banners . 4. Configuration Check (Workspace Users) If you are part of a Google Workspace (business or education), ensure you are deploying the app with the correct settings. Execute As: Set this to "Me" (your admin/account). Who has access: Set this to "Anyone within [Your Domain]" rather than "Anyone" . In some organizational settings, this can minimize the severity of the warning banner. Summary of Options: Verification Free / Time Intensive Professional, public-facing apps . Browser Extension Private internal tools or personal dashboards . Separate Hosting Free (GitHub/Netlify) Developers who want a fully custom UI . Are you building this app for public use or for private/internal tasks? While there is no direct "off" switch in the Google Apps Script settings to remove the branding banner for free, you can use technical workarounds to hide it from your end users. Google includes this banner as a security measure to alert users that the application was not created by Google itself. Workaround 1: Embedding via Iframe The most common free method to "remove" the banner is to hide it by embedding your web app into a separate website using an <code><iframe></code>. How it works: When the script is embedded, the banner typically does not display. Implementation: You can host a simple HTML file for free on services like <a href="https://github.com/rbbydotdev/someday">GitHub Pages</a> or Google Sites. Example Code: <code><iframe src="YOUR_WEB_APP_URL" width="100%" height="500px"> Use code with caution. Copied to clipboard Workaround 2: Google Workspace Domain

If you are part of a Google Workspace organization, the banner is automatically hidden for other users within your same domain. It will only appear to external users outside of your organization. Workaround 3: Verified Add-ons

For a truly professional appearance without the banner, you must publish your script as a verified Google Workspace Add-on.

Requirements: This requires a verified Google Cloud project and an official review process by Google.

Cost: While publishing itself is free, obtaining the necessary verification often requires a Workspace account, which is a paid service. Important Limitations "This application was created by a Google Apps

Authentication: If your web app requires the user to log in ("Execute as: user accessing the app"), an iframed version may fail to show the login screen due to security restrictions.

Mobile Scaling: Some users have reported that the banner can cause horizontal scrolling issues on mobile devices, which embedding in a responsive site can help fix.

The banner "This application was created by a Google Apps Script user" is a mandatory security feature for scripts running on free consumer accounts. While there is no "off" switch in the settings, several workarounds can effectively hide or remove it for your users. ⚡ Quick Solutions (Free) 1. Embed as an iFrame

The most common free method is to embed your Apps Script URL into a standard HTML page using an </code>. The Result: The banner is often suppressed or hidden within the container of the hosting site. Free Hosting: You can host the container page for free on platforms like <a href="https://github.com/rbbydotdev/someday">GitHub Pages</a> or Google Sites. Crucial Setting: In your script editor, you must set the <code>X-Frame-Options</code> to <code>ALLOWALL</code> to permit embedding. 2. Browser Extensions (For Personal Use) If you are the only person using the app, or you can control the user's environment (e.g., a dedicated display), you can use a browser extension like <a href="https://stackoverflow.com/questions/59659626/google-apps-script-hide-running-script-notification">uBlock Origin</a> or <a href="https://stackoverflow.com/questions/33635284/google-apps-script-remove-warning-banner">Custom JavaScript for websites</a> to inject CSS. Use this CSS to hide the banner: <code>#warning display: none !important; </code>. 🛠️ Comparison of Methods Difficulty iFrame Embedding Public-facing apps/websites Google Sites Internal or team-based tools Workspace Account Professional/Commercial use Browser Extension Personal use or dedicated kiosks 💡 Important Considerations Security Verification: For a permanent, "official" removal without workarounds, you must associate your script with a Google Cloud Project and go through the OAuth verification process. This typically requires a verified domain and a privacy policy. Domain Restrictions: If you use a Google Workspace account, the banner will not appear for other users within the same domain. Terms of Service: Ensure your app complies with Google's <a href="https://www.reddit.com/r/GoogleAppsScript/comments/1mne5uu/is_there_any_way_to_remove_the_banner/">commercial use rules</a> if you are monetizing the service. ⚠️ Note: Standard CSS within your <code>HtmlService</code> code (like <code>style="display:none"</code>) will not work because the banner is generated outside of your app's <code>body</code> tag in a parent iFrame controlled by Google. If you'd like to try the iFrame method, I can provide the specific code snippets for your <code>index.html</code> and <code>code.gs</code> files. Is there any way to remove the banner? : r/GoogleAppsScript 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? The message " This application was created by a Google Apps Script user " is a security banner automatically added by Google to web apps deployed via Google Apps Script (GAS). It serves as a warning that the application is not officially created or verified by Google. Can it be removed for free? no official "free" setting within Google Apps Script to toggle this banner off. However, there are specific deployment methods and workarounds that can hide or eliminate it. Ways to Eliminate the Banner Use a Google Workspace Organization Account The banner is generally to other users within the same Google Workspace domain as the script owner. If you deploy the app for "Internal" use within an organization, members will not see the message. Embed in Google Sites If you embed your Apps Script web app as a gadget within a Google Site , the banner is typically hidden from view. Publish as a Workspace Add-on Developing and publishing your script as a verified Google Workspace Add-on removes the top-level banner, as the code runs within a sidebar or dialog instead of a standalone web app page. Client-Side Workarounds (Visual Only) These methods do not remove the banner for all visitors but can hide it on your own browser or specific displays (like a public dashboard): Browser Extensions : Using a tool like Custom JavaScript for websites or a script manager, you can inject a CSS rule to hide the element: document.getElementById('warning').style.display = 'none'; Dedicated Plugins : There are community-built browser plugins specifically designed to detect and remove this iframe message automatically. Why the Banner Exists Google implements this banner to prevent and malicious use. Because Apps Script allows anyone to create a functional web page for free, the banner ensures visitors know they are interacting with a third-party script rather than an official Google service. to hide this banner? Is there any way to remove the banner? : r/GoogleAppsScript You're looking for information on removing an application created by a Google Apps Script user for free. Here's some relevant content: Removing a Google Apps Script Project If you've created a Google Apps Script project and want to remove it, you can do so by following these steps: Deleting a Google Apps Script Project Created by Another User If you're an administrator or have ownership of a Google Apps Script project created by another user, you can delete it by following these steps: Free Resources to Remove Google Apps Script Projects If you're looking for free resources to help you remove Google Apps Script projects, here are a few options: Best Practices for Removing Google Apps Script Projects Before removing a Google Apps Script project, make sure to: By following these steps and best practices, you should be able to remove your Google Apps Script project created for free. 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. 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 <code dir="ltr" class="KDcb0c" jsaction="" jscontroller="hNviFe" data-sfc-root='c' jsuid="sw2Ktb_19" data-sfc-cb="">fetch()</code> or <code dir="ltr" class="KDcb0c" jsaction="" jscontroller="hNviFe" data-sfc-root='c' jsuid="sw2Ktb_1a" data-sfc-cb="">google.script.run</code> to send data to your Apps Script (deployed as a Web App). The Result: Since the user is visiting <code dir="ltr" class="KDcb0c" jsaction="" jscontroller="hNviFe" data-sfc-root='c' jsuid="sw2Ktb_1e" data-sfc-cb="">yourwebsite.com</code> instead of <code dir="ltr" class="KDcb0c" jsaction="" jscontroller="hNviFe" data-sfc-root='c' jsuid="sw2Ktb_1f" data-sfc-cb="">://google.com</code>, 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. <hr> If your app uses sensitive scopes and will have >100 users, submit for Google verification: Once verified, the scary message disappears and users see your app name and branding. <hr> To replace the message with your own app name and developer info: If you have a Google Workspace account (even the free legacy edition), you can publish the script internally without verification. Steps: Why this works: Google trusts internal apps within the same Workspace domain. No verification is required, and the warning is gone for all domain users. Cost: Free if you already have Workspace. If not, you can create a single-user Workspace account (starts at ~$7.20/month but includes a free trial). However, the method described here is for existing domain users. <hr>