How To Clear Cache On Mac

Tips
1

My Mac has been running really slow and apps like Safari and Chrome keep freezing or taking forever to load pages. I’ve heard clearing the cache can help, but I’m not sure which caches are safe to delete (system, browser, app) or the right steps to do it without messing something up. Can someone walk me through the safest way to clear cache on a Mac and what I should avoid removing?

2

Happens a lot on older Macs. Clearing cache helps, but you need to avoid nuking the wrong stuff.

Start with browsers.

Safari:

  1. Open Safari.
  2. Top menu: Safari > Settings > Advanced.
  3. Check “Show Develop menu in menu bar”.
  4. New menu appears: Develop > Empty Caches.
  5. Then go Safari > History > Clear History. Pick “all history” if you want a full reset.
    This removes stored pages, slows first load, then speeds up.

Chrome:

  1. Open Chrome.
  2. Top menu: Chrome > Clear Browsing Data.
  3. Choose “Cached images and files” and “Cookies and other site data”.
  4. Time range: “All time” if things feel messed up.
  5. Click Clear data.
    Close and reopen Chrome after.

System caches in Finder:

  1. Quit all apps.
  2. In Finder, press Shift + Command + G.
  3. Type:
    ~/Library/Caches
  4. Select everything inside Caches folder, not the folder itself.
  5. Move to Trash.
  6. Do the same for:
    /Library/Caches (no tilde, needs admin password)
    Do not touch anything that looks like installer logs or things outside Caches.

DNS cache:
Sometimes web feels slow because of DNS, not browser.

  1. Open Terminal.
  2. For recent macOS versions run:
    sudo dscacheutil -flushcache
    sudo killall -HUP mDNSResponder
  3. Enter your password.
    No output is normal.

Free disk space:
macOS slows down hard when free space drops under 10 to 15 percent.
Check Apple menu > About This Mac > More Info > Storage.
If you have less than 15 to 20 GB free, remove large files or move them to external storage.

Login items:
Slow at startup often comes from apps that auto launch.

  1. Apple menu > System Settings > General > Login Items.
  2. Disable stuff you do not use daily.

Quick sanity checks:

  1. Restart after clearing caches.
  2. During freeze, open Activity Monitor and check CPU and Memory tabs.
    Look for:
    • kernel_task super high
    • any browser process stuck using huge CPU or memory
  3. If memory pressure is yellow or red, add RAM if the Mac allows it, or close heavy apps.

Stuff you should not delete:

  • Anything in /System
  • Anything in /Library that is not inside a Caches folder
  • Things you do not recognize outside Caches directories

If things still feel slow after all this, run Disk Utility:

  1. Open Disk Utility.
  2. Select your main drive.
  3. Click First Aid.

This hits the safe areas. Browser caches, user and system caches, DNS, login items, and storage. Usually fixes freezing Safari and Chrome unless there is a deeper hardware or OS issue.

3

