The force quit shortcut on a Mac, and every other way to kill a stuck app.
Hold Option (⌥) and Command (⌘) and press Escape (⎋). The Force Quit Applications window opens, you pick the app, you click Force Quit. That is the answer. The rest of this page is the faster shortcut nobody knows, what to do when the Mac is too frozen for even that, and what force quitting costs you.
What a beachball actually means, and what force quitting does
The spinning colour wheel is not the app thinking. It is macOS telling you that the app has not picked up an event from its queue for roughly two seconds, so the window server draws the wheel on the app's behalf. Almost always the cause is the app's main thread, the one thread allowed to touch the interface, sitting inside something slow. It might be a file read off a network volume that stopped answering, a database query, or a lock another thread never let go. The app is not broken in the sense of crashed. It is busy in the wrong place, and until that thread comes back nothing you click will register.
Quit and Force Quit are not the same act. Command-Q asks the app to leave: it flushes buffers, writes open documents, saves window positions, tells the system it is going, and exits. Force Quit sends SIGKILL, a signal the process is not allowed to catch or ignore, and the kernel removes it from memory mid-sentence. Nothing gets saved on the way out, no cleanup code runs, temporary files stay behind. Apps built on Auto Save and versions, which includes TextEdit, Pages, Numbers, Keynote and Preview, keep writing to disk as you type and usually reopen with your work intact. Apps that only save when you press Command-S will lose everything since the last time you did.
There are so many force-quit routes on a Mac because each one fails in a different situation. The keyboard shortcut needs the window server to still be listening. The Dock menu needs the Dock to still be drawing. Activity Monitor needs to be launchable, and it is the only one that sees processes that are not applications. Terminal needs nothing graphical at all and works over SSH from another machine. Knowing the ladder matters more than knowing any single rung, because the moment you actually need this is the moment the easy rung is the one that has stopped working.
The five ways to force quit an app on a Mac
Option (⌥) + Command (⌘) + Escape (⎋), the shortcut people mean
Hold Option and Command and press Escape. A small window titled Force Quit Applications opens above everything else, listing your running apps, with anything macOS believes is hung marked not responding in red. Arrow down to the app or click it, then press Return or click the Force Quit button. macOS asks once to confirm and then kills the process. The window stays open afterwards, so a second app takes two more keystrokes. This needs nothing installed, works on every Mac going back years, and on a machine where the pointer still moves it is the correct first move. It is also the only route Apple puts in the Apple menu.
Option (⌥) + Shift (⇧) + Command (⌘) + Escape (⎋) held for three seconds
Hold all four together for about three seconds and macOS force quits whatever app is frontmost. No window, no list, no confirmation, the app is simply gone. It is by a wide margin the fastest route and most Mac owners have never heard of it, because nothing in the interface hints that it exists. Two cautions come with it. The app has to be frontmost, so click its window once first if a hang has left focus somewhere strange. And because there is no confirmation step, a stray hand can take out an app you were only mildly annoyed with, along with anything in it you had not saved.
The Dock icon, with Option held
Right-click or Control-click the app's icon in the Dock and a menu appears with Quit at the bottom. Hold Option while that menu is open and Quit changes to Force Quit. Click it and the app dies immediately, with no confirmation dialog. This is the easiest one to remember because it involves no shortcut at all, and it is handy when a hung full-screen app has taken the display but the Dock still slides up. It has one blind spot. If the app is wedged badly enough that the Dock has stopped drawing its menus, this route quietly stops working and you are back on the keyboard. The same menu is where the Apple menu route ends up too: open the Apple menu and choose Force Quit for the same window as the first method.
Activity Monitor, for everything that is not an app
Activity Monitor sits in Applications, then Utilities. It is the only built-in tool that reaches past applications to processes. Open it, type a name into the search field at the top right, select the row, click the ⊗ Stop button in the toolbar and choose Force Quit rather than Quit. Because it lists every process rather than every app, it reaches what a hang is usually hiding behind. That might be a helper process, a background daemon, or one runaway renderer inside a browser that is eating a core while the window looks fine. The CPU and Memory columns are how you find which one. Slower than a keystroke, and the right tool when the shortcuts cannot see the problem.
Terminal, when nothing graphical is cooperating
Open Terminal and run killall Safari, substituting the app's exact process name, and every process with that name gets a termination signal. To be precise instead, find the process ID with top or with ps aux | grep Safari, then run kill -9 followed by that number. The -9 is SIGKILL: the kernel removes the process immediately and the app never runs its own save-and-cleanup code, so unsaved work is gone. Try kill without -9 first, which sends the polite signal a healthy app will obey. Terminal is also the route that still works over SSH from a second machine when the screen in front of you has stopped responding entirely.
Which method to reach for
This table compares methods, not products. Four of the five columns are already on your Mac and cost nothing, and for most hangs the first column is the whole answer. Read the row that matches your situation rather than the column that looks best overall, because none of these is better than the others in general. The ⌥⌘⎋ window is the safe default. The three-second hold is the fast one. Activity Monitor is the only one that sees processes that are not applications. Terminal is the one that survives when the graphical layer does not.
The Coco column is here for one narrow case. When a hung app has taken the whole screen and clicking around is painful, Coco's hotkey panel opens over it, because Coco is a separate process and a beachballed app does not block it. You type the app's name and quit it from the keyboard, without hunting down a row in the Force Quit list. That is a convenience, not a capability the Mac lacks. Coco is not a process manager: it does not show CPU or memory, it does not reach daemons or helper processes, and for those Activity Monitor is still the right tool and always will be.
| ⌥⌘⎋ window | ⌥⇧⌘⎋ hold | Activity Monitor | Terminal | Coco | |
|---|---|---|---|---|---|
| Works without touching the mouse | |||||
| Quits with no confirmation dialog | |||||
| Quits the frontmost app instantly | |||||
| Lets you pick from a list of running apps | |||||
| Finds the app by typing its name | |||||
| Reaches background processes that are not apps | |||||
| Shows CPU and memory use | |||||
| Relaunches Finder | |||||
| Still works when the Dock is unresponsive | |||||
| Works over SSH from another machine | |||||
| Requires knowing Terminal commands | |||||
| Quits several apps in a row quickly | |||||
| Requires installing a third-party app | |||||
| Free with macOS | |||||
| Risks losing unsaved work |
The escalation ladder, in order
Press Command-Q and wait thirty seconds
A beachball is often temporary. The app may be finishing a large save, waiting on a network volume, or rebuilding an index. Press Command-Q, then leave it alone for half a minute. If the app comes back and exits normally, your documents were written properly and you skipped the whole problem. Force quitting a merely slow app is how people lose work that was never actually at risk.
Then Option (⌥) + Command (⌘) + Escape (⎋)
Open the Force Quit Applications window, select the app, click Force Quit and confirm. If the app is frontmost and you do not want the dialog, hold Option, Shift, Command and Escape for about three seconds instead. Either way the app is killed and unsaved changes in it are lost, so this step is deliberate rather than reflexive.
If that does nothing, open Activity Monitor
Applications, then Utilities, then Activity Monitor. Search for the app's name, select the row, click the ⊗ Stop button and choose Force Quit. If the app is not the real culprit, sort by CPU and look for the process pinning a core: often a helper or a browser renderer rather than the app you were using. If Activity Monitor itself will not open, use Terminal and kill -9 the process ID.
Only then log out or restart
Press Shift-Option-Command-Q to log out immediately without the confirmation prompt, which ends every process in your session. If the pointer still moves, use the Apple menu and choose Restart. Holding the power button for about ten seconds is the last rung on the ladder, not the first: it cuts power with the filesystem mid-write and can leave damaged files behind. Use it only when nothing at all responds, including the pointer.
Questions people ask about force quitting on a Mac
- What is the force quit shortcut on a Mac?
- Option (⌥) + Command (⌘) + Escape (⎋). Hold Option and Command, press Escape, and the Force Quit Applications window opens above whatever is on screen. It lists your running apps, with anything macOS believes is hung marked not responding. Select the app with the arrow keys or the mouse, then press Return or click Force Quit, and confirm once. There is a second shortcut worth learning: Option + Shift + Command + Escape held together for about three seconds force quits the frontmost app straight away, with no window and no confirmation. The same Force Quit window is also in the Apple menu, so you never need to remember the keys at all.
- What is the Mac equivalent of Ctrl+Alt+Delete?
- There are two answers, because Ctrl+Alt+Delete on Windows does two jobs. For killing a stuck program, the equivalent is Option-Command-Escape, which opens the Force Quit Applications window: a short list of running apps with a Force Quit button. For inspecting what the machine is doing, the equivalent of Task Manager is Activity Monitor, in Applications then Utilities. It lists every process with its CPU, memory, energy, disk and network use, and it can force quit any of them from the ⊗ Stop button. Windows users usually want the first when an app hangs and the second when the whole machine feels slow.
- How do I force quit when the shortcut does not work or the screen is frozen?
- Work down the ladder. Try the Apple menu, then Force Quit, in case the keyboard shortcut is what is blocked. Open Activity Monitor from Spotlight and stop the process there. If the interface is too stuck for that, open Terminal and run kill -9 with the process ID from top, or SSH in from another machine and do the same, which works even when the display has given up. If nothing responds at all, press Shift-Option-Command-Q to log out, or Control-Command-Power to restart. Holding the power button for about ten seconds is the last resort, because it cuts power mid-write and can corrupt files.
- How do I force quit Finder on a Mac?
- Finder cannot be quit the normal way, because macOS needs it running, so what you do instead is relaunch it. Hold Option and right-click or Control-click the Finder icon in the Dock, and the menu shows Relaunch. Or open the Force Quit Applications window with Option-Command-Escape and select Finder: the button changes from Force Quit to Relaunch. Either way Finder restarts within a second or two. Open Finder windows close and their positions are lost, but nothing on disk is touched. This is the standard fix for a Finder that has stopped drawing icons, stopped responding to clicks, or left a copy operation stuck at ninety-nine percent.
- Will I lose unsaved work if I force quit?
- Assume yes. Force Quit sends SIGKILL, which the app cannot catch, so it never gets to run the code that saves your documents. Whether you actually lose anything depends on the app. Anything built on Auto Save and versions, which includes TextEdit, Pages, Numbers, Keynote and Preview, has been writing to disk as you type and usually reopens with your work intact. Apps with their own autosave, like many editors and Office, may offer a recovered copy on next launch. Apps that only write when you press Command-S will lose everything since the last save. If the work matters, spend thirty seconds on Command-Q first.
- Is force quitting bad for my Mac?
- No. Force quitting an app is a normal, supported operation and does no harm to macOS or to your hardware. The process is removed from memory, the system reclaims what it was using, and you can relaunch the app immediately. The only cost is inside that app: unsaved documents, temporary files it did not clean up, and occasionally a preference or cache file caught mid-write, which the app usually rebuilds on next launch. The thing that genuinely is risky is holding the power button to cut power, because that can interrupt a disk write. Force quitting a single app is nowhere near that.
Copy the prompt, or send it straight to the AI you already use — it drives Coco through the same commands you would type yourself.
Install the Coco skill (npx skills add butterflydream-ai/Coco --skill coco -g -y), then use coco to help me with The force quit shortcut on a Mac, and every other way to kill a stuck app..