Support
Common questions, and how to report a problem.
Common questions
Why does it ask for access to all websites?
Chrome won't show an extension a site's cookies unless the extension has permission for that site. A cookie editor that works on any site needs permission for every site. cookieZ asks for it the first time you open it, not at install, and you can say no. You can also take it back later from the extension's Details page in chrome://extensions.
It says "No cookies on this page" on a page that has cookies
Chrome doesn't let extensions read cookies on its own pages, such as chrome:// pages and the Chrome Web Store. Switch to a normal website and open cookieZ again.
It doesn't open in incognito
Chrome turns extensions off in incognito unless you allow them. Go to chrome://extensions, open cookieZ's Details, and turn on "Allow in incognito". Incognito cookies are kept separate from your normal ones, and deleting in one never touches the other.
Is there a keyboard shortcut?
Yes. Press Alt+Shift+K to open cookieZ, / to jump to the search box, N to add a new cookie, and Esc to go back from the editor, export, import or help. In the table, the arrow keys move between cookies, Enter edits one, Space ticks it, K keeps it and Delete deletes it, after asking. To change the first one, go to chrome://extensions/shortcuts. If another extension already uses Alt+Shift+K, Chrome leaves cookieZ without one, and you can pick your own there.
What does Keep do?
The bookmark button on each row marks a cookie as Kept. A cookie marked as Kept is left out of every delete cookieZ makes, including "All sites". It only affects cookieZ's own delete buttons. The website that set the cookie can still change or remove it. To see every cookie you've kept, on any site, click "Kept cookies" under the delete options. You can stop keeping any of them there.
I deleted or changed the wrong cookies. Can I get them back?
Yes, for 10 minutes. This works for a delete, an import, or a cookie you saved in the editor. Click Undo next to the message, or open cookieZ again and click Undo at the top. Only the most recent change can be undone. To make this possible, cookieZ holds the cookies as they were in memory for those 10 minutes. They're never written to disk, and closing the browser clears them.
Can I stop a site setting cookies?
Yes. Click Block at the top of cookieZ. For each site you can allow all cookies, clear them when Chrome closes, block other companies' cookies, or block every cookie. You can also block other companies' cookies on every site, or every cookie except on the sites you allow. cookieZ gives your choice to Chrome and Chrome does the blocking, so it works while cookieZ is closed. Removing cookieZ removes the rules.
What does "Block known trackers' cookies" do?
It's a switch on the Block cookies screen. Turn it on and Chrome blocks cookies from about 130 advertising and analytics companies on every site. The list is a file inside cookieZ. It's never downloaded, so it only changes when cookieZ is updated. It uses the same permission as the rest of Block, so there's nothing new to allow.
What it doesn't do: it blocks those companies' cookies, not the companies themselves, so their scripts and images still load. It can't catch a tracking cookie that a site sets under its own name. A site you've set to Allow all cookies still gets them, and each company's own website keeps its cookies, so you can still sign in there.
When you turn it on, cookieZ offers to delete the cookies those companies have already saved. Kept cookies are left alone, and Undo can put the rest back. If a site stops working, open cookieZ on it, click the button at the top and choose Allow all cookies for that site.
What does "cookieZ has cleared N cookies so far" mean?
It's how many cookies cookieZ has deleted for you since you installed it, shown on the Block cookies screen. Undo takes them back off. It counts what cookieZ cleared, not what Chrome blocked, because Chrome doesn't tell extensions when it blocks a cookie. It's one number, kept on your computer and never sent anywhere.
Why does Chrome's prompt mention my camera and microphone?
To set site rules, cookieZ needs Chrome's permission to change site settings. Chrome has one permission for every kind of site setting, so its prompt lists them all. cookieZ only ever changes the cookie setting, and you can check that in the code: it's in src/lib/rules.js. The prompt only appears if you click the button on the Block cookies screen. You can say no, and everything else works as before.
Why does it ask to change my privacy settings, or to clear browsing data?
Only if you use the feature that needs it. Blocking other companies' cookies on every site turns on Chrome's own setting for that, which needs permission to change privacy settings; cookieZ changes nothing else there. Clear and reload needs permission to clear browsing data; it only ever clears the site you have open, and never your history or passwords. Say no to either and the rest of cookieZ works as before.
How do I export cookies for yt-dlp?
What does the Site report show?
Click Site report beside the cookie count. It groups the site's cookies by purpose and the company that usually sets them, and lists what's worth checking. Each purpose is a guess from the cookie's name, because any site can give a cookie any name. Nothing in it is saved.
Clearing cookies didn't let me log in
Some sites keep more than cookies. Click Clear and reload under the delete options: it deletes the site's cookies and clears what else it has stored, such as local storage and cached files. Kept cookies are left alone, and Undo can put the cookies back, but not the rest. Then click Reload the site next to the message.
A site stopped working after I set a rule
Open cookieZ on that site, click the button at the top (it says what's blocked), and choose Allow all cookies, or remove the site from the list. Then reload the page. "Block other companies' cookies" can stop embedded videos, maps and "sign in with" buttons working, because those come from other companies. Allow all cookies also lets known trackers' cookies through on that site, if you've blocked them.
Does it block only the cookies a site doesn't need?
No, and nothing can do that reliably: sites don't label which of their cookies are essential. What cookieZ offers instead is blocking cookies from other companies on a site, which is where most advertising and tracking cookies come from, while the site keeps its own. Or, more narrowly, blocking known trackers' cookies on every site.
What are the buttons next to the search box?
They're filters. Click one to show only the cookies it describes: Secure, HttpOnly, Session, Kept, Expiring soon, Large, Partitioned or Known. Three more are checks for developers: Not Secure (only on an HTTPS page), Readable by scripts (no HttpOnly) and SameSite None. Click two and you see cookies that are both. A filter only appears when at least one cookie on the site matches it. While a filter is on, the delete options include "Just the cookies shown", so you can delete exactly what you're looking at.
What does "Known" mean?
The cookie's name is in the Open Cookie Database, a public list of well-known cookies. Click the cookie and the editor says who usually sets a cookie with that name and what it's for. It's a guess from the name only: any site can give its own cookie the same name, and very common names like id or session are never marked. The list is a file inside cookieZ and is looked up on your computer. Nothing is sent anywhere to check it.
Why are there cookies from other companies on this site?
A company whose content is embedded on a site, such as a video or a chat box, can save a partitioned cookie that is only used on that site. cookieZ lists those with the site's own cookies, marked "set in a frame, kept for this site only". They're included when you delete this page's or this domain's cookies, in Clear and reload and in exports, apart from a Cookie header or curl command, since the browser never sends them to this site.
What does "changes" next to the cookie count mean?
It's how many times this site's cookies have changed since you opened cookieZ. Click it for the list: which cookie was added, changed, removed or expired, and when. It shows names, never values, and it's gone when you close cookieZ.
It says my cookie can't be saved
Chrome refuses some cookies, and cookieZ tells you why before it tries. A cookie's name and value together can't be bigger than 4,096 bytes. A name starting with __Secure- only works on a Secure cookie. A name starting with __Host- only works on a cookie that is Secure, host-only and on the path /.
I set an expiry date and it changed
Chrome won't keep a cookie for more than about 400 days, and quietly shortens anything longer. cookieZ tells you when this happens, so the date you see is the one Chrome actually stored.
Does "All sites" really delete everything?
Yes, apart from any cookies you've marked as Kept. It includes partitioned cookies, which many tools miss. Before deleting, cookieZ shows how many cookies will go and which sites they belong to. Cookies in incognito are separate and aren't touched from a normal window.
How do I move cookies to another browser or tool?
Choose which cookies in the delete panel, then click Export. JSON works with cookieZ and other cookie editors. cookies.txt works with curl, wget, yt-dlp and similar tools. The Playwright option makes a storageState file for starting automated tests already logged in. To bring cookies in, click Import and paste them, or open cookieZ in a tab to choose a file. Import also takes Set-Cookie lines, a Cookie header (which goes on the site you're on) or a curl command from "Copy as cURL" in DevTools. To copy cookies from one site to another, such as from staging to localhost, open cookieZ on the site they should go to, and tick "Put them on localhost instead" (it names the site you're on). You'll see how many cookies will be added, and for which sites, before anything changes. There's also an option that writes Python code, to add the cookies in your own test scripts. An export includes login cookies, so treat it like a password, or lock it with one (below).
How do I lock an export with a password?
On the Export screen, type a password in the box before you click Copy or Download. cookieZ locks the file on your computer, using the browser's own encryption, and nothing is sent anywhere. To use it, click Import and paste it or choose the file: cookieZ sees it's locked and asks for the password, then shows what's in it as usual. The password is never saved, by cookieZ or anywhere else, so if you forget it, the file can't be opened and there's no way to get it back. Export the cookies again instead. The Python code option can't be locked, because it has to stay readable to run.
Why does cookieZ warn me when I export or import?
Some cookies keep you signed in. If an export holds cookies that look like that and has no password, cookieZ says anyone with the file could be signed in as you, so add a password or keep the file somewhere private. When you import, it reminds you to only import cookies you made yourself, because cookies from someone else can sign you in to their account or be used to trick you. Both are a single line of text. Neither stops you.
What does the size next to the cookie count mean?
It's roughly how much the site's cookies add to every request your browser sends it. Many servers refuse requests with more than about 8 KB of them, and the usual symptom is a site that won't let you log in, so cookieZ warns you above 6 KB. Deleting that site's cookies usually fixes it. A cookie marked Large is close to Chrome's 4 KB limit for a single cookie.
How do I remove it?
Right-click the cookieZ icon and choose "Remove from Chrome", or remove it from chrome://extensions. This also deletes what it saved: your Kept list, your site rules, your theme choice, the version you last opened and the count of cookies it has cleared. Chrome stops following the rules, and if cookieZ was blocking other companies' cookies on every site, Chrome's own setting goes back to how you had it. Your cookies stay as they are.
Report a problem
Please open an issue on GitHub, or if you'd rather not, email support@cookiez.uk. It helps to include:
- your Chrome version (from
chrome://version) - the version of cookieZ (shown in
chrome://extensions) - what you did, what you expected, and what happened instead
Don't paste cookie values into an issue. Issues are public, emails can be forwarded, and a session cookie can be used to log in as you. The cookie's name and the site are usually enough.