How to Clear Chrome's Cache on Mac (Properly)

Chrome’s cache clearing has become weirdly elaborate. There’s a basic version, an advanced version, time ranges, what to keep, what to clear, and — the bit most guides skip — multiple profiles each with their own cache. Get any of it wrong and you sign yourself out of every site, lose your bookmarks, or fail to actually clear what you intended.

Here’s the proper way to do it on macOS.

Method 1: The standard Chrome way

The default cache-clearing UI is at chrome://settings/clearBrowserData. Or: Chrome menu → Clear Browsing Data (cmd-shift-Delete).

Two tabs:

• Basic — Browsing history, cookies, cached images and files
• Advanced — Adds passwords, autofill, site settings, hosted app data

What “Cached images and files” includes: just the cache. No history, no cookies, no sign-ins. This is what you want most of the time.

Time range options:

• Last hour
• Last 24 hours
• Last 7 days
• Last 4 weeks
• All time

For a full clean, pick “All time” and tick only “Cached images and files.” Click Clear data. Done.

The multi-profile gotcha

Chrome supports multiple profiles. You can see them by clicking your avatar in the top right. Each profile is essentially a separate Chrome — separate bookmarks, history, cookies, and yes, separate cache.

When you clear cache via cmd-shift-Delete, you’re clearing only the current profile’s cache. If you have a Personal profile and a Work profile and you’re trying to fix a stuck site, clearing Personal won’t help if you opened the site in Work.

To check what profile you’re in, look at the avatar icon. To switch profiles and clear another, click the avatar → pick the other profile → that opens a new window in that profile → cmd-shift-Delete in that window.

Where Chrome’s cache lives

For each profile, on macOS, the cache lives at:

• Default profile: ~/Library/Application Support/Google/Chrome/Default/Cache/
• Other profiles: ~/Library/Application Support/Google/Chrome/Profile 1/Cache/, Profile 2/, etc.

You can check sizes in Finder: cmd-shift-G, paste the path, hit return, then cmd-I (Get Info) on the Cache folder. On a Chrome that’s been running for months, each profile’s cache can hit 1-2 GB easily.

Other relevant folders inside each profile:

• Cache/ — main HTTP cache
• Code Cache/ — JavaScript bytecode cache
• GPUCache/ — GPU-related cache
• Service Worker/ — service worker cache (some PWAs use this heavily)
• Application Cache/ — legacy app cache

The Clear Browsing Data dialog handles all of these. Manually deleting the folders works too, but you have to quit Chrome first or it’ll fight you.

Method 2: Per-site cache clear (the precise option)

For one specific website, much better than nuking everything:

1. Visit the site
2. Click the lock icon (or “Not Secure” if it’s HTTP) in the address bar
3. Click “Cookies and site data” or “Site settings”
4. Hit “Clear data”

This wipes just that domain’s cookies and cache. Reload, fresh fetch, no impact on the rest of your browsing.

Or via DevTools (the developer way):

1. Open DevTools: cmd-option-I or right-click → Inspect
2. Right-click the reload button (with DevTools open)
3. Choose “Empty Cache and Hard Reload”

That site reloads with cache bypassed for the current load. Often the fastest way to verify a cache problem is fixed.

Method 3: Chrome Task Manager (for stuck pages)

Sometimes the issue isn’t cache — it’s a tab that’s stuck or hung. Chrome has its own Task Manager: Window → Task Manager (or shift-Esc).

You can see CPU and memory per tab. If one tab is at 100% CPU and frozen, end it directly here. Faster than clearing cache.

Clear caches across every browser at onceSweep clears Safari, Chrome, Firefox, and Arc caches in a single pass. Free download for Mac →

Reasons to clear Chrome’s cache

In rough order of how often it actually helps:

1. A specific site is misbehaving — most common reason
2. You’re a developer testing fresh assets — though hard reload (cmd-shift-R) usually does it
3. Storage is tight and Chrome’s cache is huge — 2-3 GB recoverable in some cases
4. Privacy — clearing what your cache reveals
5. Chrome itself feels slow — sometimes helps, often the issue is elsewhere

What clearing the cache does NOT fix:

• Slow Chrome overall (usually too many tabs or extensions)
• Sites that are genuinely down
• Login issues (those are cookie issues — clear cookies for that site, not cache)
• Sync issues across devices
• Crashes

Cookies vs cache vs site data

The Clear Browsing Data dialog has separate checkboxes for these. They’re different:

• Cookies and other site data — sign-in tokens, preferences, cart contents. Clearing means you sign out everywhere.
• Cached images and files — copies of images, scripts, fonts. Cleared means slower next page load, then back to normal.
• Browsing history — your visit log. Doesn’t affect site behaviour.
• Hosted app data — for installed PWAs

For “the site is broken, fix it,” start with cache only. If that doesn’t work, also clear cookies for that specific site (not all of them).

Incognito as a cache-bypass test

If you want to test whether your cache is the problem without clearing it, open Incognito (cmd-shift-N). Incognito has no cache from your normal browsing. If the site works there but not in normal Chrome, the cache (or an extension) is the issue.

If it’s broken in Incognito too, the site itself has a problem.

Disable cache while DevTools is open

For developers: open DevTools, go to Network tab, tick “Disable cache.” While DevTools is open, every request hits the network. Useful for testing.

This only applies while DevTools is open. Closing DevTools restores normal caching.

Storage that isn’t cache

Chrome stores a lot more than just cache. If you’re hunting for storage:

• Cache folders (covered above) — usually the biggest chunk
• Bookmarks, history, sessions — small
• Extensions — each one’s data lives in ~/Library/Application Support/Google/Chrome/Default/Extensions/
• Local Storage and IndexedDB for web apps — can grow significantly for sites you use heavily (Notion, Figma, Google Docs)
• Service Worker caches — for PWAs

If Chrome’s eating 5+ GB and your cache is only 1 GB, the rest is probably extensions and web app storage.

Skip the manual huntSweep finds every cache, log, and forgotten file in seconds — only removes what you OK. Download Sweep free →

The multi-browser problem

Honestly, if you’re like most people, you’ve got Chrome, Safari, and maybe Firefox or Arc all installed. Each accumulates cache independently. Clearing them one at a time involves three different UIs.

A cleaning tool that handles all of them in one scan is meaningfully faster, and gives you a single picture of how much storage is being used by browser caches across your Mac.

Quick reference

The fastest paths:

• Clear all caches for current profile: cmd-shift-Delete → Basic → “Cached images and files” only → All time → Clear data
• Clear one site: address bar lock icon → Cookies and site data → Clear
• Hard reload one page: cmd-shift-R
• Empty cache and hard reload: DevTools open → right-click reload → Empty Cache and Hard Reload
• Multi-profile: repeat the cache clear in each profile

Don’t bother manually deleting the Cache folder unless you’ve quit Chrome and you specifically want to. Chrome’s UI handles it cleanly.

Sweep clears Chrome’s cache (across all profiles), Safari’s, Firefox’s, and Arc’s in a single pass — useful if you’ve been collecting browsers and want to reclaim a few gigabytes without clicking through each one’s UI.