How to Forcefully Quit an Application on Mac
When an app freezes, stops responding, or just won't close through normal means, macOS gives you several ways to shut it down without restarting your entire computer. Knowing which method to use — and when — depends on how unresponsive the app is, what you were doing in it, and how comfortable you are with different parts of the system.
Why Apps Stop Responding on Mac
Before jumping to force quitting, it helps to understand what's actually happening. An app becomes unresponsive when it gets stuck in a process loop, runs out of memory to work with, or encounters a conflict with another process or system resource. macOS will often display the spinning beachball cursor as a visual indicator that something is blocking normal operation.
Sometimes an app recovers on its own within a few seconds. Other times, it's genuinely frozen and won't come back. The methods below work regardless of which situation you're in — though it's worth waiting 10–15 seconds before force quitting, especially if the app is handling a large file or complex task.
Method 1: The Force Quit Menu (Keyboard Shortcut)
The fastest route for most users is the Force Quit Applications window, opened with:
Command (⌘) + Option + Escape
This brings up a small panel listing all currently open apps. Apps that are frozen typically show (Not Responding) in red next to their name. Select the app, click Force Quit, and confirm.
This method works even when the frozen app is covering your screen, and it doesn't require you to navigate the menu bar.
Method 2: Force Quit from the Apple Menu
If you prefer using the mouse:
- Click the Apple logo (🍎) in the top-left corner of the screen
- Select Force Quit...
- Choose the unresponsive app from the list
- Click Force Quit
This opens the same Force Quit Applications window as the keyboard shortcut. It's a reliable fallback if your keyboard isn't responding properly or you simply prefer menu navigation.
Method 3: Right-Click the Dock Icon
If the app is in your Dock, you can force quit directly from there:
- Right-click (or Control-click) the app's icon in the Dock
- If the app is frozen, hold Option — the "Quit" option changes to Force Quit
- Click Force Quit
This method is quick when you can clearly see the Dock and want to avoid opening additional windows.
Method 4: Using Activity Monitor
Activity Monitor is macOS's built-in task manager and gives you the most detail about what's running on your system. This is the method to use when:
- You're not sure which process is causing a problem
- A background process (not a visible app) is consuming excessive CPU or memory
- The app doesn't appear in the standard Force Quit window
To use it:
- Open Activity Monitor via Spotlight (Command + Space, then type "Activity Monitor") or through Applications → Utilities
- Find the app or process in the list — you can sort by CPU or Memory usage to identify heavy consumers
- Select it and click the X button in the toolbar
- Choose Force Quit when prompted
Activity Monitor shows both user-facing apps and background system processes, so it's worth being cautious about force quitting anything you don't recognize.
Method 5: Terminal (Kill Command)
For users comfortable with the command line, the Terminal offers precise control using the kill command. This method is most useful when an app isn't showing up in Activity Monitor's visible list, or when you need to force-terminate a process by its ID.
The PID (Process ID) is a unique number assigned to every running process. You can find it in Activity Monitor's PID column, or by running ps aux | grep [app name] in Terminal.
The -9 flag sends an immediate, unignorable termination signal — the most forceful option available.
This approach is best suited to users who are familiar with the command line, since terminating the wrong process can cause unintended side effects.
What to Expect After Force Quitting
Force quitting an app terminates it immediately without a normal shutdown sequence. This means:
| Outcome | Details |
|---|---|
| Unsaved work is lost | Any changes made since the last save will not be recovered unless the app has autosave/autorecover features |
| Temporary files may remain | Some apps leave behind temp files; these are usually cleaned up on next launch |
| The app can relaunch normally | Force quitting doesn't damage the app itself |
| macOS may offer to reopen | Some apps prompt to restore the previous session on next launch |
Variables That Shape Your Experience
How smoothly this process goes — and which method is right for you — depends on a few things that vary from user to user:
- macOS version: The Force Quit window and Activity Monitor interface have evolved across versions. Older macOS releases may display options slightly differently.
- Apple Silicon vs. Intel: Both support all the methods above, but performance behavior and how apps handle memory differ between architectures, which can affect how often freezes occur in the first place.
- App type: Native macOS apps, web-based Electron apps, and virtualized Windows apps each behave differently under stress and respond differently to force quit signals.
- Technical comfort level: Terminal is powerful but requires knowing what you're targeting. Most users won't need it for typical app freezes.
The right method isn't the same for everyone — and even for the same person, the right method might change depending on what's frozen and how badly.