How to Clear Chrome Cache on Mac (Full and Per-Site)

In short: Pages loading wrong or stuck on an old version? Clearing Chrome's cache usually fixes it. This guide walks you through the full clear and the faster per-site option, so you can free up space without logging out of every account you use.

When a website looks broken, keeps serving an outdated layout, or Chrome starts feeling sluggish, a stale cache is often the reason. The cache is a folder of saved images, scripts, and page fragments that Chrome keeps so sites load faster on your next visit. Most of the time it helps. Occasionally it holds onto a bad copy and refuses to let go. Clearing it is safe, reversible in the sense that Chrome simply rebuilds it on your next visit, and it takes about a minute.

This guide covers two approaches: a full cache clear across all sites, and a targeted per-site clear that fixes one stubborn page without signing you out of everything else. Both work on macOS 14 (Sonoma) and macOS 15 (Sequoia) with current Chrome.

Clear Chrome's Cache for All Sites

This is the standard fix. It removes cached files across every site while letting you keep your history and passwords if you want to.

1. Open Chrome and press Command + Shift + Delete. This opens the Delete browsing data dialog directly.
2. Set the Time range at the top. Choose All time to clear everything, or a shorter window like Last hour if you only need to fix something recent.
3. Under the Basic tab, check Cached images and files. Leave Browsing history and Cookies and other site data unchecked if you only want the cache gone and would rather stay signed in to your accounts.
4. Click Delete data.

That is it. Chrome discards the saved files and rebuilds them as you browse. You will not lose bookmarks, saved passwords, or extensions. If you also checked cookies, expect to sign back in to some sites, which is worth knowing before you commit.

Clear the Cache for One Site Only

You often do not need the sledgehammer. If a single site is misbehaving, you can clear its cache and cookies alone and leave every other login untouched. This is the tidiest fix.

1. Open the misbehaving site in Chrome.
2. Click the icon at the far left of the address bar (a tune or slider icon, or the site name), then choose Site settings. Alternatively go to the three-dot menu, More tools is not needed here, so use the address-bar icon.
3. On the Site settings page, click Delete data near the top and confirm.

This clears cached files and stored data for that one domain. You will likely need to sign back in to that site, but every other tab and account stays exactly as it was. It is the fastest way to fix one broken checkout page or a dashboard that will not update.

Reload Without Clearing Anything

Before you clear anything, try the lightest option. A hard reload tells Chrome to fetch a fresh copy of the current page and skip the cache for that request only.

• Press Command + Shift + R to force a full reload of the page.
• Or open Chrome's DevTools with Command + Option + I, then right-click the reload button and choose Empty Cache and Hard Reload.

This fixes many "the page looks wrong" moments in seconds and touches nothing else. Reach for the full clear only when a hard reload does not do the job.

Where the Cache Lives, and Why You Should Not Delete It by Hand

Chrome keeps its cache inside your user Library, typically under ~/Library/Caches/Google/Chrome and within the profile folders in ~/Library/Application Support/Google/Chrome. It can be tempting to open Finder and drag those folders out, but do not. Deleting cache files while Chrome is running can corrupt the profile, and there is no reason to touch system paths. Let Chrome manage its own cache through the steps above. Never delete anything inside /System.

A Quick Word on Safety and Privacy

The good news about clearing a cache is that it is low-risk. You are removing regenerated files, not documents. If you use a dedicated cleaning app for a broader tidy-up, the same principle applies: it should preview what it plans to remove, touch only user-level junk by default, and send removals to the Trash so anything can be restored. A cleaner has no reason to phone home either, and you can confirm that yourself with a firewall like Little Snitch watching its traffic.

If you want one that follows those rules, CoreSweep is our top free pick: free forever, an optional one-time Pro at $49, zero telemetry, and every removal goes to the Trash so it stays reversible. For a lighter-weight, best-value runner-up, SkoonMac is free with a one-time $19 Pro. Either way, clearing Chrome's cache on your Mac is a safe first step, and now you know how to do it fully or one site at a time.

Frequently asked questions

Does clearing Chrome's cache on Mac log me out or delete my passwords?

No. If you check only "Cached images and files" in the Delete browsing data dialog, Chrome keeps your history, bookmarks, saved passwords, and extensions. You only get signed out of sites if you also clear "Cookies and other site data," so leave that unchecked if you want to stay logged in.

How do I clear the cache for just one website in Chrome on a Mac?

Open the misbehaving site, click the icon at the far left of the address bar, and choose Site settings. On that page, click Delete data near the top and confirm. This clears cached files and stored data for that one domain only, so every other tab and login stays exactly as it was.

Is it safe to delete Chrome's cache folder manually in Finder?

It is not recommended. Deleting cache files under ~/Library while Chrome is running can corrupt your profile, and there is no reason to touch system paths. Let Chrome rebuild its own cache through its settings instead, and never delete anything inside /System.

← All Mac cleaning guides · Back to the comparison