Clearing Finder Cache in macOS: A Complete Guide for Mac

Introduction

Finder Cache consists of temporary files that macOS stores to speed up access to frequently used folders and files. Over time, the cache can become too large or corrupted, leading to slowed Finder performance, display errors, or search issues. Clearing the cache is a simple and effective way to restore system performance without deleting your data. After completing this guide, Finder will operate faster and more stably.

Requirements / Preparation

Before you begin, ensure that:

• You have a computer with macOS (macOS 13 Ventura or newer is recommended).
• You are logged into an account with administrator privileges (required for clearing system cache, but not for user cache).
• It is recommended to back up important data via Time Machine or another method (although cache clearing is safe and does not affect user files).
• You are familiar with basic Terminal usage. If not, the instructions below describe each step in detail.

Step 1: Close All Finder Windows

Before clearing the cache, make sure all Finder windows are closed. This will prevent conflicts with active processes and ensure proper cache deletion. Simply close all windows, or right-click the Finder icon in the Dock and select "Quit".

Step 2: Open Terminal

Terminal is the built-in application for executing commands. Open it using one of these methods:

• Navigate to the Utilities folder in Finder or via the menu "Go" → "Utilities".
• Use Spotlight: press Cmd+Space, type "Terminal", and press Enter.
• Or find Terminal in Launchpad.

Step 3: Clear the User Cache

The Finder cache for the current user is stored in the folder ~/Library/Caches/com.apple.finder/. To delete its contents:

1. In the open Terminal, enter the following command and press Enter:

   rm -rf ~/Library/Caches/com.apple.finder/*
   

   
   This command deletes all files and folders inside the Finder cache. The symbol ~ represents your home folder.
2. If the system requests confirmation (for example, if rm -i is used), type y and press Enter. In standard macOS, the rm -rf command does not request confirmation, so be careful.

⚠️ Important: The rm -rf command permanently deletes files. Ensure you have entered the path correctly. An error could lead to data loss. The path ~/Library/Caches/com.apple.finder/ is safe to delete.

Step 4: (Optional) Clear the System Finder Cache

The system Finder cache is stored in protected folders and requires administrator privileges. This step is optional but may help in complex cases where user cache does not resolve the issue.

1. In Terminal, enter the command:

   sudo find /var/folders/ -name com.apple.finder -exec rm -rf {} \;
   

   
   This command searches for all folders named com.apple.finder within /var/folders/ and recursively deletes them.
2. Enter your administrator password when prompted. The password will not be displayed as you type — this is normal. Press Enter.

⚠️ Caution: Using sudo with rm -rf can be dangerous if the command is entered incorrectly. Ensure you have copied the command exactly. Do not interrupt the process until it completes.

Step 5: Restart Finder

After deleting the cache, you must restart Finder so it creates new empty cache files and applies the changes.

In Terminal, enter:

killall Finder

This command terminates the Finder process, and the system will automatically restart it. You will see the Finder icon in the Dock disappear and reappear.

Step 6: Verify the Result

After restarting Finder, open several folders and check:

• Have folder openings sped up?
• Have previous errors disappeared (e.g., "Cannot open folder" messages or icon distortions)?
• Are there any display anomalies?

You can also check memory usage: open "Activity Monitor" (in the Utilities folder), find the Finder process in the list, and look at the "Memory" value. If the cache was large, memory usage should decrease.

Potential Issues

Issue: "Operation not permitted" error when deleting system cache

Cause: Insufficient privileges or System Integrity Protection (SIP) blocks access. Solution: Ensure you are using sudo and have entered the correct password. If the problem persists, clearing the user cache (Step 3) is usually sufficient. SIP prevents modification of system files, so the system Finder cache may be protected.

Issue: Finder does not restart after killall Finder

Cause: The Finder process may be stuck or conflicting with other applications. Solution: Try restarting your computer. Alternatively, terminate the Finder process via Activity Monitor: find "Finder" in the list, click "Force Quit", then relaunch Finder via Spotlight.

Issue: Finder runs slower after cache clearing

Cause: The cache needs to be recreated automatically, which may take time when opening folders for the first time. Or not all caches were deleted. Solution: Give the system a few minutes while actively using Finder (open various folders). If the problem persists, check if you cleared the cache for all users (if multiple accounts exist on the computer). Also consider clearing other system caches.

Issue: Not all cache files were deleted or new errors appeared

Cause: Finder cache may be stored in multiple locations, or the command was executed incorrectly. Solution: Repeat Step 3 and Step 4, ensuring the paths are accurate. Check the folder ~/Library/Caches/com.apple.finder/ in Finder (via the menu "Go" → "Go to Folder" and enter ~/Library/Caches/com.apple.finder/) — it should be empty after clearing. If errors are related to specific folders, try resetting Finder preferences via defaults delete com.apple.finder (caution: this will reset all Finder settings).