MainspringGuides › Chrome disk cleanup
macOS Guide

Chrome Taking Up Space on Mac? Clean It Up Safely

Updated July 2026 · 3 min read

Chrome doesn't just take space as an app — it accumulates it. Caches, per-site storage, service workers, and whole forgotten profiles pile up under your Library folder, and plenty of Macs are carrying 10 GB of Chrome data without knowing it. Here's how to measure it and clear the fat without losing passwords or bookmarks.

Measure what Chrome is actually using

# profiles, extensions, site data (read-only)
du -sh ~/Library/Application\ Support/Google/Chrome
# Chrome's disk cache (read-only)
du -sh ~/Library/Caches/Google/Chrome

The first folder is your Chrome life — bookmarks, passwords, extensions, and per-site storage. The second is disposable cache. A big number in Caches is safe to clear; a big number in Application Support needs the more surgical approach below. Whatever you do, don't delete either folder wholesale in Finder — that's how people lose every bookmark at once.

Quit Chrome before measuring or cleaning; it holds these files open while running. Inside each profile folder, the usual heavyweights are Service Worker, Code Cache, and GPUCache — but you don't need to touch them directly. The steps below clear them through Chrome's own UI, which keeps the profile database consistent.

Clear the cache the safe way — inside Chrome

  1. In Chrome, press Cmd+Shift+Delete, or go to Settings → Privacy and security → Delete browsing data. (Older Chrome versions call it Clear browsing data.)
  2. Set the time range to All time.
  3. Tick Cached images and files only. Leave cookies unticked — clearing them signs you out of every site — and leave history alone unless you want it gone.
  4. Click Delete data.

On a heavily used profile this alone recovers gigabytes. There's no undo, but nothing here needs one: the cache rebuilds itself as you browse, at the cost of slightly slower first loads for a day or two.

Skip the ritual cleaning, though. The cache exists to make browsing faster, and clearing it weekly just makes Chrome re-download the same assets. Clean when disk pressure is real, not on a schedule.

Clear per-site storage and service workers

Web apps like Figma, YouTube, and Google Drive can each park hundreds of megabytes of offline storage via service workers — the machinery behind offline mode and instant loading. Handy for the three sites you live in, pure dead weight for the one you visited once in 2023. To see who's hoarding:

  1. Open Settings → Privacy and security → Site settings.
  2. Click View permissions and data stored across sites.
  3. Sort or search, then use the delete control next to any site you don't need offline. You'll be signed out of that site; nothing else is lost — bookmarks, passwords, and extensions are untouched.

Repeat the check every few months if you try a lot of new web apps; abandoned ones keep their storage until you evict them.

Hunt down abandoned profiles

Every Chrome profile keeps its own full set of data in a folder named Default, Profile 1, Profile 2, and so on. An old work profile can hold gigabytes you forgot existed:

# size of each profile folder (read-only)
du -sh ~/Library/Application\ Support/Google/Chrome/Default \
       ~/Library/Application\ Support/Google/Chrome/Profile*

To remove one, use Chrome itself rather than Finder: click your avatar in the toolbar to open the profile list, hover over the unwanted profile, and choose Delete from its menu. This permanently deletes that profile's local bookmarks, passwords, and history — if any of it matters, sign into the profile first and confirm sync is on, so a copy lives in its Google account.

Clean up settings, not just caches

While you're decluttering, Mainspring turns 90+ hidden macOS settings into labelled, reversible toggles — Finder, Dock, screenshots, and privacy tweaks, each with a built-in way back.

Try Mainspring free →

Signed & notarized by Apple · 1-day free trial · $29 once

Space is one problem, memory is another

If Chrome is also making your Mac feel slow, disk isn't the culprit — RAM is. See Chrome using too much memory on Mac for that side of the cleanup.