How to Check the Cookies in Chrome: A Complete Guide
Cookies are small data files that websites store in your browser to remember your preferences, keep you logged in, and track your browsing activity. Chrome gives you several ways to view, inspect, and manage these files — but the method that works best depends on what you're actually trying to do.
What Are Browser Cookies and Why Would You Check Them?
When you visit a website, the server may instruct Chrome to store a small text file locally. That file — the cookie — gets sent back to the server on your next visit so the site can recognize you. Cookies handle everything from saved shopping carts to login sessions to advertising preferences.
You might want to check cookies for several reasons:
- Debugging a website that isn't loading correctly or keeps logging you out
- Privacy auditing to see which sites are storing data about you
- Security troubleshooting to identify unexpected or suspicious cookies
- Development work where you need to read, modify, or delete specific cookie values
Chrome provides two main access points depending on your goal: browser settings for general cookie management and DevTools for deep inspection.
Method 1: Check Cookies Through Chrome Settings
This is the straightforward path for everyday users who want to see what's stored and manage site permissions.
Steps:
- Open Chrome and click the three-dot menu (⋮) in the top-right corner
- Go to Settings
- Select Privacy and security from the left sidebar
- Click Third-party cookies (or Cookies and other site data depending on your Chrome version)
- Scroll down and click See all site data and permissions
This view shows you every domain that has stored cookies, cache, or local storage data in your browser. You can search for a specific site, see how much data it's storing, and delete individual entries or all cookies at once.
What you can see here:
- Which domains have stored data
- Total storage size per site
- Option to delete site-specific data without clearing everything
What you cannot see here are the actual cookie names, values, or expiration dates. For that level of detail, you need DevTools.
Method 2: Inspect Cookie Details Using Chrome DevTools 🔍
DevTools is Chrome's built-in developer toolkit and gives you full visibility into every cookie associated with the current page — including name, value, domain, path, expiration, and security flags.
Steps:
- Navigate to the website you want to inspect
- Press F12 (or Ctrl+Shift+I on Windows/Linux, Cmd+Option+I on Mac) to open DevTools
- Click the Application tab at the top of the DevTools panel
- In the left sidebar, expand the Storage section
- Click Cookies, then select the domain listed underneath
You'll see a table with every cookie currently set by that site.
Understanding the Cookie Table Columns
| Column | What It Tells You |
|---|---|
| Name | The cookie's identifier (e.g., session_id, _ga) |
| Value | The stored data — often encrypted or hashed |
| Domain | Which domain set the cookie |
| Path | The URL path where the cookie is active |
| Expires/Max-Age | When the cookie expires; "Session" means it deletes when you close the tab |
| Size | Storage size in bytes |
| HttpOnly | If checked, JavaScript can't access this cookie — a security feature |
| Secure | If checked, the cookie only transmits over HTTPS |
| SameSite | Controls cross-site cookie behavior (Strict, Lax, or None) |
These flags matter. A cookie without Secure enabled on an HTTP site, for example, could be intercepted. The HttpOnly flag is specifically designed to reduce cross-site scripting (XSS) risks.
Method 3: Check Cookies for a Specific Site Directly
Chrome also lets you inspect cookies for any site without navigating there first.
Steps:
- Click the padlock icon (or information icon) in the address bar while on a page
- Select Cookies and site data
This shows a quick breakdown of cookies in use on the current page, organized by domain — including any third-party cookies loaded by embedded scripts, ads, or analytics tools. It's a fast way to see how many parties are tracking a given page visit.
Variables That Affect What You'll Find
The cookies you find — and what you can do with them — varies based on several factors:
- Chrome version: The interface for cookie settings has shifted across versions as Google phases in third-party cookie restrictions. Older and newer Chrome builds may show different options and labels.
- Site behavior: Some sites set dozens of cookies; others set none. Single-page apps, e-commerce platforms, and ad-heavy sites tend to store significantly more.
- Cookie consent choices: If you declined non-essential cookies on a site's consent banner, fewer cookies will be present than if you accepted all.
- Browser profiles: If you use multiple Chrome profiles, cookies are isolated per profile. A cookie visible in one profile won't appear in another. 🍪
- Incognito mode: Cookies in an Incognito window are temporary and won't appear in your main settings view — they're deleted when the Incognito session closes.
What the Data Actually Means Varies by User
A developer inspecting cookies will use DevTools to verify that authentication tokens are flagged HttpOnly and Secure, or to confirm a third-party analytics cookie is setting the right domain scope. A privacy-conscious user might use the site data view in settings to periodically clear cookies from sites they've only visited once. A casual user might just want to understand why a site keeps forgetting their preferences after they clear everything.
The same Chrome tools are available to all of these users — but what counts as a useful finding, and what action makes sense to take afterward, depends entirely on the reason for looking in the first place.