Where Chrome Stores Its Cache on a Mac and How to Clear It Safely

Chrome keeps every profile's data in ~/Library/Application Support/Google/Chrome/, with the first profile you ever set up in a folder called Default and each additional one in a folder named Profile 1, Profile 2, and so on. Inside each of those folders sits a Cache directory, a Service Worker directory, an IndexedDB directory backing installed web apps and offline-capable sites, and a set of SQLite databases holding history, cookies, and bookmarks. If you run du -sh against a Chrome profile folder and the number looks larger than you expected, the answer usually isn't one runaway file — it's this whole structure, sometimes duplicated across several profiles you forgot you had. This article covers what lives where, why clearing it through Chrome's own settings matters, and how per-site storage controls let you target one bloated app instead of your whole browsing history.

The profile folder layout

A typical Chrome installation on macOS looks like this on disk:

~/Library/Application Support/Google/Chrome/
├── Default/
│   ├── Cache/
│   ├── Service Worker/
│   ├── IndexedDB/
│   ├── History          (SQLite)
│   ├── Cookies           (SQLite)
│   └── Bookmarks         (JSON)
├── Profile 1/
│   ├── Cache/
│   ├── Service Worker/
│   ├── IndexedDB/
│   └── ...
└── Profile 2/
    └── ...

Cache holds the standard HTTP resource cache — images, scripts, stylesheets — the same kind of thing every browser keeps to avoid re-downloading unchanged assets. Service Worker and IndexedDB are what back progressive web apps and any site that registers offline support: a webmail client, a chat app, a design tool you've "installed" from Chrome. Those two directories are frequently where the real size is, because a Service Worker-backed app can cache a meaningful portion of its own interface and, in some cases, working data, so it loads instantly and keeps functioning without a network connection.

Alongside those, each profile carries a handful of other SQLite databases with narrower jobs: Login Data holds saved passwords, Web Data holds autofill entries, and History and Cookies are named for what they store. None of these tend to grow large on their own, but they are further reasons to leave the profile folder alone and let Chrome manage its own files. Installed extensions add to the total too — each one gets its own storage area, keyed by its extension ID, under the same IndexedDB and Local Extension Settings directories, so a handful of extensions you installed once and stopped using can be sitting on storage of their own inside a profile that otherwise looks tidy.

Why you clear it through Chrome, not by deleting files

History, Cookies, and several other files in a Chrome profile are SQLite databases, and Chrome expects to be the only process reading and writing them while it's running. They are also interdependent — bookmarks, history entries, and site permissions reference each other internally. Deleting or editing one of these files while Chrome is open, or while it still has a lock on the profile, is a good way to end up with a corrupted or inconsistent profile rather than a clean one. The supported path is Chrome's own clearing tool: open chrome://settings/clearBrowserData, or reach it through Settings > Privacy and security > Clear browsing data. From there you can choose a time range, pick which categories to clear — browsing history, cookies and site data, cached images and files — and let Chrome handle its own databases consistently.

Multiple profiles multiply your storage use

If you use Chrome profiles to separate work and personal browsing, or you've added a profile for a client project and never removed it, each one carries its own complete copy of this structure: its own Cache, its own Service Worker data, its own IndexedDB, its own history and cookie databases. Clearing browsing data in one profile does nothing for the others — chrome://settings/clearBrowserData only ever acts on the profile you're currently in. It is easy to clean up Default diligently for months while Profile 2, created once for a project that finished a year ago, sits untouched and slowly growing. If your Chrome folder in Application Support is larger than a single profile's cache would explain, checking how many Profile N folders exist is usually the fastest way to find out why.

Finding the one bloated site instead of clearing everything

Clearing all browsing data is a blunt instrument — it signs you out of every site and discards history you might still want. When the goal is narrower, Chrome's Site Settings is the better tool. Under Settings > Privacy and security > Site Settings, and specifically the storage view for an individual site, Chrome shows how much a given origin is using and lets you clear just that site's data. This is the right approach when you already suspect the cause: a single web app you use daily that has quietly accumulated a large IndexedDB store, or a site you tried once whose Service Worker never got cleaned up. Clearing that one entry frees the space without touching cookies, history, or storage for every other site you use.

A quick way to spot which profile is the problem

Before reaching for Chrome's UI at all, it's often faster to just look at the sizes on disk:

du -sh "~/Library/Application Support/Google/Chrome/"*/Cache
du -sh "~/Library/Application Support/Google/Chrome/"*

Running the first command with Chrome closed gives you a size for each profile's cache directory individually, which tells you immediately whether the size is concentrated in Default or spread across several profiles you may have stopped using.

Conclusion

Chrome's storage footprint on a Mac is rarely one mysterious file — it's the predictable, repeated structure of profile folders, each carrying its own cache, Service Worker data, and databases, multiplied by however many profiles you've created over the years. Once you know the layout, the cause of an oversized Chrome folder is usually obvious within a minute of looking.

We built VolumeLens because we needed exactly this kind of multiplied, spread-out storage — Chrome profiles, developer caches, forgotten project folders — to be visible in one honest map rather than guessed at folder by folder. It has no network code, so nothing about your browsing or your files ever leaves your Mac, and its only action is Move to Trash after you've reviewed what's being removed. See how it lays out a Chrome profile alongside everything else on your disk on the features page.