How to Clear Safari's Cache on Mac (and Why You'd Want To)

Safari’s cache is doing something useful — storing copies of images, scripts, and fonts so pages load faster on revisit. But sometimes you want to clear it: a website’s broken in Safari but works in private mode, you’re a developer testing fresh assets, or Safari’s just chewing through more storage than seems reasonable.

There are three ways to clear it, and only one of them clears just the cache. The others wipe your history and cookies along with it, which is usually not what you actually want.

Method 1: Clear History (the blunt option)

This is the obvious one. Safari → menu bar → History → Clear History. Pick a time range (Last hour, Today, Today and yesterday, All history). Click Clear.

What this clears:

• Browsing history
• Cookies (signing you out of every site)
• Cache
• Visited link colors
• Saved passwords for cleared cookies in some cases
• Recent searches

This is fine if you want a fresh slate. It’s bad if you just had a stuck stylesheet on one site and now you’re logged out of everything.

Method 2: Manage Website Data (the targeted option)

If you only want to clear cache and cookies for a specific site, use this. Safari → Settings (cmd-comma) → Privacy → Manage Website Data. Wait a few seconds for it to populate.

You’ll see every domain that’s stored data, plus what kind (cookies, cache, local storage). You can:

• Type in the search box to find one site
• Select it and click Remove
• Or click Remove All to nuke everything (same effect as Clear History, minus the history itself)

This is the move when one site is misbehaving. Clear just that domain’s data, refresh, see if it fixes it.

Method 3: Develop Menu (cache only, no signing out)

This is the one most people don’t know about. There’s a hidden Develop menu in Safari that lets you clear just the cache without touching cookies. So you stay signed in everywhere.

To enable it:

1. Safari → Settings → Advanced
2. Tick “Show features for web developers” (or “Show Develop menu in menu bar” on older Safari versions)
3. Close Settings

Now you have a Develop menu. Click it → Empty Caches. Done. Cache is gone, cookies are intact, you’re still signed in to everything.

Keyboard shortcut: cmd-option-E.

This is what developers and tech support use. It’s the cleanest cache clear you can do.

Where Safari’s cache actually lives

For the curious, Safari’s cache files live in:

• ~/Library/Caches/com.apple.Safari/ — main cache
• ~/Library/Containers/com.apple.Safari/Data/Library/Caches/ — sandboxed cache
• ~/Library/Safari/ — bookmarks, history, top sites, reading list

You can see how much space these take in Finder by selecting the folder and pressing cmd-I (Get Info). On a Mac that’s been running for a year or two, the Safari cache can easily be 1-3 GB.

You technically can manually delete the cache folder. Don’t. macOS doesn’t always handle this gracefully and Safari will recreate things in unexpected ways. Use the Develop menu method instead.

Why clear the cache at all?

A few legitimate reasons:

1. A website’s stuck on an old version. You know they pushed an update but you’re still seeing the old one. Cache clear forces a fresh fetch.
2. A site you trust is misbehaving. Login pages that hang, images that won’t load, layouts that look broken. Often a cache problem.
3. You’re a developer testing changes. Cache clear (or Disable Caches via Develop menu) is part of your workflow.
4. Storage is tight and you want some space back. Cache can be 1-3 GB.
5. Privacy reasons. You want to clear what your cache reveals about your browsing.

What clearing the cache won’t fix: slow Safari overall (different problem), websites that are genuinely down, or extensions causing issues.

Clear caches across every browser at onceSweep clears Safari, Chrome, Firefox, and Arc caches in a single pass. Free download for Mac →

What about cookies, separately?

Cookies and cache are different things, even though they’re often cleared together. Cookies are tiny pieces of data each site stores to remember you (logged in, preferences, cart contents). Cache is copies of resources to make pages load faster.

To clear just cookies, in Safari → Settings → Privacy → Manage Website Data, you can selectively remove cookies for specific sites. There’s no built-in “clear cookies, keep cache” toggle, but Manage Website Data lets you do it manually.

To block cookies more aggressively going forward: Safari → Settings → Privacy → “Prevent cross-site tracking” (on by default in Sonoma 14 and Sequoia 15) and “Block all cookies” (off by default — turning it on breaks lots of sites).

Private Browsing as a cache-bypass

If you don’t want to clear your real cache but want to test a site fresh, Private Browsing windows have their own ephemeral cache that’s wiped when you close them.

File → New Private Window (cmd-shift-N). Visit the site. When you close the window, the cache for that session disappears. No effect on your normal browsing data.

Cache clearing as a troubleshooting routine

If a website is misbehaving in Safari, here’s a fast troubleshooting order:

1. Reload while bypassing cache: cmd-shift-R (forces a fresh fetch ignoring cache)
2. If still broken, Develop menu → Empty Caches → reload
3. If still broken, Manage Website Data → remove that site’s data → reload
4. If still broken, try in a Private window
5. If broken in Private too, the site itself has an issue, not your cache

Safari extensions can also cache

Some extensions (ad blockers, content modifiers) do their own caching. If a site’s misbehaving and clearing Safari’s cache didn’t fix it, try disabling extensions: Safari → Settings → Extensions → uncheck them all → reload the site.

If the site works with extensions off, re-enable them one by one to find the offender.

Doing this across multiple browsers

If you’re like most people, Safari isn’t your only browser. You probably also have Chrome for one specific site, Firefox for another, and maybe Arc out of curiosity. Clearing cache across all four manually is tedious — different menus, different shortcuts, different steps.

A cleaning tool that handles all installed browsers in one pass is genuinely faster. You scan once, see how much each browser’s cache is using, and clear them together (or selectively).

There’s a faster waySweep does the same hunt in seconds, with a preview before anything is removed. Try Sweep free →

How often to clear

Honestly, almost never, for most people. Safari manages its cache automatically — old entries are evicted to make room for new ones. Manually clearing the cache offers no performance benefit on a modern Mac with reasonable storage. It just slows down the next few page loads while the cache rebuilds.

Times to actually do it:

• A specific site is broken (cache might be the cause)
• You’re a developer or QA tester
• Storage is genuinely tight and Safari’s cache is huge
• You’re handing a Mac to someone else

Otherwise, leave it alone.

Summary

Three options, in order of usefulness:

• Develop menu → Empty Caches — cache only, keep cookies and history. Best for everyday use.
• Manage Website Data — targeted clear for one site or set of sites
• Clear History — nuclear option, also wipes cookies and history

For Mac users running Sonoma 14 or Sequoia 15, the Develop menu method is the move 90% of the time. Cookies stay. Sign-ins stay. The site fetches fresh resources. Done.

Sweep handles the across-all-browsers case if you want to clear Safari, Chrome, Firefox, and Arc in one pass — useful when you’ve used them all and want to reclaim the storage.