Editor is hard to used. And not easy for multi account.

Causes Firefox startup to hang for between 30s to 60s. Otherwise it's a great extension.

Cookiebro - My Main Man!

A hearty "thank you" to the developer for demonstrating how useful and important
it is to be able to blacklist cookies.

(I cannot believe how many developers omit this critical and time-saving feature when writing these types of extensions.)

This cookie manager allows the user to go in, examine each individual cookie, and decide whether or not you want it on your machine. Sure, I get that auto-deleting cookies is useful, but you've probably noticed that sites will dump many cookies into your browser that you simply do not need.

Why not prevent a problem before it even starts?

It is a great pity that the developer hasn't done anything with this in months; I can only hope he/she has not decided to abandon it. If they need donations to keep this thing going, I would be willing to slip him/her a few dollars, and gladly.

(The Cookie Log feature is particularly brilliant. You can even blacklist cookies while you are in there without having to go into the editor. How cool is that?)

As an earlier reviewer said: This add-on should have far more users than it has.

The setting "Auto-delete indexedDB and localStorage of websites at browser startup" causes blank pages for several sites including imgur, ticktick.com, and qfc.com. Clearing cookies now throws an error message as well.

К сожалению, хотя в описании и написано про поддержку контейнеров, по факту в Cookiebro Editor не найден функционал управления cookies-ами выбранного контейнера. Как в "Cookie Quick Manager". А нужно было именно это.

This is a very functional cookie manager with an intuitive user interface. A very nice feature is that you can export/import your whitelist and blacklist. It even has built-in help. Thanks to the developer for this great add-on!

One thing that's not clear in the help is whether whitelisting *.foobar.com also whitelists foobar.com — or do I have to whitelist both to whitelist all pages from that site?

Also, does whitelisting *.foobar.com allow cookies from deeper sub-domains, such as bar.bletch.foobar.com — or do I need to whitelist *.*.foobar.com to allow cookies from that domain?

Superb cookie manager. Simple to use and the best.

The only add on that worked for importing json, Recommended.

This should be recommended by Mozilla. Like Feedbro, by the same author, it's the best.

i deleted the unwanted cookies and then i had to log in to all sites!! whats your definition of unwanted cookies sir? also there is no option to add the domain to black list , in toolbar icon.

I could get this to work and show the Icon with FireFox 83 ... 32 Bit ......... The 64 Bit would never show the Icon at the top.

All-in-One Cookies manager and easy to use.

This is a must have after Firefox removed its built-in cookie viewer. Thanks!

This is a must have extension for me!

I have a small problem though: if I remove the "session" checkbox and set an expiration date on a cookie, those settings get lost as soon as the cookie is set again by the server. In a case like that only the value should get updated. Or maybe provide a "lock" option to prevent a cookie from being changed at all by the server?

And a small useability enhancement: it would be nice if you could delete a cookie by hitting the del key instead of having to open the context menu. Also if the contents of cookie would be shown immediately when moving to it with the arrow keys, would IMHO be more intuitive than having to additionally press the enter key.

It works, but I really don't like cookie logging. I very much don't like the way that cookie logging is enabled by default either and how it resets to being enabled whenever I run CCleaner and Bleachbit on my system. Other than that though, this extension does a great job of deleting unwanted cookies without restarting Firefox, and it also does great at protecting cookies that I don't want to lose. As I said though, logging should be turned off by default. In fact, I don't see any excuse for there to be logging of cookies in any event. I see it as a possible privacy exploit. Webextension data SHOULD be cleaned. Perhaps the extensions settings should be stored some other way if possible. I have no intention of ending my use of such tools as CCleaner and Bleachbit.