This cookie editor reads cookies in the three formats people pass around most, shows every cookie in an editable table, and writes them back out in the format the next tool needs. It's useful when a cookie export from one browser or extension has to go into another tool, a script or a browser profile, and the formats don't match. Everything happens in this page; the cookies you paste are not sent to our server or stored.
What a cookie editor does
A cookie editor lets you look inside cookies and change them without touching the website that set them. Each cookie has a name and a value, plus a few attributes that tell the browser where and how to send it:
- Domain and path: which websites and pages receive the cookie. A domain that starts with a dot, such as
.example.com, also covers subdomains. - Expires: when the browser deletes it. A cookie without an expiry is a session cookie and usually disappears when the browser closes.
- Secure: only sent over HTTPS.
- HttpOnly: hidden from page scripts, sent only with requests.
- SameSite: whether the cookie goes along with requests from other sites (Strict, Lax or None).
Browsers have a built-in editor too. In Chrome, open DevTools and go to Application → Storage → Cookies, then pick a site; there you can view, add, edit and delete cookies and filter them by name or value (Chrome DevTools documentation). The DevTools pane doesn't list an export option, which is why cookie editor extensions and tools like this one exist.
Formats it reads and writes
| Format | Looks like | Common source | Read | Write |
|---|---|---|---|---|
| JSON | [{"name":"sid","value":"…","domain":".example.com",…}] |
Cookie editor browser extensions, exports from apps | Yes | Yes |
| Playwright / Puppeteer JSON | [{"name":"sid","value":"…","domain":".example.com","path":"/","expires":…}] |
Automation scripts, storageState files |
Yes | Yes |
| Netscape cookies.txt | One cookie per line, seven tab-separated fields | curl, wget, many download tools | Yes | Yes |
| Cookie header | sid=abc; theme=dark |
Copied from a request in DevTools | Yes | Yes |
JSON
Most cookie editor extensions export a JSON list with one object per cookie. The fields vary a little between tools: the expiry may be called expirationDate, expires or expiry, in seconds or milliseconds, and SameSite may be written lax, Lax or no_restriction. The editor accepts all of these and also reads a Playwright storageState file, which keeps its cookies under a cookies key.
When it writes JSON for extensions, it uses the common field set: domain, expirationDate, hostOnly, httpOnly, name, path, sameSite, secure, session, storeId and value.
Playwright and Puppeteer
Playwright's browserContext.addCookies() takes name and value, plus either a url or both domain and path. expires is Unix time in seconds, and sameSite is one of Strict, Lax or None (Playwright documentation). The Playwright output follows those rules, so you can pass it straight to addCookies(). Session cookies get expires: -1.
Netscape cookies.txt
The Netscape format is a plain-text file with one cookie per line and seven fields separated by tabs: domain, a TRUE/FALSE flag for subdomains, path, a TRUE/FALSE secure flag, the expiry in seconds since 1970 (or 0), the name and the value. Lines starting with # are comments, except that a #HttpOnly_ prefix marks an HttpOnly cookie (curl's description of the format). The editor writes a # Netscape HTTP Cookie File header line, which many tools look for.
Cookie header
A Cookie: request header only contains names and values: name=value; name2=value2. It doesn't say which website the cookies belong to, so type the website's domain in the Website domain box before converting header cookies to another format. Header cookies are marked Secure by default; untick it if the site runs over plain HTTP.
How to use the cookie editor
- Paste your cookies into the box at the top. Pasting reads them right away; you can also click Read cookies.
- Check the summary. The line next to the buttons says how many cookies were found, in which format, and for how many domains.
- Edit any domain, name, value or path in the table. Tick or untick Secure and HttpOnly, and choose SameSite. Use the filter box to find cookies by name or domain, Delete to remove one, and Add cookie to create one.
- Convert. Choose the output format under the table, then Copy it or Download it as a file (
cookies.jsonorcookies.txt). - Clear the editor when you're done.
Expiry dates are shown in UTC. Editing an expiry isn't supported in the table; convert, edit the number in the output if you must, and paste it back.
Use your cookies in a Multime profile
Multime profiles import cookies in the same three formats: JSON, Netscape cookies.txt and name=value pairs. Open a profile, paste the cookies into its Cookies field and choose whether to merge them with the cookies the profile already has. Multime stores them encrypted on your computer and saves the profile's cookies when it closes, so you can export them again later. Read more on the cookie import and export page.
Keep cookies safe
A login cookie is as good as a password: whoever has it can often use the account without signing in. So:
- Only edit cookies for accounts you own or manage with permission. Using someone else's session cookies is unauthorized access.
- Don't share cookie files by email or chat. If you must move them, delete the copies afterwards.
- Log out to end a session. Logging out on the website usually invalidates the session cookie on the server, which makes any copies useless.
- Mind the tab. This page keeps cookies only in the open tab's memory. Click Clear or close the tab when you're done.