Cookiebro alternative

TL;DR: CookieVault is an open-source Cookiebro alternative on Manifest V3. It provides Cookiebro’s combined feature set — cookie management plus whitelist-based auto-deletion — across two focused, MIT-licensed extensions (Editor and Guardian), and adds end-to-end encrypted sync. Install both for full Cookiebro parity, or just the half you need.

CookieVault is a free, MIT-licensed alternative to Cookiebro that delivers the same two core capabilities — cookie management and whitelist-based auto-deletion — but as two focused extensions rather than one bundle. CookieVault Editor handles cookie viewing and editing; CookieVault Guardian handles auto-delete on tab close. Both are Manifest V3 native and open source, and Guardian’s cleanup reaches beyond cookies to localStorage, IndexedDB, and other modern storage.

What Cookiebro does, and how CookieVault maps to it

In short: Cookiebro bundles cookie editing and auto-deletion in one extension. CookieVault splits them into Editor (management) and Guardian (cleanup) so you install only what you need. Install both for the full Cookiebro-equivalent feature set.

Why two focused extensions

In short: Separation of concerns keeps each extension lighter and lets you grant only the permissions you use. A developer editing cookies does not need auto-deletion running; a privacy user wanting cleanup does not need a full editor.

Three reasons CookieVault splits what Cookiebro bundles:

• Minimal permissions — Editor requests cookie access; Guardian requests the broader browsingData access needed for cleanup. Installing only one means granting only the permissions that feature actually requires.
• Lighter footprint per extension — you are not carrying auto-delete machinery if you only edit cookies, or a full editor UI if you only want cleanup.
• Independent updates — each extension ships on its own cadence, so a fix to one does not require re-reviewing the other.

You can, of course, install both — and most users replacing Cookiebro will — for the complete combined feature set, sharing a single Pro account across them.

What CookieVault adds over Cookiebro

In short: Open-source code, Manifest V3-native architecture, expanded cleanup scope, and end-to-end encrypted sync.

• MIT open source + reproducible builds — Cookiebro is closed source; CookieVault publishes all code and lets you verify the store binary against a Git commit.
• Expanded cleanup scope — Guardian cleans localStorage, sessionStorage, IndexedDB, Cache Storage, and Service Worker registrations, not just cookies.
• End-to-end encrypted sync — cookies, profiles, and whitelist rules replicate across devices with client-side encryption (Pro).
• Manifest V3 native — built on the platform Chrome supports going forward.

Feature comparison

How to migrate from Cookiebro

1. Open Cookiebro settings and export your cookies and whitelist (JSON)
2. Install CookieVault Editor and CookieVault Guardian from the Chrome Web Store
3. Import the cookie JSON into Editor (Settings → Import)
4. Import the whitelist into Guardian (Settings → Import)
5. Verify cookies appear in Editor and whitelist domains appear in Guardian
6. Test Guardian’s cleanup on a non-whitelisted site, then enable Pro sync if you want cross-device replication

See also

• CookieVault Editor — cookie management half
• CookieVault Guardian — auto-delete half
• Cookie AutoDelete alternative — if you primarily want cleanup
• EditThisCookie alternative — if you primarily want editing
• Pricing — Free / Pro / Team breakdown
• What is a cookie? — the underlying protocol