Remove This Application Was Created By A Google Apps Script User [portable] Jun 2026

If you are building the application exclusively for your personal use or a tiny tech-savvy team, you can block the DOM element locally using content filters.

In certain environments, Google naturally hides the banner because the "untrusted" risk is minimized: Internal Workspace Domain : If the script owner and the user are in the same Google Workspace domain, the banner often does not appear. Google Sites Embedding : Embedding your web app within a Google Site typically prevents the banner from showing to visitors. Google Workspace Add-ons : Converting your script into a verified Google Workspace Add-on

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

: It warns users that the app's creator is an individual user, not Google, preventing phishing or malicious data collection. Mobile Responsiveness Issues

Use code with caution.

To summarize your options for dealing with the message:

Note: While this method hides the header elements, users may still encounter standard OAuth access authorization screens during their first launch if your application interacts directly with their internal Google Drive or Gmail resources. Method 2: Native Google Sites Integration

Method 4: Transition to Custom HTML with Google Apps Script as an API

Deploy your script project as a Web App from the Google Apps Script Editor: Click > New deployment . Set Execute as to Me . If you are building the application exclusively for

If you cannot upgrade your account, you can use a frontend workaround to visually hide the footer. You do this by embedding your Apps Script URL into an external website using an and cutting off the bottom portion of the frame. Create a container on your external website.

For Elias, a self-taught coder working out of a cramped studio, that banner was a neon sign pointing to his amateur status. He had built "The Oracle," an algorithm designed to predict localized market crashes, using nothing but Google Sheets and a dream. But every time he pitched it to a venture capitalist, their eyes drifted to that tiny, gray disclaimer. To them, it didn't look like a revolution; it looked like a hobby.

This guide explains why this banner appears and provides step-by-step methods to remove or bypass it. Why Does This Warning Appear?

Once verified and published as an add-on, your code executes natively inside Gmail, Calendar, or Drive sidebars, bypassing web app layout banners entirely. Summary of Deployment Options Banner Status Best Used For Requirements Visible ⚠️ Rapid debugging or developer testing Free Google Account HTML IFrame Embedding Hidden 🟢 Public MVPs, contact forms, client tools External host (e.g., GitHub Pages) Workspace Domain Lock Hidden 🟢 Internal enterprise tools & dashboards Google Workspace account Marketplace Add-on Hidden 🟢 Commercial SaaS distribution GCP Verification Process Local Workaround for Developers: Browser Extensions Google Workspace Add-ons : Converting your script into

If the application is published as a (for Sheets, Docs, Forms, or Gmail), Google replaces the generic footer with an “Powered by Google Apps Script” notice that is less intrusive and can be accompanied by your logo. However, the attribution remains but is integrated into the add-on sidebar/menu rather than as a floating banner.

: Open your deployed web app link, click the uBlock Origin Extension icon, open the element picker, click on the light-blue banner frame, and choose Create Filter .

For public-facing applications that cannot be restricted to a Workspace domain, the official way to remove security warnings is through Google Cloud verification.

To remove the "This application was created by a Google Apps Script user" banner, you generally need to change how you host or verify the application To summarize your options for dealing with the

Many developers attempt to use JavaScript or CSS directly inside their Apps Script Index.html file to remove the footer.

The warning, which typically states, " This application was created by another user, not by Google, " first started appearing more prominently in July 2017. It's not a bug or an error, but a deliberate security measure introduced by Google to protect users from potentially malicious or deceptive applications. Essentially, it serves as a notification that the app you're using hasn't been reviewed or verified by Google, and the data you share with it may not be as protected as it would be with an official app.