You're staring at a beach ball that never stops spinning, and your app won't respond to anything. Yeah, that's annoying. Let's fix it right now.
The Direct Fix: Force Quit + Kill the Process
Most guides tell you to press Cmd+Option+Esc, pick the app, and hit Force Quit. That's step one, but it's not always enough. Sometimes the app window disappears, but the process is still running in the background, eating CPU and keeping your Mac sluggish.
Step 1: Force Quit the Normal Way
Press Cmd+Option+Esc (that's the Force Quit dialog). Select the frozen app and click Force Quit. If that works, you're done. If the app relaunches immediately and freezes again, or if the dialog itself won't close, move to step 2.
Step 2: Kill the Process from the Terminal
Open Terminal (you can find it in Applications > Utilities). Type this:
ps aux | grep -i "appname"Replace appname with the actual name of the app, like Safari or Microsoft Word. You'll see a list of processes. Look for the one that's actually running (the grep line itself is just the search, ignore it). Note the PID — that's the number in the second column.
Then kill it:
kill -9 PIDSo if the PID is 1234, you'd type kill -9 1234. The -9 flag is the nuclear option — it tells the system to terminate the process immediately, no cleanup, no second chances. That's exactly what you want when the app is truly stuck.
If you don't want to deal with PIDs, use this one-liner instead:
pkill -9 -i "appname"That kills every process with that name, ignoring case. Works in one shot.
Why This Works
What's actually happening here is that the app's main thread is stuck — usually waiting on something that never comes back, like a network request or a disk read. The Force Quit dialog sends a normal terminate signal, but if the app is frozen in a way that ignores it, the signal gets lost. The kill -9 command bypasses all that. It tells the kernel to just remove the process from the scheduler. No chance for the app to ignore it.
The reason step 3 works is that the kernel doesn't care about the app's state. It's the difference between asking someone politely to leave and having security escort them out. Same result, but one is guaranteed.
Less Common Variations of the Same Issue
The App Keeps Relaunching Itself
If you force quit and the app immediately reopens, it's probably set to reopen on login or the system is trying to restore your session. To stop that, hold Shift while logging in to prevent apps from reopening. Or go to System Settings > General > Login Items and remove the app from the list.
The Dock Icon Is Unresponsive
Right-click the Dock icon, hold Option, and you'll see Force Quit in the menu. That works without opening the dialog. If the Dock itself is frozen, you can restart it with:
killall DockThat won't log you out — it just restarts the Dock process. Your windows stay put, and the Dock reappears after a second. This is a known trick for a stuck Dock, and it's safe.
Finder Won't Respond
Finder is special. You can't force quit it from the dialog because it's always running. But you can restart it with the same killall command:
killall FinderThis is the fix I use when Finder shows the spinning beach ball for no obvious reason. It takes a moment, but it clears the freeze.
App Shows 'Not Responding' in Activity Monitor
Open Activity Monitor (in Applications > Utilities), find the app in the list, select it, and click the X button at the top-left. That's the same as force quit, but you get to see the CPU usage beforehand. If the app is using 100% CPU, it's likely stuck in a loop. The kill -9 from Terminal is still the most reliable, but Activity Monitor's button is a good visual alternative.
Prevention: Stop the Freeze Before It Starts
You can't prevent every freeze, but you can reduce them. The biggest culprits are memory pressure and disk I/O. If your Mac has less than 8GB of RAM, you're more likely to see this. Close apps you're not using, and consider using Safari over Chrome if you're on an older Mac — Chrome's per-tab processes eat RAM like it's free.
Also, check your disk space. If your startup disk is nearly full, apps will hang when they try to write temporary files. macOS needs about 10-15% free space to breathe. If you're under that, clear some cache or move photos to an external drive.
Finally, update your apps. A lot of freezes are bugs that get fixed in updates. I've seen Safari freeze on a specific site, and the next version handled it fine. The same goes for macOS updates — Apple ships fixes for system-level issues that cause app hangs.
Keep a habit of running killall on a frozen app instead of rebooting. A reboot is overkill, and you lose your session. The targeted kill is faster, and you learn which apps are prone to freezing — that knowledge is worth more than any generic tip.