When Finder is not responding on a Mac, what to try in which order

The spinning pointer appears over a Finder window and stays there. Clicking the Dock icon does nothing. The desktop icons will not drag. Every other app still works, but anything that touches files is stuck, which on a Mac means most of the day's work is stuck with it.

Most advice for this situation is a list of ten fixes in no particular order. The order matters more than the list. Some steps cost nothing and rule out whole categories of cause. Others take twenty minutes and only make sense after the cheap ones have failed. What follows is the sequence, with the reason for each step, so that whatever happens, the next move is clear.

First, decide whether Finder is frozen or just waiting

A Finder that is not responding is often not broken at all. It is waiting for something else to answer. Finder asks the disk, the network, and any cloud storage provider for information about every item it displays. If one of those sources is slow, Finder waits, and while it waits it shows the spinning pointer.

Three questions narrow this down in under a minute.

Did the freeze start when a specific folder was opened? A folder on a network share, an external drive that is spinning up, or a cloud folder whose files are not downloaded yet can all stall Finder for a long time. If the freeze began the moment a particular location was clicked, the location is the suspect, not Finder.

Is a drive or server involved? A network volume that dropped off Wi-Fi, a sleeping NAS, or a USB drive with a failing cable produces exactly this symptom. Finder keeps trying to reach it.

Is the Mac under heavy load? Open Activity Monitor from Spotlight with Command and the space bar. If a backup, a Spotlight reindex, or a large copy is running, Finder may be slow rather than stuck.

If any of these apply, give it two minutes. Waiting sounds like non-advice, but a stalled network request often times out on its own and Finder recovers with no data lost. Forcing it to quit mid-copy is a worse outcome than a short wait.

If nothing points to an outside cause, or two minutes pass with no change, move on.

Relaunch Finder from the Force Quit window

The first real fix is the one Apple documents directly. Press Option, Command and Esc together, or choose Force Quit from the Apple menu. A window lists running apps. Finder behaves differently from the others in this list:

The Finder is always open, but if it stops responding, you can force it to quit and reopen: Select Finder in the Force Quit window, then click Relaunch. Source: support.apple.com

The button says Relaunch rather than Force Quit because Finder cannot stay closed. The system starts it again immediately. Open windows close, and Finder comes back with a fresh process.

This step solves a large share of cases, because most freezes are a single stuck request inside one Finder process. A new process does not inherit that request.

Two things to know before clicking. First, a copy or move that is in progress will be interrupted. The source files stay where they were, but the destination may hold a partial copy that needs checking. Second, if the freeze was caused by an unreachable network volume, Finder may freeze again the moment it tries to show that volume in the sidebar. If it does, eject or disconnect the volume before relaunching again.

A second route to the same result: hold Option, then right-click the Finder icon in the Dock. Relaunch appears at the bottom of the menu. This is useful when the keyboard shortcut does not open the Force Quit window quickly.

Use Terminal when the menus do not respond

Sometimes the Force Quit window opens but the Relaunch button has no effect, or the Dock itself is sluggish. Terminal gives a more direct route. Open it from Spotlight or from the Utilities folder inside Applications, then type:

killall Finder

This sends a quit signal to every Finder process. The system relaunches Finder on its own a moment later, so there is no need to start it by hand.

If Finder is still unresponsive after that, check whether it actually restarted:

ps aux | grep -i finder

A line containing the Finder application path with a recent start time means a new process is running. If the process is present but the windows still spin, the cause is almost certainly outside Finder: a volume, a cloud provider, or an extension. That points to the next section rather than to more relaunching.

Terminal is also the fallback when the Dock has frozen alongside Finder. The Dock can be restarted the same way with killall Dock, and it relaunches automatically as well.

Rule out volumes, cloud folders and extensions

If Finder relaunches and freezes again within seconds, something it loads at startup is causing it. The usual suspects fall into three groups.

Suspect How it shows up What to try
Network volume Freeze when the sidebar loads or a share is opened Eject the volume, or turn off Wi-Fi briefly, then relaunch
External drive Freeze begins when the drive is connected Unplug it, relaunch, then run First Aid in Disk Utility
Cloud storage provider Freeze in a synced folder or on the whole sidebar Quit the provider app, relaunch Finder, test again
Finder extension Freeze or crash with any window open Turn extensions off one at a time

Finder extensions are the least obvious item on that list. Cloud storage apps, version control tools and file tagging utilities add badges and menu items to Finder through extensions, and a misbehaving one can stall every window. Apple's documentation places the switches in System Settings, under General, then Login Items & Extensions. Extensions installed by other developers are listed there, and Finder extensions have a separate checkbox.

The fastest test is to switch off every third-party Finder extension, relaunch Finder, and see if the freeze stops. If it does, turn them back on one at a time until the freeze returns. The last one enabled is the cause, and its developer's update page is the next stop.

