Chrome is using more space than you think, and the cache is not why
Clearing browsing data barely helps. On a real Mac, Chrome held 8 GB, and most of it was profiles, service workers and extensions rather than cache.
Chrome reports as a few hundred megabytes in Finder. On the Mac this guide was written on it was using 8.1 GB, and clearing browsing data would have recovered a fraction of it.
Check yours. This takes two seconds and is the whole point:
du -sh ~/Library/Application\ Support/Google/Chrome
du -sh ~/Library/Caches/Google/ChromeWhere it actually goes
Two locations, and the larger one is not the cache. On the machine above: 5.9 GB in Application Support against 2.2 GB of cache. Clearing browsing data touches the smaller number.
The profiles are the real answer
Every Chrome profile keeps its own complete set of data. Not a little: a full copy of extensions, storage and service workers, per profile. The Mac above had several, and the largest was not even the default one:
du -sh ~/Library/Application\ Support/Google/Chrome/* | sort -rh | head| Profile | Size |
|---|---|
| Profile 3 | 1.5 GB |
| Default | 1.4 GB |
| Profile 4 | 942 MB |
| Profile 21 | 479 MB |
Profiles accumulate quietly. Signing into a second Google account creates one, and it is never removed when you stop using that account. A Mac with eight profiles is carrying eight sets of extensions.
Inside one profile, it is not what you would guess
| What | Size | Cleared by Clear browsing data? |
|---|---|---|
| Service Worker | 571 MB | Only with Cookies and site data |
| Extensions | 558 MB | No |
| IndexedDB | 88 MB | Only with Cookies and site data |
| File System | 64 MB | Only with Cookies and site data |
Service workers are offline copies that sites install so they work without a network. Every web app you have opened has one, including sites you visited once. Nothing prompts you about them and nothing ages them out aggressively.
What to actually do
- Remove profiles you no longer use. Chrome menu, Profile, Manage Profiles, then delete. This is the single largest win and it is a supported operation.
- Remove extensions you do not use.
chrome://extensions. Half a gigabyte in one profile is common, and it is duplicated per profile. - Clear cached images and files through Chrome's own Clear browsing data. Safe, and smaller than people expect.
- Leave cookies and site data alone unless you want to sign in to everything again. That is what clearing service workers and IndexedDB costs.
The same is true of every browser
Edge, Brave and Opera share Chrome's architecture and behave identically, in their own folders under Application Support. Firefox and Safari differ in layout but not in principle: the profile is large, the cache is the part everyone clears.
This is the general shape of app storage on a Mac, and it is why an app's real cost is never what Finder shows. See uninstalling leaves files behind for what happens when you remove one of these apps.
Common questions
Why is Chrome taking up so much space on my Mac?
Mostly profiles rather than cache. Each Chrome profile keeps its own complete set of extensions, service workers and site storage, and profiles are created whenever you add a Google account but never removed when you stop using it. On the Mac this guide was written on, Chrome held 8.1 GB across several profiles.
Does clearing Chrome's cache free much space?
Less than expected. Cached images and files are the smaller of Chrome's two locations. The larger one is Application Support, holding extensions, service workers and site storage, and Clear browsing data only touches those if you also clear cookies and site data.
Can I delete Chrome profile folders manually?
No. Profiles are tracked in a Local State file, and removing a folder behind Chrome's back leaves the browser starting with an empty profile and no explanation. Delete profiles from Chrome menu, Profile, Manage Profiles.