Force quit a frozen app on Mac — 5 ways that always work

When a Mac app stops responding — the spinning beach ball, an unclickable window, a process eating 100% CPU — the normal Quit command does nothing. Force quitting bypasses the app's shutdown sequence and kills the process immediately. Here are five ways to do it, from the fastest to the most reliable when things are really locked up.

Method 1: keyboard shortcut (fastest)

Command + Option + Escape opens the Force Quit Applications dialog. This works even if the frozen app is covering your entire screen.

1. Press ⌘ + ⌥ + Esc simultaneously.
2. A small panel appears listing all open apps. The frozen one usually shows "(Not Responding)" next to its name.
3. Select the app and click Force Quit.

The app quits immediately without any save prompt. If you have unsaved work in the frozen app, it will be lost — but if the app is genuinely frozen, there is no way to save it anyway.

You can also open this dialog from the Apple menu: click → Force Quit.

Method 2: right-click the Dock icon

If the app is in your Dock and the Dock itself is still responsive:

1. Right-click (or Control-click) the frozen app's icon in the Dock.
2. A context menu appears with a Quit option at the bottom.
3. Hold Option — the Quit item changes to Force Quit.
4. Click Force Quit while still holding Option.

This is useful if the ⌘⌥Esc dialog is already open and you want a different method, or if the keyboard shortcut is being captured by something else.

Method 3: Activity Monitor

Activity Monitor is the right tool when you want to see what is actually happening before killing it — CPU usage, memory pressure, threads, or whether a background process is the real culprit rather than the visible app.

1. Open Activity Monitor from Applications → Utilities (or search with Spotlight: ⌘Space → type "Activity Monitor").
2. Click the CPU tab and sort by % CPU to find the heaviest process.
3. Select the process you want to kill.
4. Click the × (Stop) button in the toolbar.
5. Choose Force Quit in the confirmation dialog.

Activity Monitor shows all processes — including background daemons and helper processes that never appear in the Dock. If your Mac is slow but no visible app seems to be the culprit, check here first.

Method 4: Terminal (most reliable)

When the UI is partially locked and clicking feels unreliable, Terminal usually keeps working. There are two approaches:

Kill by name (simplest):

# replace "AppName" with the exact app process name
killall AppName

Examples: killall Finder, killall "Google Chrome". Note that app names with spaces need quotes.

Kill by PID (most precise):

# find the process ID
ps aux | grep AppName

# then kill it (replace 1234 with the actual PID)
kill -9 1234

The -9 flag sends SIGKILL — it is the unconditional "stop now" signal that the process cannot catch or ignore. Use this when a regular kill is not enough.

You can also get the PID straight from Activity Monitor: select the process, and the PID is shown in the bottom info bar.

Method 5: Apple menu with Option

There is a lesser-known trick built into the Apple menu. Click in the menu bar while the frozen app is focused, then hold Option. The standard menu item changes:

• Force Quit appears as an option for the current app.

This is the same as ⌘⌥Esc but accessed through the menu. It is handy if you forget the keyboard shortcut.

When force quit does not work

Occasionally a process is stuck in a kernel-level wait state — waiting for disk I/O, a network socket, or hardware. In these cases even kill -9 will not terminate it immediately; the process shows up in Activity Monitor as "(Not Responding)" and stays there until the wait resolves or the Mac is restarted. If you encounter this, a full restart is the cleanest fix. Hold the power button for a few seconds if the Mac itself has stopped responding.

Frequently asked questions

Will force quitting an app corrupt my files?

It can. Force quitting skips the app's normal save-and-close sequence, so any unsaved changes in that app are lost. For apps that auto-save (like Pages or TextEdit in Auto Save mode), the last auto-saved state is usually intact. For apps without auto-save, assume anything unsaved since your last explicit save is gone.

Can I force quit Finder?

Yes, and it just relaunches immediately. In the ⌘⌥Esc dialog, select Finder — the button says "Relaunch" instead of "Force Quit," but it does the same thing. This is useful when Finder is misbehaving.

Is there a way to prevent apps from freezing?

Not a single fix, but a few things help: keeping macOS updated (many freezes are bugs that get patched), keeping free disk space above 10–15% of total (low disk causes strange behavior), and checking Activity Monitor if a particular app freezes repeatedly to see if it is leaking memory over time.