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.
This is the standard method to stop a script from accessing your data (Gmail, Drive, Calendar, etc.).
The message “This application was created by a Google Apps Script user” is a security feature, not a bug. It protects users from malicious scripts. However, for legitimate developers, it creates unnecessary friction.
To remove it:
The process requires patience, especially with Google’s review team, but it is entirely possible. Verified apps build trust, increase adoption, and look professional.
If you are just prototyping, ignore the message. But before you launch a tool for real users, invest the time to remove that warning. Your users will thank you.
Have you successfully removed the Apps Script warning? Share your experience in the comments below.
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 This is the standard method to stop a
To remove the "This application was created by a Google Apps Script user" banner, you must transition from a personal script to a Google Cloud Project (GCP) with an OAuth consent screen that has been verified by Google. Phase 1: Create a Standard Google Cloud Project
By default, Apps Script uses a "Default" project that triggers the warning. You need to link it to a manual project. Open your script at google.com. Go to Project Settings (gear icon).
Under Google Cloud Platform (GCP) Project, click Change project.
Enter the Project Number of a project you created in the Google Cloud Console. Phase 2: Configure the OAuth Consent Screen
The banner acts as a safety warning for unverified developers. To lift it, you must identify your "app."
In the GCP Console, go to APIs & Services > OAuth consent screen.
Select External (if you want people outside your workspace to use it) or Internal (for Google Workspace users only). Fill out the required App Information: App name: The name users will see. User support email: Your email. Developer contact info: Your email.
Add the Scopes your script uses (e.g., https://googleapis.com). Phase 3: Verification (The Critical Step) Remove Access: Click on the application name to
The banner will only disappear once Google trusts the application.
For Internal Apps: If you are a Google Workspace user and set the app to "Internal," the banner usually disappears immediately for members of your organization. For External Apps: You must click Submit for Verification.
Google will review your privacy policy and terms of service.
Once approved, the "unverified app" warning and the footer banner are removed. Quick Workarounds If you cannot go through full verification:
Google Workspace: Deploy the script within a managed organization. If the script and the user are in the same domain, the banner is often suppressed.
Web App URL: Ensure you are using the /exec URL and not the /dev URL, as the development mode always shows debugging headers.
Custom Domain: Embedding the script in a site via an can sometimes hide the footer, but it may still appear if the user interacts with a Google-hosted UI element.
💡 Note: Google keeps this banner as a security measure to prevent phishing. If your script is for public use, verification is the only official way to remove it. If you tell me more about your setup, I can help further: Using a personal Gmail or Workspace account? Targeting internal colleagues or public users? Linking to a Google Form or a Web App?
Paper version 1.0 – Prepared for technical decision-makers evaluating Google Apps Script deployment strategies.
The "This application was created by a Google Apps Script user" banner is a mandatory security feature. Google includes this footer on standalone web apps to notify users that the application was built by an independent developer, not by Google itself.
While there is no single "disable" button for this banner, you can bypass or remove it using several methods depending on your environment. 1. Embed the Script in a Website
The most reliable way to hide the banner for external users is to embed your Apps Script Web App within another webpage.
Method: Use an tag on your own domain or a platform like GitHub Pages.
Security Header: You must ensure your script allows embedding by setting the X-Frame-Options header to ALLOWALL in your doGet() function: javascript
return HtmlService.createHtmlOutputFromFile('Index') .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); Use code with caution. Copied to clipboard 2. Google Workspace Internal Use
If you are part of a Google Workspace (Business, Enterprise, or Education) organization, the banner behavior changes based on who is viewing it.
Same Domain: The banner is automatically hidden for users logged into the same Workspace domain as the script owner.
External Users: If someone outside your organization views the app, they will still see the banner. 3. Verification and Standard Cloud Projects
For production-level applications, you can move away from the default Apps Script banner by associating your script with a standard Google Cloud Platform (GCP) project.
Brand Verification: By switching to a standard Cloud project, you can submit your app for OAuth verification. Verified apps often provide a more professional interface, though this is primarily for removing the "unverified app" warning during login rather than the footer itself.
Add-on Development: Publishing your script as a Google Workspace Add-on often removes this specific web-app footer because the code runs within a sidebar or dialog inside a Google app (like Sheets or Gmail) rather than as a standalone webpage. 4. Client-Side Workarounds (Not Recommended for Users)
Some developers use browser-based tools to hide the banner on their own screens, but these do not remove it for other visitors.
Chrome Extensions: Tools like "Custom JavaScript for websites" can inject CSS (e.g., #warning display: none !important; ) to hide the element locally.
In-Script CSS: Standard CSS within your HtmlService file cannot hide the banner because the banner exists in the "parent" frame, and browser security policies prevent scripts inside an iframe from modifying the parent page.
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