Cookie Manager

A full cookie editor for Chrome & Brave — view, add, edit, delete, import & export cookies for the current site.

Install · Features · How it works · Releases

---

Editing a cookie in the browser means opening DevTools, finding the Application tab and squinting at a table. Cookie Manager puts cookies in your toolbar instead: every cookie for the site you're on, searchable and filterable, fully editable — with lossless export and import in three standard formats. No account, no API keys, no build step, and it never makes a single network request.

Features

• View cookies for the current site — live list with search (name, value or domain) and filters: All, Session, Persistent, Secure, HttpOnly, each with a live count
• Full cookie editing — name, value, domain, path, expiry (date-time picker), SameSite (None/Lax/Strict) plus Host-only, Session, Secure and HttpOnly flags; renaming or moving a cookie replaces the old one in a single save
• Add & delete with undo — one-click add pre-filled for the current site; delete one, or delete all with a two-click confirm; every delete carries an Undo in the toast
• Export three ways — JSON (full detail, re-importable), header string (name=value; …) and Netscape cookies.txt for curl / wget / yt-dlp — to the clipboard or as a file
• Import with auto-detect — paste JSON, a header string or a Netscape file; the format is detected automatically and invalid lines are skipped
• Site favicon in the header — shows the site's own icon when available, falling back to the cookie glyph
• Theming & behavior — Auto/Dark/Light theme, six system-style accent colors (blue by default), sort by name / domain / expiry / size, show-domain-on-cards, export-to-clipboard-or-file preference
• Zero footprint — no background page, no network requests, MV3, zero dependencies, no build step

Design

The popup follows the same clean, Apple-native system as the sibling Temp Mail extension: system type, one inset grouped list with hairline separators, tinted badges, native-feeling switches and segmented controls, and semantic system colors in light and dark. Copying a cookie's value is one always-visible click; the row expands in place to edit; the delete button appears on hover and every delete is undoable. The popup height fits its content up to the 600 px cap. There are no bundled fonts or remote assets. Icons are Lucide (ISC), see THIRD_PARTY_LICENSES.md; product and design context lives in PRODUCT.md.

Install

Works in Chrome and Brave (Manifest V3). No build step, no dependencies.

git clone https://github.com/nullstacks/cookie-manager.git

Then open chrome://extensions (or brave://extensions) → enable Developer mode → Load unpacked → select the cloned folder.

Prefer a zip? Download the .zip attached to the latest release, unzip, and load that folder instead.

📖 Full walkthrough — including updating, uninstalling and troubleshooting: INSTALL.md

How it works

Reading & writing	Everything goes through the browser's own chrome.cookies API for the active tab's site — the popup itself never touches the network. Changes apply immediately, including HttpOnly cookies you can't touch from page JavaScript.
Export	JSON keeps full detail (domain, path, SameSite, flags, store) and re-imports losslessly; the header string is what you paste into curl -H; Netscape is the standard cookies.txt format understood by curl, wget and yt-dlp.
Import	Paste any of the three formats — detection is automatic (JSON → header → Netscape). Missing fields are defaulted sanely: domain = current site, expiry = +1 year for header cookies.
Safety nets	Deletes are restorable via Undo; "Delete all" asks for a second click; name and expiry are validated before the browser sees them, and rejections surface a readable message instead of a silent failure.

Privacy

• Everything (cookies you view, your settings) stays local in your browser — the extension makes no network requests at all
• No analytics, no trackers, no telemetry
• Uses only the cookies, clipboardWrite and storage browser APIs; <all_urls> host access exists only so the cookies API can read and write per-site, never to fetch anything (site favicons shown in the header are fetched by the browser itself from the site's favicon URL — same as Chrome's own tab UI — and are never stored or sent anywhere)
• Nothing is stored beyond your own preferences in chrome.storage.local

Contributing

Issues and PRs welcome — open an issue or fork and send a pull request. For bugs, include your Chrome/Brave version and the site or cookie that misbehaves.

License

MIT © Nullstacks