Deploy Gmail Cleaner on your own server.

Gmail Cleaner is a privacy-focused self-hosted tool to bulk unsubscribe, delete, archive, and mark Gmail messages as read by sender. It runs locally with your own Google OAuth credentials and keeps auth tokens in persistent storage.

Deploy Gmail Cleaner View source

Your infrastructureAutomatic HTTPSNo lock-in

Screenshots

A closer look at Gmail Cleaner.

Setup time

A few minutes

Deployment

Your own server

Services

1 connected service

Why Gmail Cleaner

Everything you need, running where you choose.

Get the full Gmail Cleaner experience with Easypanel handling the repetitive infrastructure work around it.

Bulk unsubscribe and delete

Remove unwanted newsletters and sender groups with progress tracking.

Mark read, archive, and labels

Apply common Gmail mailbox actions in bulk.

OAuth callback support

Exposes the callback listener port for Google OAuth login flow.

Inbox cleanup at scale

Process large amounts of email by sender with bulk actions and filters.

Privacy-first deployment

Runs on your infrastructure with your own Google credentials.

Persistent auth and data

Stores OAuth token and app data in a mounted volume.

How it works

From template to live app in three steps.

Easypanel turns the template into real services, storage, and domains on the server you already control.

Already have Easypanel? Open your dashboard at the URL or IP of your own installation.

Installation guide

Open your dashboard

Visit the URL or IP of your Easypanel installation and choose the target project.

Choose Gmail Cleaner

Open Templates, select Gmail Cleaner, then review its service names and configuration.

Deploy and open your app

Easypanel starts every service and provisions an HTTPS domain for you.

Installation options

The template asks for these values before creating your services.

Option	Default	Required
App Service Name	gmail-cleaner	Required
Gmail Cleaner Image	ghcr.io/gururagavendra/gmail-cleaner:v1.3.0	Required
Credentials JSON Paste the full Google OAuth client JSON content	—	Required
OAuth Callback Internal Port	8767	Optional
OAuth Callback External Port	8767	Optional
OAuth Host Hostname used when building OAuth redirect URI	$(PRIMARY_DOMAIN)	Optional
Enable Web Authentication	true	Optional

Before you deploy

Paste your downloaded Google OAuth client JSON into Credentials JSON before deploying. In Google Cloud Console, add an Authorized redirect URI that uses your OAuth host and external OAuth port (for example, https://your-domain/). After deploy, open the app domain, click Sign In, and complete the OAuth flow.

Resources

Project documentation and source code.