All articles

Why the Finder Freezes on a Network Drive, and What to Do

· 6 min read

You open a folder on your NAS or an SMB share, and the Finder shows the spinning wheel. Sometimes for a second, sometimes for a minute, sometimes until you force it to quit. The short answer: the Finder is waiting for the server. When the server is slow, asleep or out of reach, the Finder window can stop responding until the answer arrives. Most of the time the fix is on the network or server side, and a few Finder settings make the wait shorter. This guide goes through the usual causes, what to check, how to get the Finder back, and how to work so that a slow server never blocks your Mac.

Why the Finder hangs on a network drive

A folder on your Mac answers in a fraction of a millisecond. A folder on a server answers only after a round trip over the network, and only if the server is ready. To show a folder, the Finder needs more than the list of names: icons, previews, sizes, labels. Each of those can mean another question to the server. When the answers are slow to come back, the window waits with them.

The most common situations:

  • The NAS disks are asleep. Many NAS models spin their drives down after a while. The first folder you open has to wait until they spin back up, which can take several seconds.
  • The Mac woke from sleep, or changed network. The share still appears in the sidebar, but the connection behind it is gone. The Finder waits for a server it can no longer reach, until the connection times out.
  • Wi-Fi is weak or busy. Large folders over a slow link mean many small requests, each one slowed down.
  • The folder is huge, or full of photos and videos. Icon previews are read from the files themselves, on the server.
  • The server is overloaded. A backup, an indexing job or a RAID check running on the NAS can make every request slow.
  • The server stopped answering altogether. It crashed, lost power, or the VPN dropped. This is the worst case: the Finder can hang until macOS gives up on the connection.

Getting the Finder back right now

  1. Wait a little. If the NAS was asleep, the wheel usually stops on its own once the drives are up.
  2. Disconnect the share. Click the eject button next to the share in the Finder sidebar. If macOS shows a message that the server connection was interrupted, choose to disconnect.
  3. Relaunch the Finder. Press ⌥⌘⎋, select Finder, then click Relaunch. Your files are not affected; the Finder simply restarts.
  4. Reconnect. In the Finder, choose Go › Connect to Server (⌘K) and type the address, for example smb://192.168.1.20/Photos. Using the server's IP address avoids waiting for the name to be found on the network.

If a share refuses to eject because something is still using it, see how to eject a disk that says it's in use.

Settings that make network folders faster

None of these is a guaranteed cure, but each removes work that the Finder would otherwise ask the server to do.

Stop .DS_Store files on network shares

The Finder writes a hidden .DS_Store file in folders to remember their view settings. Apple documents a setting that stops it from doing so on network volumes, to make SMB browsing faster. In Terminal:

defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE

Then log out and back in, or relaunch the Finder. The trade-off: the Finder no longer remembers the view options of each folder on the share.

Lighter views on the share

Open the share and press ⌘J for the view options. In icon view, turn off Show icon preview: the Finder then shows generic icons instead of reading every photo and video. In list view, leave Calculate all sizes off, so it does not walk through every subfolder. List view is generally lighter than icon or gallery view on a large folder.

SMB packet signing

On recent macOS versions, SMB connections are signed, which costs some speed. Apple has published a support article on turning off packet signing through the /etc/nsmb.conf file. Only consider it on a network you trust, and check Apple's current article for your version of macOS before changing anything: signing protects you against tampering on the network.

On the server

  • Check the NAS power settings: a longer delay before the disks sleep, or no sleep during your working hours.
  • Use a wired connection for large transfers when you can.
  • Prefer SMB; AFP is an old protocol that Apple has been phasing out.
  • Schedule heavy NAS tasks (backups, scans, media indexing) outside your working hours.

How Folia Files handles a slow or frozen server

Folia Files is a file manager for Mac, built so that a network drive never freezes the window. Everything that lives on a network disk is read in the background: folder contents, names, icons, whether a file exists. When a server stops answering, only the pane that shows it waits. The window, the other panes, the sidebar and your copies elsewhere carry on. We test this against servers that are deliberately frozen in the middle of browsing.

The Folia Files sidebar with its Servers section, next to two panes

A few details that matter in practice:

  • Servers in the sidebar. Your shares are listed in the Servers section. Click Add Server… to add a connection once: SMB, AFP, NFS, WebDAV or FTP. A mounted share is a disk for the whole Mac, so it also shows in the Finder and in every app's Open and Save dialogs. Passwords are kept in the macOS Keychain.
  • No wait in menus. The path bar's folder menus show The server isn't responding after half a second instead of hanging.
  • Reconnecting by itself (website edition). Right-click a network volume in the sidebar and choose Keep Connected (Reconnect Automatically). In Settings › Files and Network › Network, the option Reconnect automatically after sleep, a network change or a drop brings these shares back quietly; a share that stays out of reach is reported once.
  • Copies that survive a drop. With Resume a copy interrupted by the network or an unplugged disk automatically turned on (Settings › Files and Network), a copy cut by the network keeps what was already copied and continues where it stopped once the server is back.
  • No .DS_Store from Folia Files. It never writes .DS_Store files (its own view settings are kept elsewhere). The section Finder's .DS_Store Files in Settings › Files and Network has the option Don't create .DS_Store files on network volumes for the Finder, with a Relaunch Finder button, so you don't need Terminal.

Settings › Files and Network: the Finder's .DS_Store files and automatic reconnection

Website and Mac App Store editions

Network shares (SMB, AFP, NFS, WebDAV, FTP) work in both editions, and both read them in the background. The automatic reconnection settings are in the website edition only. In the Mac App Store edition, the .DS_Store option for the Finder needs Folia Files Companion, a small free app, because Apple's sandbox does not let an app change another app's preferences. For SFTP and S3, see how to connect to SFTP and S3 without macFUSE.

A quick checklist

  • The wheel appears only on the first folder after a pause: the NAS disks were asleep. Lengthen their sleep delay.
  • It appears after the Mac wakes up: the connection is stale. Disconnect and reconnect, or let automatic reconnection do it.
  • It appears in big photo folders: turn off icon previews on the share, or use list view.
  • It never stops: relaunch the Finder with ⌥⌘⎋, then check that the server is on and reachable.

A slow server is often a network problem rather than a Mac problem. But your file manager doesn't have to stop with it.