How to Check Cookies in Any Browser (And What You're Actually Looking At)
Cookies are small text files that websites store on your device to remember information about you — your login status, preferences, shopping cart contents, and browsing behavior. Knowing how to check them gives you real visibility into what sites are tracking and storing. Here's exactly how to do it across major browsers, plus what to make of what you find.
What Cookies Actually Contain
Before diving into steps, it helps to know what you're looking at. Each cookie is a key-value pair — a label and its associated data. A cookie might store something like session_id = a3f92x or preferred_language = en-US. They also carry metadata:
- Domain — which site set the cookie
- Expiry date — when it expires (or "session" if it dies when you close the browser)
- Secure flag — whether it only transmits over HTTPS
- HttpOnly flag — whether JavaScript can access it (a security consideration)
- SameSite attribute — controls cross-site behavior to limit certain attacks
Most of this isn't sensitive in isolation, but understanding it tells you a lot about how a site is tracking your session.
How to Check Cookies in Chrome 🔍
Method 1: Browser Settings
- Open Chrome and go to
Settings → Privacy and security → Third-party cookies(or Cookies and site data) - Click See all site data and permissions to browse cookies by domain
Method 2: DevTools (more detail)
- Right-click anywhere on the page → Inspect
- Click the Application tab
- In the left panel, expand Storage → Cookies
- Select the domain to see every cookie name, value, domain, expiry, and flags
DevTools gives you the most complete picture and lets you manually delete individual cookies.
How to Check Cookies in Firefox
- Right-click → Inspect (or press
F12) - Go to the Storage tab
- Expand Cookies in the left panel and select the domain
Firefox's storage inspector displays the same fields as Chrome's DevTools. Firefox also has a built-in Enhanced Tracking Protection panel — click the shield icon in the address bar to see a summary of what's been blocked on that page.
How to Check Cookies in Safari
On Mac:
- Enable the Develop menu:
Safari → Settings → Advanced → Show features for web developers - Go to
Develop → Show Web Inspector - Click Storage → Cookies
Alternatively, Settings → Privacy → Manage Website Data gives a simpler per-site view without the technical detail.
On iPhone/iPad: Safari on iOS doesn't expose raw cookie data to users directly. You can clear cookies under Settings → Safari → Clear History and Website Data, but inspecting individual values requires a desktop browser or third-party tool.
How to Check Cookies in Edge and Other Chromium Browsers
Microsoft Edge, Brave, Opera, and Vivaldi all use the Chromium engine, so the DevTools method is identical to Chrome:
- Press
F12or right-click → Inspect - Go to Application → Storage → Cookies
The layout and field names are the same across all Chromium-based browsers.
What the Different Cookie Types Mean
| Cookie Type | What It Does | Common Example |
|---|---|---|
| Session cookie | Expires when browser closes | Keeping you logged in temporarily |
| Persistent cookie | Has a future expiry date | Remembering your preferences |
| First-party cookie | Set by the site you're visiting | Cart contents on a shopping site |
| Third-party cookie | Set by an external domain | Ad networks, analytics tools |
| Secure cookie | Only sent over HTTPS | Authentication tokens |
| HttpOnly cookie | Inaccessible to JavaScript | Protects against XSS attacks |
Third-party cookies are the ones most commonly associated with cross-site tracking. Many browsers are actively restricting or phasing them out, which is why some sites prompt you to accept cookies before loading content.
Checking Cookies Without DevTools
If you'd rather not use developer tools, a few alternatives exist:
- Browser cookie manager extensions — various extensions display cookies in a cleaner interface and let you filter, edit, or delete them without opening DevTools
- Browser built-in privacy dashboards — Firefox, Edge, and Brave each have simplified privacy dashboards accessible from the address bar
- Online cookie checkers — some web tools display cookies set on a given page, though these have limited access compared to local inspection
🛡️ For security research or auditing purposes, browser extensions designed for developers (like EditThisCookie or Cookie-Editor) surface the same data in a more accessible UI.
Factors That Change What You'll Find
How many cookies a site sets — and what's in them — varies considerably depending on:
- Whether you're logged in — authenticated sessions carry more cookies (tokens, user IDs, preferences)
- The site's ad and analytics stack — heavy use of third-party tools generates more third-party cookies
- Your browser's tracking protection settings — Firefox and Brave block many third-party cookies by default before they're ever set
- Whether you've cleared cookies recently — a fresh browser profile will show far less data
- Extensions you have installed — ad blockers and privacy tools may intercept cookies before they appear in storage
A site that appears to set a dozen cookies in Chrome might show only three in Brave, not because the site changed, but because the browser filtered the rest.
What "Checking Cookies" Actually Tells You
Viewing raw cookie data is most useful for developers debugging login or session behavior, privacy-conscious users who want to audit what's being tracked, and anyone troubleshooting why a site isn't remembering their preferences. For everyday users, the built-in settings view (not DevTools) is usually enough to see which sites have stored data and clear it selectively.
Whether raw cookie inspection or a simplified privacy dashboard gives you what you need depends entirely on why you're looking — debugging a broken session, auditing third-party tracking, or just cleaning up stored data are meaningfully different goals that point toward different tools and levels of detail.