Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


When you find Finder not responding on Mac, protect any copy or move that is still running, then press Option+Command+Esc, select Finder, and click Relaunch; if that fails, restart the Mac from the Apple menu.[1] Before you relaunch, compare a new Finder window and a known local folder with the location that triggers the freeze, because one cloud folder, network share, external drive, preview, or unfinished copy can hold the window while Finder itself is healthy.
Check for active file operations before you relaunch Finder or restart the Mac. Relaunching can close windows and interrupt a copy, move, rename, or archive operation, so preserve the evidence and the data first.
Key Takeaways
- Compare Finder itself with one local and one problem location.
- Wait for or protect active file operations before relaunching.
- Use Finder's Relaunch action before a forced shutdown.
- Isolate external devices, cloud locations, files, and extensions.
- Back up data before Disk Utility First Aid or other recovery work.
If several apps or system features are unresponsive, use the device and app troubleshooting guide to establish whether the failure is Finder-specific or affects the whole Mac.
Try opening a new Finder window, then open a small test folder with only a few ordinary files that you have confirmed is on the Mac's startup disk, is not cloud-backed or network-redirected, and is not on an external drive. Compare it with the original location without changing views, disconnecting devices, or relaunching yet.
| Observation | Stronger branch |
|---|---|
| A new local window works | One folder, device, share, preview, or sidebar item |
| Finder freezes on Home or Recents only | Recent item, search, cloud, or unavailable location |
| Every Finder window freezes | Finder session, account, update, extension, or storage |
| One external volume freezes | Drive, cable, adapter, file system, or media condition |
| One network share freezes | Server, network, credentials, or permission |
| Only typed search is wrong | Spotlight or Finder search rather than the whole window |
If the window opens and browsing works but search results are wrong or absent, use the Spotlight search troubleshooting guide. If a third-party app is the only process that freezes, use the app launch and response guide.
Open the same problem folder through a direct path or a different trusted sidebar location if possible. If only a favorite or recent-item entry hangs, the target may be unavailable even though Finder is healthy. Remove only a known stale sidebar item; do not clear every recent item or delete the underlying folder.
Use a neutral test folder with non-sensitive files when you need to reproduce the problem for support. That gives useful evidence without exposing private filenames or locations.
A Finder window can show a spinning pointer or Not Responding while it waits for a slow drive, reads metadata, calculates folder size, generates previews, or completes a copy. Look for a progress window and check whether the destination is changing before you relaunch.
If a trusted copy or move is still progressing and the device is stable, allow it to finish. Do not unplug an external drive, disconnect a network share, or start the same move again into the same destination.
Record the source, destination, current item, elapsed time, and whether progress changes. If the operation contains irreplaceable files, confirm another backup before retrying or forcing Finder to close.
Apple explains that quitting an app normally lets it save changes, while force quitting can lose unsaved changes. Finder is always open, but if it stops responding Apple provides a Relaunch action in the Force Quit window.[1] Treat that warning as applying to the work Finder is coordinating, not only to text documents.
After an interrupted copy, compare the source and destination before deleting anything. A destination may contain a partial set even if Finder did not show a completion message.
First try closing the affected window normally if it responds. Save work in other apps, finish or pause file operations, and note which location caused the problem.
Press Option+Command+Esc or choose Apple menu > Force Quit. Select Finder and choose Relaunch. Apple specifically documents this Finder action, and recommends restarting the Mac if an unresponsive app cannot be forced to quit.[1]
The desktop and Finder windows may disappear briefly. When Finder returns, repeat the exact same new-window, local-folder, and problem-location tests. Do not reconnect a drive or change the view at the same time.
If Relaunch does not restore Finder, restart the Mac normally through the Apple menu after saving work. Use a forced power-off only when normal restart controls cannot respond. Holding the power button can interrupt storage writes and lose unsaved work.
Record whether the fix lasts. A failure that returns only after sleep, connecting one device, opening one folder, or enabling one extension is more actionable than a one-time freeze.
Apple notes that Finder is always open, so a Finder that won't open is usually running but not responding.[1] Click the Finder icon in the Dock first. If no window appears or the icon does nothing, treat it as an unresponsive Finder rather than reinstalling anything.
To restart Finder without the Force Quit window, hold Option, Control-click the Finder icon in the Dock, and choose Relaunch. It is the same relaunch described above, so the warning about active file operations still applies. If neither route brings Finder back, restart the Mac normally.
Apple's general Mac guidance recommends comparing another file, checking software updates, disconnecting recently connected peripherals, and removing incompatible third-party plug-ins or enhancements when an app freezes or quits unexpectedly.[2] Those comparisons also help with Finder because it opens files, previews metadata, and integrates with devices and extensions.
If one folder triggers the freeze, test List view and close the Preview pane only after the window is responsive. Large media, archives, damaged files, or metadata can make thumbnails and previews slow. Restore the original view if the comparison changes nothing.
If right-click or a toolbar action triggers the freeze, note the file type and recently installed trusted software. Remove a known Finder extension only through its app's supported settings or uninstaller. Do not delete system extensions or Library files from a random online list.
Disconnect a recently added peripheral only after its writes have stopped and macOS allows safe ejection. If an external drive does not appear at all, follow the external-drive detection guide instead of repeatedly relaunching Finder.
For cloud-backed folders, confirm the provider's web or server copy before removing local files, turning off synchronization, or unlinking an account. Use the cloud storage sync guide to preserve both sides.
Install supported macOS updates and updates for trusted software, then restart if required. Keep the Mac connected to power during a system update and do not interrupt it because Finder has not immediately returned.
If the problem began after a recent app or macOS update, record the versions and any Finder extension involved. A third-party enhancement may no longer be compatible, as Apple's guidance notes.[2] Contact its developer if the supported uninstall or disable path resolves the symptom.
Compare another authorized Mac user account only if one already exists or support requests it. If Finder works there, preserve the affected account and report an account-specific symptom. Do not rename the home folder, copy hidden preference databases, or delete the account to force a rebuild.
On a managed Mac, sidebar items, network shares, cloud providers, security extensions, and access permissions may be controlled by the organization. Do not remove device management, security software, certificates, or profiles. Capture the exact policy or error and send it to IT.
If the whole Mac is slow, several apps freeze, or storage warnings appear, Finder may only be the most visible symptom. Stop treating it as a single-window issue and move to system or storage support.
First Aid is not a routine first step for one stale Finder window. Consider it only when evidence points toward a storage structure problem: repeated file corruption, several apps quitting around the same volume, a device that behaves incorrectly, or startup trouble.
Apple states that Disk Utility can check and repair some formatting and directory-structure errors, but it cannot detect or repair every disk problem. Apple also says to back up and replace a disk if Disk Utility reports that it is about to fail.[3]
Create or confirm a current backup before running First Aid. For the startup disk, Apple's procedure may require macOS Recovery and checking volumes, containers, and the device in order. Follow the current Apple instructions for the exact volume rather than improvising commands.
If First Aid cannot repair the disk, stop repeated attempts that write to a potentially failing device. Back up as much as possible and seek service. Reformatting or reinstalling macOS is a separate recovery project with clear data-loss consequences, not a Finder refresh.
Do not use a third-party disk repair or cleaner merely because it promises to fix Finder. Granting such a tool full disk access can increase both data and privacy risk.
Prepare a short reproducible record:
Avoid sending full paths, filenames, server names, account identifiers, or screenshots of private documents. Replace them with neutral labels unless the support owner specifically needs the detail.
Stop local troubleshooting if a disk disconnects, files become unreadable, First Aid reports impending failure, or the only copy of important data is at risk. Preserve data and let Apple, the storage vendor, or the organization choose the next action.
Open a new Finder window and a small known local folder. If those work but one location freezes, investigate that location, device, preview, or integration rather than the entire Finder process.
First check whether the copy is still progressing. Relaunching can interrupt it and leave a partial destination, so protect irreplaceable data and record the current state before acting.
It does not intentionally delete files, but it can interrupt active copy, move, rename, or archive operations. Verify both source and destination afterward before removing anything.
The drive, cable, adapter, file system, power, or media condition may be the trigger. Eject safely when possible, preserve a backup, and use the drive-specific troubleshooting path.
Yes. A placeholder, sync client, account, service, or unavailable network can delay Finder. Confirm the server copy before deleting local files or unlinking the account.
A file, metadata reader, Quick Look component, or third-party extension may be involved. Test a simple local file and remove only known software through its supported controls.
Yes, after saving work and protecting file operations. Use the normal Apple menu restart; reserve a forced power-off for a Mac that cannot respond to normal controls.
No. Use it when evidence suggests a storage problem and only after confirming a backup. One location-specific or temporary Finder freeze usually deserves narrower checks first.
Sources checked 4 October 2026.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





