How to View Internet Cookies in Any Browser
Internet cookies are small text files that websites store on your device to remember who you are, what you've done, and sometimes what you prefer. They power everything from staying logged in to a shopping cart remembering your items. But most people never actually look at them — and knowing how to find and read them gives you real visibility into what's happening behind the scenes of your browsing sessions.
What Are Cookies, Actually?
Before diving into where to find them, it helps to understand what you're looking at. A cookie is a key-value pair — essentially a label and a value — stored in plain text. A site might store a cookie like session_id=abc123 to keep you logged in, or theme=dark to remember your display preference.
Cookies have a few key properties beyond their value:
- Domain — which website set the cookie
- Path — which part of the site the cookie applies to
- Expiry date — when it expires (session cookies disappear when you close the browser; persistent cookies survive)
- Secure / HttpOnly flags — security settings that restrict how the cookie can be accessed or transmitted
- SameSite attribute — controls whether the cookie is sent with cross-site requests, relevant to tracking and security
When you view cookies in a browser, you're seeing all of these fields, not just the value.
How to View Cookies in Chrome 🍪
Chrome's developer tools give you the most detailed view:
- Open any webpage
- Press F12 (or right-click → Inspect)
- Click the Application tab
- In the left sidebar, expand Storage → Cookies
- Select the domain — you'll see every cookie for that site in a table
Each row shows the cookie name, value, domain, path, expiry, size, and flags. You can click any row to inspect it further.
For a quicker, less technical view, go to Settings → Privacy and security → Third-party cookies or See all site data and permissions → View permissions and data stored across sites. This lists sites that have stored data, though it's less detailed than DevTools.
How to View Cookies in Firefox
Firefox also uses developer tools:
- Press F12 to open the toolbox
- Click the Storage tab
- Expand Cookies in the left panel
- Select a domain to see all its cookies
If the Storage tab isn't visible, click the + icon in the toolbar to add it. Firefox's interface is nearly identical to Chrome's in terms of what data it exposes.
How to View Cookies in Safari
Safari handles this a bit differently depending on whether you're on macOS or iOS.
On macOS:
- Go to Safari → Settings (or Preferences) → Privacy
- Click Manage Website Data — this shows which sites have stored cookies and other data
- For a full technical view, enable the Develop menu: Settings → Advanced → Show features for web developers
- Then use Develop → Show Web Inspector → Storage tab
On iPhone/iPad: Safari on iOS doesn't expose individual cookie contents to users natively. You can see which sites have stored data under Settings → Safari → Advanced → Website Data, but you cannot inspect individual cookie values on iOS without third-party tooling.
How to View Cookies in Edge
Microsoft Edge uses the same Chromium engine as Chrome, so the process is identical:
- Press F12
- Go to the Application tab
- Expand Storage → Cookies in the left panel
The interface is nearly pixel-for-pixel the same as Chrome's DevTools.
Browser Extensions for Cookie Viewing
If you'd rather not use developer tools, several browser extensions surface cookie data in a more accessible format. These typically add a toolbar icon that displays all cookies for the current site in a readable panel. Common options include cookie managers and privacy inspection tools available in the Chrome Web Store and Firefox Add-ons library.
Extensions vary significantly in how much detail they show and what additional features they offer — some let you edit or delete cookies, others focus on read-only inspection. Privacy-conscious users should check an extension's own permissions before installing, since a cookie manager by definition needs access to your cookie data.
What the Data Actually Tells You
| Field | What It Means |
|---|---|
| Name | The label the site uses to identify this data |
| Value | The actual stored data (often encoded or encrypted) |
| Domain | Which site set it — .example.com means all subdomains |
| Expires / Max-Age | When it expires; "Session" means it deletes on browser close |
| HttpOnly | Can't be accessed by JavaScript — reduces XSS risk |
| Secure | Only sent over HTTPS connections |
| SameSite | Controls cross-site sending behavior |
Most cookie values you see will be hashed or encoded strings — they're not meant to be human-readable. A session token like eyJhbGciOiJIUzI1NiJ9... is a JWT; it has structure, but decoding it requires separate tooling. What you can read clearly are simpler cookies like preference settings or analytics identifiers.
What Varies Between Users 🔍
How useful cookie inspection is — and which method makes sense — depends on a few things:
- Browser choice determines which interface you use and how much granular data is exposed
- Operating system affects Safari users most significantly, since macOS and iOS offer very different levels of access
- Technical comfort level shapes whether DevTools feels approachable or overwhelming
- Purpose matters too: a developer debugging a login issue needs the full DevTools view, while someone just checking what a site is storing might find a simple extension more practical
- Privacy goals influence whether you're inspecting to understand, to delete selectively, or to block certain cookies entirely
The gap between inspecting cookies and acting on what you find — blocking trackers, managing storage, adjusting browser settings — depends entirely on what you're trying to accomplish with the information.