The Spinning Beachball Won't Stop? Here's the Real Fix

The spinning beachball — officially the “spinning wait cursor” — appears when an app stops responding to events for more than a few seconds. macOS shows it to tell you “this app is stuck, but maybe not dead, hold on.” A fleeting beachball is normal. A constant one means something is genuinely wrong, and the cause is almost always identifiable.

If you’re seeing the beachball multiple times an hour, every day, this guide is for you. The fix depends on which app is beachballing, when, and why.

What the beachball actually means

When an app’s main thread doesn’t process events for ~4 seconds, macOS shows the beachball cursor over that app’s windows. The app is technically still running — it’s just busy or stuck on something.

Common causes, ranked by frequency:

1. Disk I/O blocking — the app is waiting for disk reads/writes that are slow
2. Network blocking — waiting for a request that hasn’t returned
3. CPU-bound work on main thread — the app is computing something heavy
4. Memory pressure — the system is swapping, and the app is waiting on RAM
5. Inter-process communication blocking — waiting on another process to respond
6. Genuinely stuck — the app has a bug or deadlock

Identifying which is happening tells you the fix.

Step 1: When does the beachball appear?

Pay attention. Does it happen:

• In one specific app, always? That app has a problem (or your data file is huge)
• In multiple apps, simultaneously? System-wide issue — usually disk or memory
• At specific actions (saving, opening files)? I/O-related
• Randomly throughout the day? Background process eating resources
• After waking from sleep? Sleep/wake bug, often in a specific app
• When connected to a network drive? Network mount issues

Write down what you observe. The pattern matters more than any single instance.

There’s a faster waySweep handles this automatically and lets you approve before anything’s deleted. Try Sweep free →

Step 2: Activity Monitor while it’s happening

This is the diagnostic step that catches almost everything. Open Activity Monitor (Spotlight: “Activity Monitor”). Leave it open in a corner.

When a beachball appears, immediately check:

• CPU tab, sorted by % CPU — what’s pegged?
• Memory tab, Memory Pressure graph — green/yellow/red?
• Disk tab — what’s reading or writing heavily?
• Network tab — anything maxing out?

A beachballing app is often listed in red as “(Not Responding)” in Activity Monitor. The other apps and processes near the top of CPU usage are usually the cause.

Common culprit: full or failing disk

A nearly-full SSD beachballs constantly. Below 10% free, every disk write becomes slow because macOS is shuffling data to find space. Below 5%, even basic operations beachball.

Apple menu → System Settings → General → Storage. If you’re tight, free up space — that alone often fixes “constant beachball” entirely.

A failing SSD also beachballs. If you’ve got an older Mac (5+ years) and beachballs are increasing in frequency over weeks or months, suspect the drive. Open Disk Utility (Applications → Utilities → Disk Utility), select your drive, run First Aid. If it reports errors, back up immediately and consider replacement.

Common culprit: memory pressure

Look at Activity Monitor’s Memory tab. The Memory Pressure graph at the bottom is the real indicator:

• Green — fine
• Yellow — system is using memory compression, slight slowdown
• Red — actively swapping to disk, beachballs likely

If you’re in yellow or red regularly, you’re either running too many apps for your RAM or you have one app that’s leaking. The Memory tab sorted by Memory descending shows you who’s at fault.

Common memory hogs:

• Browsers with many tabs (especially Chrome)
• Video editing apps with timelines open
• Photoshop with many large files
• Logic Pro with heavy sessions
• Any Electron app left open for days (memory leaks accumulate)

Common culprit: a specific app gone wrong

If beachballs are concentrated in one app, that app has a problem. Try, in order:

1. Quit and relaunch the app — clears in-memory state
2. Restart the Mac — clears system-level state
3. Update the app — the bug might be fixed in a newer version
4. Clear the app’s cache — ~/Library/Caches/[bundle ID]
5. Reset the app’s preferences — ~/Library/Preferences/[bundle ID].plist
6. Reinstall the app — uninstall, remove all support files, reinstall fresh

A clean reinstall, where you also remove ~/Library/Application Support/[app] and ~/Library/Containers/[app], often fixes long-running issues that other troubleshooting can’t.

Common culprit: network mounts

If you’ve got network drives mounted (NAS, file server, cloud drive), and the network gets slow or the server unreachable, every Finder operation that touches those drives beachballs the entire Finder. Even just having “Recent Servers” with old entries can cause this.

Finder → Cmd+Comma → Sidebar and remove any network locations you don’t actively use. Eject any mounted servers you don’t need right now.

If your home or work network has flaky Wi-Fi and you’ve got network drives auto-mounting, you’ll get beachballs every time the Wi-Fi hiccups.

Common culprit: cloud sync apps

Dropbox, Google Drive, OneDrive, iCloud Drive can all cause beachballs in Finder when they’re scanning, indexing, or syncing big changes. The Finder waits on filesystem operations that the sync app is performing slowly.

If you suspect cloud sync, quit the cloud app temporarily and see if Finder recovers. If it does, the cloud sync is the issue. Reduce what you’re syncing, pause sync during heavy work, or move some files out of the synced folder.

Common culprit: Spotlight indexing

Spotlight reindexing after macOS updates or large file imports can cause widespread beachballs. Symptoms: Activity Monitor shows mds_stores or mdworker_shared consistently using significant CPU.

You can wait it out (usually finishes in hours to days) or speed it up by leaving the Mac on, plugged in, and idle.

If indexing has been running for over a week and seems stuck, force a clean reindex:

1. System Settings → Siri & Spotlight → Spotlight Privacy
2. Add your startup disk
3. Wait 30 seconds
4. Remove it

Make this a one-click jobSweep does the same hunt in seconds. Always shows you what’s about to go. Free for macOS →

When Finder itself beachballs

Finder is often the most-beachballing app because it touches everything. If Finder is constantly stuck:

1. Force quit Finder — Cmd+Option+Esc, select Finder, click “Relaunch”
2. Check for problematic items — folders with thousands of files, mounted server volumes
3. Reset Finder preferences — quit Finder, delete ~/Library/Preferences/com.apple.finder.plist, relaunch
4. Disable iCloud Desktop & Documents if active — adds latency to every Finder operation

A Finder relaunch is essentially free and fixes a lot of stuck-Finder situations.

Force quitting beachballed apps

If an app has been beachballing for more than a minute or two, it’s stuck for real. Force quit and start over:

• Cmd+Option+Esc — Force Quit window
• Select the app, click Force Quit
• Or right-click the dock icon, hold Option, click “Force Quit”

You’ll lose any unsaved work in that app. Some apps recover better than others on restart — Pages, Numbers, and most modern apps auto-save and recover well. Older apps may not.

When it’s not the app — when to suspect hardware

If beachballs:

• Started suddenly with no software changes
• Are increasing in frequency week over week
• Happen across many different apps for no clear reason
• Are accompanied by kernel panics or unexpected restarts

These point to hardware. Run Apple Diagnostics:

• Apple Silicon: shut down, hold power until startup options, hold Cmd+D until diagnostics start
• Intel: shut down, press power, immediately hold D

If diagnostics flag anything, that’s your answer. If they don’t, try booting from external storage to see if the internal drive is the issue.

Stop the beachball cycle

Most chronic beachballs come from accumulated junk: full disk, memory pressure from too many apps, sync apps left running, mountains of cached data. Clearing these out — in order — usually drops beachball frequency from “many times a day” to “barely ever.”

If you’ve cleaned up and the beachballs persist in one specific scenario, that’s usually a single app needing replacement or update. Find that app, fix that app, and you’re done.