If Finder is slow when opening or browsing a network folder on your Mac, first compare a small folder with the problem folder, then reconnect directly to the server and check whether the delay follows the folder, the network, or the server. This sequence helps narrow the cause without changing server settings or relying on undocumented commands.

1. Identify where the delay happens

Note what is slow: connecting to the server, opening one folder, scrolling through its contents, or opening files. Try the same share from another device or ask a colleague whether they see the same delay. Then test a smaller folder on the same share, if one is available. These comparisons are diagnostic clues: if only one folder is slow, its contents or the server’s work retrieving them may be involved; if all folders are slow for multiple users, the server or network is a stronger lead. These are inferences from the pattern, not proof of a specific cause.

For a large folder, switch Finder to List view: click the List view button in the toolbar, or choose View > as List. If you use Column or Gallery view, Finder shows a preview of the selected item; you can also close the Preview pane with View > Hide Preview. Temporarily hiding previews and testing again can show whether the browsing experience changes when Finder is not displaying that extra information. Apple documents Finder’s available views and preview controls, but does not say that changing views will fix network latency. Apple’s Finder view guide, Apple’s Preview pane guide.

2. Reconnect directly to the share

In Finder, choose Go > Connect to Server. If you have the address, enter it in the form smb://server-name/share-name for an SMB share, then click Connect and authenticate if prompted. Apple also supports an IP address in place of the server name. Ask the server owner or administrator for the correct address and share name if you do not have them; do not guess credentials or addresses. Apple’s connection instructions, server address formats.

If the direct connection is responsive while selecting the server through Finder’s Network view is slow, the discovery path may be contributing to the delay. If both routes are slow, that points toward something shared by both attempts, such as the connection, server, or share. Reconnecting tests the path; it does not repair an overloaded or misconfigured server.

3. Check your Mac’s network connection

Open Apple menu > System Settings > Network and check that the indicator for your active network connection is green. If you use Wi-Fi, compare the share from a stronger or more stable connection when practical, or test with another device on the same network. Apple says a Mac and a local Bonjour or Windows SMB server should be on the same local network or subnetwork for discovery; a server may also be unavailable or disconnected. Apple’s connection troubleshooting guide.

For Wi-Fi issues, hold Option while clicking the Wi-Fi menu and choose Open Wireless Diagnostics, then follow its prompts. Apple says the tool analyzes the Wi-Fi connection and reports detected issues; it does not change network settings. It is a useful check when Wi-Fi is suspect, but it is not a Finder or SMB performance test. Apple’s Wireless Diagnostics guide.

4. Use Activity Monitor as a clue, not a verdict

Open Activity Monitor and click Network while reproducing the delay. Its Network pane reports data received and sent, including throughput over time. If Finder feels stalled while there is little incoming data, that alone cannot tell you whether the cause is Wi-Fi, the server, or waiting for a response; Activity Monitor reports network activity, not the reason for a delay. If you see sustained transfers, another process may also be using the connection. Share the pattern and timing with your network administrator rather than treating one reading as a diagnosis. Apple’s Activity Monitor guide.

5. Know when the server administrator needs to step in

If the same folder remains slow after reconnecting, compare results with another user and note the exact share, folder, time, and actions that cause the pause. If multiple users see delays across the share, or a single folder consistently causes them, the server administrator can investigate server availability, permissions, storage, and network conditions. Apple’s guidance directs users to the owner or network administrator when a shared computer or server cannot be located or reached. Avoid changing server configuration or deleting files as a Finder troubleshooting step.

A useful handoff is specific: “Opening the Projects share by SMB is responsive, but entering Archive/2024 pauses for about 20 seconds; another user sees the same pause.” Include whether you were on Wi-Fi or Ethernet and whether a smaller folder behaved differently. That evidence helps distinguish a Mac-specific symptom from a share-wide problem without claiming the cause before it is checked.

Sources