The Text:
"This application was created by a Google Apps Script user."
How to remove this text:
If you are using the MailApp or GmailApp service in your script, Google automatically appends this footer to prevent spamming. You cannot remove it using the standard free tier of Google Apps Script.
To remove it, you must switch to using the Gmail API in your script. Here is a basic example of how to send an email without the footer using the API:
function sendEmailWithoutFooter() var recipient = 'example@email.com'; var subject = 'Test Subject'; var body = 'This is the body of the email.';// Create the raw email content var raw = 'To: ' + recipient + '\r\n' + 'Subject: ' + subject + '\r\n\r\n' + body;
// Encode the message var encodedMessage = Utilities.base64EncodeWebSafe(raw);
// Send using the Gmail API Gmail.Users.Messages.send( raw: encodedMessage , 'me');
Note: You must enable the Gmail API service in your script project (Services > Gmail API) for this code to work.
The banner "This application was created by a Google Apps Script user" is a security feature implemented by Google to inform users that the web app they are accessing was created by a third party and not by Google itself.
While there is no direct "off" switch in the script settings for free accounts, you can remove or bypass it using the following methods: 1. Using a Google Workspace Account
If you are part of a Google Workspace organization, the banner will not be displayed to other users within your same domain.
Limitations: External users outside your domain will still see the banner.
Verification: For the banner to be removed for all users (including those outside your domain), the script must typically be published as a verified Google Workspace Add-on or associated with a verified Google Cloud project. 2. Embedding in a Website (iframe)
You can hide the banner by embedding your Google Apps Script web app into another webpage using an .
How it works: Host a simple HTML file on a service like GitHub Pages and use an iframe to display your script.
Constraint: This method primarily works if the web app is deployed with the access setting "Anyone" (anonymous access). If it is set to "Anyone with a Google account," the login prompt may fail to load inside the iframe due to security restrictions. 3. Deploying via Google Sites
Embedding the script directly into a Google Site can often suppress the standard Apps Script header, as Google Sites handles the integration more seamlessly for users. Summary of Options User Account Type Effectiveness Workspace Internal Hidden for members of your own domain. GCP Verification Workspace/Paid Hidden for all users once verified. iframe Embedding Free/Workspace Hidden but may break login for non-anonymous apps. Google Sites Free/Workspace Hidden in many embedded contexts. Remove web app warning for Anyone with Google Account
How to Remove the "Created by a Google Apps Script User" Banner for Free
When you deploy a Google Apps Script as a web app, Google automatically inserts a grey header banner that reads: "This application was created by another user, not by Google." This is a security measure to inform users they are interacting with third-party code rather than an official Google product.
While there is no "off" switch in the settings for free consumer accounts, there are several effective workarounds to hide or remove this banner.
1. Embed the App in a Google Site (Most Effective Free Method)
The most reliable way to hide the banner for free is to embed your script's URL into a Google Site. When the web app is viewed through an iframe on a Google-hosted site, the warning banner is typically suppressed.
Step 1: In your Apps Script editor, click Deploy > New deployment.
Step 2: Select Web app and set "Execute as" to your account and "Who has access" to "Anyone". Step 3: Copy the Web App URL.
Step 4: Go to your Google Sites project, click Embed, paste the URL, and publish the site. 2. Self-Host with a GitHub Pages Wrapper
If you want to host the app on your own domain or a custom site for free, you can use a "wrapper" approach.
Create a simple HTML file (hosted on GitHub Pages) that contains an pointing to your Apps Script URL.
Ensure your Apps Script deployment is set to XFrameOptionsMode.ALLOWALL in your doGet function to allow it to be framed by external sites. 3. Use Browser Extensions (Internal/Personal Use)
If the app is only for your personal use or a small internal team, you can use a browser extension to hide the banner locally.
Install an extension like Custom JavaScript for websites or uBlock Origin.
Note: This only works for users who have the extension installed. 4. Professional Alternatives (Verification)
For a permanent solution that doesn't involve workarounds, you can link your script to a verified Google Cloud Project (GCP).
Once your app is verified by Google, the banner disappears for all users.
This process is free but requires a detailed security review if your script uses sensitive data.
For a walkthrough on how to properly deploy and access your web app URL:
To remove the "This application was created by a Google Apps Script user" banner for free, you must embed your Google Apps Script web app into another webpage. Google automatically adds this banner to standalone web apps as a security notice to users.
The most effective free method is to use Google Sites or GitHub Pages to iframe the application. Phase 1: Prepare Your Google Apps Script
Before embedding, you must modify your code to allow other sites to "frame" your application. Open your Google Apps Script project.
In your doGet() function, locate where you return your HTML output.
Add the .setXFrameOptionsMode() method to your HtmlService call: javascript
function doGet() return HtmlService.createHtmlOutputFromFile('Index') .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); Use code with caution. Copied to clipboard
Deploy as a Web App: Click Deploy > New Deployment. Set "Who has access" to Anyone. Copy the Web App URL provided after deployment. Phase 2: Choose an Embedding Method Method A: Using Google Sites (Easiest)
This is the most seamless way to remove the banner for free within the Google ecosystem. Go to Google Sites and create a new site. On the right panel, click Embed. Paste your Web App URL into the "By URL" tab. Resize the embedded box to fit your application perfectly.
Publish your site. When users visit your Google Site URL, the Apps Script banner will be hidden. Method B: Using GitHub Pages (Custom URL)
Use this if you want a cleaner URL or more control over the surrounding page. Create a new repository on GitHub. Create a file named index.html.
Paste the following iframe code, replacing YOUR_SCRIPT_URL with your actual web app URL:
Use code with caution. Copied to clipboard
Enable GitHub Pages in the repository settings to host the site for free. Alternative: Verified Publisher (Advanced)
If you do not want to embed the app, the only "official" way to remove the banner is to link your script to a Google Cloud Project and go through the OAuth verification process. This is complex and usually requires a privacy policy and a domain name. Summary of Limitations The Text:
Permissions: Embedding only hides the visual banner. Users will still see an authorization popup the first time they run a script that requires access to their Google data.
Mobile View: Ensure your CSS is responsive, as iframes can sometimes behave differently on mobile devices.
To remove the message "This application was created by a Google Apps Script user" (or "This application was created by another user, not by Google") from your web app, you should understand that this is a security feature designed to protect users from phishing or malicious scripts .
While there is no "free" button to toggle this off, here are the most effective ways to manage or remove it: 1. The Official Professional Route (Verified Publisher)
The most "correct" way to remove the banner for all users is to have your application verified by Google. Once verified, the banner typically disappears because the publisher is now trusted .
Create a GCP Project: You must associate your Apps Script project with a standard Google Cloud Platform (GCP) project .
Request Verification: Submit your app for OAuth verification through the Google Cloud Console. This process can take several weeks and may require identifying yourself (which often requires a paid Workspace account) . 2. The Browser-Side "Fix" (For Personal Use)
If you only want to hide the banner for yourself or a small group of users who are willing to install an extension, you can use a browser-based CSS injector .
Use a Browser Extension: Install an extension like Custom JavaScript for websites or Tampermonkey.
Inject CSS: Use the following code to hide the banner's container: javascript document.getElementById('warning').style.display = 'none'; Use code with caution. Copied to clipboard
Note: This only works for users who have the extension active . 3. Alternative Hosting (Avoiding the Apps Script Domain)
If you want a professional look without the banner, you can move your front-end away from script.google.com.
Embed via iFrame (Partial Success): Some users try embedding the Apps Script URL in another website. However, the banner often remains because it is tied to the Apps Script domain .
Use a Front-End Framework: Host your UI on a free platform like GitHub Pages or Netlify and use the Google Apps Script purely as a Backend API (via doGet or doPost). This completely bypasses the Apps Script web app UI and its associated banners . 4. Configuration Check (Workspace Users)
If you are part of a Google Workspace (business or education), ensure you are deploying the app with the correct settings. Execute As: Set this to "Me" (your admin/account).
Who has access: Set this to "Anyone within [Your Domain]" rather than "Anyone" . In some organizational settings, this can minimize the severity of the warning banner. Summary of Options: Verification Free / Time Intensive Professional, public-facing apps . Browser Extension Private internal tools or personal dashboards . Separate Hosting Free (GitHub/Netlify) Developers who want a fully custom UI . "This application was created by a Google Apps Script user
Are you building this app for public use or for private/internal tasks?
Removing the "This application was created by a Google Apps Script user" banner is a common goal for developers who want to provide a professional, white-labeled experience for their users. While this footer is a security feature designed by Google to prevent phishing, there are several legitimate ways to minimize its visibility or remove it entirely depending on how you deploy your project. Understanding the Banner’s Purpose
Before attempting to remove the notice, it is important to understand why it exists. Google automatically attaches this disclaimer to any Web App or script-based UI that is not part of a verified Google Workspace domain or a published Google Cloud project. It serves as a warning to end-users that the application is third-party and not officially vetted by Google. Method 1: Upgrade to a Google Workspace Account
The most straightforward way to remove the "created by a user" branding is to use a professional Google Workspace (formerly G Suite) account rather than a personal @gmail.com account.
When you deploy a Web App within a Workspace domain and set the access permissions to "Anyone within [Your Domain]," the banner is typically removed for internal users. This is because Google assumes a level of trust within a managed organizational environment. However, if the app is shared with external users outside the domain, the banner may reappear to protect those external parties. Method 2: Link to a Standard Google Cloud Project
By default, Apps Script projects use a "Default" Google Cloud Platform (GCP) project. To gain more control over the branding and consent screens, you can switch to a "Standard" GCP project. Create a project in the Google Cloud Console. Go to "Project Settings" and copy your Project Number.
In your Apps Script editor, go to Project Settings and click "Change Project." Enter your Project Number. Configure your OAuth Consent Screen in the GCP Console.
While this doesn't always instantly vanish the footer, it allows you to submit your application for "Verification." Once Google verifies your app, the "unverified app" warnings disappear, and the footer becomes much less intrusive. Method 3: Use a Custom Domain with an Iframe Wrapper
If you are hosting the script as a Web App, you can embed it into your own professional website using an iframe. This doesn't technically delete the code from the script's source, but it places the application within your own branded environment.
To do this, ensure your script's HtmlService is set to allow embedding:
output.setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL);
By wrapping the script in a container on your own domain (e.g., yourdomain.com), the user’s focus remains on your URL and your website’s header/footer, making the Google disclaimer at the very bottom of the frame feel like a minor technical footnote rather than a primary branding element. Method 4: Transition to AppSheet
If your Apps Script is primarily used for data entry or internal tools, consider migrating the logic to AppSheet, Google’s no-code app building platform. AppSheet provides a significantly more professional interface and does not include the "Apps Script user" footer. Since AppSheet is now included in most Workspace tiers, it offers a more "enterprise-ready" look and feel for your tools without the script-specific baggage. Important Security Note
You should never attempt to use CSS or JavaScript hacks (like DOM manipulation) to hide the Google footer programmatically. Google’s security headers often block such attempts, and more importantly, bypassing security notices can lead to your script being flagged for "Terms of Service" violations, resulting in the permanent suspension of your project or your entire Google account.
For a truly "free" experience that looks professional, focus on clean UI design within your HtmlService files. A well-designed, functional application will often earn the user's trust regardless of the small disclaimer at the bottom of the page.
The message " This application was created by a Google Apps Script user How to remove this text: If you are
" is a mandatory security banner added by Google to identify that a web app was not developed by Google itself. While there is no official "free" button to toggle it off, you can bypass or hide it using the following methods: 1. Embed as an iFrame
The most common way to hide the banner is by embedding your Apps Script web app into another website using an : In your Apps Script code ( ), ensure your HtmlOutput allows iframing by adding: javascript HtmlService.createHtmlOutputFromFile(
) .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); Use code with caution. Copied to clipboard
: When viewed directly via the script URL, the banner remains, but when viewed through your external site's iframe, the banner is typically hidden. 2. Embed in a Google Site
If you don't have a personal website, you can embed the web app into a Google Sites : Open a Google Site, use the tool, and paste your web app's "Exec" URL.
: This often strips the grey header/footer branding for users within the same organization or domain. 3. Use Workspace Internal Deployment If you are part of a Google Workspace
(formerly G Suite) organization, the banner is often automatically removed for other users within your same domain
: Deploy the web app and set access to "Anyone within [Your Domain]" instead of "Anyone" or "Anyone with a Google Account". 4. Browser-Side Hiding (For Personal Use)
If you only want to remove the banner for yourself (e.g., for a public kiosk or personal dashboard), you can use a browser extension to hide the element. : Use an extension like uBlock Origin or a custom CSS injector (like ) to set the banner's container to display: none;
: This only works on the browser where the extension is installed; other users will still see the banner. Summary of Limitations No Script-Level Removal : There is no
you can write inside the script itself to delete the banner because it is injected by Google's servers outside of your HTML body. Security Purpose
: Google maintains this banner to prevent phishing, so complete removal for anonymous public users is intentionally difficult. Further Exploration View community discussions on Stack Overflow regarding the X-Frame-Options workaround. Read more about web app deployment configurations on the official Google for Developers exact HTML code to create the iframe for your own website?
There is no direct "free" button or setting to remove the "This application was created by a Google Apps Script user" banner within the Google Apps Script editor. This banner is a security feature automatically applied to web apps and deployments that are not formally verified.
However, you can use several workarounds to hide or bypass this warning: Professional & Official Methods
Embed in Google Sites or External Webpages: The banner is often hidden when you embed the script's URL as an within a Google Site or your own website.
Google Workspace Accounts: If you are part of a Google Workspace organization, users within your same domain generally will not see this banner when accessing your scripts.
Create an Add-on: Converting your script into a verified Google Workspace Add-on removes the banner entirely for all users, though this requires a more formal development and review process. Technical Workarounds
Host the HTML Yourself: You can host your app's frontend HTML/JS on a service like GitHub Pages and call your Google Apps Script as a backend API. This prevents the banner from appearing because users are not viewing a script.google.com URL directly.
Browser Extensions (Developer Only): For personal use or public displays, you can use browser extensions like uBlock Origin or custom CSS injectors to set the banner's container (often with an ID like warning) to display: none;. Note that this only hides the banner for you, not other users.
Removing "This application was created by a Google Apps Script user" from a Google Apps Script Project
When you create a Google Apps Script project, it automatically adds a message to the project's UI, stating "This application was created by a Google Apps Script user." While this message is a good indication that the project was created using Google Apps Script, you might want to remove it for aesthetic or professional reasons. In this report, we'll explore how to remove this message from your Google Apps Script project.
Understanding the Message
The message "This application was created by a Google Apps Script user" is a default message added by Google Apps Script to all projects created using the platform. This message is displayed at the top of the project's UI and serves as a indicator that the project was built using Google Apps Script.
Removing the Message
To remove the message, you need to use the setTitle method of the HtmlService class. Here's an example code snippet that removes the message:
function doGet()
var html = HtmlService.createHtmlOutputFromFile('index');
html.setTitle('Your Application Title'); // Set your application title here
return html;
In the code snippet above, replace 'Your Application Title' with your desired application title. By setting a custom title using the setTitle method, the default message "This application was created by a Google Apps Script user" will be replaced with your custom title.
Additional Steps
If you want to completely remove the message and not replace it with a custom title, you can use the following approach:
By following these steps, you can remove the message from your Google Apps Script project.
Conclusion
Removing the "This application was created by a Google Apps Script user" message from a Google Apps Script project is a straightforward process. By using the setTitle method or adjusting the deployment settings, you can easily remove or replace the message with a custom title. This report provides a step-by-step guide on how to remove the message, giving you more control over the UI of your Google Apps Script projects.
Recommendations
Troubleshooting
There are three common reasons people search for “remove this application was created by a google apps script user free”:
Each scenario requires a different approach. Below, we cover all three for free.
The phrase “remove this application was created by a google apps script user free” brings thousands of people to forums and help desks every month. The confusion is understandable—Google’s warning text is stark and alarming. But now you know the truth: it’s a standard security feature, not a flaw.
You can remove the application causing the warning for free in under two minutes. Or, if you are the developer, you can remove the warning from your app by completing Google’s free verification process.
Do not pay for cleaners, removers, or so-called “experts” who promise to delete the warning. They are preying on your frustration. Use the official, free methods outlined above, and you will never be bothered by the “Google Apps Script user” message again.
Next Step: Open your Google Account permissions page and take control of every application connected to your data—right now, for free.
If you’ve built a Google Apps Script project and shared it with others, you may have noticed an authorization screen that says:
“This application was created by a Google Apps Script user free”
This message appears because your script hasn’t been verified by Google. It’s Google’s way of warning users that the app comes from an unverified developer (you, the free user).
While you cannot remove this message entirely for unverified apps, you can replace it with your own branding and remove the “free user” label by completing Google’s OAuth verification process.
No, it just means Google hasn’t reviewed the app. Only run scripts from sources you trust.