How to Force Quit on Mac When the App Isn't Listed

The beachball has been spinning for two minutes. You press Option-Command-Esc, the Force Quit window opens, and the thing that is actually frozen is not in the list. That is the exact moment most guides abandon you.

Nearly every page explaining how to force quit on Mac hands you the same three-key shortcut and stops there. It works most of the time. But that window only shows apps, and a good share of the things that lock up a Mac are not apps.

So here is the whole ladder, in the order I actually use it, plus the warning Apple prints on one support page and leaves off the other.

How to force quit on Mac, the way Apple documents it

Apple's advice starts one step earlier than you would expect. Before you force anything, try Command-Q, or Quit from the app's own menu. A normal quit lets the app close its files properly, and a surprising number of half-frozen apps will still take it.

If nothing happens, press Option (or Alt), Command and Esc together. On a Mac with a Touch Bar, Esc sits at the left end of the Touch Bar. You can also choose Force Quit from the Apple menu, which is worth remembering if the keyboard itself is misbehaving. Both routes are in Apple's support article.

A window opens listing your open apps. Select the one that has stopped responding and click Force Quit. That is also the answer to "control alt delete on Mac", which is what a lot of people arriving at this question are really asking.

One exception: the Finder. It is always running, so it cannot be quit outright. Select it in that same window and the button changes to Relaunch, which restarts it without restarting your Mac. Apple does document this, though you would never guess it from the top of Google.

Why the Force Quit window cannot see what is actually frozen

The Force Quit window lists apps. It does not list helper processes, menu bar agents, background daemons, or the separate renderer processes a browser spawns for tabs and extensions.

That matters, because those are precisely the things that pin your fans at full speed or wedge the pointer. If Safari's interface is fine but one tab is chewing a core, force quitting Safari is a sledgehammer that takes every other tab with it.

And here is the part nobody on the first page of results mentions: Apple's force quit article does not use the words Activity Monitor once. The page that solves this particular problem sits in a completely different section of Apple's support site, and nothing links the two together.

Worth separating two problems here, because they get muddled constantly. A Mac that is frozen needs the ladder below. A Mac that is merely slow, with a full disk and a fan that never stops, usually needs a look at what is eating the storage instead. Force quitting things will not fix that one.

Activity Monitor is the other half of the answer

Open Activity Monitor from Applications, then Utilities. Or press Command-Space and type the name, which is quicker. Sort the CPU tab by % CPU and the culprit usually names itself within about three seconds.

Select the process and use the stop button in the toolbar. You get two options, and the difference between them is real. Apple's Activity Monitor guide explains that Quit behaves like choosing Quit inside the app: macOS ends the process when it is safe to do so, and the system may refuse if stopping it right now would cause trouble. Force Quit ends it immediately and waits for nothing.

The wording on that page is noticeably blunter than anything on the force quit article. Apple states plainly that "If the process has files open, you may lose data." It adds that other apps relying on that process could run into problems, and suggests switching to View, then All Processes, Hierarchically, so you can see what is sitting underneath before you kill it.

That hierarchical view is the underused bit. It shows you that the process gobbling CPU is a child of something else, which tells you whether to kill the child or the parent. Kill the wrong one and it simply respawns.

The warning Apple prints on only one of the two pages

Put the two documents side by side and the inconsistency is hard to miss. The force quit article walks you through terminating an app and says nothing whatsoever about unsaved work. The Activity Monitor page, describing the same underlying action, opens with a data-loss warning.

In practice the risk depends entirely on the app. Apple's own document apps write as you go, so force quitting Pages or Preview has never cost me anything. Plenty of third-party apps still hold everything in memory until you press save, and those are the ones where Apple's sterner warning is the accurate one.

That last paragraph is my experience rather than Apple's documentation, so weigh it accordingly. The safe habit is simple: if the frozen app is one where you would be upset to lose ten minutes of work, spend thirty seconds trying Command-Q before you escalate.

The full escalation ladder, in order

Seven routes, from gentlest to most destructive. Work down it rather than jumping to the bottom.

