Remove This Application Was Created By A Google Apps Script User Free [repack] -
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: To remove the "This application was created by
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
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.
The light-blue warning banner stating "This application was created by a Google Apps Script user" is a security feature automatically added by Google to all web apps deployed via Apps Script
. There is no official "button" to turn it off for free consumer accounts, but you can bypass or hide it using these methods: Google Issue Tracker 1. Embed in a Website or Google Site The most common legitimate way to remove the banner is by your web app URL into another page. Google Sites: When you embed a script into a Google Site , the banner is typically suppressed for users. External Iframe: You can host a simple HTML page on a platform like GitHub Pages and use an
to load your Apps Script URL. This often hides the banner, though it may not work if your app requires a Google Account login. 2. Google Workspace (Business/Education) If you are part of a Google Workspace organization: The banner is to other users within the same domain.
For external users, the only way to remove it is by publishing the script as a verified Google Workspace Add-on , which requires a more complex review process. 3. Use a Browser Extension (Personal Use Only)
If you only want to remove the banner for yourself or on a specific display (like a public kiosk), you can use a browser extension to hide the element: Custom CSS/JS Extensions: Use tools like uBlock Origin In the code snippet above, replace 'Your Application
or a custom JavaScript injector to set the banner's display style to Example Script:
The banner often uses a specific ID or class that can be targeted with: document.getElementById('warning').style.display = 'none'; 4. Technical Workarounds Self-Hosting Content: Instead of using HtmlService.createHtmlOutput()
, you can host your front-end content (HTML/CSS/JS) on a standard web host and use the Apps Script only as a back-end API (receiving requests). This avoids the Google-hosted UI entirely. Important Note:
Google includes this banner as a security precaution to warn users that the script is not an official Google product and may access their data. iframe embed to bypass this banner?
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: Open your Google Apps Script project
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:
- Open your Google Apps Script project.
- Click on the "Deploy" button in the top right corner of the editor.
- Select "New deployment".
- Choose "Web App" as the deployment type.
- In the "Web App" settings, uncheck the box next to "Display a 'This application was created by a Google Apps Script user' message".
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
- Use a custom title that reflects your application's name or purpose.
- Consider adding a custom logo or branding to your application to give it a more professional look.
- If you're deploying your application to a wider audience, consider removing the message to provide a more seamless user experience.
Troubleshooting
- If you've followed the steps above and the message still appears, ensure that you've saved your changes and redeployed your application.
- If you're using a custom domain or URL for your application, ensure that the message is not being cached by your browser or server.
The banner "This application was created by a Google Apps Script user" is a mandatory security feature for scripts running on free consumer accounts. While there is no "off" switch in the settings, several workarounds can effectively hide or remove it for your users. ⚡ Quick Solutions (Free) 1. Embed as an iFrame
The most common free method is to embed your Apps Script URL into a standard HTML page using an .
The Result: The banner is often suppressed or hidden within the container of the hosting site.
Free Hosting: You can host the container page for free on platforms like GitHub Pages or Google Sites.
Crucial Setting: In your script editor, you must set the X-Frame-Options to ALLOWALL to permit embedding. 2. Browser Extensions (For Personal Use)
If you are the only person using the app, or you can control the user's environment (e.g., a dedicated display), you can use a browser extension like uBlock Origin or Custom JavaScript for websites to inject CSS.
Use this CSS to hide the banner: #warning display: none !important; . 🛠️ Comparison of Methods Difficulty iFrame Embedding Public-facing apps/websites Google Sites Internal or team-based tools Workspace Account Professional/Commercial use Browser Extension Personal use or dedicated kiosks 💡 Important Considerations
Security Verification: For a permanent, "official" removal without workarounds, you must associate your script with a Google Cloud Project and go through the OAuth verification process. This typically requires a verified domain and a privacy policy.
Domain Restrictions: If you use a Google Workspace account, the banner will not appear for other users within the same domain.
Terms of Service: Ensure your app complies with Google's commercial use rules if you are monetizing the service.
⚠️ Note: Standard CSS within your HtmlService code (like style="display:none") will not work because the banner is generated outside of your app's body tag in a parent iFrame controlled by Google.
If you'd like to try the iFrame method, I can provide the specific code snippets for your index.html and code.gs files. Is there any way to remove the banner? : r/GoogleAppsScript
Step 3: Submit for verification
If your app uses sensitive scopes and will have >100 users, submit for Google verification:
- Go to OAuth consent screen > Submit for verification
- Provide a video, privacy policy, and terms of service
- Wait for Google’s review (3–5 business days)
Once verified, the scary message disappears and users see your app name and branding.
Part 5: Common Myths About Removing the Warning
| Myth | Truth | |------|-------| | “You must pay Google $100 every year.” | Only for restricted scopes. Basic verification is a one-time ~$25 fee. | | “Deleting and recreating the script removes it.” | No. The warning follows the script ID and sharing settings. | | “Publishing to the Marketplace automatically removes it.” | No. You still need verification unless publishing internally. |
Conclusion
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.
Alex was a freelance developer who lived by a simple rule: automate everything
. One afternoon, while scouring a forum for productivity hacks, he found a legendary "Life Dashboard" script designed to sync tasks, emails, and calendars into one seamless interface [1, 2].
He spent hours customizing the code. It felt perfect—until he hit "Deploy." A glaring, grey banner appeared at the top of his screen:
"This application was created by a Google Apps Script user."
To a perfectionist like Alex, it was an eyesore. It felt like leaving a price tag on a designer suit [1]. He tried every trick he knew: He dove into the , trying to hide the container [1, 3]. He attempted to use
to mask the source, but the banner just followed him like a shadow [1].
He even tried writing a second script to "delete" the banner from the first one—a digital snake eating its own tail [1, 2].
Deep in a developer thread, he finally found the "secret." The banner wasn't a bug or a mistake; it was Google's security seal
[1, 3]. It existed to let users know the app wasn't an official Google product, preventing phishing and keeping the ecosystem safe [1].
Alex realized that removing it via code was nearly impossible because it was injected at the server level
, far above his script's pay grade [1, 3]. The only way to get a "clean" look was to upgrade to a Google Workspace Enterprise account or deploy the project as a Google Cloud
web app—options that cost money he didn't want to spend [3].
He sat back and looked at the banner again. Instead of a flaw, he started seeing it as a badge of honor
. It was proof that he had built something from scratch using nothing but logic and a free tool [1, 2]. He stopped trying to hide it and shared the dashboard with his friends, banner and all.
As it turns out, no one else cared about the grey bar. They were too busy being amazed that the app actually worked [1, 2]. of Google Apps Script or see the workarounds for creating a custom UI without the banner?
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.
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.
The message " This application was created by a Google Apps Script user
" 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?
4) Testing vs production
- While in testing mode (unverified app), Google will show warnings and limited user access. To remove warnings and generic labels, complete verification and publish to production.