Finder crashing the instant you open it, every single time, is more disruptive than almost any other Mac problem because you need Finder to do almost anything else. The good news is that this symptom has a small, well-understood list of causes, and working through them in order usually finds it quickly.

The first 30 seconds: relaunch cleanly

Before anything else, try a clean relaunch rather than repeatedly clicking the Dock icon:

  1. Hold Option and right-click the Finder icon in the Dock.
  2. Choose Relaunch.

If that doesn't hold, open Terminal (which runs independently of Finder, so it stays available even while Finder is crash-looping) and run:

killall Finder

macOS restarts Finder automatically after this, since it's a core system process rather than a normal app. If it crashes again within a second or two of restarting, move to the steps below rather than repeating this.

Step 1: rule out a stuck network or external drive

This is the single most common cause of Finder crashing or freezing specifically on launch: Finder tries to reconnect to every drive and network share it remembers, and one that's gone missing, asleep, or unresponsive can hang or crash the whole process while it waits.

  1. Disconnect any external drives physically.
  2. If you connect to network shares (SMB, AFP, or similar), disconnect from your network temporarily, or check System Settings for any saved network locations with a grayed-out or disconnected icon.
  3. Try relaunching Finder again with everything disconnected.

If Finder behaves normally with external and network drives disconnected, reconnect them one at a time to identify which one is causing it, rather than assuming all of them are safe to leave connected going forward.

Step 2: check available storage

Finder, along with much of macOS, becomes unstable when a drive is nearly full. If your startup disk has very little free space, that alone can cause exactly this symptom.

  1. If you can get Finder open even briefly, check available space: Apple menu > About This Mac > Storage.
  2. If Finder won't open long enough for that, check from Terminal instead: 
    df -h /
  3. Aim to keep at least 15 to 20 percent of your startup disk free. See our System Data guide if a large, unclear category is eating your space.

Step 3: reset Finder

A corrupted preferences file is the most common software-level cause of persistent Finder crashes. Resetting it is safe; you'll lose some Finder window customizations like sidebar order and view settings, but no files.

  1. Open Terminal.
  2. Back up the current preferences file first, in case this doesn't fix it and you want to compare: 
    cp ~/Library/Preferences/com.apple.finder.plist ~/Desktop/finder-backup.plist
  3. Delete the preferences file: 
    rm ~/Library/Preferences/com.apple.finder.plist
  4. Relaunch Finder: 
    killall Finder

macOS rebuilds a fresh preferences file automatically. If Finder opens normally now, the old file was corrupted, and you're done; delete the backup from your Desktop once you're confident it's resolved.

Step 4: a corrupted Finder window state

If resetting preferences alone doesn't help, Finder's saved window and tab state can also be the culprit, separately from the main preferences file:

rm -rf ~/Library/Saved\ Application\ State/com.apple.finder.savedState
killall Finder

This clears any windows, tabs, and their layout that Finder was trying to restore on launch. If a specific saved window, particularly one pointing at a broken network location or a corrupted folder, was the trigger, this resolves it.

Step 5: test in a new user account

This step isolates whether the problem is specific to your user account or something broader on the Mac:

  1. System Settings > Users & Groups > Add Account, create a new standard account.
  2. Log into the new account and open Finder.
  3. If Finder works fine there, the cause is something specific to your main account's settings, Login Items, or Launch Agents, not the Mac or macOS installation itself.

If it's account-specific, check System Settings > General > Login Items & Extensions for anything unfamiliar that might be interfering with Finder on launch, particularly third-party Finder extensions or sync tools.

Step 6: check the actual crash report

For a precise diagnosis rather than trial and error, macOS keeps a log of exactly why Finder crashed each time:

  1. Open Console (Applications > Utilities > Console).
  2. In the sidebar, select Crash Reports under your Mac's name.
  3. Look for the most recent entry starting with "Finder."
  4. Near the top, look for a line mentioning a specific framework, extension, or third-party component by name. That name is usually the actual cause, more precise than anything a general guide can guess.

If the crash report names a specific third-party Finder extension or sync client, that app's own support page or a reinstall of that specific app is the most direct fix from here.

If it is still happening after all of this

  • Check for a macOS update. See which update your Mac needs; a point release can fix an underlying bug that none of the steps above would catch.
  • Rule out malware if the crash started suddenly and coincides with other odd behavior. See our guide to checking a Mac for malware.
  • As a last resort, a clean reinstall of macOS, after backing up, resolves persistent system-level corruption that nothing short of it will touch. This should be the final step, not an early one.

The short version

  • Disconnect external and network drives first; a stuck or missing one is the most common trigger for Finder crashing on launch.
  • Check free disk space; a nearly full startup drive causes exactly this symptom.
  • Reset Finder's preferences and saved window state with Terminal, both of which macOS rebuilds automatically.
  • Test in a new user account to confirm whether the cause is account-specific.
  • Console's Crash Reports will usually name the actual culprit directly if the steps above don't resolve it.