Remove This Application Was Created By A Google Apps Script User 【TOP ●】

One common but invalid approach attempts to hide the footer using injected CSS or DOM manipulation:

<style>
  .footer-branding  display: none; 
</style>

Why it fails:


Paper version 1.0 – Prepared for technical decision-makers evaluating Google Apps Script deployment strategies.

To remove the "This application was created by a Google Apps Script user" banner from your web app, you generally need to change how the script is hosted or verified, as it is a built-in security feature for unverified scripts. Primary Solutions

Embed in a Google Site: The banner is typically hidden when the web app is embedded within a Google Site or another website.

Use a Google Workspace Account: If the script and the users are within the same Google Workspace domain, the banner does not appear.

Deploy as a Google Workspace Add-on: Building and publishing your project as an Editor Add-on will remove this specific web app banner.

Link to a Standard GCP Project: Instead of the default project, create a new Google Cloud (GCP) project, associate it with your script, and go through the official OAuth verification process. Client-Side Workarounds (Developer/Internal Use)

These do not remove the banner for other users but can hide it on your own browser: One common but invalid approach attempts to hide

Browser Extensions: Use extensions like uBlock Origin or Custom JavaScript for websites to inject code that hides the warning element.

JavaScript Injection: For internal displays, you can use a script to set the banner's display style to none: javascript

document.getElementById('warning').style.display = 'none'; ``` Use code with caution. Copied to clipboard

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

  • Outcome (single sentence): state the result and any residual issues. Example: "Banner gone across all users; no other UI changes observed."

  • Troubleshooting tips (2–3 bullets): common pitfalls and fixes.

  • Rating (optional, short): give a quick verdict. Example: "4/5 — effective solution; could use clearer instructions on manifest edits."

  • Use or adapt any of the lines above to fit your exact experience. Why it fails :

    Sometimes the warning appears because of overly broad scopes. You can reduce or remove scopes to avoid triggering the warning altogether.

    False. The warning has nothing to do with the title “This application was created by a Google Apps Script user.” Changing the script name or logo does nothing.

    If your app truly needs full, unrestricted access to user emails and Google Drive and serves the general public, removing the warning might be impossible without a security assessment. In that case, consider building a native web app using Cloud Run or Firebase instead of Apps Script.


    | Situation | Can you remove the line? | |-----------|----------------------------| | Unverified external app | ❌ No | | Internal Workspace app | ⚠️ Changes to domain name | | Verified public app | ✅ Yes (replaced with your name) |

    If you just want a clean user experience for a small tool, consider making the app internal or hosting it on another platform (e.g., Glide, Bubble, or a simple Node.js server).


    Removing the "This application was created by a Google Apps Script user" banner is a common goal for developers looking to create a more professional-looking web app. This banner is a security feature by Google to alert users that the application was not created by Google itself.

    While there is no single "off" switch in the settings for free accounts, you can use these methods to hide or remove it: 1. Embed the Web App in Google Sites

    The most effective "native" workaround is to embed your Google Apps Script web app into a Google Sites page. Paper version 1

    When a web app is viewed through an embedded frame on a Google Site, the banner is typically suppressed for visitors.

    This is the preferred method if you want a professional presentation without requiring users to install anything. 2. Verify Your Project with Google Cloud (GCP)

    For a permanent and official solution, you must associate your script with a standard Google Cloud Project and go through the OAuth verification process.

    Create a GCP Project: Link your script to a new project in the Google Cloud Console.

    Verification: Submit your app for verification. Once Google verifies you as a "verified publisher," the banner is removed for all users.

    Note: This process can be technical and may take several weeks to complete. 3. Use within a Workspace Domain

    If you are part of a Google Workspace (formerly G Suite) organization:

    The banner is generally not shown to other users within the same domain as the script owner.

    For users outside your domain, the verification process (Method 2) is still required to remove the warning. 4. Client-Side Browser Extensions (Personal Use)

    If you only want to hide the banner for yourself or a specific set of users, you can use browser-based tools: Google Apps Script remove warning banner - Stack Overflow