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

Before attempting to remove the message, you must understand its cause. The warning appears when a Google Apps Script application attempts to access sensitive user data (like Drive, Gmail, Sheets, or Contacts) or perform actions on behalf of a user without completing Google’s verification process.

Specifically, the message triggers when:

In essence, Google is saying: “We don’t know who built this. Be careful.”

For internal company tools (users in the same domain), this message is sometimes less severe, but for external users, it is a major red flag.

This method removes the visible footer by masking the GAS URL behind your own domain using a reverse proxy.

How it works:

Example NGINX configuration:

location / 
    proxy_pass https://script.google.com/macros/s/AKfycb.../exec;
    proxy_set_header Host script.google.com;
    sub_filter '<div class="footer-branding">' '</div><!-- removed -->';
    sub_filter_once off;
    proxy_ssl_server_name on;

Advantages:

Disadvantages:

❌ Deleting the line from appsscript.json
❌ Changing oauthScopes to empty
❌ Using ScriptApp.getProjectTriggers() tricks
❌ Deploying as “Execute as me” without sharing

These do not remove the warning.

The message "This application was created by a Google Apps Script user" is a mandatory security banner added by Google to identify scripts not created by Google itself. While you cannot directly delete this text from the script's code, you can bypass it using several development strategies:

Embed as an iFrame: The most common workaround is embedding your Apps Script web app into another website using an Use code with caution. Before attempting to remove the message, you must

The Result: While the banner still technically exists inside the iframe, it stays contained within that frame. If you style your website correctly, the banner feels less like a "system warning" and more like a small footer or header element within a specific window. Method 2: Using a Custom Domain with a Proxy (Advanced)

If you want to completely strip the banner, you cannot host the app on Google’s servers directly. Instead, you can use a "proxy" or a middle-man server.

Using a service like Cloudflare Workers or a simple Node.js/Express server, you can fetch the HTML content from your Google Apps Script, strip out the Google-injected header tags, and serve the cleaned HTML on your own custom domain. Pros: Complete removal of the banner; professional URL.

Cons: Requires significant coding knowledge; may violate Google’s Terms of Service regarding masking the origin of the script.

Method 3: Switching to Google Cloud Run (The Professional Path)

If the "Created by a Google Apps Script user" banner is a dealbreaker for a professional project, it may be time to move beyond Apps Script.

Google Apps Script is designed for quick internal tools. For client-facing applications, developers often migrate their logic to Google Cloud Run or Firebase Hosting.

Cloud Run: Allows you to run code in any language (Python, Node.js, Go) without any forced headers.

No Disclaimers: Since you are hosting the environment, Google does not inject any security banners. Why Does Google Put It There?

It is important to remember why this exists. Google Apps Script allows anyone to write code that can access Google Drive, Gmail, and Calendar data. Without that banner, a malicious actor could easily build a fake "Google Login" page that looks identical to a real one. The banner serves as a "Proceed with Caution" sign for the end-user.

To summarize your options for dealing with the "This application was created by a Google Apps Script user" message:

Accept it: For internal company tools, it is rarely an issue. In essence, Google is saying: “We don’t know

Iframe it: Embed it into your own site to make it feel like part of a larger dashboard.

Migrate: If branding is paramount, move your project to a dedicated hosting platform like Firebase or Vercel.

By understanding these limitations, you can better plan your project's user experience from the start.

Here are concise, useful review suggestions you can use for "remove this application was created by a google apps script user":

Use or adapt any of the lines above to fit your exact experience.

To remove the "This application was created by a Google Apps Script user" banner, you generally need to embed your web app in an iframe on another site, or use a Google Workspace (paid) account to deploy it within your own domain.

How to Remove the "Created by a Google Apps Script User" Banner

If you’ve ever built a web app with Google Apps Script, you’ve likely seen that persistent blue or gray banner at the top of your page. While it serves as a security feature for Google, it can make your professional project look like a "test script." Here is the reality of how to handle it. 1. The "Free" Workaround: Use an iFrame

The most common way to hide the banner without spending money is to embed your Apps Script web app into another website using an How it works: This method removes the visible footer by masking

When the script is rendered inside an iframe on an external site, the banner is typically suppressed. You must update your script’s function to allow embedding: javascript HtmlService.createHtmlOutputFromFile(

) .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); } Use code with caution. Copied to clipboard Users have reported success embedding these apps into Google Sites , which often removes the warning for viewers. 2. The Professional Solution: Google Workspace

The banner is a "price" of using the free consumer platform. If you use a paid Google Workspace

account (Business or Education), you can deploy apps that don't show this warning to other users in your same domain. Internal Access:

When you deploy and set access to "Anyone within [Your Domain]," the banner is removed for your colleagues. Verification:

For apps intended for the general public, you must link your script to a standard Google Cloud Project (GCP) and go through the OAuth verification process to be recognized as a "verified publisher". 3. What Doesn't Work

It is important to note that you cannot hide this banner using internal CSS or JavaScript within your script. Google intentionally isolates the web app in a different domain (e.g., googleusercontent.com

) to prevent your code from accessing the parent page's elements, including the banner itself. Summary Table: Removal Options Difficulty iFrame Embedding Hides banner on the host site Google Sites Often suppresses banner for viewers Workspace (Internal) No banner for users in your domain GCP Verification Removes banner for public users linking to a GCP project Google Apps Script remove warning banner - Stack Overflow

The banner "This application was created by a Google Apps Script user" is a built-in security disclaimer designed by Google to warn users that the application has not been verified by Google and may be untrustworthy. Direct Solutions

There is no single "off" switch in the script settings, but you can remove or hide it using these methods:

Embed in Google Sites: The most reliable official method is to embed your web app URL into a Google Site. When viewed through the Google Sites interface, the banner is typically suppressed.

Self-Hosting via Iframe: You can host a simple HTML file on your own domain (e.g., via GitHub Pages) and embed the Apps Script URL within an