Live cookie monitoring
Every cookie for the active tab, updated the moment it changes. The toolbar badge keeps the count in view.
Features
Every cookie on the page, under your control
CookieMan is a Manifest V3 cookie editor for Chromium browsers that turns cookie work into a two-click job: inspect what a site set, change any attribute, and move cookies between tools in whichever format they expect.
No account No network calls MIT licensed
Nine things it does well
No dashboards, no onboarding wizard. The popup opens on the cookies for the tab you are looking at and everything is one click away.
Full attribute editing
Name, value, domain, path, expiration, Secure, HttpOnly, SameSite, host-only and partitioned — all editable.
Import with auto-detection
Paste anything. The parser identifies the format, previews what will be written, then applies it.
Export in six formats
Current site or every accessible cookie, converted to the format you need, copied or downloaded.
Instant search
Filter by name, value or domain as you type — useful when a site sets fifty cookies.
Partitioned (CHIPS) aware
Reads and writes the partition key, so third-party cookies under CHIPS behave correctly.
Local by design
No servers, no analytics, no network code at all. Cookie data never leaves the browser.
Light, dark & system
A popup that matches your OS theme, in English or Russian, with the choice remembered.
Manifest V3
Built on the current extension platform — no deprecated background pages, no forced sunset.
Inspect
Real-time cookie monitoring
Open the popup and the list is already populated for the active domain — name, value, domain, path, expiry and the flags that matter, without expanding a single row. The toolbar badge carries the cookie count, so you can watch a login flow write and rotate its session cookie without opening DevTools.
- Updates as the browser writes, deletes or replaces cookies
- Search filters by name, value or domain as you type
- HttpOnly cookies are visible — the API sees what page scripts cannot
- Clear empty states for restricted pages such as
chrome://
Edit
Full attribute editing, including the awkward flags
Editing a cookie value is easy anywhere. Editing a SameSite=None; Secure
partitioned cookie without breaking it is not. CookieMan exposes every field the
browser accepts, applies them in one write, and tells you when the browser rejects the
result instead of silently doing nothing.
| Field | Notes |
|---|---|
| Name | The cookie key, rewritable in place. |
| Value | Any string, including long JWTs and signed session blobs. |
| Domain | Host-only or dot-prefixed for subdomain sharing. |
| Path | Scope the cookie to a route prefix. |
| Expiration | Pick a date and time, or switch to a session cookie. |
| Secure | Restrict the cookie to HTTPS requests. |
| HttpOnly | Hide the cookie from JavaScript in the page. |
| SameSite | None, Lax or Strict cross-site behaviour. |
| Host-only | Send only to the exact host, never subdomains. |
| Partitioned | CHIPS partition key for third-party contexts. |
Add a cookie from scratch, delete one row, or clear every cookie for the current domain when you need a clean session.
Import
Paste anything — detection does the rest
Cookie data arrives in whatever shape the tool that produced it felt like using: a
cookies.txt file from curl, a JSON array from another extension, a
Cookie: header copied out of DevTools, a Base64 blob from a CI secret. Paste
it as-is. The parser identifies the format, reports what it found, and shows a preview of
the cookies it is about to write so nothing is applied blind.
- 1 Paste into the import box
- 2 Read the detected format and cookie count
- 3 Check the preview rows
- 4 Apply — cookies are written per domain
Malformed lines are reported rather than dropped quietly, so a partial paste never turns into a mystery session bug.
Export
Export in the format the next tool expects
Choose the scope — just this site, or every cookie the browser will hand over — then the output format. Copy it to the clipboard for a quick paste into a REST client, or download a file for curl, a test fixture or a teammate.
curl & wget REST clients Test fixtures Another browser profile
Need a conversion without installing anything? The online cookie converter runs the same parser in the page. Destination-specific files: curl cookies.txt, CHIPS / partitionKey, JSON vs cookies.txt loss table.
Interchange
Six supported cookie formats
Every format below works in both directions — import and export — in the extension and in the online converter.
| Format | What it is | Typical consumer | Example |
|---|---|---|---|
| JSON Array EditThisCookie / Cookie-Editor style | Full-fidelity array of cookie objects with every attribute. The safest choice for backups and transfers. | Cookie extensions, test fixtures | [{ "name": "session_id", "value": "abc123", "domain": ".example.com",
"path": "/", "secure": true, "httpOnly": true, "sameSite": "lax" }] |
| JSON Map name → value | Flat key/value object. Compact and easy to read, but attributes are not preserved. | Quick scripts, API clients | { "session_id": "abc123", "theme": "dark" } |
| Netscape cookies.txt tab-separated | The classic seven-field text format understood by command line HTTP clients. | curl, wget, yt-dlp | .example.com TRUE / TRUE 1789200000 session_id abc123 |
| Header String Cookie: request header | A single line ready to paste into a request header, REST client or fetch call. | Postman, DevTools, fetch() | Cookie: session_id=abc123; theme=dark |
| Set-Cookie lines response headers | One Set-Cookie header per cookie, attributes included — how a server would issue them. | Server logs, HAR files | Set-Cookie: session_id=abc123; Path=/; Secure; HttpOnly; SameSite=Lax |
| Base64 encoded JSON array | A JSON array wrapped in Base64 for pasting through fields that mangle punctuation. | CI secrets, chat transfer | W3sibmFtZSI6InNlc3Npb25faWQiLCJ2YWx1ZSI6ImFiYzEyMyJ9XQ== |
Privacy
Local by architecture, not by promise
Cookies are credentials. An extension that can read them should be boring and auditable,
so this one has no backend to talk to: there is no fetch call, no analytics
SDK and no remote configuration anywhere in the source. The
code is on GitHub under the MIT license if you
would rather check than trust.
Cookie values are read from the browser API, rendered in the popup, and forgotten when
it closes. The only thing stored is your theme and language choice.
| Permission | Why it is requested |
|---|---|
cookies | Read, create, update and delete cookies. This is the whole product — without it there is nothing to show. |
storage | Remember your theme and interface language between sessions — one storage key holding two values. Preferences only, never cookie data. |
tabs / activeTab | Resolve the domain of the tab you are looking at so the popup lists the right cookies and the badge shows the right count. |
host access | Chrome scopes the cookies API by host. Broad host access is what allows the extension to read cookies for the site you are on and for “all cookies” export. |
In context
CookieMan next to Chrome DevTools
DevTools is excellent at inspecting one page in depth. An extension wins on the repetitive parts: moving, converting and re-applying cookies dozens of times a day.
| Task | DevTools Application panel | CookieMan |
|---|---|---|
| See cookies for the current site | Application → Cookies, after opening DevTools | One click on the toolbar icon, count visible on the badge |
| Edit an attribute | Inline table editing, one cell at a time | A form with every attribute, validated and saved together |
| Bulk import cookies | Not supported | Paste any supported format, preview, apply |
| Export / convert | Copy rows by hand | Six formats, current site or everything, copy or download |
| Watch cookies change live | Refresh the panel | List and badge update as the browser writes cookies |
Coming from a Manifest V2 extension that Chrome retired? The EditThisCookie migration guide covers what changed and how to bring your cookies across. Cookie-Editor users should start at the Cookie-Editor alternative instead.
Feature questions, answered
Does CookieMan send my cookies anywhere?
No. The extension contains no network code at all — no fetch, no analytics, no telemetry. Everything happens inside the popup, and data only leaves the browser if you export a file. See the privacy policy.
Which cookie formats can it import and export?
JSON Array, JSON Map, Netscape cookies.txt, Header String, Set-Cookie lines and Base64-encoded JSON. Imports are auto-detected, so you can paste without picking a format first. The same engine powers the free online cookie converter.
Can it edit HttpOnly and Secure cookies?
Yes. Because the extension uses the browser cookies API rather than page JavaScript, HttpOnly cookies are fully readable and editable, and the Secure, SameSite, host-only and partitioned flags are all writable.
Does it support partitioned (CHIPS) cookies?
Yes. The partition key is read and written, so third-party cookies stored under CHIPS stay in the right partition when you edit or re-import them.
Is it a Manifest V3 extension?
Yes — version 1.1.0 ships as Manifest V3 with a service worker background script, so it keeps working after Chrome's Manifest V2 shutdown. If you used EditThisCookie, see the migration notes.
Does it work in Edge, Brave and other Chromium browsers?
It targets the Chromium extension platform, so Chrome and Edge are the tested targets and other Chromium browsers that support Manifest V3 load the same package.
How much does it cost?
Nothing. It is free, MIT-licensed and open source — there is no account, no paid tier and no upsell.
Ready to stop fighting cookies?
Install the extension, or convert a file first in the browser-only converter.
Free and MIT-licensed · Chrome, Edge and other Chromium browsers · Nothing leaves your machine