Every Mac user knows the feeling: you click something and your cursor turns into a small, rainbow-coloured spinning circle. You wait. You wait a bit longer. Nothing happens. That's the spinning beach ball, and if it's happening more than it used to, something has changed about how much your Mac has to deal with. Let's walk through what it is, why it shows up, and how to make it go away.
Quick note on a related problem: this post is specifically about the beach ball cursor that appears during app hangs. If your Mac is completely unresponsive, not just one app but the whole system, that's a full freeze, which is covered separately in why is my Mac freezing. The two problems share some causes but need different responses.
What is the beach ball, exactly?
Apple officially calls it the Spinning Wait Cursor or the Spinning Pinwheel. It's the multi-coloured circular cursor that replaces your normal pointer whenever an app is too busy to respond to input. Think of it as macOS waving a flag on the app's behalf: "hold on, I'm not ignoring you, I'm just occupied."
A brief beach ball is completely normal. Loading a large Photoshop file, opening a complex spreadsheet, launching a heavy app for the first time, these operations take a moment and the beach ball will appear. That's fine. The cursor clears in a second or two and you carry on.
It becomes a problem when:
- It appears regularly during light tasks, like switching browser tabs or opening a new document.
- It lasts longer than 5 to 10 seconds at a time.
- The same app consistently triggers it, suggesting something is wrong with that specific app rather than a one-off hiccup.
If any of those describe your situation, keep reading.
Why is it happening more often than it used to?
The beach ball appears when an app or the operating system can't respond fast enough. That usually comes down to one of these causes:
Low memory (RAM). RAM, short for Random Access Memory, is the temporary workspace your Mac uses to hold everything currently running: apps, browser tabs, documents, background services. It's shared across everything. When RAM gets close to full, macOS starts writing overflow data to your storage disk in a process called swap. That's much slower than actual RAM, and while it's happening, apps stall and beach balls appear. The more tabs and apps you have open, the more likely this is. This is probably the single most common cause for most users. See what memory pressure means on Mac for the full picture.
One app hogging the CPU. Your Mac's processor (CPU) is also shared. If one app is running an intensive operation, like compressing a video, scanning for viruses, or running heavy code in a browser tab, it can consume most of the processor's capacity, leaving little for anything else. The apps you're trying to use get starved and the beach ball appears.
A slow or nearly-full disk. macOS uses your storage as overflow space when RAM runs low. If that disk is nearly full, or if it's reading and writing a lot of data at once, it slows down, and anything that depends on it slows with it. A good rule of thumb: keep at least 10 to 15% of your storage free. You can check via Apple menu › About This Mac › More Info › Storage.
An app waiting on a network or sync operation. Cloud storage services, email clients, and backup tools regularly read and write files in the background. If one of them is in the middle of a large sync and you try to open or save a file in the same location, the foreground app stalls until the background operation clears. This is less obvious because the app looks idle to you even though it isn't.
A memory leak in a specific app. A memory leak is when an app gradually consumes more and more RAM over time without releasing it, even when it's not doing anything obvious. Apps with known leaks include some versions of Safari, certain versions of Chrome extensions, and various third-party utilities. If a specific app always seems to trigger beach balls after it's been open for a while, a memory leak is a plausible explanation. Quitting and relaunching it usually helps temporarily.
How to make it stop right now
When the beach ball appears and won't clear, here's what to do:
Wait 5 to 10 seconds first. Some operations, like autosave, cloud sync, or a background index rebuild, resolve on their own. If the cursor clears and everything feels normal again, it was a transient operation and nothing to worry about.
If one specific app is hung: open Activity Monitor to confirm. Press Command-Space, type "Activity Monitor", and press Return. The unresponsive app will be listed in red, with "Not Responding" next to its name. If you see that, press Command-Option-Esc to open the Force Quit window, select the app, and click Force Quit. You'll lose any unsaved work in that app, but nothing else is affected. After force-quitting, watch the Memory Pressure graph in Activity Monitor (bottom of the Memory tab). If it was red, it should begin to settle. See how to use Activity Monitor on Mac for a full walkthrough of what to look for.
If the whole system feels sluggish and beach balls are coming from multiple apps: memory pressure is probably high across the board. Quit every app you don't immediately need, close browser tabs you're not reading, and wait a minute. macOS will reclaim memory and things should improve. If they don't, a restart is the fastest reset.
If storage is nearly full: empty your Trash, delete old downloads, and move files you don't need daily to an external drive or cloud storage. Give macOS room to breathe.
How to stop it happening again
Fixing the current beach ball is step one. Preventing the next one requires a small change in habits:
Quit apps you're not using, not just close their windows. On a Mac, closing a window doesn't quit the app. The app stays in memory. Right-click the icon in the Dock and choose Quit to actually free that memory. This is especially important for browsers: Chrome and Edge typically use far more RAM than Safari for an equivalent number of tabs. If you have thirty browser tabs open and only need three of them, closing the rest is probably the most effective single thing you can do for your Mac's performance.
Restart once a week. A regular restart clears accumulated swap, ends background processes that have been quietly growing for days, and resets anything that has developed a memory leak. A Friday-afternoon restart is a good habit. It takes two minutes and consistently makes a noticeable difference.
Watch for repeat offenders. If beach balls always appear after you've been using a particular app for a while, open Activity Monitor and sort the Memory column by clicking it. If that app is in the top few with a large and growing memory number, it likely has a memory leak. Check whether there's an update for it. If not, quitting and relaunching it when it gets sluggish is the workaround until a fix ships.
Keep macOS updated. Memory leak patches and process-stability fixes land in the small incremental macOS updates between major versions. Staying current means you're less likely to hit a known bug that Apple has already fixed.
Free up RAM proactively. If memory pressure is regularly yellow or red even after quitting apps, you may be running close to the limit of what your Mac's RAM can handle for your workload. The options and what actually works are covered in detail in how to free up RAM on Mac. Apple's official support page on what to do if an app is not responding is also worth bookmarking for quick reference.
If beach balls are tied to specific apps rather than general memory pressure, it's also worth checking whether those apps are set to run in the background or at login. System Settings › General › Login Items shows everything that starts when you log in. Removing items you don't need there means fewer apps competing for resources from the moment you start your Mac.