How to Force Quit an App on Mac (Plus Why It Sometimes Won't Quit)

The spinning beachball, then nothing. Cmd+Q does nothing. The Dock icon won’t respond. The window is frozen. You need to force quit, and your usual method isn’t working.

There are actually five increasingly aggressive ways to force quit an app on Mac. The reason this matters: each one closes the app in a different way, and some apps will only respond to the heavier methods.

Method 1: Cmd+Option+Esc

The classic. Hit Cmd+Option+Esc and you get the Force Quit window — a list of running apps with a Force Quit button.

This works for 90% of cases. It tells the app to terminate, gives it about a second to save state, and forces it to close if it doesn’t comply.

When this fails, it’s usually because:

• The app is hung in a way that ignores quit signals
• A child process is keeping it alive
• The app is doing something that macOS won’t interrupt cleanly (e.g. a sandbox-locked operation)

Method 2: Force Quit from the Apple menu

Same effect as Cmd+Option+Esc, just a different way to get there. Apple menu → Force Quit….

Useful when one of your hands is on the trackpad and the keyboard is across the room.

Method 3: Right-click the Dock icon, hold Option

Right-click the app’s Dock icon. The menu shows Quit. Hold Option, and Quit changes to Force Quit. Click it.

Sometimes this works when the Force Quit dialog won’t appear, because it’s targeting the specific app rather than going through the system-wide window.

Method 4: Activity Monitor

When the app doesn’t even appear in the Force Quit window — or when there are multiple processes for one app and you need to kill them individually:

1. Open Activity Monitor (/Applications/Utilities/Activity Monitor.app).
2. Search for the app’s name.
3. Select it.
4. Click the X button in the toolbar.
5. Choose Force Quit.

Activity Monitor shows every process, including helpers and child processes. If an app has multiple entries (Chrome, for instance, has dozens), you can kill the parent and the children follow.

Method 5: Terminal — kill and killall

The nuclear option. From Terminal:

killall "AppName"

For a single specific process:

ps aux | grep AppName
kill -9 <PID>

-9 is SIGKILL, which the OS sends without giving the process a chance to clean up. Use this when nothing else works. Avoid using it as a default — it can leave files in inconsistent states.

Make this one clickSweep handles all of this automatically and lets you approve before anything is deleted. Free for macOS →

Why apps sometimes refuse to quit

A few common reasons:

• Saving in progress. Office apps, Photoshop, video editors — they’ll finish the save before quitting. If the save is hung, the app appears frozen.
• Modal dialog hidden behind another window. The app is waiting for input on a dialog you can’t see. Cmd+~ cycles through windows in the app, sometimes reveals it.
• Background sync. Cloud apps (Dropbox, OneDrive, Backblaze) sometimes wait for a sync transaction to finish.
• Hung helper process. The main app is fine but a helper (an updater, a license check, a render farm) is hung. Killing the parent doesn’t kill the child.
• Kernel extension or system-level lock. Rare on modern macOS but possible — typically related to anti-virus tools or virtualization software.
• Crashed but still in the dock. macOS sometimes leaves the icon visible after the underlying process is gone. Right-click → Quit usually clears it.

How to figure out what’s stuck

Open Activity Monitor and sort by CPU. A hung app frequently shows 100%+ CPU on one core, doing nothing useful (it’s stuck in a loop). Or it shows 0% with a “(Not Responding)” tag in red.

The CPU spike pattern tells you it’s actively misbehaving. The “Not Responding” pattern tells you it’s waiting on something it can’t get.

When force-quitting causes problems

Force-quitting can:

• Lose unsaved work
• Corrupt application data
• Leave temp files behind
• Confuse cloud sync (uploading partial changes)

The first one is the most common. If you’ve been working in an app and it goes unresponsive, give it a minute before force-quitting. Some apps recover.

For text-heavy work (writing, code), most modern apps have autosave and won’t lose more than the last few seconds. For binary work (Photoshop, Logic Pro), there’s a real risk.

What about background processes that won’t quit?

Some apps install helpers that keep running even after you quit the main app — sync clients, anti-cheat, anti-virus, virtualization tools. Activity Monitor shows them.

Killing them is straightforward:

1. Open Activity Monitor
2. Find the helper (usually has a name like AppNameHelper or <vendor>updater)
3. Force quit it

But the bigger question is why it keeps running. Usually it’s because there’s a LaunchAgent in ~/Library/LaunchAgents/ (or /Library/LaunchAgents/) configured to relaunch the helper. You’ll force quit it and 30 seconds later it’s back.

To stop it permanently:

1. Find the matching .plist in ~/Library/LaunchAgents/
2. Move it to the desktop
3. Force quit the helper one more time
4. The relaunch won’t happen

If you don’t want to do this manually, an uninstaller with helper-tool management does it for you. Sweep, for example, identifies helpers and their associated LaunchAgents during normal app uninstall — but you can also use it to clean up orphan helpers without uninstalling the parent app.

Apps that legitimately won’t quit

A small set of apps are designed to resist normal quit:

• Anti-virus / endpoint protection. Often configured to require admin password to disable.
• Backup software. Won’t quit during an active backup.
• VPN clients. Some require you to disconnect before quit.
• Background sync managers. Some wait until sync is done.

For these, the right approach is to use the app’s own UI to disable or pause first, then quit normally.

What I do in practice

My usual escalation:

1. Cmd+Q. Wait two seconds.
2. Right-click Dock icon, hold Option, Force Quit.
3. Cmd+Option+Esc. Pick the app, click Force Quit.
4. Open Activity Monitor, search for it, kill the process and any helpers.
5. Terminal kill -9 <PID>.
6. If even kill -9 fails (very rare), restart the Mac.

Each step is a small escalation. Most of the time, step 2 is enough.

There’s a faster waySweep does the same hunt in seconds, with a preview before anything is removed. Try Sweep free →

When restart is the right answer

If kill -9 fails, restart. There’s no normal way to recover from that situation, and continuing to fight it usually means time wasted plus the same outcome.

Restart is also right when:

• The Mac is generally sluggish, not just one app
• Multiple apps are unresponsive
• The Finder itself is hung (in which case Cmd+Option+Esc still works)
• You’ve force-quit the same app three times and it keeps re-hanging

A restart clears all process state, which is sometimes the only fix.

After a force quit

A few things to do after the dust settles:

1. Relaunch the app and check whether it auto-recovers (most modern apps do)
2. Check Console.app for crash logs to see why it hung
3. If the app keeps hanging, consider a full reset (clear preferences and caches before reinstalling)
4. If a helper kept relaunching, find and remove the orphan LaunchAgent

The last one is where most people stop too early. A force-quit fixes the symptom; an orphan LaunchAgent keeps the disease.

Quick recap

Five ways to force quit, in order:

1. Cmd+Option+Esc → Force Quit window
2. Apple menu → Force Quit
3. Right-click Dock icon, Option-click Quit → Force Quit
4. Activity Monitor → X button → Force Quit
5. Terminal: killall AppName or kill -9 <PID>

If you find yourself force-quitting the same app repeatedly, the right next move isn’t another force-quit — it’s resetting the app’s preferences and caches, or hunting down a misbehaving helper.