Is ~/Library/Caches Safe to Delete on Mac? What to Know

What is ~/Library/Caches on Mac?

~/Library/Caches is a directory in your personal Library folder. It is used by applications to store cache data associated with your macOS account. You can find it here: ~/Library/Caches The ~ symbol represents your home directory. For example, if your Mac account is named alex, the full path is: /Users/alex/Library/Caches A cache stores information that an application can use again instead of generating or downloading it every time. This can improve performance and reduce repeated work. Apple's Foundation documentation describes the Caches directory as a place for data that an application does not require to operate but that can improve performance. Its examples include database cache files and transient, downloadable content. Common examples of cache data include: - Browser resources: Locally stored copies of website images, scripts, stylesheets and other resources. - Database caches: Temporary or derived information that an application can regenerate from its underlying data. - Downloaded resources: Files an application can retrieve again when it needs them. - Application previews: Certain generated thumbnails and preview resources, depending on how the application manages them. The exact contents vary by application. Two applications can use their cache directories in very different ways. Apple's guidance also makes an important distinction: an application should not rely on cache files being present. It should be able to regenerate them when necessary.

Read more: Apple Developer: Using the file system effectively · Apple Developer: macOS Library Directory Details

Where are Mac cache folders stored?

There isn't just one directory named Caches on macOS. You may encounter several locations, and they do not all have the same purpose. 1. User caches: ~/Library/Caches This is the standard user-level cache directory for non-sandboxed macOS applications. It can contain folders belonging to individual applications. The folder names may use an application name, developer name or bundle identifier. For example, Chromium documents this Chrome cache location: ~/Library/Caches/Google/Chrome/Default Chrome's corresponding profile data is stored separately: ~/Library/Application Support/Google/Chrome/Default This distinction is useful: the cache directory and the browser profile are not the same thing. 2. Sandboxed application caches Some applications store their data inside an individual macOS sandbox container rather than directly under ~/Library/Caches. Apple documents that sandboxed Mac applications have their own containers under ~/Library/Containers. Their application support files, caches and temporary directories are kept within the sandbox at ~/Library/Containers/<app-bundle-id>/Data/Library/Caches. Do not assume that every application's cache will appear directly inside ~/Library/Caches. 3. System-wide caches: /Library/Caches This directory is in the computer-wide Library location rather than an individual user's Library. Apple describes /Library as a location where applications can store resources shared between users of the Mac. As a result, cache files stored here may serve applications or components beyond your personal account. For routine storage cleanup, leave this directory alone unless an application's developer provides specific instructions. 4. macOS system caches: /System/Library/Caches This location belongs to the system Library and is reserved for Apple. Modern macOS protects system content through mechanisms including System Integrity Protection and the Signed System Volume. These protections restrict modification of operating-system files. You should not attempt to clean this directory manually or disable macOS security protections to remove its contents.

Read more: Chromium Documentation: User Data Directory · Apple Developer: Accessing files from the macOS App Sandbox · Apple Developer: File System Protections · Apple Platform Security: Signed System Volume

What happens when you delete ~/Library/Caches?

The result depends on which application's cache you remove. When an application loses cache data, it may need to download or generate that information again. This can affect the next launch or the next time you access a particular feature. Here are some possible outcomes:

Will deleting cache files make my applications slower? Possibly, especially immediately after cleanup. Caches exist partly to avoid repeated downloads, calculations and file processing. After removing them, an application may need to perform that work again. For example, a browser may need to download website images and other resources that it previously stored locally. Once the required cache data is recreated, performance returns to its usual behaviour. Can deleting caches cause application errors? It can, particularly when files are removed while an application is actively using them. Apple warns that uncoordinated access to files by multiple processes can cause data loss, corruption or application crashes. Closing the application before removing its cache is a sensible precaution.

Read more: Apple Developer: Improving performance and stability when accessing the file system

Which Mac caches should you leave alone?

Although application caches are intended to be replaceable, some directories require more care than others. 1. Spotlight search index data Spotlight maintains search indexes so macOS can find files and other supported content. These indexes should not be confused with ordinary application cache folders. Deleting random folders with names such as com.apple.Spotlight or com.apple.metadata is not a recommended general cleanup method. If Spotlight is failing to find files, use Apple's supported reindexing procedure through System Settings > Spotlight > Spotlight Privacy. 2. Font-related system files Avoid manually deleting system font files or unfamiliar font-related folders while trying to free storage. macOS manages its installed fonts, and Apple notes that system fonts cannot be deactivated or removed through Font Book. Use Font Book's validation and restoration features instead. 3. iCloud Drive synchronization data Do not manually remove unfamiliar files or internal folders used by iCloud synchronization. Before changing anything related to iCloud Drive, check whether files have finished syncing in Finder by enabling the iCloud Status column in View Options. Pay attention to statuses such as Downloaded, In iCloud, Waiting to Upload, and Out of Space. Do not delete local data that is still waiting to upload. 4. System-level cache directories Avoid manually cleaning /System/Library/Caches, which is protected by macOS security mechanisms. Also avoid deleting everything inside /Library/Caches, as shared system components use this computer-wide location.

