To clear an application’s cache on a Mac, you manually delete the cache files stored in the user’s ~/Library/Caches folder or use the app’s own built-in cache-clearing option. This guide explains exactly where caches live, which ones are safe to delete, and how to do it without breaking your apps.
What Is an Application Cache?
An application cache is a temporary storage folder where apps keep files they expect to need again soon: thumbnails, downloaded fonts, web page assets, login tokens, and computed data. The goal is speed—reading a cached file from your SSD is much faster than regenerating it or downloading it again. Over time, however, caches can grow large, become corrupted, or contain outdated data that causes visual glitches, slow launches, or crashes.
On macOS, most caches live in ~/Library/Caches (the tilde means your home folder). Each app typically has its own subfolder named after the app or its developer. Some apps also store caches in ~/Library/Application Support, but that folder usually contains important settings and data, not just throwaway files—so you should not delete it indiscriminately.
Why You Might Want to Clear a Cache
Clearing a cache is not a routine maintenance task like emptying the trash. You should do it when you notice a specific problem:
- An app is misbehaving: showing old content, crashing on launch, or displaying corrupted graphics.
- An app is using excessive disk space: some caches (like browser or video-editing caches) can grow into gigabytes.
- You are troubleshooting: after a macOS update or an app update, stale caches sometimes conflict with new versions.
- You are about to sell or give away your Mac: clearing caches helps remove personal data remnants, though it is not a substitute for a full wipe.
If your Mac is simply running slowly, clearing caches is rarely the fix. macOS manages caches automatically, and deleting them can temporarily slow down apps as they rebuild the data.
How to Clear a Single App’s Cache (Safest Method)
This method targets one app and leaves everything else untouched. It is the recommended approach because it minimizes the risk of deleting something important.
- Quit the app whose cache you want to clear. If it is running, its cache files may be locked or in use.
- Open Finder and press Shift + Command + G (Go to Folder).
- Type
~/Library/Cachesand press Return. You will see a list of folders, usually named after the app or its developer (e.g.,com.google.Chromefor Chrome,com.apple.Safarifor Safari). - Locate the folder for the app you want to clear. If you are unsure, look for the app’s name or its bundle identifier (the
com.company.appformat). - Drag that folder to the Trash (or right-click and choose Move to Trash). Do not empty the Trash yet—if the app misbehaves after relaunching, you can restore the folder.
- Relaunch the app. It will create a fresh cache as needed.
If the app has its own “Clear Cache” button (common in browsers like Safari, Chrome, and Firefox, and in some creative apps), use that instead—it is designed for the task and often clears only the relevant data.
How to Clear All App Caches at Once
If you want to clear every app’s cache in one go, you can delete the entire contents of the ~/Library/Caches folder. This is safe in the sense that no app will lose its settings or documents—only temporary files. However, it is more disruptive: every app will have to rebuild its cache, which can make your Mac feel slower for a few minutes or hours.
- Quit all running apps (you can leave Finder and System Settings open).
- Open Finder and press Shift + Command + G, then type
~/Library/Caches. - Select all items (Command + A) and drag them to the Trash. You may need to enter your password for some system-level caches.
- Restart your Mac. This ensures all apps start fresh and rebuild their caches cleanly.
Do not delete the ~/Library/Caches folder itself—only its contents. The folder needs to exist for macOS to function correctly.
What About System Caches and Other Locations?
Besides the user-level ~/Library/Caches, macOS also keeps caches in /Library/Caches (shared across all users) and /System/Library/Caches (system-level). You should never manually delete files from /System—that can break your Mac. The /Library/Caches folder is rarely the cause of app problems, and modifying it requires administrator privileges.
Some apps also use hidden caches outside the Caches folder. For example, browsers store website data (cookies, local storage) in ~/Library/Application Support or in the app’s own folder. If you are trying to clear a browser’s cache to fix a webpage display issue, use the browser’s built-in “Clear browsing data” option instead of hunting for files.
macOS itself has a separate cache for system services (like Spotlight and font caches). You generally do not need to clear these unless you are following a specific troubleshooting guide for a known issue (e.g., Spotlight not indexing). In those cases, the recommended method is usually to restart the service via System Settings, not to delete files manually.
Common Mistakes and Misconceptions
One widespread misconception is that clearing caches will speed up your Mac. In reality, a full cache is often faster than an empty one. The only time clearing improves performance is when a cache is corrupted or so large that it consumes significant disk space.
Another mistake is confusing caches with preferences or saved data. For example, deleting ~/Library/Application Support will remove app settings, login info, and even documents for some apps. Always double-check that you are in the Caches folder, not a sibling folder.
A third error is deleting caches while the app is running. This can cause the app to crash or write new cache files into a half-deleted folder. Always quit the app first.
Finally, do not use third-party “cache cleaner” apps unless you trust them. Many of them do nothing more than what you can do manually, and some may delete the wrong files. The built-in tools (Finder, and the app’s own settings) are sufficient for almost every need.
Frequently Asked Questions
Is it safe to delete everything in ~/Library/Caches?
Yes, generally it is safe. These are temporary files, and apps will recreate them. However, you might lose some convenience, like offline cached web pages or saved login states in some apps. If you are concerned, delete one app’s cache at a time and test the app.
Will clearing caches delete my passwords or login info?
No. Passwords and login tokens are stored in your Keychain, not in caches. Clearing an app’s cache will not log you out of websites or services, though some apps may take longer to load your profile the first time.
How do I clear the cache for a specific app like Chrome or Safari?
For Chrome, go to Chrome menu > Clear Browsing Data and choose “Cached images and files.” For Safari, go to Safari > Settings > Advanced and enable “Show features for web developers,” then use the Develop menu to empty caches. For any other app, use the Finder method described above.
Does clearing caches free up a lot of disk space?
It depends. Browsers and media apps can have caches of several gigabytes, but most apps have small caches. You can check the size of each folder in ~/Library/Caches by viewing it in Finder (Command + J, then choose “Calculate all sizes”). If you need space, look for large folders there.
Why does my Mac still show the same cache size after I delete it?
Because apps are constantly writing new cache files. If you delete a cache while the app is running, it may immediately recreate it. Also, macOS may keep some files in memory until you restart. To see the freed space, empty the Trash and wait a few minutes.
Is there a built-in Mac tool to clear caches?
No. macOS does not have a “Clear Cache” button in System Settings. The manual Finder method is the built-in way. Some apps include their own cache-clearing options, which is the cleanest approach when available.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Credential Manager: Seamless Sign-In Explained
- API Governance for Public Data: What Growing Portfolios Need
- Samsung Smart Speaker Rollable Display: Facts
- HP 9730e: Wide Prints, Not A3 Scans
- What 8888 Does When You Use It as DNS Server
- Enterprise AI Hidden Cost: Data Architecture ROI