2026 Guide
How to delete browser caches & bloat (2026 Guide)
Chrome, Brave, Edge, and Arc keep a second pile of website data that Apple's Storage settings and even Chrome's own "Clear browsing data" often miss. If you use more than one Chrome profile, that pile is duplicated for every person on the machine. This guide shows how MacMop's Browser Bloat scanner finds it, what is safe to delete, and what CacheStorage actually is.
Scan every Chrome profile in one pass
MacMop lists CacheStorage, IndexedDB, and more — without touching passwords or bookmarks.
Why this matters if you have multiple Chrome profiles
Each Chrome profile is a separate user on disk: Work, Personal, a client account, a kids profile. Chrome stores them as folders named Default, Profile 1, Profile 2, and so on under ~/Library/Application Support/Google/Chrome/.
Clearing cache in the profile you have open only cleans that profile. The other nine keep their service-worker caches, offline Google Docs data, and compiled JavaScript. That is why a Mac with many Chrome profiles can hide several gigabytes that never show up in Chrome Settings.
MacMop reads Chrome's Local State file so the table shows the name you actually gave the profile (Work, Personal) plus the folder name, so you can tell them apart.
What Browser Bloat looks like in MacMop
Open MacMop → Browser Bloat → Scan Browser Data. You get a total across every Chromium profile, a safety tag on each row, and filters for browser, profile, type, size, and age.
Browser Bloat
Scan AgainBrowser Bloat: 2.4 GB found across 10 browser profiles
Learn more →
Persistent website app data. Deleting it does not remove passwords or bookmarks.
3 items — 957 MB total
| Domain / File | Size | Profile | Type | Safety |
|---|---|---|---|---|
CacheStorage ~/Library/Application Support/Google/Chrome/Profile 1/Service Worker/CacheStorage | 457 MB | Work Profile 1 | CacheStorage | Safe |
docs.google.com ~/Library/Application Support/Google/Chrome/Profile 2/IndexedDB/https_docs.google.com_0.indexeddb.leveldb | 312 MB | Personal Profile 2 | IndexedDB | Review |
Code Cache ~/Library/Application Support/Google/Chrome/Default/Code Cache | 188 MB | Person 1 Default | Code Cache | Safe |
How to clean it (2 minutes)
- Quit Chrome, Brave, Edge, or Arc so files are not locked.
- Open MacMop and run Browser Bloat.
- Filter to Safe if you want a no-drama cleanup (Cache, Code Cache, GPU Cache, CacheStorage, ScriptCache).
- Use the profile filter if you only want to clean Work, or only an unused profile.
- Click Delete All Safe or tick rows and Delete Selected.
Rows marked Review (IndexedDB, File System) can reset a site's offline data. Caution (Local Storage / Session Storage) can log you out of that site. Passwords, cookies, bookmarks, and history are never in this scanner.
File type deep dive: CacheStorage
A typical large row looks like this:
~/Library/Application Support/Google/Chrome/Profile 1/Service Worker/CacheStorage
This is the browser Cache API used by service workers — the same mechanism PWAs and many Google, Microsoft, and Figma tabs use to keep assets offline. Inside the folder, Chrome stores opaque hashed origin directories. You will not see tidy names like "youtube.com"; you will see long IDs. The parent CacheStorage folder is the unit MacMop reports.
| Question | Answer |
|---|---|
| What is usually in it? | Cached scripts, images, fonts, and API responses that a site's service worker saved for faster loads and offline use. |
| Is it safe to delete? | Yes. MacMop marks CacheStorage as Safe. Chrome rebuilds it the next time those sites run a service worker. |
| What you might notice | Those sites may load a bit slower once, or briefly feel "fresh" instead of instant. Offline PWAs may need a network trip to refill the cache. |
| What is not deleted | Passwords, cookies, bookmarks, history, extensions, and the rest of the Chrome profile. Only this cache tree. |
| Why it gets huge | Every profile keeps its own copy. Heavy web apps (Google Workspace, Figma, Notion, YouTube) write a lot here and rarely prune it themselves. |
Related folders in the same profile: Service Worker/ScriptCache (also safe), Cache and Code Cache (HTTP and compiled JS caches, also safe). Do not delete the parent Chrome Application Support folder — that is the whole browser profile.
How to match Profile 1 to a name in Chrome
- Switch to that Chrome user, then open
chrome://version. - Read Profile Path. The last segment is the folder name.
- The avatar in the top-right of Chrome is the display name MacMop shows in the Profile column.
Clean every profile without guessing folders
MacMop is a native Mac app. Browser Bloat is built for people who keep more than one Chrome profile.
Download MacMop Free