Couple of extra angles to add on top of what @codecrafter already wrote, without redoing all the same steps.

  1. Don’t obsess over all system caches
    macOS is actually pretty smart about caching. Nuking every cache folder all the time can make things slower for a while and occasionally cause weird app behavior. I’d treat manual deletion of /Library/Caches as a “once in a while” thing, not a weekly chore. If your Mac is ancient and spinning‑disk based, disk speed is usually the real bottleneck, not leftover cache files.

  2. Target app‑specific junk instead of carpet bombing
    Some apps get bloated way faster than others. For slow browsers and random freezes, I’d also look at:

  • Safari:

    • In Settings > Extensions, disable anything you don’t truly need. A bad extension can freeze pages worse than any cache issue.
    • Also in Privacy, “Manage Website Data” and remove data for sites you don’t care about. That’s more precise than wiping everything.

  • Chrome:

    • Type chrome://extensions in the address bar and turn off any extension you don’t recognize.
    • Type chrome://flags only if you know what you did there. Reset to default if you’ve been experimenting.

  1. User cache vs app data
    In ~/Library/Caches, most stuff is safe to delete, but if an app is mission‑critical for work, I’d skip its folder and only clear caches for things that are clearly browsers or games or random utility apps. Deleting is usually safe, but the “it’s just cache” mantra has occasionally broken cranky old apps that weren’t written well.

  2. Use built‑in tools before going full manual
    Instead of manually digging into cache folders right away, try:

  • Safe Mode:
    • Shut down.
    • Power on and immediately hold Shift until you see the login window.
    • Log in, let it sit a few minutes, then restart normally.
      Safe Mode triggers some automatic cleanup and cache rebuilds, plus it can reveal if a third‑party extension or kext is your real problem.
  1. Check for out‑of‑control sync and cloud features
    Slow browsing is sometimes network thrash, not cache:
  • iCloud: In System Settings > Apple ID > iCloud, check if Desktop & Documents syncing or Photos is hammering your bandwidth and CPU.
  • Chrome sync: Too many tabs and history syncing across devices can make Chrome act like it’s underwater. Try turning off sync temporarily and see if freezing improves.
  1. Look at profiles & content blockers
  • If you ever installed VPNs, adblockers, “security” apps, or corporate profiles, they can intercept traffic and make Safari / Chrome crawl.
    • System Settings > Privacy & Security > Profiles
    • Also check any third‑party “network filter” or antivirus and temporarily disable it.
  1. Disk space: be more aggressive than “15–20 GB free”
    Here’s where I slightly disagree with @codecrafter: on newer macOS versions with APFS and snapshots, I’ve seen performance issues even with 30–40 GB free on smaller drives, especially if Time Machine local snapshots pile up.
  • Open Time Machine settings and either plug in your backup drive so snapshots can be flushed or temporarily turn Time Machine off and back on.
  • Then in Terminal, tmutil listlocalsnapshots / to see if there’s a ton of them. You can remove old ones with tmutil deletelocalsnapshots <date> if you’re comfortable with Terminal.
  1. Don’t forget the nuclear but safe option: new user account
    Before you go hunting every obscure cache:
  • System Settings > Users & Groups
  • Create a new test user, log into that user, open Safari/Chrome, and see if the system is still slow.
    • If it’s fast there, your issue is almost certainly user‑level junk: browser profiles, login items, per‑user caches.
    • If it’s still slow, you’re looking at system, hardware, or disk problems, not just cache.
  1. When not to keep clearing cache
    If you clear everything, it speeds up for a day, then bogs down again, that’s a red flag for something ongoing:
  • Failing drive (especially old HDDs)
  • Browser profile corruption (make a fresh Chrome profile and test)
  • Too many tabs + low RAM (watch memory pressure in Activity Monitor like @codecrafter mentioned)

So yeah, clear browser cache and some user caches, but treat cache clearing as a one‑off fix and use it along with:

  • Safe Mode once
  • New user test
  • Extension cleanup
  • Checking for overzealous sync / cloud / security tools

If after all that Safari and Chrome still freeze constantly, it’s probably time to suspect hardware, not just dust in the cache folders.

4

If clearing cache is your main strategy, you’re only seeing a slice of what actually makes a slow Mac fast again. @codecrafter already nailed a lot of the basics, so here are some different angles that matter just as much, often more than manually nuking cache folders.

1. Before cache: check what is actually choking the Mac

Instead of assuming “cache = problem,” open Activity Monitor and look at:

  • CPU tab

    • If kernel_task is spiking, that can be thermal throttling, not cache. Fans clogged, hot environment, or a dying sensor.
    • If one app sits at 150%+ regularly, that app is the real villain.

  • Memory tab

    • Ignore the raw “GB used.” Focus on Memory Pressure graph at the bottom.
    • If it’s frequently yellow or red while Safari/Chrome freeze, you’re running out of RAM. Clearing cache may free some disk space but will not fix RAM pressure.
    • Real fix: fewer tabs, fewer background apps, or, if possible, more RAM on older machines.

If your Mac is pegged on CPU or memory, caches are a side show.

2. “Clear system cache” is often overrated

Here is where I slightly disagree with the heavy cache-focused approach:

  • macOS aggressively manages a lot of cache on its own.
  • Clearing system-level caches (/Library/Caches) can temporarily slow things down while the OS rebuilds them.
  • You should only touch those if:
    • You just removed big apps or drivers and something is glitchy.
    • You are troubleshooting specific bugs, not generic slowness.

Browser and user-level caches are fair game. Whole-system cache carpet bombing is rarely worth the risk or the time.

3. Browser performance: profile problems vs cache

