The warning does not mean your app is dangerous. It simply means Google has not yet verified your identity and compliance with their API policies.
| 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).
The gray banner at the bottom of the screen was a digital scar. It read:
"This application was created by a Google Apps Script user."
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.
One Tuesday, Elias snapped. He didn't just want the banner gone; he wanted the
He spent forty-eight hours straight buried in documentation. He learned that the banner was a security feature, a permanent "badge of origin" for scripts running on Google’s infrastructure. It was there to protect users from phishing, ensuring they knew the app wasn't an official Google product.
"I don't want to hide," Elias whispered to his glowing monitor, "I want to be independent."
He realized he couldn't just "CSS-hide" his way out of this. To remove the mark, he had to graduate. He began the grueling process of migrating his entire codebase. He moved the logic from Apps Script to a dedicated Node.js server. He swapped the Google Sheet for a robust SQL database. He replaced the simple function with a professional front-end framework.
As he hit 'Deploy' on his own private domain, the banner finally vanished. The interface was clean, white, and professional.
A week later, Elias sat across from a high-tier investor. The man looked at the screen, scrolled through the seamless, branding-free dashboard, and nodded. "Impressive. It feels solid. Built this from scratch?"
Elias smiled, remembering the gray banner that had once haunted him. "It had humble beginnings," he said, "but it grew up." technical steps
to migrate a project away from Apps Script, or should we refine the narrative arc of the story?
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
. Google displays this message as a security feature to inform users that the app is not an official Google product and was created by a third party. Methods to Remove or Bypass the Warning The warning does not mean your app is dangerous
The most effective way to eliminate this banner is to avoid viewing the app directly via the script.google.com Embed in a Website or Google Sites If you embed your Web App into another webpage using an
, the banner is often suppressed. For this to work, you must set the X-Frame-Options in your Apps Script code to allow embedding: javascript HtmlService.createHtmlOutputFromFile(
) .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); } Use code with caution. Copied to clipboard Google Workspace Verification
The banner typically does not appear for users within the same Google Workspace domain
as the script owner. If you are targeting external users, you must publish the script as a verified Google Workspace Add-on or associate it with a verified Google Cloud project Browser Extensions (Developer Workaround)
If you only need the banner gone for your own view (e.g., on a public display or TV), you can use browser extensions like "Custom JavaScript for websites" to inject CSS and hide the element. CSS to hide #warning display: none; Google Groups Why the Banner is There Security & Transparency
: It warns users that the app's creator is an individual user, not Google, preventing phishing or malicious data collection. Mobile Responsiveness Issues
: As of late 2023, the banner transitioned to a blue format that can cause scaling issues on mobile devices. Summary of Solutions Complexity External users Workspace Domain Internal organization users GCP Project Verification Public/External users Browser Extension Only the local viewer to embed your script into a Google Sites
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. | Situation | Can you remove the line
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
How to Remove the "This application was created by a Google Apps Script user" Header
If you have ever built a web app using Google Apps Script (GAS), you have likely encountered the persistent gray banner at the top of the page that reads: "This application was created by a Google Apps Script user."
While Google includes this for security and transparency—to ensure users know they aren't interacting with an official Google product—it can be a major eyesore for developers trying to create a professional, branded experience.
In this guide, we will explore the reality of this disclaimer and the best ways to work around it. Can You Directly Remove the Banner?
The short answer is no. There is no "off switch" in the Google Apps Script settings to hide this banner.
Because the web app is hosted on the ://google.com domain, Google injects this iframe header as a security measure to prevent phishing and spoofing. Even with a Google Workspace (formerly G Suite) Business or Enterprise account, the banner remains.
However, depending on your technical skills and how you intend to share the app, there are three primary workarounds. Method 1: Embedding the Web App in an Iframe
The most common way to "mask" the Apps Script environment is to embed your Google Apps Script URL into your own personal or business website.
Deploy your Script: In the Apps Script editor, click Deploy > New Deployment. Select Web App and set "Who has access" to Anyone. Copy the Web App URL: It will look like https://google.com.
Embed on your Site: Use the following HTML code on your own website:
Use code with caution.
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. The gray banner at the bottom of the
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.
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.
By default, Apps Script uses a hidden default GCP project. To control trust settings, you must switch to a standard GCP project.