CookieMop

The original Cookie AutoDelete is gone. Here is how to replace it in two minutes.

Chrome stopped running Manifest V2 extensions in 2025 (Chrome 139, stable on August 5, 2025), and the Chrome Web Store removed the last ones on August 31, 2026 (Chrome’s timeline). The original Cookie AutoDelete was a Manifest V2 extension and went with them. There are now several Manifest V3 options, compared below. CookieMop does the same job — delete a site's cookies when its last tab closes, keep the sites you whitelist — rebuilt from scratch for Manifest V3, open source, with a one-click import for your old whitelist.

Install CookieMop — free

Migrate your whitelist

If you still have Cookie AutoDelete installed (even disabled), your rules can come across:

1

Export from Cookie AutoDelete

Open its settings → Expression Options → Export expressions to JSON. If the extension is already gone, skip to step 3 — rebuilding a whitelist takes a minute in the popup as you browse.

2

Import into CookieMop

CookieMop options → Import from Cookie AutoDelete → choose the JSON file. WHITE entries become whitelist, GREY become greylist. Wildcard prefixes like *.example.com are normalized automatically.

3

Check the delay and scope

Default: 15 seconds after the last tab closes, cookies only. Both are adjustable in options — the delay from 0 to 60 seconds, the scope up to localStorage, IndexedDB, CacheStorage and Service Workers.

What carries over, honestly

COOKIE AUTODELETECOOKIEMOP
Auto-clean on tab closeYes — same model: cleaned only when no other tab uses the site
Whitelist / greylistYes, unlimited, free
Badge cookie counterYes
localStorage & site-data cleaningYes — optional scopes up to IndexedDB, CacheStorage, Service Workers
Whitelist importYes — reads Cookie AutoDelete's own JSON export
Wildcard expressions (*.example.com)Not yet — subdomains of a listed domain are covered automatically; pattern rules are on the roadmap
Per-cookie exceptionsYes — keep one login cookie while the rest of the site is cleaned (part of Pro, $9.99 once)
Open sourceYes — MIT, the store build comes from the public repo, no build step, no dependencies
One real difference: "cleaned when the browser closes" (greylist) is implemented as clean-on-next-startup, because that is the only reliable hook Manifest V3 offers. The practical effect is the same; the timing label is different. Limitations are documented in the README, not hidden.

Manifest V3 options, compared

The original Cookie AutoDelete is gone, but it is no longer the only choice. Here is how the three Manifest V3 extensions that do this job differ, using only what each one publishes.

AS OF 2026-10-14COOKIE AUTODELETE V3COOKIE GUARDIANCOOKIEMOP
SourceOpen source (MIT), per its store listingNot open source, as its developer statesOpen source (MIT)
PriceNo price shown on its listingFree; Premium is $3.49 onceFree; Pro is $9.99 once
Free whitelist sizeNo limit stated on its listing15 sites (23 after leaving a review), per its listingNo limit, no review needed
Licence checkNo paid tierChecks with a licensing server at start-up and hourly, per its developerOffline signature check on your device, no activation call
Check before you decide. These facts come from each extension's public store listing and one public GitHub thread, read on 2026-10-14. Listings change. CookieMop is an independent project and is not affiliated with either of the others. Where CookieMop falls short today: no wildcard patterns yet (see above), and Pro costs more than Cookie Guardian's Premium. If a free, MIT-licensed extension is all you need, Cookie AutoDelete V3 is a reasonable choice.

Why trust a new extension with all-site access

You shouldn't have to take anyone's word for it. The CookieMop extension makes zero network requests — no analytics, no accounts, no remote code, and nothing to phone home to. That claim is checkable: the entire runtime source is plain JavaScript on GitHub with no build step, so the code you read is the code that runs. Even the optional Pro license is verified on your own device, with no activation call. The one Danorie endpoint is the key lookup page, which receives the email and order number you type so it can issue your key; it does not store them.

Questions

Is it free? Yes. The core is free and stays free: auto-clean on tab close, a whitelist and greylist with no size limit, the one-click import and the wider cleaning scopes. Nothing that was free has moved behind a payment. Pro ($9.99, one payment, no subscription) adds two extras: rule profiles and the per-cookie whitelist.

Firefox? Not yet — Chrome first, while the need is acute. The source is MIT-licensed if you want to help.

Something missing? Open an issue — the roadmap is shaped by what migrating users actually miss.

Install CookieMop — free