How to view and edit cookies in Chrome manually

Whether you're debugging session state, testing how a site behaves with a modified consent cookie, or copying a login between profiles, sooner or later you need to change a cookie by hand. Chrome gives you two built-in options, and both run out of road quickly.

What DevTools can and can't do

DevTools → Application → Cookies shows every cookie for the current page, and you can edit a value by double-clicking it or delete rows. But creating a new cookie from scratch, changing flags like HttpOnly or SameSite, setting a precise expiry, or moving cookies between machines is somewhere between clunky and impossible — and document.cookie in the console can't even see HttpOnly cookies. EditThisCookie used to fill this gap; it was delisted in 2024, and much of its former audience is still looking for a maintained replacement.

Use a dedicated cookie editor

CookieVault Editor is an MV3-native cookie manager, open source under the MIT license. Click the icon on any site and it lists every cookie for that site, grouped by domain, with search-as-you-type filtering by domain or cookie name — no digging through DevTools panels.

Edit every field inline

Expand a cookie and edit anything: name, value, domain, path, SameSite, the Secure / HttpOnly / Host-only flags, and expiry (session, or until a specific date). Because it uses Chrome's cookies API rather than page scripts, it can create and modify HttpOnly cookies that console tricks can't touch. Deleting is one click with a confirmation toast, and the popup is reactive — if the site or another extension changes a cookie while you're looking, the list updates by itself. Partitioned (CHIPS) cookies are surfaced with a "P" tag so you can tell which partition a cookie belongs to.

Import and export as JSON

Export puts all visible cookies into a tidy JSON file you can re-import on another machine or hand to a colleague reproducing a bug. Import is drag-and-drop and accepts two formats: CookieVault's own cookievault/v1 and EditThisCookie's legacy bare-array export — so a JSON file you saved from EditThisCookie years ago loads with no conversion step.

Nothing leaves your browser

Cookie data is sensitive by definition — session cookies are your logins. The Editor stores everything locally, makes no network requests, and ships no analytics, telemetry or third-party SDKs. Being MIT-licensed, the source is public, so none of this has to be taken on faith. For the complementary problem — automatically deleting the cookies you don't want to keep — see how to auto-delete cookies except a whitelist.