For Safari and Chrome freezing:

  • Safari

    • If clearing website data helps only for a day, suspect:
      • A broken extension
      • Heavy content blockers
      • Sync issues with iCloud Tabs or iCloud Keychain
    • Try temporarily turning off iCloud sync for Safari to see if pages stop freezing.

  • Chrome

    • Instead of just clearing cache, create a fresh Chrome profile:
      • Settings → Manage people / profiles → add a new one.
      • Log in without extensions first.
    • If that new profile is smooth, your old one is simply bloated or corrupted.

Constantly wiping cache in a corrupted profile is like vacuuming a house with a broken floor.

4. When clearing cache is genuinely useful

If you still want targeted cache cleanup:

  • User-level caches (~/Library/Caches)

    • Safe-ish to remove for browsers, messaging apps, and random utilities.
    • Avoid mission‑critical pro tools (audio, video, or legacy business software). Those sometimes stash quirky data in what they call “cache.”

  • Browser caches

    • Fine to clear, especially image/script caches and site data for problematic sites.
    • Just expect sites to load slightly slower the first time after you do it.

Run this kind of cleanup occasionally, not weekly.

5. Disk health matters more than most guides admit

If your Mac has a hard drive or an old SSD:

  • Run Disk Utility → First Aid on your main volume.
  • A flaky disk or a failing SSD can make apps look like they are “waiting on cache” when they are actually waiting on failing storage.
  • If First Aid shows repeated errors or you hear scratching/clicking from an HDD, that is a hardware issue. No amount of cache clearing fixes that.

Also, try to keep at least 15–20% of disk space free. I am less aggressive than @codecrafter on the 30–40 GB rule, because on big drives percentage matters more than a fixed number of gigabytes, but if you are under 10% free, performance absolutely tanks.

6. Startup & background items: the invisible slowdown

Many slow Mac problems come from:

  • Login items
  • Auto-start menu bar tools
  • “Helper” apps from printer, scanner, VPN, and “cleaning” software

Check:

  • System Settings → General → Login Items
    • Disable anything you do not genuinely need daily.
  • Also check for any third-party cleaners or “optimizers.” Ironically, some of these run constant background scans and do more harm than good.

If Safari and Chrome are hanging but CPU shows a bunch of strange background stuff at the top, fix that before worrying about system cache.

7. Test in a clean environment

This was hinted at but is worth stressing:

  • Safe Mode: You already saw this suggestion, but treat it as a diagnostic, not just a cleanup step.

    • If your Mac is snappy in Safe Mode, then normal mode adds some extension, driver, or login item that causes trouble.

  • New user account:

    • If that fresh account runs both Safari and Chrome smoothly, 99% chance your slowdown is in:
      • User caches
      • Browser profiles
      • Login items and per-user sync features

Instead of blindly clearing every folder, you can then focus on what differs between your main account and the new one.

8. About using a “How To Clear Cache On Mac” type approach

A dedicated “How To Clear Cache On Mac” style checklist can be useful if it emphasizes:

Pros

  • Gives you a structured path: browser → user cache → login items → Safe Mode.
  • Good for one big cleanup session when things feel really sluggish.
  • Helps people discover built-in tools like Activity Monitor and Disk Utility instead of installing random cleaners.

Cons

  • If it encourages routine full cache purges, it can reduce performance short term or hide underlying problems like bad extensions or failing storage.
  • Too much focus on caches may lead you to ignore RAM limits, overheating, sync loops, and dodgy third-party software, which are often the real cause.

Compared with what @codecrafter laid out, I would use that kind of “How To Clear Cache On Mac” flow once, then switch to diagnosing root causes rather than repeating the same cleanup every week.

9. When to stop clearing cache and suspect something serious

If you notice this pattern:

  • You clear caches
  • Mac feels OK for a few hours or a day
  • It bogs down again, fans spin, browsers freeze

Then you should investigate:

  • Hardware:
    • Old HDD, failing SSD, swollen battery causing thermal throttling
  • Software:
    • A single misbehaving background app
    • Overflowing browser profile or memory leaks
  • Environment:
    • Extremely low disk space coming back quickly after cleanup

At that point, clearing cache is just temporarily moving the pain, not solving it.

If you want to post specifics like your Mac model, OS version, how much RAM you have, and a quick screenshot of Activity Monitor (CPU and Memory tabs), the troubleshooting can be much more targeted than “clear everything and hope.”