A cookie editor does not need access to every website you visit
Free, and it installs without the read-all-your-data warning.
Every cookie editor I looked at asks for access to all websites at install time. None of them need it. A cookie editor needs the site you opened it on, Chrome has supported asking for exactly that for years, and the broad request is there because it is less work than handling permission granted later.
So this one asks per site, when you open it there. The install prompt is short and the difference in what you can do is nothing.
The other decision worth explaining is the side panel. A popup closes the moment you click back into the page, which is precisely when you want to change a cookie and watch what happens. A panel stays open while you test.
How to use it
- Go to the site whose cookies you want.
- Open the panel and grant access to that site when it asks.
- Every cookie for the site is listed. Search if there are a lot, which there usually are.
- Edit any field, including SameSite, Secure, HttpOnly and expiry.
- Export as JSON if you need to move a session to another profile.
The 400 day thing
Chrome silently truncates any cookie expiry longer than 400 days. Set ten years, get 400 days, no message. I lost a genuinely annoying amount of time to that before working out what was happening.
So this shows the real limit and the real resulting date. If you ask for longer, it tells you what you will actually get rather than accepting the number and quietly doing something else.
What it can access, and why
| Permission | Why it needs it |
|---|---|
| Cookies | Reading and editing them is the entire function. Edits happen in your browser's own cookie store. |
| The current tab | To know which site you are on, so it can show that site's cookies. |
| Side panel | So the editor stays open beside the page while you test a change. |
| Per-site access (optional) | Requested for one site at a time, when you open the editor there. |
Full detail in the privacy policy.
FAQ
Can I use this to stay logged in somewhere longer?
Sometimes. Extending a session cookie past its expiry works when the site trusts the cookie by itself. Plenty of sites also record the session server-side with their own timeout, and in that case the cookie will still be valid while the server has already forgotten you. No extension can fix that half.
Is editing cookies safe?
For your own accounts on your own machine, yes, though you can log yourself out by mangling a session cookie. It is worth exporting before a big change. What it is not safe for is pasting in a cookie someone sent you, since that is how session hijacking works and you would be the target.
Why can I not see httpOnly cookies in the page itself?
That is the point of the flag. JavaScript on the page cannot read them, which is what protects a session cookie from a cross-site scripting bug. This extension can show them because it uses the browser's own cookie interface rather than reading them from the page.
Does it sync my cookies anywhere?
No. There is no server involved at any point. Import and export write to and read from a file you choose.