Remove This Application Was Created By A Google Apps Script User — Top-Rated

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.

| Situation | Can you remove the line? | |-----------|----------------------------| | Unverified external app | ❌ No | | Internal Workspace app | ⚠️ Changes to domain name | | Verified public app | ✅ Yes (replaced with your name) | The message “This application was created by a

If you just want a clean user experience for a small tool, consider making the app internal or hosting it on another platform (e.g., Glide, Bubble, or a simple Node.js server).


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 Have you successfully removed the Apps Script warning

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)

The banner will only disappear once Google trusts the application. or a simple Node.js server).

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