Remove This Application Was Created By A Google Apps Script User Free !exclusive! ❲SAFE ✪❳

</style> </head> <script> window.onload = (e) => const gasappurl = 'YOUR_GAS_WEB_APP_URL_HERE'; let ifm = document.getElementById('gasiframe'); ifm.src = gasappurl + window.location.search;

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.

Sometimes, modifying your deployment settings can change the banner's visibility.

To replace the message with your own app name and developer info:

While you cannot remove this message entirely for unverified apps, you replace it with your own branding and remove the “free user” label by completing Google’s OAuth verification process . &lt;/style&gt; &lt;/head&gt; &lt;script&gt; window

Developer forums show this is a widely shared frustration. On the Google Developer Forum, one developer shared: "I have over 29 screenshots that gave ppl that were using my app script a heart attack thinking I was scamming them". Another added: "This makes my custom google sheet feature completely unusable for real world customers, I cannot have this warning message displayed to them when they go to authorize the script".

Google treats internal embedding between Apps Script and Google Sites as a safe environment. As a result, the banner is natively removed without breaking the responsive layout logic of your underlying HTML templates. Method 3: Keep it Within a Google Workspace Domain

If your application demands absolute professionalism, brand uniformity, and no intrusive warnings, Google Apps Script might eventually bottleneck your growth. Consider migrating your front-end code to these highly capable, completely free developer ecosystems:

Google explicitly warns that "scripts and add-ons are provided 'as is' and without warranty of any kind". The extension author himself cautions: "pages from scripts.google.com are not trustworthy. Clearly by installing this plugin you must be aware of that." Therefore, only install this extension if you fully understand and accept the potential risks. To replace the message with your own app

Instead of returning HTML with HtmlService.createHtmlOutput() , program your script to accept requests and return raw data using ContentService .

Note: If you change "Who has access" to "Anyone" (making it public to users outside your business domain), the banner will reappear to those outside users to protect their security.

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.

If you use a Google Workspace account, the banner will not appear for other users within the same domain . Another added: "This makes my custom google sheet

Users outside your domain will see the unverified app warning screen. Additionally, unverified apps have a user cap (typically 100 users), and you'll see a warning message each time users attempt to authorize the script.

In your Google Apps Script code, you must add the .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL) setting. This allows your web app to be embedded within external frames.

This makes your application look entirely native to your brand, and the end-user will never see the underlying script URL or the default banner. Method 4: Use a Browser Extension for Internal Use

Only hide the banner using these methods if your application is safe, serves legitimate business functions, and handles user data responsibly. If you want to fine-tune your setup, let me know:

When you create a Google Apps Script application, it automatically generates a message that says "This application was created by a Google Apps Script user." While this message may be useful for debugging purposes, it's not exactly the most visually appealing thing to see on your application. Moreover, it can make your application look less professional and raise questions about its legitimacy.