How to delete cookies in Chrome

TL;DR: Chrome has three reliable ways to delete cookies — the Settings UI for bulk or per-site deletion, the DevTools Application panel for surgical per-cookie deletion, and a Manifest V3 extension for one-click repeatable workflows. Pick the method that matches your goal: full wipe, per-site cleanup, or repeated debugging.

Deleting cookies in Chrome is a built-in browser operation that does not require any third-party tool. The fastest method depends on your goal — a full wipe, a per-site reset, or a repeatable per-cookie workflow during debugging. This guide walks through all three approaches in order of how often a typical user needs them, plus the eight-step authoritative path through Chrome Settings, plus what actually happens to your other browser data when you delete cookies¹.

Quick comparison: which method to pick

In short: Use Settings if you are clearing once and rarely. Use DevTools if you are debugging a specific session bug. Use a Manifest V3 extension if you do this more than once a week, need to export cookies before deletion, or want to script the workflow.

The three Chrome cookie-deletion paths, side by side:

A 2024 Mozilla research summary of cross-browser privacy controls² notes that built-in cookie tools are designed for “occasional manual housekeeping,” not high-frequency workflows — which is why extensions exist for the latter category.

Method 1: Chrome Settings (the authoritative path)

In short: Chrome’s built-in Settings UI deletes cookies plus all other site data (localStorage, IndexedDB, Cache Storage, Service Worker registrations) in a single per-site click. Eight steps from opening Settings to verified deletion.

This is the official method Google documents for end users³. The full eight-step ordered path:

1. Open Chrome Settings — click the three-dot menu (kebab) in the top-right of Chrome and choose “Settings”. Or type chrome://settings directly into the address bar.
2. Navigate to Privacy and security — in the left sidebar choose “Privacy and security”, then click “Cookies and other site data” in the main panel.
3. Click “See all cookies and site data” — near the bottom of the Cookies and site data page. Chrome opens a paginated list of every domain with stored data, sorted alphabetically.
4. Filter to the site (or select all) — use the search box in the top-right to filter by domain. To delete everything, scroll to the top and click “Remove all”.
5. Click the trash icon next to the entry — Chrome deletes cookies, localStorage, IndexedDB, Cache Storage, and Service Worker registrations for that origin.
6. Confirm in the dialog — Chrome asks for confirmation before deleting.
7. Verify by visiting the site — open the affected site in a new tab. You should be logged out and any session-based preferences reset.
8. Optionally export first — for important sessions, export cookies via a Manifest V3 extension before deleting, as a recovery backup.

Important: Step 5’s trash icon is more aggressive than just “cookies” — it removes the entire storage scope for that origin. If you only want to delete cookies but keep localStorage data, use Method 2 (DevTools) instead.

For bulk deletion across all sites at once, the shortcut is Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac) → choose a time range → check “Cookies and other site data” → “Delete data”.

Method 2: Chrome DevTools (surgical per-cookie removal)

In short: DevTools Application panel is the right tool for deleting one cookie at a time — for debugging session bugs, reproducing user issues, or removing a tracking cookie without losing your login. F12 → Application → Cookies → select → Delete key.

The seven-step DevTools workflow for per-cookie deletion:

1. Open the target site in a tab
2. Press F12 (or right-click → Inspect) to open DevTools
3. Click the Application tab in the DevTools top bar
4. In the left sidebar expand Storage → Cookies and click the domain
5. Use the filter box above the cookie list to narrow by name or value
6. Select rows (Ctrl+click for multi-select) and press the Delete key — or right-click → “Clear all” to wipe every cookie for that domain
7. Reload the page if you need the deletion to take effect on the next request

DevTools is the only built-in Chrome path that lets you read and modify the SameSite, HttpOnly, Secure, and Expires attributes of an individual cookie. The Settings UI gives you “delete the whole site” only.

Method 3: Manifest V3 extension (one-click, repeatable)

In short: For workflows you repeat — clearing trackers without touching logins, exporting cookies for QA test fixtures, switching profiles between work and personal — an extension is faster and scriptable. CookieVault Editor and CookieVault Guardian are open-source, MIT-licensed Manifest V3 options.

A Manifest V3 cookie extension gives you three capabilities that the built-in UI does not:

• Per-cookie delete from a popup — no DevTools required, no Settings navigation; click the toolbar icon → click cookie → Delete
• Export to JSON / Netscape cookies.txt / HAR — backup before deletion, share test fixtures with QA, feed cookies to curl or Playwright
• Auto-delete on tab close (Guardian) — Chrome has no built-in equivalent; whitelist sites you trust, everything else cleans automatically when its last tab closes

For one-off deletions, the built-in UI is fine. For workflows you do more than once a week, an extension pays back its install time within days.

What deleting cookies actually does (and does not do)

In short: Deleting a cookie removes that key-value record from your browser’s cookie store. It does not delete localStorage, fingerprinting state, or your password manager entries. The site’s server still has whatever it stored about you on its end — deleting cookies is a client-side action.

Six things that happen when you delete a cookie:

• The cookie record disappears from the browser’s per-domain cookie store
• The next request to the matching domain does not include that cookie
• Server-side, the site sees a request without a session cookie and typically treats you as a new visitor
• If the site re-issues a Set-Cookie on the same response, a fresh cookie gets stored — deletion is one moment, not a permanent state
• Other browser storage (localStorage, IndexedDB, Cache Storage) is not affected unless you used Method 1 step 5 (which deletes the whole site-data scope)
• Saved passwords in Chrome’s password manager are independent of cookies — they survive cookie deletion

Six things that do not happen when you delete cookies:

• You do not become anonymous (browser fingerprinting works without cookies)
• Your IP address does not change
• Sites that use server-side session-on-IP do not log you out
• Federated logins (Google / Apple / GitHub) re-authenticate silently the next time you visit a connected site
• Third-party trackers that use localStorage or fingerprinting continue working
• Your browsing history is not cleared — that is a separate setting

See also

• Clear cookies but stay logged in — selectively delete trackers while preserving session cookies for trusted sites
• How to edit cookies in Chrome — change cookie values, expiry, SameSite, HttpOnly via DevTools or extension
• How to export Chrome cookies to JSON — backup before deletion
• Auto-delete cookies on tab close — the automated equivalent of manual deletion
• What is a cookie? — the underlying protocol explained
• CookieVault Editor — the open-source Manifest V3 cookie manager