What do I do about the spinning beachball on a Mac?
The multicoloured wheel means one application has stopped answering, not that the Mac has crashed. How to get control back without losing work, and how to find out which of four causes is behind it.
- Difficulty
- beginner
- Time
- 25 min
- Read
- 5 min
Short answer
The beachball belongs to one application, not to the Mac. Move the pointer to the menu bar or click another window — if the pointer changes back to an arrow, everything else is alive and you only need to deal with the stuck app. Wait a minute before force-quitting, because many beachballs resolve themselves and force-quitting loses unsaved work.
macOS shows the spinning wait cursor when the application under the pointer has not responded to events for a couple of seconds. It is a per-application signal, which is the most useful thing to know about it: the rest of the machine is usually running perfectly, and the panic response of holding the power button throws away work in every other open application for no reason. What causes an application to stop answering divides into four families — it is genuinely busy, it is waiting on something slow such as a network drive, it has run out of memory, or it has deadlocked — and Activity Monitor distinguishes them in under a minute.
Step by step
- Establish whether it is one app or the whole machine.Move the pointer over the desktop or another window. An arrow cursor there means only the app under the beachball is stuck. A beachball everywhere, including the menu bar, means the system is struggling, which is a different and rarer problem.
- Wait sixty seconds before doing anything.A great many beachballs are an application finishing something large — a save, an import, a search, a spreadsheet recalculation. Waiting costs a minute; force-quitting costs whatever was unsaved. This is the same discipline as the catalogue's guide on a frozen computer.
- Open Activity Monitor and look at what the app is doing.Command-Space, type Activity Monitor. An application shown in red as Not Responding, using almost no processor time, is deadlocked or waiting on something. One using a great deal of processor is working, and may well finish. Those two lead to different decisions.
- Check the memory pressure graph while you are there.In the Memory tab, the pressure graph is the number that matters — green is fine at any percentage, yellow means swapping, red means the machine is out of memory and the whole system will beachball. If it is red, closing browser tabs and large applications is the fix.
- Suspect the network if the app touches files elsewhere.An application waiting on a disconnected network share, an unmounted external drive, or a cloud folder that is downloading will beachball indefinitely and use no processor at all. Disconnecting the share or turning wifi off briefly often releases it immediately, which is a strong diagnostic in itself.
- Force quit properly when you decide to.Command-Option-Escape opens the force quit window; Activity Monitor's stop button does the same with more information. Force-quitting one application does not affect the others and does not require a restart.
- Look for a pattern rather than treating each one.Always the same application, always when opening a particular file, always after the machine has been on for days, always when the external drive is connected. The pattern names the cause far more reliably than any individual incident.
- Treat system-wide beachballing as a resource or disk problem.If the menu bar itself beachballs, look at free disk space first — macOS needs working room and behaves very badly without it — then memory pressure, then disk health. Persistent system-wide freezing on an older Mac with a mechanical drive is often the drive.
Common mistakes
- Holding the power button at the first beachball — It hard-powers the whole machine, losing unsaved work in every application, when in almost every case the rest of the Mac was working and only one application needed force-quitting.
- Force-quitting an application that is saving a large file — That is exactly when you get a corrupted file. High processor use in Activity Monitor means it is working, and waiting is the right choice.
- Installing a maintenance utility to fix beachballing — The causes are memory, disk space, a stalled network location or one badly behaved app. None of those are fixed by clearing caches, and Activity Monitor tells you which you have for free.
If it doesn't work
One app beachballs, everything else is fine
Cause: That app is busy, stuck or waiting — Fix: Wait a minute, then check it in Activity Monitor before force-quitting. Zero processor use means waiting; high use means working.
Beachball whenever you open or save to a particular location
Cause: A network share or external drive that is slow or gone — Fix: Disconnect the share and see whether it releases. Applications hold references to locations that have vanished and wait for them for a long time.
Whole machine beachballs, memory pressure is red
Cause: Out of memory — Fix: Close browser tabs and large applications. If it happens routinely on everyday work, the Mac needs more memory — on Apple silicon that is not upgradable, which is a buying decision rather than a repair.
Started after a macOS upgrade
Cause: Background reindexing, or an incompatible app — Fix: Spotlight reindexes the whole drive after a major upgrade and can take a day, during which everything is slower. If it persists beyond that, look for an application or extension that has not been updated.
Beachballs on wake from sleep, then settles
Cause: Storage or network reconnecting — Fix: Normal for a few seconds. If it lasts minutes, an external drive or a mounted share reconnecting is the usual cause.
Free space is very low and everything beachballs
Cause: macOS has no working room — Fix: Free space urgently. This is one of the few situations where the Mac behaves genuinely badly, and the catalogue's guide on Mac System Data covers where the space has gone.
Questions people ask
Why is it called a beachball?
Apple's name for it is the spinning wait cursor; everyone else calls it the beachball or the pinwheel. It appears when an application has not processed events for about two seconds, and it is drawn by the window server rather than by the application itself — which is why it appears even when the app is completely wedged.
Does a beachball mean my Mac is old or failing?
Not on its own. Occasional beachballs are normal on any Mac when something takes longer than expected. What indicates a real problem is frequency, whether it is system-wide, and whether it correlates with low free space, red memory pressure or a specific drive.
Should I restart my Mac regularly to avoid it?
Macs are designed to run for weeks and mostly do so happily. If beachballing reliably appears after several days of uptime, that points at an application leaking memory rather than at macOS, and Activity Monitor sorted by memory will name it after a few days.
Is there a Windows equivalent?
Yes — the window greying out and the title bar showing "Not Responding" is the same signal for the same reason. The catalogue's guide on a computer that freezes covers both, and the discipline of waiting before force-quitting is identical.