5 min read · 14 views

Cookie AutoDelete is disabled in Chrome — what happened and what to do

TL;DR: Chrome disabled all Manifest V2 extensions in its stable channel by early 2025, and Cookie AutoDelete — which was never rewritten for Manifest V3 — was disabled along with them. It still works on Firefox. For Chromium browsers, the Manifest V3 successor is CookieVault Guardian, which restores tab-close cleanup and extends it beyond cookies.

Cookie AutoDelete is the privacy-community extension that automatically deleted cookies when you closed a browser tab — and on Chromium browsers it no longer works. The cause was not a bug or a maintainer dispute; it was the completion of Chrome's long-planned Manifest V2 sunset^[1]. This post explains what happened, the architectural reason a beloved extension could not simply be patched, and the Manifest V3 path forward.

What happened

In short: Cookie AutoDelete had a reported peak of around 280,000 weekly active Chrome users^[2]. Chrome's Manifest V2 sunset disabled all MV2 extensions in the stable channel between June 2024 and early 2025. Cookie AutoDelete depended on a persistent MV2 background page and was not rewritten for MV3, so it was caught in the disablement wave.

Google announced the Manifest V3 transition in 2019 and published a phased timeline^[1:1]. The final phase — disabling all Manifest V2 extensions in Chrome stable — began rolling out in June 2024 and completed in early 2025. Cookie AutoDelete was one of thousands of privacy and ad-blocking extensions affected.

The extension was created by Kenny Do and maintained as a community open-source project under the Cookie-AutoDelete GitHub organization^[3]. Its core mechanism — listening to tab-removal events from a persistent background page and reconciling the open-tab set against the cookie store — was built on exactly the MV2 architecture that Manifest V3 removed.

Why it could not just be patched

In short: Manifest V3 is not a minor API revision — it removes the persistent background page Cookie AutoDelete's tab-tracking logic depended on, replacing it with ephemeral service workers. Porting the extension meant re-engineering its core, which the maintainers indicated was not on their roadmap.

Three architectural changes in Manifest V3 that broke the extension:

• No persistent background page. MV3 replaces the always-running background page with a service worker that the browser can terminate at any time. Cookie AutoDelete's tab-lifecycle tracking assumed a process that never stopped.
• Declarative-first APIs. MV3 pushes extensions toward declarative APIs (e.g., declarativeNetRequest) and away from the imperative patterns MV2 allowed. Some of Cookie AutoDelete's logic had no direct declarative equivalent.
• Stricter lifecycle guarantees. Reliable "the last tab on this domain just closed, clean now" detection is harder when your code can be suspended mid-operation, requiring a different state-management approach.

The maintainers signalled^[3:1] that the MV3 rewrite was not a priority. The repository remains open under the MIT license — a community fork could undertake the rewrite — but none has reached maturity.

What you lost (and on which browsers)

In short: On Chrome / Edge / Brave / Opera / Vivaldi / Arc, you lost automatic tab-close cleanup entirely. On Firefox, nothing changed — Cookie AutoDelete still works there because Firefox kept Manifest V2 support.

Browser-by-browser status as of 2026:

If you were relying on Cookie AutoDelete for privacy hygiene on a Chromium browser, the gap is real: cookies, localStorage, and other site data now persist across sessions until you clear them manually.

What to do

In short: On Chromium browsers, install a Manifest V3 successor that restores tab-close cleanup. On Firefox, you can stay on Cookie AutoDelete or migrate for the broader storage coverage and cross-browser whitelist sync.

The seven-step migration checklist:

1. Identify your browser — if Firefox-only and satisfied, you can stop here
2. Export your Cookie AutoDelete whitelist — while it is still installed, Settings → Export → save JSON
3. Install CookieVault Guardian from the Chrome Web Store (or Edge / Firefox Add-ons)
4. Import the whitelist — Guardian Settings → Import → Cookie AutoDelete JSON
5. Verify your domains transferred — check the Whitelist tab
6. Test cleanup — visit a non-whitelisted site, close the tab, reopen, confirm you are logged out
7. Tune cleanup targets — enable/disable storage types if a specific site breaks

The Manifest V3 alternative

In short: CookieVault Guardian is a strict superset of Cookie AutoDelete — same whitelist / greylist UX, plus localStorage / IndexedDB / Cache Storage / Service Worker cleanup that Cookie AutoDelete never had. Free and MIT-licensed.

What Guardian carries over from Cookie AutoDelete, and what it adds:

• Carried over: tab-close cleanup, whitelist, greylist, wildcard patterns, Firefox container support, manual "clean now" button
• Added: localStorage, sessionStorage, IndexedDB, Cache Storage, and Service Worker cleanup; cross-device whitelist sync (Pro); Manifest V3 compatibility
• Honest tradeoff: Guardian's install is larger (~480 KB vs ~150 KB) and it is newer on Firefox, where Cookie AutoDelete has a multi-year track record

The full feature-parity matrix and migration guide is on our Cookie AutoDelete alternative page.

See also

• Cookie AutoDelete alternative — full migration guide and feature matrix
• CookieVault Guardian vs Cookie AutoDelete — direct comparison
• CookieVault Guardian — the Manifest V3 successor
• Auto-delete cookies on tab close — setup walkthrough
• EditThisCookie is gone — the parallel story for the cookie editor
• What is a cookie? — the underlying protocol