Remove This Application Was Created By A Google Apps Script User Free |link|

Use code with caution.

Use standard JavaScript fetch() in your hosted HTML file to send and receive data from your Apps Script URL. Because the user never visits the actual Google Apps Script web link directly, they will never see the Google warning banner. Summary Comparison Difficulty Permanence Low (Google updates code often) iFrame Embedding Medium (Depends on layout) Workspace Restrictions High (Internal domain only) API Architecture High (Permanent professional fix)

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 code with caution

Here is how to do that for free:

function doGet() var html = HtmlService.createHtmlOutputFromFile('index'); html.setTitle('Your Application Title'); // Set your application title here return html; However, this is less reliable than the previous

In some specific configurations, embedding your Web App within a (google.com) can mask the header. However, this is less reliable than the previous methods as Google frequently updates their iframe security policies. Important Security Note

If you have outgrown the limitations of the Apps Script web app environment and need a genuinely professional public URL without any injected code, the best path forward is migrating the frontend logic to a dedicated cloud hosting platform. the warning banner is typically suppressed.

As a result, via code or hacks. There is no removeWarning() function. The only official methods are:

If your app uses sensitive scopes and will have >100 users, submit for Google verification:

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.