How to Clear Cache on Mac: Sequoia, Sonoma, Ventura & Tahoe

Knowing how to clear cache on Mac isn't a single procedure — it depends on which macOS version you're running and which type of cache you're targeting. User caches, system caches, and app caches each live in different places, behave differently across Ventura, Sonoma, Sequoia, and the upcoming Tahoe, and carry different levels of risk when deleted. This guide walks through exactly where they are, what's safe to remove, and the correct steps for each version.

User Cache vs System Cache: What's the Difference?

Before touching anything, it helps to understand the two main categories.

• User cache lives inside your home folder at ~/Library/Caches. These files belong to your account only and are created by apps you run. They are generally the safest to delete — an app will simply rebuild its cache the next time it needs it.
• System cache lives at /Library/Caches (no tilde) and is owned by root. It includes caches for system daemons, software update metadata, and shared frameworks. Some of these rebuild automatically; others take a reboot to regenerate. Deleting system cache files while a daemon is actively using them can cause instability.
• App-specific caches are sometimes stored outside these standard paths — for example, browser caches inside ~/Library/Application Support, or Xcode derived data at ~/Library/Developer/Xcode/DerivedData.

Which macOS Versions This Guide Covers

The underlying cache folder structure (~/Library/Caches, /Library/Caches, /private/var/folders) has been stable since macOS 10.15. Version differences affect which apps write large caches, not where they live.

How to Clear User Cache on Mac (All Versions)

Clearing your user cache is safe and non-destructive. Apps will rebuild their caches on next launch. You may notice slower app startup once after clearing.

1. Quit any apps whose caches you want to clear. Deleting a cache while an app is writing to it can corrupt the rebuilt version.
2. Open Finder, then press Shift + Command + G to open Go to Folder.
3. Type ~/Library/Caches and press Return.
4. Select the folders you want to remove. To delete everything, press Command + A to select all, then move to Trash.
5. Empty the Trash (Shift + Command + Delete, then confirm).

You can do the same thing from Terminal:

rm -rf ~/Library/Caches/*

Note the /* — this deletes the contents of the Caches folder, not the folder itself, which is the correct behavior.

How to Clear System Cache on Mac

System cache cleanup is more involved and carries more risk. Only delete system caches if you understand what a specific folder does, or if you're following explicit vendor guidance (e.g., clearing a corrupted font cache).

1. Open Terminal (/Applications/Utilities/Terminal.app).
2. List the contents of the system cache folder first:

ls /Library/Caches

3. To clear a specific subfolder (example: the Apple software update cache):

sudo rm -rf /Library/Caches/com.apple.SoftwareUpdate/*

4. Restart your Mac. Many system caches are memory-mapped; a clean reboot ensures daemons reinitialize properly.

Do not run sudo rm -rf /Library/Caches/* as a blanket command. Some system services — particularly those handling security policy or network configuration — may not recover cleanly without a reboot, and clearing mid-session can produce errors in unrelated apps.

Clearing Specific App Caches

Safari

Safari stores its cache in ~/Library/Caches/com.apple.Safari. The cleanest way to clear it without losing bookmarks or history is through Safari's own menu: Develop > Empty Caches. If the Develop menu isn't visible, enable it under Safari Settings > Advanced.

Chrome and Firefox

Both browsers manage their own cache directories under ~/Library/Application Support and ~/Library/Caches respectively. Use the built-in clear-browsing-data dialog (Command + Shift + Delete) rather than deleting folders manually — this avoids corrupting the browser's internal database.

Xcode Derived Data (Ventura, Sonoma, Sequoia)

Xcode derived data accumulates quickly and is completely safe to delete:

rm -rf ~/Library/Developer/Xcode/DerivedData

Xcode rebuilds this on the next build. You can also delete it from Xcode: Xcode > Settings > Locations > Derived Data > arrow icon.

iPhone Mirroring Cache (Sequoia and Tahoe)

If you use iPhone Mirroring on macOS Sequoia or Tahoe, a mirroring-related cache appears in ~/Library/Caches under a com.apple.ScreenTimeAgent or mirroring-related bundle identifier. This is safe to delete with iPhone Mirroring closed; the session cache rebuilds on reconnect.

The "System Data" Section in About This Mac Storage

On Ventura, Sonoma, and Sequoia, About This Mac > Storage often shows a large "System Data" category. This is an umbrella label that includes:

• Purgeable space (caches macOS can reclaim automatically under disk pressure)
• System cache files in /Library/Caches
• Time Machine local snapshots
• Virtual memory swap files
• Rosetta 2 translation caches

Purgeable space does not need to be manually cleared — macOS reclaims it automatically. If System Data is consuming a genuinely large amount of non-purgeable space, use a tool that can identify exactly which folders are responsible before deleting anything.

What Is Safe to Delete — and What Isn't

A note on permanence: deleting cache files is permanent. While apps rebuild their caches, any cached data that was effectively a shortcut — such as a partially downloaded file or a saved rendering — will need to be regenerated, which costs time and bandwidth.

Faster Alternative: One-Click Clean with Crumb

If manually navigating ~/Library/Caches and auditing subfolders isn't something you want to do every few months, Crumb handles this automatically. Its one-click Clean scans user caches, system caches, logs, and temp files, identifies what's safe to remove based on app state, and shows you exactly what will be deleted before anything is touched. It also handles purgeable space and System Data cleanup that the manual process above doesn't easily reach.

For anyone who wants to see what's actually taking up space before cleaning, Crumb's Visualize mode shows a treemap of your entire disk, so you can identify a 20 GB Xcode cache or a forgotten virtual machine before deciding what to remove.

Conclusion

Clearing caches on Mac is straightforward once you know which type of cache you're dealing with. User caches in ~/Library/Caches are safe to clear at any time with apps closed. System caches in /Library/Caches warrant more care and a reboot afterward. The underlying paths are consistent across Ventura, Sonoma, Sequoia, and Tahoe — what changes between versions is which apps write the largest caches, not where they write them. If you'd rather skip the manual audit, download Crumb and let it handle the identification and cleanup safely.