How to View Cookies for a Website With Cookie Editor
Open the right tab, click the icon, and read the cookie list properly, including how to search it and why entries sometimes look duplicated.
Cookie Editor shows the cookies for the page in the active tab, nothing more, nothing less. That one rule explains most confusion: if the list looks wrong, you are usually looking at the wrong tab, the wrong site, or a search filter you forgot about. Here is the reliable way to view a site's cookies and read what you find.
View a site's cookies in four steps
- Open the exact page
Navigate to the website you want to inspect and let it finish loading. If the preference you care about appears only after signing in or changing a setting, do that first.
- Click the Cookie Editor icon
Use the toolbar icon, or open your browser's extensions menu and choose Cookie-Editor. The panel opens over the current tab.
- Read the list
Each row is one cookie, labelled by name. The count reflects cookies whose domain matches this site, including parent-domain cookies the browser sends here.
- Expand an entry
Click a cookie name to open its details: value, domain, path, expiry and flags such as Secure, HttpOnly and SameSite. These fields are explained in our cookie fields guide.
Search a long list
Busy sites can store dozens of cookies. Use the search field at the top of the panel and type part of a name, for example theme, lang or consent, to narrow the list. Clear the search before concluding a cookie is missing: a leftover filter is the most common reason a list looks empty. If the unfiltered list is still empty, reload the page and reopen the panel; the site may set its cookies only after an interaction.
Why the same name can appear twice
Two entries can share a name when they differ by domain or path. A site might store theme for example.com with path / and another for a sub-area with path /account. They are separate cookies, and the browser sends the one whose domain and path match the page you are on. Always compare domain and path before editing or deleting, so you change the record the page actually reads.
| Panel element | What it tells you |
|---|---|
| Cookie name | The key the site uses, such as theme, lang or session_id |
| Value (in the expanded entry) | The stored state, such as dark, en or a long random token |
| Domain | Which host the cookie belongs to; a leading dot means subdomains are included |
| Path | Which part of the site the cookie is sent to; / means the whole domain |
| Expiry | When the browser will discard it; “Session” means it goes when the browser closes |
View cookies without an extension: the DevTools route
Every desktop browser can also show cookies through its built-in developer tools: open DevTools (F12), go to the Application tab in Chrome and Edge or the Storage tab in Firefox, and expand the Cookies section for the site. It is more powerful and more cluttered, and on mobile it is effectively unavailable, which is why most people prefer a dedicated panel for everyday checks. But DevTools is a good cross-check: if Cookie Editor and DevTools disagree about a cookie, the difference is almost always scope (domain or path filtering) rather than an error, and comparing the two lists teaches you the scope rules faster than any article.
Reading a real cookie list, line by line
Open a busy site and the list can look intimidating, so impose an order on it. First, find the entries you recognise: a theme, a language, a region. Those prove the panel is showing the right store. Second, look for the entries with expiry dates far in the future; those are the site's long-term memory of you, usually identifiers and preferences. Third, look at what is missing: if you just changed a setting and no entry changed, the site is storing that setting somewhere else, in local storage or on its own servers against your account. Reading a list this way turns a wall of names into a story about how the site remembers you.
Sorting out the same-name puzzle
Two entries with the same name are not a glitch. A site can set one cookie for its main domain and another for a subdomain, or the same name at two different paths, and the browser keeps all of them, sending whichever matches the page being loaded. Cookie Editor shows them as separate rows because they are separate records. When you test, change one at a time and reload; the one whose change alters the page is the one that page actually reads, and the other belongs to a different part of the site.
| You see | It usually means | Worth doing |
|---|---|---|
| A preference you just set | The panel is reading the right store | Nothing, carry on testing |
| Same name twice | Different domain or path scopes | Change one, reload, compare |
| Nothing at all | Wrong tab, wrong profile, or the site uses no cookies | Check the tab and profile first |
| A cookie returns after deletion | The site writes it on every load | Compare value and expiry to confirm |
Frequently Asked Questions
Why can I see a cookie but the website ignores it?
Check the domain and path, the page may be reading a different entry with the same name, or the site may store that preference in local storage instead of a cookie.
Can I view cookies in a private window?
Only if you allowed the extension in private windows (Firefox) or the equivalent setting in your browser, and the list then reflects the private session's separate cookie store.


