How to Clear Application Cache on Mac: Step-by-Step (2026)

Over time, apps on your Mac accumulate cache files — temporary data stored to speed up loading and improve performance. Occasionally these caches grow oversized, become corrupted, or simply take up space you need back. This guide walks you through how to clear application cache on Mac safely, whether you want to target one specific app or do a broader sweep.

What Is Application Cache and Is It Safe to Delete?

Application cache lives in ~/Library/Caches/ (per-user) and /Library/Caches/ (system-wide). Each app typically gets its own subfolder named by bundle identifier, for example com.apple.Safari or com.spotify.client.

Cache files are designed to be regenerated — deleting them won't break your apps. The app simply rebuilds the cache the next time it runs, which means it may feel slightly slower on first launch. However, a few caveats apply:

• Safe to delete: Most app caches, browser caches, thumbnail caches, and font caches.
• Use caution: Some apps (creative tools like Lightroom, Final Cut Pro) store project-related data inside their cache folders. Deleting these can force lengthy re-indexing or re-rendering.
• Do not delete while the app is running: Always quit the app before clearing its cache to avoid file-lock errors or partial writes.
• Cleaning is permanent: macOS does not move cache files to Trash when you delete from the Caches folder. Once gone, they are gone.

How to Clear App Cache on macOS Using Finder (No Tools Needed)

This is the manual method — surgical, free, and requires nothing beyond macOS itself.

1. Quit the target app. Right-click its Dock icon and choose Quit, or press Cmd + Q.
2. Open Finder and press Shift + Cmd + G to open the Go to Folder dialog.
3. Type ~/Library/Caches and press Return.
4. Locate the subfolder that matches the app. It is usually named by bundle ID (e.g., com.apple.mail) or by the app's display name.
5. Drag that single folder to the Trash, or open it and select all contents (Cmd + A) and move those to the Trash instead — keeping the parent folder is slightly safer.
6. Empty the Trash to reclaim the disk space.
7. Relaunch the app. It will rebuild its cache automatically.

If you are not sure which bundle ID corresponds to an app, you can right-click the app in /Applications, choose Show Package Contents, and open Contents/Info.plist — the CFBundleIdentifier key shows the exact name.

How to Clear App Cache on Mac via Terminal

Terminal gives you fine-grained control, especially useful if you want to clear multiple app caches at once or automate the process.

Delete a single app's cache folder

# Replace com.example.appname with the actual bundle ID
rm -rf ~/Library/Caches/com.example.appname

List all cache folders sorted by size (useful for targeting the biggest offenders)

du -sh ~/Library/Caches/* | sort -rh | head -20

Clear all user-level caches at once (do this carefully)

rm -rf ~/Library/Caches/*

The wildcard version clears everything in your user Caches folder. This is generally safe but will cause many apps to rebuild caches on next launch, temporarily increasing CPU usage. Quit all apps first.

Which App Caches Are the Biggest Culprits?

On most Macs, a handful of apps account for the bulk of cache growth:

Clearing System-Level Caches

Beyond your user account, macOS maintains system caches in /Library/Caches/. These require administrator privileges to modify and are generally best left alone unless you are troubleshooting a specific system issue.

# List system cache folders (requires admin)
sudo du -sh /Library/Caches/* | sort -rh | head -10

macOS's memory pressure system and Optimized Storage already manage many of these automatically. Manually clearing system caches without a specific reason is rarely necessary.

Clearing App Cache Without Hunting Folders

The manual Finder method works well for one or two apps. When you want to clear app cache across macOS without opening a dozen subfolders, Crumb handles the process in a single click — it scans your Caches folder, shows each app's footprint, and lets you select exactly which app caches to remove without touching anything else.

Crumb also surfaces caches hidden in non-obvious locations (Xcode DerivedData, iOS device support files, system logs) and marks anything genuinely risky so you can make an informed decision. If you are unsure what a particular folder is, the built-in "Is this safe to delete?" AI explains the folder's purpose and removal risk in plain language. You can download Crumb and run one free cleanup to see what is taking up space before committing to anything.

How Often Should You Clear Application Cache on Mac?

There is no universal schedule. Some useful rules of thumb:

• When an app is misbehaving — corrupted cache is a common culprit for crashes and rendering glitches. Clearing it is one of the first troubleshooting steps.
• When storage is critically low — cache folders are the safest place to reclaim gigabytes quickly.
• After major macOS upgrades — old caches built against the previous OS version can occasionally cause compatibility issues.
• Not on a fixed schedule — clearing caches preemptively too often offers no performance benefit and just causes apps to re-fetch data unnecessarily.

Quick Summary

• App caches live in ~/Library/Caches/; each app gets its own subfolder.
• Always quit the app before deleting its cache.
• Use Finder's Go to Folder (Shift + Cmd + G) to navigate there without revealing the hidden Library in the menu.
• Terminal's rm -rf gives you precise, scriptable control.
• Deletion is permanent — move carefully, especially with creative and development tool caches.
• Clearing cache is a fix, not a routine chore: do it when you have a reason.

Once you know where the files live, clearing application cache on Mac is straightforward. The manual approach gives you full control; a tool like Crumb is there when you want the same precision without the folder spelunking.