How to Fix the Spinning Beach Ball on a Mac

The rainbow wheel — officially the spinning wait cursor, universally the beach ball — is not an error. It's macOS telling you that the app under your pointer hasn't responded to input for a couple of seconds, so the system is drawing the cursor on its behalf. That's a useful message: the app is waiting for something. Find out what, and the beach ball stops being mysterious.

First: is it one app or everything?

Move the pointer over a different app's window or over the Desktop. If the cursor turns back into an arrow, only that one app is stuck — the Mac is fine. If it spins everywhere, the problem is system-wide, and the frozen Mac guide applies instead.

Wait, or force quit?

Wait first. Genuinely — a beach ball that clears after fifteen seconds cost you fifteen seconds; a force quit costs you everything unsaved. Give it a minute or two, especially if the app was opening a large file, saving to a network drive, or syncing.

Force quit when it's been several minutes with no progress, or when you know what it was doing and it clearly isn't doing it any more. Press ⌘ + Option + Esc, select the app shown as (not responding), click Force Quit. The other routes work too.

Find out what it was waiting for

This is the part almost nobody uses, and it's the most useful thing on the page. macOS can take a stack sample of a stuck app and tell you where it's blocked.

1. Open Activity Monitor while the app is still beach-balling.
2. Select the app in the list — it will be in red, marked Not Responding.
3. Click the ⋮ (or gear) button in the toolbar and choose Sample Process.

You get a few seconds of stack traces. You don't need to read the code — scan for recognisable words. Anything mentioning read, write or a file path means it's blocked on disk. Anything with socket, CFNetwork or NSURL means it's waiting on the network. Anything naming a third-party framework points at a plug-in.

# Same thing from Terminal: sample a process for 5 seconds by name
sample Finder 5

# Find a process ID first if you prefer
pgrep -l Finder

The five causes, in order of how often they're it

1. It's waiting on the network

By far the most common cause, and the most misdiagnosed. An app that has a file open on a network share, a NAS, or a mounted server will beach-ball indefinitely when that share becomes unreachable — the Mac is fine, the app is politely waiting for a server that isn't answering. Finder is especially prone to this after a Wi-Fi drop with a share still mounted. Disconnect the share and it clears.

The same applies to cloud storage: opening a file that lives only in iCloud Drive means downloading it first. The Finder status icons tell you what's local, and a stalled sync is its own problem.

2. You're out of memory

Under red memory pressure, switching to an app that was swapped out means reading it back from disk, and everything beach-balls. If beach balls come in clusters — several apps, one after another — check the Memory tab first. How to read memory pressure and how to reduce it.

3. The startup disk is nearly full

Saving, caching and swapping all slow down when there's no room, and the app blocks while it waits. What to do when the disk is almost full.

4. The app is doing something genuinely large

Opening a 400 MB spreadsheet, rendering a long document, or importing thousands of photos is real work. If the sample shows it busy rather than blocked, the answer is patience — or a smaller file.

5. A plug-in or extension is hanging

Finder extensions, audio units, and browser extensions run inside their host app and can hang it. If one app beach-balls repeatedly, disable its plug-ins and add them back one at a time. For Finder specifically, check System Settings → General → Login Items & Extensions.

When it's the Finder

The Finder beach-balls more than anything else, usually because it's polling something that doesn't answer: a disconnected network share, a failing external drive, or a folder with tens of thousands of items. Force quitting the Finder is safe — select it in the Force Quit window and click Relaunch; macOS restarts it immediately and nothing is lost. More on quitting the Finder.

Stopping it coming back

• Keep 10–15% of the startup disk free.
• Unmount network shares before disconnecting from Wi-Fi, rather than after.
• Keep memory pressure green — usually a matter of browser tabs.
• Replace or stop using external drives that produce beach balls; a drive that's beginning to fail causes exactly this symptom before it fails properly.
• If one app is responsible every time, update it, then reset its preferences, then reinstall it — see the crash guide for the sequence.

The settings-level fixes above are one-click, reversible toggles in Mainspring — labelled in plain English, with an undo button for every one.

Common questions

What does the spinning beach ball mean on a Mac?

It means the app under your pointer has not responded to input for a couple of seconds, so macOS draws the wait cursor for it. It indicates the app is waiting or busy, not that the Mac has failed.

Should I wait or force quit when the beach ball appears?

Wait a minute or two first, particularly if the app was opening a large file or working over a network. Force quitting discards unsaved work, so it is worth spending a little time before resorting to it.

Why does Finder keep beach balling?

Usually because it is waiting on something that does not answer: a network share that has gone away, a failing external drive, or a folder with a very large number of items. Force quitting and relaunching the Finder is safe and loses no data.

Does the beach ball mean my Mac is broken?

No. It is a normal part of macOS and appears whenever an app blocks for a moment. It only indicates a problem when it happens frequently, in which case memory pressure, free disk space and network volumes are the places to look.

How do I find out what an app is waiting for?

Select the unresponsive app in Activity Monitor and choose Sample Process from the toolbar menu. The sample shows whether it is blocked on disk, on the network, or inside a third-party plug-in.