This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

How do I find out what cookies a site has set?

  • 5 antwoorde
  • 1 het hierdie probleem
  • 11 views
  • Laaste antwoord deur ptoye

more options

I want to see exactly what cookies a particular site has set. I'm sure there used to be a way in earlier versions of FF (I'm on 70.0.1), but it seems to have disappeared. I don't want to delete all cookies from that site, just to examine them and if necessary delete them individually.

I want to see exactly what cookies a particular site has set. I'm sure there used to be a way in earlier versions of FF (I'm on 70.0.1), but it seems to have disappeared. I don't want to delete all cookies from that site, just to examine them and if necessary delete them individually.

Gekose oplossing

For me it's just Shift + F9.

Lees dié antwoord in konteks 👍 1

All Replies (5)

more options

Gekose oplossing

For me it's just Shift + F9.

more options

So it is. How intuitive.

more options

Another question - how on earth do you find this out? It's not on https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly

more options

At the very bottom you have a link to Developer shortcuts. It's there.

But I've just checked it in my Firefox :).

more options

I've now found that page, but it doesn't say any thing about cookies. Just "storage inspector" which isn't a lot of help.

Also, why is finding your cookies relegated to the "developer" page? I'm not a developer, but still need to look at my cookies.

Seems like Firefox is going backwards here.