CookieVault Editor

TL;DR: CookieVault Editor is a free, MIT-licensed Manifest V3 browser extension that gives you complete control over the cookies stored by your browser — view, edit, search, export, multi-profile, and end-to-end encrypted sync. Built as the modern replacement for the EditThisCookie extension Google removed from the Chrome Web Store in September 2024.

CookieVault Editor is a Manifest V3 browser extension that gives developers, QA engineers, and privacy-aware users full read-write control over the cookies their browser stores. It is open source under the MIT license, ships with zero telemetry, and reproduces the per-site cookie-editor workflow that EditThisCookie users relied on for nearly a decade1 — extended with end-to-end encrypted cross-device sync, cookie history with undo, and named multi-account profiles.

Who CookieVault Editor is for

In short: Anyone who needs to view, edit, or move cookies more than occasionally. The three core audiences are developers debugging session and auth flows, QA engineers reproducing user-reported bugs, and privacy-conscious users who want first-class control over the small text records browsers leave behind on their behalf.

Four common workflows the Editor optimizes for:

If your job involves looking at the Application → Cookies tab in DevTools more than once a week, the Editor will save you minutes every session.

What the Editor does

In short: Everything a serious cookie manager should do — full CRUD with attribute editing (SameSite / HttpOnly / Secure / Expires / Domain / Path), search across all domains, multi-format export (JSON / Netscape / HAR), multi-account profile switching, dark mode. Free tier has no functional limits.

Eight Editor capabilities, in approximate decreasing order of how often a typical user touches them:

  1. View every cookie for the current site (or all sites) in a sortable, filterable list
  2. Edit any attribute — Name, Value, Domain, Path, Expires, HttpOnly, Secure, SameSite — with inline validation
  3. Search across all cookies by name, value, or domain pattern (regex supported in Pro)
  4. Export to JSON (structured), Netscape cookies.txt (for curl / wget), or HAR (for full request archives)
  5. Delete single cookies, all cookies for a domain, or all cookies matching a pattern
  6. Create new cookies from scratch with all attributes pre-validated
  7. Switch profiles — load a saved named cookie snapshot, push the previous one to history
  8. Sync across devices (Pro) — every cookie change replicates to your other browsers via end-to-end encrypted channels

Browser support

In short: Every modern Chromium browser uses the same Chrome Web Store build (Chrome, Edge, Brave, Opera, Vivaldi, Arc). Firefox uses a separate Manifest V3-compatible build on the Firefox Add-ons site. There are no separate Mac / Windows / Linux builds — extensions are browser-only.

BrowserSourceNotes
ChromeChrome Web StorePrimary target; tested on every Chrome stable release
EdgeEdge Add-ons (or CWS)Same Chromium build, dual-distributed
BraveChrome Web StoreSame build as Chrome
OperaChrome Web StoreSame build (Opera supports CWS extensions)
VivaldiChrome Web StoreSame build
ArcChrome Web StoreSame build
FirefoxFirefox Add-onsSeparate Manifest V3 compatible build
SafariNot supportedSafari Web Extensions have a different model

A 2024 StatCounter snapshot2 shows the seven browsers above cover roughly 95% of global desktop browser usage, so the combined Chromium + Firefox build set lands the Editor in front of nearly every workflow that needs it.

Pricing

In short: Free forever for local cookie management. $4/month or $36/year (25% off) for the Pro tier with end-to-end encrypted sync, cookie history, named profiles, and team sharing. No per-cookie limits, no time-bombed trials. See the pricing page for the full breakdown.

The pricing line is deliberately simple — two tiers, three numbers:

The Free tier covers the entire EditThisCookie-equivalent workflow. Pro is only worth the money if you use more than one device and want them to stay in sync, or if you want the safety net of cookie-history undo.

How CookieVault Editor compares

CookieVault Editor sits in the same product space as Cookie-Editor and the (now-removed) EditThisCookie. The honest comparison:

How to install

  1. Chrome Web Store — search “CookieVault Editor” and click “Add to Chrome”
  2. Edge Add-ons — same build, Microsoft store
  3. Firefox Add-ons — separate Firefox Manifest V3 build
  4. Direct CRX (Opera / Vivaldi / Arc / Brave / Whale / Sidekick) — download the signed CRX from the GitHub release page and drag it into the extensions page
  5. Build from source — clone the GitHub repo, run npm install && npm run build, load the unpacked extension via chrome://extensions → Developer Mode

See the download page for the actual store links and source URL.

See also

Footnotes

  1. EditThisCookie was the dominant Chrome cookie editor for nearly a decade before being removed from the Chrome Web Store on 2024-09-28 following a maintainer-account transfer incident. See our EditThisCookie alternative page for the full timeline with footnoted sources. ↩

  2. Cross-browser desktop usage shares are tracked publicly by StatCounter (search “StatCounter desktop browser market share”). StatCounter blocks automated HEAD / GET probes, so we do not link a deep URL that would link-rot in our footnote checker; the rolling 12-month chart from the StatCounter site is the canonical reference. The “Chromium browsers + Firefox cover ~95% of desktop” claim is approximate and varies month to month. ↩