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 tag. When viewed through the parent site, the banner is typically hidden. Use a Google Workspace Account : If you run the script within a Google Workspace (business or education) domain, the banner will not show for other users within that same domain. Publish as an Add-on : Converting your script into a verified Google Workspace Add-on removes the banner, as the application becomes a "verified publisher". This requires a more intensive development and verification process . Google Sites Integration : Embedding the web app directly into a Google Site in Full View mode can also suppress the warning message. Alternative Hosting If the banner is a dealbreaker for your user interface, consider migrating your front-end (HTML/CSS/JS) to a standalone hosting service and using the Google Apps Script API or a backend service to interact with Google data. If you'd like to try the iFrame method, Is there any way to remove the banner? : r/GoogleAppsScript
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: 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
Complete Guide: How to Remove the "This application was created by a Google Apps Script user" Banner When you deploy a Google Apps Script project as a public web application, Google automatically inserts a prominent blue or gray warning banner at the very top of the page. The banner reads: "This application was created by a Google Apps Script user." This article explains why this banner exists, details the three developer workarounds to bypass or eliminate it, and outlines how end-users can hide it locally. Why Does Google Display This Banner? Google implements this banner as a mandatory security feature. Because Google Apps Script runs on Google’s trusted infrastructures ( script.google.com ), malicious actors could easily abuse the platform to build phishing pages that look exactly like official Google login screens or services. The banner serves two primary purposes: Security Awareness : It alerts users that the application is built by an independent third party, not by Google engineers. Abuse Mitigation : It prevents bad actors from masking malicious interfaces as native Google utilities. While critical for security, the banner can disrupt responsive web design, create unwanted horizontal scrolling on mobile devices, and lower the perceived professionalism of a client-facing web app. Developer Solutions to Remove or Bypass the Banner Because the banner is injected directly by the parent Google Workspace infrastructure via an iframe wrapper, you cannot hide it using standard CSS or JavaScript inside your Index.html file. However, you can eliminate it by changing how your application is deployed, hosted, or configured. 1. Embed the Web App via Google Sites The easiest native way to remove the banner is by embedding your deployed Apps Script web app into a Google Sites page. How it works : When a Google Apps Script web app is cleanly embedded into an official Google Site, Google’s security policies suppress the warning banner because the hosting environment is verified within the ecosystem. Steps : Open your project in the Google Apps Script Editor. Click Deploy > New Deployment . Select Web app , set access parameters, and copy the provided Web App URL. Open your target website on Google Sites. In the right panel, select Embed . Paste your Web App URL and click Insert . The application will render cleanly inside the page layout without the banner. 2. Restrict Access to Your Workspace Domain If you are developing an internal business tool rather than a public-facing website, you can remove the banner completely by limiting your deployment permissions.
To remove the "This application was created by a Google Apps Script user" banner, you must deploy the script as a Web App and access it via a Google Workspace (Business/Education) account rather than a personal @gmail.com account . 🛠️ Why the Banner Exists Google displays this header as a security measure . It ensures users know the application is custom-built and not an official Google product. This helps prevent phishing and data misuse by identifying the script's origin. ✅ Methods to Remove or Hide the Banner 1. Use a Google Workspace Account The most effective way to remove the banner is to host the script within a paid Google Workspace domain . Personal Accounts (@gmail.com): The banner is mandatory and cannot be removed. Workspace Accounts: If the script is shared only with users inside your organization , the banner typically disappears. External Users: If you share a Workspace script with someone outside your domain, the banner may reappear to warn them. 2. Embed the App in an Iframe If you are using the script as a Web App, you can embed it into your own website. This doesn't "delete" the banner code, but it can visually isolate the app within your own branding. Set the X-Frame-Options to allow embedding. Use the following code in your doGet() function: javascript return HtmlService.createHtmlOutputFromFile( 'Index' ) .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); Use code with caution. Copied to clipboard 3. Transition to Google Cloud Project (GCP) Linking your Apps Script to a Standard Google Cloud Platform project (instead of the default "Default" project) gives you more control over the consent screen and branding. Go to Project Settings in the Apps Script editor. Change the Google Cloud Platform (GCP) Project . Configure the OAuth Consent Screen in the GCP Console to "Internal." 4. Use Google App Sheet If your goal is to create a professional-looking interface without the "Apps Script" branding, consider Google AppSheet . It converts Google Sheets into mobile/web apps. It provides a white-label experience (on higher-tier plans). It removes the script-specific headers entirely. ⚠️ Important Limitations No "Hack" Exists: There is no CSS or JavaScript trick to hide the banner within the Apps Script environment itself. Google injects this at the top level of the iframe for security. Published Add-ons: If you publish your script as a formal Google Workspace Add-on in the Marketplace, the banner does not appear because the script has undergone an official review process. To give you the best advice on which path to take, could you tell me: Are you using a personal Gmail or a Work/School account ? Is this app for internal team use or for public customers ? Do you have a website where you could potentially embed the tool? I can then walk you through the specific technical steps for that setup! The message "This application was created by a
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. 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
Remove the “This application was created by a Google Apps Script user” message When you publish or deploy a Google Apps Script web app or add-on, users sometimes see the banner or message “This application was created by a Google Apps Script user.” That line can feel impersonal, undermine trust, or simply look unpolished — especially for organizations or developers presenting a polished product. Below is a descriptive, engaging guide explaining why the message appears, when it matters, how to remove or replace it, and practical suggestions to present a professional interface. Why that message appears
Ownership and safety: Google displays this notice to signal that the script was created by a Google account rather than an app verified by Google. It’s a lightweight attribution and a safety cue for end users. Default metadata: For scripts deployed under individual user accounts (rather than a managed G Suite/Google Workspace project with branding and verification), the platform may not have a verified app name, logo, or trusted OAuth verification status to show instead. Consent and trust flows: The message is tied to Google’s OAuth and publishing flows — it helps users identify that the app originates from a user account and that OAuth scopes may require consent. Use a Google Workspace Account : If you
When it matters
Public-facing apps: If you’re sharing a web app with external users, customers, or clients, the message may reduce perceived credibility. Enterprise use: Internal tools for a company are better served when they show the organization’s name and branding rather than a generic user attribution. Distribution at scale: Apps expected to be used by many people, or integrated into workflows, benefit from a clean, branded user-facing experience and verified OAuth consent.
How to remove or replace the message (high-level steps) Note: the specific UI and flow can change, but the core options remain consistent. Google Sites Integration : Embedding the web app
Use a Google Cloud project with proper OAuth branding
Create or select a Google Cloud Project (GCP) and link your Apps Script project to that GCP project. In Google Cloud Console, open “OAuth consent screen” and configure the app name, support email, and add a logo. Add the scopes your app needs, and provide privacy policy and terms of service URLs if required.