Cloud folders deserve one more check. When a storage provider keeps only placeholders on the Mac and downloads files on demand, opening a large folder can make Finder request hundreds of downloads at once. The window stays blank or spinning until the provider catches up. Quitting the provider app, relaunching Finder, and opening the same folder again shows whether the provider or Finder is the slow party. If the folder opens instantly with the provider closed, the fix belongs on the provider side: mark the folder to stay downloaded, or split it into smaller folders so that fewer items are requested at once.

Restart, then try safe mode

A full restart is the next step. It clears every cached connection, remounts every volume, and reloads every extension. Apple's own troubleshooting for frozen apps lists it second, right after force quitting. If Finder is so stuck that the Restart command in the Apple menu does nothing, holding the power button for up to 10 seconds turns the Mac off, as Apple describes on the same force quit page.

If the problem returns after a restart, safe mode separates macOS from everything added on top of it. Apple describes what safe mode does:

Prevents certain software from loading as your Mac starts up. This includes login items and extensions that aren't required by macOS, and fonts that weren't installed by macOS. Source: support.apple.com

On a Mac with Apple silicon, shut down, then press and hold the power button until startup options appear. Select the startup disk, hold Shift, and choose Continue in Safe Mode. On an Intel Mac, hold Shift immediately after pressing the power button.

The result is a clean verdict. If Finder works in safe mode, the cause is something that loads normally but not in safe mode: a login item, an extension, a font. If Finder still freezes in safe mode, the cause is closer to macOS itself or to the disk.

Narrow down the rest with a second user account

If safe mode did not settle it, one more comparison helps. Create a new user account in System Settings under Users & Groups, log in to it, and use Finder there for a few minutes.

A clean account has default Finder preferences, an empty sidebar, no custom view settings, and no login items. If Finder is fine in the new account, the problem lives in the original account's files. The Finder preference file and the sidebar list are the two most likely culprits, and resetting them is a contained job that does not touch documents.

If Finder freezes in the new account too, the cause is system wide. At that point, run First Aid on the startup disk in Disk Utility, install any pending macOS updates, and check free disk space. A startup disk with only a few gigabytes free makes everything slow, and Finder is often the first place it shows.

Keep the test account until the problem is solved. It is a useful control for comparing behavior, and deleting it afterwards takes a few seconds.

Why this keeps happening to some people

A Mac that needs Finder relaunched once a month is normal. A Mac that needs it daily usually has a structural cause. The pattern that recurs most often is a working day spread across many windows: Finder for files, Terminal for commands, an editor, a browser, and increasingly an AI assistant in yet another window. Every one of those windows asks Finder or the file system for something, and a folder that is open in five places is a folder that can stall five ways.

Two habits reduce the load without new software. Keep network shares unmounted when they are not needed, so Finder does not poll them. And close Finder windows that point at slow locations instead of leaving them open in the background all day.

Some people go further and move the file work into a single window that shows folders, a terminal and an AI assistant side by side, so that only one app is reading a given folder at a time. A file manager with a built-in terminal takes Finder out of the hot path for the heaviest tasks while leaving it in place for everything else. The features page for that kind of tool describes the layout, and the comparison with other file managers sets out what each approach covers.

What to change first

Start with the two-minute wait and the Relaunch button, because between them they settle most freezes at no cost. If Finder freezes again right after relaunching, turn off network volumes and third-party Finder extensions before anything else, then use safe mode to get a clear answer. If the freezes follow a day of juggling many windows over the same folders, Atriens puts folders, a terminal and AI in one window so that fewer apps compete for them.

Frequently asked questions

Will relaunching Finder delete any of my files?

No. Relaunching Finder only restarts the app that displays files. Documents, folders and their contents are untouched. The one exception is a copy or move that was in progress, which is interrupted and may leave a partial copy at the destination that should be checked.

Why is there no Quit option for Finder in the menu?

Finder is the app that draws the desktop and handles file windows, so macOS keeps it running at all times. That is why the Force Quit window offers Relaunch for Finder rather than Force Quit. Even when Finder is stopped from Terminal, the system starts it again within seconds.

Finder freezes every time I open one particular folder. What does that mean?

The folder is almost certainly the cause. It may sit on a network share or external drive that responds slowly, it may be a cloud folder whose files are not downloaded, or it may contain a file whose preview Finder cannot generate. Moving the contents into smaller subfolders, or opening the folder in list view instead of icon view, often helps.

Is it safe to hold the power button if nothing responds?

It is the documented last resort. Apple describes holding the power button for up to 10 seconds to turn off a Mac that will not restart. Unsaved changes in open apps will be lost, so try the Force Quit window and Terminal first. After the Mac starts again, run First Aid in Disk Utility if the freezes continue.

Back to all posts