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

If you want to use the script but find the extra click annoying, you cannot “delete” the warning from Google’s servers. However, you can bypass it permanently by using the script from a trusted environment.

Here is a free workaround:

The phrase “remove this application was created by a google apps script user free” brings thousands of people to forums and help desks every month. The confusion is understandable—Google’s warning text is stark and alarming. But now you know the truth: it’s a standard security feature, not a flaw.

You can remove the application causing the warning for free in under two minutes. Or, if you are the developer, you can remove the warning from your app by completing Google’s free verification process.

Do not pay for cleaners, removers, or so-called “experts” who promise to delete the warning. They are preying on your frustration. Use the official, free methods outlined above, and you will never be bothered by the “Google Apps Script user” message again.

Next Step: Open your Google Account permissions page and take control of every application connected to your data—right now, for free.

Instead of fighting the warning, use these free, Google-approved tools:

These tools cost nothing and give you full control over which “Apps Script user” applications can interact with your data.

Verdict: ⚠️ High Risk / Likely Scam If you encounter a website, extension, or bot that displays the message "Remove this application was created by a Google Apps Script user free," you should proceed with extreme caution.

Rating: 1/5 Stars

For a more elegant solution that removes the warning entirely for all users, publish your script to the Google Workspace Marketplace.

When an app is listed on the official Marketplace, Google trusts it more. The warning “created by a Google Apps Script user” is replaced by a clean, professional authorization screen.

How to do it for free:

Once published, any user who installs your app from the Marketplace will never see the dreaded warning.

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. If you want to use the script but

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."

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]. Instead of fighting the warning, use these free,

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 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 Google Cloud Platform (GCP) project .

Request Verification: Submit your app for OAuth verification through the Google Cloud Console. 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 Tampermonkey.

Inject CSS: Use the following code to hide the banner's container: javascript document.getElementById('warning').style.display = 'none'; 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 script.google.com.

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 . These tools cost nothing and give you full

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 doGet or doPost). 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?

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 To remove the "This application was created by a Google Apps Script user" banner for free, you must embed your Google Apps Script web app into another webpage. Google automatically adds this banner to standalone web apps as a security notice to users. The most effective free method is to use Google Sites or GitHub Pages to iframe the application. Phase 1: Prepare Your Google Apps Script Before embedding, you must modify your code to allow other sites to "frame" your application. Open your <a href="https://script.google.com/home">Google Apps Script project</a>. In your <code>doGet()</code> function, locate where you return your HTML output. Add the <code>.setXFrameOptionsMode()</code> method to your <code>HtmlService</code> call: javascript <code>function doGet() return HtmlService.createHtmlOutputFromFile('Index') .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); </code> Use code with caution. Copied to clipboard Deploy as a Web App: Click Deploy > New Deployment. Set "Who has access" to Anyone. Copy the Web App URL provided after deployment. Phase 2: Choose an Embedding Method Method A: Using Google Sites (Easiest) This is the most seamless way to remove the banner for free within the Google ecosystem. Go to <a href="https://sites.google.com/">Google Sites</a> and create a new site. On the right panel, click Embed. Paste your Web App URL into the "By URL" tab. Resize the embedded box to fit your application perfectly. Publish your site. When users visit your Google Site URL, the Apps Script banner will be hidden. Method B: Using GitHub Pages (Custom URL) Use this if you want a cleaner URL or more control over the surrounding page. Create a new repository on <a href="https://github.com/">GitHub</a>. Create a file named <code>index.html</code>. Paste the following iframe code, replacing <code>YOUR_SCRIPT_URL</code> with your actual web app URL: <code><!DOCTYPE html> <html> <head> <style> iframe position: fixed; top: 0; left: 0; bottom: 0; right: 0; width: 100%; height: 100%; border: none; </style> </head> <body> <iframe src="YOUR_SCRIPT_URL"> Use code with caution. Copied to clipboard

Enable GitHub Pages in the repository settings to host the site for free. Alternative: Verified Publisher (Advanced)

If you do not want to embed the app, the only "official" way to remove the banner is to link your script to a Google Cloud Project and go through the OAuth verification process. This is complex and usually requires a privacy policy and a domain name. Summary of Limitations

Permissions: Embedding only hides the visual banner. Users will still see an authorization popup the first time they run a script that requires access to their Google data.

Mobile View: Ensure your CSS is responsive, as iframes can sometimes behave differently on mobile devices.

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)

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 No, it just means Google hasn’t reviewed the app. Only run scripts from sources you trust.