Gmail Bulk Unsubscribe & Cleanup Tool vs GMClean

Gmail Bulk Unsubscribe & Cleanup Tool helps Gmail users handle unwanted messages in batches. It supports automatic one-click and manual unsubscribe methods, and can delete messages from multiple senders, archive email, manage labels, and mark messages read or important. Filters cover date range, email size, category, sender, and labels; the tool can also download email metadata as CSV. It works through the Gmail API, so users must create their own Google Cloud project and OAuth credentials. The maker says it runs locally without external servers or data collection, keeping email on the user's machine. Its requested access is described as read and modify permissions, with users controlling their own OAuth app. Setup requires Docker or Python 3.9+ with uv, along with the user's Google credentials. The software is free under the MIT license. A one-on-one setup service is listed at $8, paid once. Deleted messages go to Gmail Trash and can be recovered there within 30 days.

GMClean is a free, self-hosted web tool for scanning email headers, classifying messages, unsubscribing in bulk, deleting email, and exporting data. It works with Gmail, Outlook, and custom IMAP mailboxes, with up to 10 mailboxes connected at once. GMClean fetches headers such as sender, subject, and List-Unsubscribe details without downloading message bodies. It can scan INBOX, Spam, Promotions, Trash, and other IMAP folders. Inbox analysis includes a 0–100 health score based on five weighted factors, sender insights, and email age distribution. Classification uses heuristic rules, with optional Gemini assistance for ambiguous cases. Users can unsubscribe with one click using RFC 8058 support or unsubscribe in bulk; bulk deletion runs in batches of 500 messages. Exports include selected subscriptions with resubscribe links and scanned emails in CSV format. The project documents deployment with npm, Docker, or Docker Compose. It says app data stays in browser IndexedDB and there is no cloud database or telemetry. Credentials are encrypted with AES-256-CBC before storage, and setup requires an ENCRYPTION_SECRET. The repository is MIT-licensed.