Cookie DevTools

Cookie DevTools is a cookie editor and cookie manager built for developers. See, edit, import, export, decode and protect the cookies of the site you're working on — in the toolbar popup, in Chrome's side panel or in a DevTools panel. No ads. No tracking. Nothing you do here leaves your device. One request, once: after you have used it on a few different days, it asks whether you would leave a review, with a separate link for reporting a problem, and it never asks again. EDIT COOKIES SAFELY - Every cookie for the current site, including partitioned (CHIPS) cookies set by embedded frames - Add, edit and delete with checks for what the browser would reject: SameSite=None without Secure, __Host- and __Secure- prefix rules, the 4096-byte limit, invalid characters - Edits never destroy the original: if the browser refuses a change, the cookie stays as it was - Host-only, partition and exact expiry are kept unless you change them - Delete All asks first, and deletes can be undone DECODE COOKIE VALUES - JWT: header and payload, with exp, iat and nbf as dates and a clear expired state (decoded on your device, never verified or sent anywhere) - URL-encoded, Base64 and Base64URL values, and pretty-printed JSON, each with a copy button IMPORT AND EXPORT COOKIES - Import JSON exported by other cookie editors, Playwright or Puppeteer; a Netscape cookies.txt file; Set-Cookie or Cookie headers; or a curl command - Preview before anything is written: what will be created, what will be replaced, and what will be skipped and why - Export cookies to JSON, cookies.txt (curl/wget), a curl command or a Cookie header — copy or download, for every cookie or just the ones you select - Encrypt an export with a password (AES-256-GCM, key derived with PBKDF2) and decrypt it on import, with the usual preview before anything is written. PROTECT AND BLOCK - Protect a cookie: when a site changes or deletes it, your saved value is put back - Block a cookie: it is deleted whenever a site sets it again WATCH COOKIE CHANGES - Live view of cookie changes on the page you're on - Optional recording for one site or all sites, with the cause (set, overwritten, expired, evicted), value and time — off until you turn it on, and kept only on your device BUILT FOR DAILY DEVELOPER WORK - Environment profiles: save a site's cookies as "staging-admin" and switch back in one click - Sort by name, domain, expiry or size; filter by Secure, HttpOnly, Session, Partitioned or SameSite=None - Side panel that stays open and follows your tabs - A Cookies panel in DevTools that follows the page you're inspecting - Keyboard friendly: / to search, arrow keys to move, Enter to edit, Delete with undo - Dark mode, with WCAG AA contrast in both themes PERFECT FOR - Debugging sign-in, session and CSRF problems - Moving a test session between browsers, profiles or automated tests - Testing consent banners, A/B buckets and feature flags - Generating curl commands with your session cookies - Checking third-party and partitioned cookies PERMISSIONS, PLAINLY When you add Cookie DevTools, Chrome warns that it can "Read and change all your data on all websites". That is how Chrome describes access to every site, and a cookie editor needs it: an extension can read and write a site's cookies only if it has access to that site, and you might be working on any site. Cookie DevTools uses that access only for cookies, and to see which site the active tab is on. It never reads page content, never injects scripts, and never sends data anywhere. Beyond that it asks only for local storage for your settings and for the side panel — not for the tabs permission. If you limit its site access in Chrome’s extension settings, it says so on sites it can’t read and offers to allow that site, rather than showing an empty list.