• Command-Q, or Quit from the app's own menu. Always first.
• Option-Command-Esc, then select the app and click Force Quit.
• Apple menu, then Force Quit, if the shortcut does not register.
• Finder only: select it in that window and click Relaunch.
• Activity Monitor, select the process, Quit.
• Activity Monitor, select the process, Force Quit.
• Hold the power button, or Touch ID on a laptop, for up to ten seconds.

By my own count across Apple's pages, the force quit article carries five of those seven and omits the two that work when the frozen thing is not an app. The Activity Monitor guide carries two and mentions neither the keyboard shortcut nor the power button. The keyboard shortcuts page carries exactly one. No single Apple document has the lot, which is the whole reason this post exists.

Step seven is a genuine last resort, because it cuts power and anything unwritten is gone. Apple's instruction is to hold for up to ten seconds, which feels considerably longer than it sounds when you are doing it. On a MacBook the power button is the Touch ID sensor, so a light tap achieves nothing. Press and hold. If your Mac then behaves oddly on the way back up, how it starts up is its own rabbit hole.

When the pointer is dead as well

Occasionally the whole interface locks and the cursor stops moving. This is where the keyboard shortcut earns its place over the Apple menu route, because the Force Quit window responds to the arrow keys, and Return triggers the Force Quit button.

So the fully keyboard-driven sequence is Option-Command-Esc, arrow down to the app, Return. No pointer required at any stage. If even that does nothing after thirty seconds or so, you are at step seven.

The shortcut half the internet still recommends

You will find no shortage of pages telling you to hold Command-Option-Shift-Esc for three seconds to kill the front app outright, with no window at all. I went and checked Apple's current keyboard shortcuts page while writing this. It lists precisely one force quit shortcut: Option-Command-Esc, described as force quit an app.

The hold variant is not on that list. I am not going to claim it definitely fails on your Mac, because undocumented behaviour has a habit of lingering in macOS for years after the documentation drops it. I am telling you Apple no longer documents it, and a guide built primarily on it is a guide built on sand.

If you are running the macOS 27 beta

One current wrinkle worth flagging. People running the macOS 27 Golden Gate beta have reported that Force Quit and Activity Monitor both fail on certain apps, Safari and Chrome among them, with Terminal the only thing that works. The reported workaround is sudo killall followed by the app name in quotes. That is beta behaviour written up by OS X Daily rather than anything Apple has acknowledged, so treat it as a report, not a fact.

Golden Gate is not a shipping release yet either, so most people reading this are on stable macOS and can ignore this section completely. If you are on the beta and force quit has quietly stopped working, it is probably not your Mac at fault. There is plenty else changing in Golden Gate worth knowing about before you install it.

Force quit on Mac: common questions

Why is the app I want to force quit not in the list?

Because it is probably not an app. The Force Quit window only enumerates apps with a user interface. Helper tools, menu bar utilities, background agents and individual browser tab processes never appear there. Open Activity Monitor instead, sort by % CPU, and you will find it.

Does force quitting on Mac lose unsaved work?

It can. Apple's Activity Monitor guide warns that a process with files open may lose data, while its force quit article does not mention the risk at all. Apple's own document apps save continuously and generally survive it fine. Many third-party apps do not, so try Command-Q first whenever the work matters.

What is Control-Alt-Delete on a Mac?

Option-Command-Esc is the closest equivalent. It opens the Force Quit window, which does the job Task Manager does on Windows for apps. For the fuller Task Manager experience, including background processes and CPU figures, Activity Monitor is the real counterpart.

My take

The three-key shortcut is not wrong, it is just incomplete, and being incomplete is why so many people end up holding down the power button for something a twenty-second trip to Activity Monitor would have fixed. Learn where the frozen thing lives before you decide how hard to hit it.

If you remember one line from this: the Force Quit window lists apps, Activity Monitor lists everything. When the window is no help, that is not a dead end, it is a signal that you are looking in the wrong place.

Source: How to force an app to quit on Mac, Apple Support