Read more: Apple Support: About Spotlight indexing and search results · Apple Support: Troubleshoot Font Book problems · Apple Support: Check your iCloud Drive file and folder status on Mac

Does deleting caches permanently free up Mac storage?

It frees the space currently occupied by the removed cache files, but the result may not last indefinitely. Applications create cache data as part of normal use. When you browse websites, open applications or access downloaded resources, some of that information may be cached again. However, there is no universal cache-rebuild schedule. One application might recreate a substantial cache quickly, while another might not need to regenerate much data at all. This is why clearing caches is better viewed as a way to reclaim temporary storage rather than a permanent solution to an ongoing storage problem. What should you clean for longer-term storage savings? If your Mac is regularly running out of space, look beyond caches. More useful places to investigate include: - Old device backups: Review backups stored by Finder before removing any you may still need. - Unused virtual machines: Virtual machine disk images can occupy substantial storage. - Old installers: Remove .dmg files and downloaded installers you no longer need. - Unneeded application data: Check leftover files from applications you have uninstalled. - Large personal files: Review old videos, archives, downloads and project exports. Apple's Storage settings also provide an overview of the categories taking up space. The System Data category can include caches, logs, virtual memory files, fonts, application support files and other runtime resources. Its size varies with the state of the Mac; it is not a direct measurement of ~/Library/Caches.

Read more: Apple Support: Free up storage space on Mac

How to find the largest cache folders on Mac

Before removing anything, find out which folders are using the most storage. You can do this with Finder or Terminal. Method 1: Find cache folder sizes using Finder 1. Open Finder. 2. Press Command + Shift + G. 3. Enter: ~/Library/Caches and press Return. 4. Switch to List View using Command + 2. 5. Press Command + J to open View Options. 6. Enable Calculate all sizes, if available. 7. Click the Size column to sort the folders. Finder may take some time to calculate folder sizes. Look for the largest application-specific folders first. Do not assume that a large folder is automatically safe to remove. Method 2: Compare cache sizes using Terminal You can use the built-in du command to list the 15 largest entries directly inside your user cache directory:

This command measures disk usage for each item directly inside ~/Library/Caches, reports sizes in kilobytes, sorts entries from largest to smallest, and displays the 15 largest entries without deleting or modifying files. To inspect one specific application cache, you can use:

Replace the path with the folder you want to inspect. These commands only report disk usage; they do not tell you whether a folder is safe to delete.

How to clear Mac caches safely: a step-by-step method

If you have identified a specific application cache that you no longer need, follow this process: Step 1: Identify the application Find out which application created the folder. Check its name, location and contents. If the folder name is unfamiliar, look up the application or developer before taking action. Step 2: Check whether it is a genuine cache A folder being located near other cache folders does not prove that all its contents are disposable. Look for an official application cleanup option or developer instructions. Do not remove files from Application Support, Containers or other Library locations simply because they look temporary. Step 3: Quit the application Close the application using Command + Q. Also consider whether it has a related background process or menu bar component that may still be using the cache. Do not force-quit unfamiliar system services just to perform cleanup. Step 4: Remove only the identified application cache Navigate to the exact cache folder you identified. Move that specific application cache folder, or its contents where the developer recommends, to Trash. Do not select every folder inside ~/Library/Caches and delete everything at once. Step 5: Test the application before emptying Trash Open the application again and check whether it behaves normally. Some resources may need to download or regenerate. If something important is missing or the application behaves unexpectedly, restore the removed folder from Trash. Only empty Trash after you are confident you no longer need the removed files. Avoid broad Terminal deletion commands: Do not run commands such as rm -rf ~/Library/Caches/*. This attempts to delete every item directly inside your user cache directory without checking whether files are in use.

Application Caches vs Application Support: what's the difference?

These folders are often confused because both live inside the Library directory. However, they have different purposes.

The key difference is that a properly implemented cache is designed to be replaceable. Application Support and container directories can hold persistent information that an application cannot simply recreate. For more detail, read our guides to Application Support on Mac and Group Containers on Mac.