System tower · floor

How to force quit on a Mac, and why the app froze

How to force quit on a mac is three keys, and they are worth knowing by heart. What is worth reading is the sentence Apple puts in front of them and the list it puts after — because the keys end the freeze and neither explain it nor make it less likely to happen again.

If Command-Q does nothing, then: there are two ways in and they open the same window.

Option (or Alt) + Command + Esc

One entry in that window behaves differently from all the others, and it is worth knowing before you meet it in a panic. Apple: “The Finder is always open, but if it stops responding, you can force it to quit and reopen: select Finder in the Force Quit window, then click Relaunch.” The button changes its name for that one row — and if the Finder is what has stopped, that row is the fix, which is a great deal cheaper than restarting the Mac.

Then the part that is easy to skip, because by the time the app is closed the problem feels solved. It is not solved; it is postponed. Apple publishes a ladder for an app that keeps doing this, and two of the rungs are not what you would guess.

The fourth of those is the one to try first out of order. Open a different file in the same app. If the second file is fine, the app was never the problem, and everything else on the list — reinstalling, updating, removing plug-ins — is effort spent in the wrong place. It costs nothing and it splits the problem in half, which is exactly what the second-device test does for a network and the Outbox does for mail.

The fifth is the one that sounds least likely and is easiest to test. Something plugged in a few minutes ago, working perfectly as far as you can tell, is on Apple’s own list of things to remove when an app will not behave. Apple does not claim it is common; it lists it, with a reason — the device “may not be compatible with your version of macOS” — and it takes one unplugging to rule out.

A last word on what force quitting actually costs, since the whole page turns on it. Apple says plainly that you may lose unsaved changes, and it names no other cost. It is not written up as a last resort either: Apple documents it as the ordinary response to an app that is not responding, with the normal quit tried first. The care belongs before the keys rather than after them — try Command-Q, give it a moment, and then stop being patient.

The floors below take it four ways: what to try before force quitting, the two routes into the window, the Finder’s own row, and the ladder for an app that keeps freezing.

What this tower will not do

It will not treat force quitting as dangerous. Apple documents it as the normal answer to an unresponsive app, and names the only cost: unsaved changes.

It will not tell you to restart the Mac first. That is second on Apple’s own list, and the Finder row makes it unnecessary more often than people expect.

And it will not stop at closing the app. An app that freezes daily has a cause, Apple publishes the ladder for finding it, and two of its rungs cost nothing. What holds instead is simple: the instruction to try Command-Q first, both force-quit routes, the Finder’s Relaunch button and the ladder for a repeatedly freezing app are quoted from Apple’s own documentation, listed below.