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.
If you still have Cookie AutoDelete installed (even disabled), your rules can come across:
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.
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.
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.
| COOKIE AUTODELETE | COOKIEMOP |
|---|---|
| Auto-clean on tab close | Yes — same model: cleaned only when no other tab uses the site |
| Whitelist / greylist | Yes, unlimited, free |
| Badge cookie counter | Yes |
| localStorage & site-data cleaning | Yes — optional scopes up to IndexedDB, CacheStorage, Service Workers |
| Whitelist import | Yes — 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 exceptions | Yes — keep one login cookie while the rest of the site is cleaned (part of Pro, $9.99 once) |
| Open source | Yes — MIT, the store build comes from the public repo, no build step, no dependencies |
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-14 | COOKIE AUTODELETE V3 | COOKIE GUARDIAN | COOKIEMOP |
|---|---|---|---|
| Source | Open source (MIT), per its store listing | Not open source, as its developer states | Open source (MIT) |
| Price | No price shown on its listing | Free; Premium is $3.49 once | Free; Pro is $9.99 once |
| Free whitelist size | No limit stated on its listing | 15 sites (23 after leaving a review), per its listing | No limit, no review needed |
| Licence check | No paid tier | Checks with a licensing server at start-up and hourly, per its developer | Offline signature check on your device, no activation call |
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.
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.