Cookie Quick Manager for Firefox: Search, Edit, Protect and Delete Cookies
Cookie Quick Manager is a free, open source Firefox extension for viewing, searching, creating, editing, protecting and deleting cookies site by site. It supports Firefox containers, imports and exports cookies as JSON or Netscape files, can wipe cookies at startup while keeping protected ones, and runs on Firefox for Android. Its last release, version 0.5rc2, dates from July 2019, so check the maintenance status below before you rely on it.
This guide explains what the extension does, how to use its manager, how cookie protection works, and when Firefox's own tools or an alternative add-on are the better choice.
What does Cookie Quick Manager do?
Cookie Quick Manager gives Firefox a full cookie editor that the browser's own settings do not offer. Firefox's built-in Manage Data dialog can only remove all data of a site; the extension shows every individual cookie with its name, value, domain, path, expiration date and flags, and lets you change any of them.
The main features listed on the official Mozilla add-ons page:
- Search cookies by domain, including subdomains.
- Create or edit cookies: domain, path, name, value, expiration, Secure and HttpOnly flags, plus the SameSite flag.
- Delete the current site's cookies in two clicks.
- Import and export one or many cookies in JSON or Netscape (cookies.txt) format.
- Container support: search and view cookies per container, copy cookies between containers or save a cookie to a specific container.
- First-Party Isolation support.
- Cookie protection and session cookie protection, so selected logins survive bulk deletion.
- An option to delete all unprotected cookies at startup.
- Deletion of LocalStorage keys and values for the current page.
- Windowed mode or a wider tab view.
The extension is licensed under GPLv3 and the code is on GitHub. Mozilla lists it with about 48,000 users and a 4.4 out of 5 rating.
How to use Cookie Quick Manager in Firefox
Cookie Quick Manager works from a toolbar button: click it on any site to open a menu with the manager and quick delete actions. The typical workflow:
- Install the extension from addons.mozilla.org and accept the permissions (access to data on all websites, clearing browsing data and reading privacy settings).
- Open a site and click the Cookie Quick Manager toolbar icon.
- Select Manage All Cookies to open the dashboard, or pick a quick option to delete the cookies of the current site.
- Type a domain into the search field. The left column lists matching domains, the middle column the cookies of the selected domain, and the right panel the details of the selected cookie.
- Edit a value, flag or expiration date in the details panel and save it, or create a new cookie for the domain.
- Right-click a cookie to copy it, export it to a file, protect it or delete it.
The context selector filters cookies by container, which pairs well with Mozilla's Multi-Account Containers extension. Copying a cookie to another container lets you reuse a login in a second container without signing in again.
How cookie protection works
Cookie protection is a whitelist: protected cookies are kept when you delete all cookies with Cookie Quick Manager, while everything else is removed. Use it for the session cookies that keep you signed in to the sites you use daily.
- Select one or more cookies in the manager and choose Protect. A padlock icon marks protected cookies in the cookie list.
- Choose Unprotect to remove the protection again.
- Enable the startup option in the extension settings to delete all unprotected cookies every time Firefox starts.
Protection only applies to deletions made by the extension. If you clear cookies through Firefox's own settings or the Clear recent history dialog, Firefox deletes protected cookies too. Pick one tool for cleanup and stay with it.
The settings page also stores the import and export template and offers a backup of the extension's own settings, useful when you move to a new Firefox profile.
Is Cookie Quick Manager still maintained?
Cookie Quick Manager still installs and works in Firefox, but it is no longer actively developed. The latest version on addons.mozilla.org is 0.5rc2 from July 9, 2019, and the GitHub repository has more than 100 open issues, with recent bug reports left without a maintainer response.
That age matters in two places:
- Firefox has changed a lot since the last release. Since June 2022, for example, Total Cookie Protection gives each site its own cookie jar by default, and the extension has had no update since.
- Open bug reports describe gaps. A December 2025 report says some cookies appear in Firefox's Manage Data dialog but not in the extension; the cause has not been identified and the report has no maintainer reply.
- An unmaintained extension with access to all websites is a risk if ownership ever changes. Review the permissions and keep an eye on updates.
If a site still shows you as signed in after a wipe, cross-check with Firefox's own tools before assuming the cookies are gone.
Built-in Firefox cookie tools and alternatives
Firefox covers basic cookie management without any extension, while dedicated add-ons cover automatic cleanup. Choose by task:
| Task | Tool | How |
|---|---|---|
| Remove all data of one site | Firefox settings | Settings, Privacy & Security, Cookies and Site Data, Manage Data |
| View or delete single cookies | Firefox Storage Inspector | Ctrl + Shift + I, Storage tab, right-click a cookie |
| Edit, protect, import or export cookies | Cookie Quick Manager | Toolbar icon, Manage All Cookies |
| Delete cookies when tabs close | Cookie AutoDelete or Forget Me Not | Automatic rules with a whitelist |
Mozilla documents the Manage Data steps in its clear cookies and site data guide. To stop consent pop-ups instead of deleting the cookies they set, configure Firefox to reject cookie banners automatically.
FAQ
Does Cookie Quick Manager work on Firefox for Android?
Yes. Mozilla lists Cookie Quick Manager as available for Firefox for Android, and the developer added Android support in November 2018.
Which file formats can Cookie Quick Manager import and export?
It imports and exports cookies as JSON or in the Netscape cookies.txt format used by many download tools. An open bug report says text exports lose container information, so use JSON for full backups.
Can Cookie Quick Manager change the SameSite flag of a cookie?
Yes. The editor supports the SameSite attribute that Firefox added in version 63, next to the Secure and HttpOnly flags.
Related: best Firefox add-ons, Multi-Account Containers sync, Cookie AutoDelete review
Question: “Delete ALL the cookies of selected context” and
“Delete ALL cookies on restart”
A logical interpretation of the word ALL is “ALL cookies”.
SO, this is confusing to me, a new user. What about protected cookies?
Thanks,
Am using Cookie Quick Manager and recently a couple cookies are showing up with a blue “fingerprint” icon (next to the number of cookies from that domain in a black circle), but there’s no explanation of what that might mean.
Anybody know? If so, please post a reply. Would love to know if it’s OK to leave it or if it should be deleted for privacy’s sake!
On some of my configurations I use Site Bleacher by wooque and can say that in some respects it works better than Cookie AutoDelete or Forget Me Not. No idea why Ghacks still hasn’t covered it.
I use “lowcarb”. Clean, simple and really works….just keeps (in a nice blue colour) the cookies you’ve asked to protect, and each time you start Firefox, all other cookies that had accumulated are all gone, leaving just your protected ones.
The only two truly “reliable” cookie extensions are Temporary Containers and First Party Isolation (technically not an extension).
To quote ghacks user.js: “APIs do not exist to allow clearing IndexedDB, Service Workers cache, appCache, or cache by host. Clearing cookies & localStorage on their own, and leaving orphaned persistent data is a false sense of privacy.”
The only cookie extension which works correctly for me is cookie exterminator in pale moon.When i leave a domain i want everything deleted,local storage the lot.Only cookie auto delete comes close in firefox.
Interesting, definitely worth a try. And I like that you can combine that with containers which I thought it already came in installed by default?
I haven’t found a cookie extension that has equivalent functionality to the Cookie Controller classic extension, since Mozilla has decided that user controlled code should no longer be given the opportunity to have full control on cookie permissions.
I’ve found Cookiebro – Cookie Manager: https://addons.mozilla.org/en-US/firefox/addon/cookiebro/ which comes the closest to the function of Cookie Controller.
Basically you need to do the following:
1. Go into the Options/Settings of the Cookiebro addon and enable the option: Enable blacklist filtering.
2. Scroll down to Blacklist Settings (Block), and add the following blocking rule: *.*
3. That’s it! Now whenever you visit a website where you want to allow cookies, click the Cookiebro icon in the toolbar and add the website to the whitelist.
I forgot to link this: this is the 4 year old bug asking for webextensions to be able to control per-site cookie permissions, “Implement contentSettings API for cookies”
https://bugzilla.mozilla.org/show_bug.cgi?id=1291841
Privacy bugs not being a priority at Mozilla… Where do they put those Google millions, in developing VR tools maybe ?
I have looked at Cookiebro and it seems that it has the same problem as all cookie webextensions: the per-domain cookie blocking managed by the extension does not translate into an actual change of the cookie/storage permission in the native per-domain permission manager, because (for no good reason) webextensions are not allowed to do that. As a result, per-domain cookie block by webexts typically relies on often unreliable tricks like clearing cookie headers and trying to outrun site javascript code in deleting cookies before they are used when they are created through javascript. And while the native storage permission affects many forms of storage beyond cookies, even blocking service workers, those webextension unreliable tricks work for cookies only.
It’s almost like if with the webext standard they didn’t want users to be able to easily manage themselves per domain storage permissions, making it a multi click inconvenience natively, and forbidding webextensions to make it easier…
You are mistaken. chrome.cookies API will let you manage cookies without any “tricks” or header management. Check the API.
Extensions don’t have access to browser’s native cookie settings but you don’t want to use both. Allow all cookies in browser settings and let the extension take care of things.
I use cookie autodelete on both ff and brave in auto mode, set up once for a site and you are done. I’ve never had a need to search, copy or save cookies, do non-developers ever do that?
Cookie AutoDelete is much better i think. There you can whitelist cookies for sites so they won’t be deleted (for search engine/site settings).
It also deletes every cookie if you close the session/tab or change domain after a given time. This way you don’t have to manually clear them ever again.
No more 3rd party or tracking cookie on your machine. Poor google.
I went with ForgetMeNot as well. I tried all the others and like this one the best.
FYI I was using Cookie AutoDelete in Firefox, and the other day I was looking at my browser data and noticed that there were quite a few cookies and a substantial amount of local storage saved for a number of websites that I had definitely not whitelisted (I double-checked my Cookie AutoDelete settings just to be sure they were correct). I’m not sure what was going on, but if you’re not doing it already then you should check your browser data periodically to be sure that Cookie AutoDelete is working correctly.
I ended up switching to Forget Me Not and configuring Firefox to delete local storage when the browser closes, and all’s well so far.
Wow! Thanks.
The only unremovable (by Cookie AutoDelete) cookie i have found is set by mozilla (addons.mozilla.org) and after changing the deletion to instantly it worked (the site too so it is absolutely unnecessary).
What if other sites could create those “sticky/unremovable” cookies too? The dream of google!
There are plenty of ways to set “supercookies” and “fingerprint” your browser. The stupid EU regulation on cookies has only accelerated this.