How to force quit on a Mac: four ways, what you lose, and when to wait instead

The four ways to force quit an app on a Mac

Every Mac has four built-in ways to force quit. They all do the same thing underneath (macOS sends the app a kill signal it cannot ignore), so pick whichever one you can reach. The order below is the order to try them in, because the first one works even when a frozen app has taken over the screen and the mouse is stuck on the spinning beachball.

1. Keyboard shortcut: Option + Command + Esc. A small Force Quit Applications window opens listing every app that is running. The stuck one is usually marked (Not Responding) in red. Select it and click Force Quit. On a MacBook with a Touch Bar or no physical Esc key, the same three keys still work; Esc is top-left on every Apple keyboard.
2. Apple menu. Click the Apple logo at the top left of the screen, choose Force Quit. It opens the same window. Holding Shift while you open the Apple menu changes the item to "Force Quit [the front app]", which skips the list.
3. The Dock. Hold Option and right-click (or Control-click) the app's icon in the Dock. The usual Quit item changes to Force Quit. This is the quickest route when you already know which app is stuck and you can still move the mouse.
4. Activity Monitor. Open it from Applications, Utilities, or type its name into Spotlight. Select the app in the list, click the X (stop) button in the toolbar, then choose Force Quit. Activity Monitor is the only one of the four that also shows background helpers and processes that have no Dock icon, which matters when the thing that is stuck is not an app at all. Our Activity Monitor guide walks through what each column means.

If the frozen app is Finder, the Force Quit window shows a Relaunch button instead of Force Quit, because Finder is always running. Relaunch ends it and starts it again in a second or two. Your desktop icons vanish and reappear; nothing is lost. There is a dedicated page on what Finder is doing when it hangs.

What force quit actually does, compared with Quit

Normal Quit (Command + Q) is a polite request. macOS tells the app you want to leave, and the app runs through its exit list: ask whether you want to save, write open documents to disk, flush caches, close network connections, tell cloud services where it left off, remember which windows were open so it can restore them next time. The app decides when it is done, and only then does it go away. That is why a big app can take a few seconds to quit and why Quit is impossible when the app is frozen: a frozen app cannot run its exit list because it is not running anything.

Force quit skips every step of that. macOS stops the process where it stands, in the middle of whatever instruction it was executing, and takes its memory back. The app gets no warning and no chance to save. Three things follow from that.

• Unsaved work is gone. Anything you typed, drew or edited since the last save is lost, unless the app autosaves (more on that below).
• Files may be left half-written. If the app was in the middle of saving when you killed it, the file on disk may be incomplete. Most modern apps write to a temporary file and swap it in at the end, so the old version survives, but not every app does.
• Settings and caches may be stale. Preferences the app had changed in memory but not yet written to disk revert. Occasionally an app comes back with a corrupted cache or a stuck lock file and misbehaves on the next launch; usually a second launch sorts it out.

None of this damages macOS. Force quitting an app, even a dozen times a day, does not harm the system, the disk or the Mac. It only risks that app's unsaved data. The one process where force quit has a wider effect is WindowServer, which owns every window on screen; ending it logs you out instantly. Activity Monitor warns you first.

When it is safe to force quit, and when to wait

The spinning beachball means one thing only: the app has stopped answering the system's requests for a while. It does not say why. There are two very different reasons, and they call for opposite responses.

Busy, not frozen. The app is doing real work on its main thread and will answer again when it is done. Common cases: saving or exporting a large document, opening a big file or project, importing photos, a video editor rendering a preview, a browser tab running heavy script, Excel recalculating, Mail rebuilding a mailbox, Photoshop applying a filter, Xcode indexing. In every one of these, force quitting throws away the work in progress and you lose whatever was being saved. The tell is context: you just asked it to do something big, and the beachball started immediately after.

Actually frozen. The app has hit a bug, a deadlock or a hung network call and will never come back. The tell: it has been unresponsive for minutes with no disk or CPU activity, it froze on its own with no big task in flight, or it beachballs the moment it opens, every time.

The practical rule: give it 30 seconds, then look. Open Activity Monitor (it opens even when another app is stuck) and find the app in the CPU tab. If its CPU column is high or its disk reads and writes are climbing on the Disk tab, it is working; leave it. If CPU is near zero and nothing is changing, and it has been like that for a couple of minutes, it is hung and force quitting costs you nothing more than waiting would. "Not Responding" in Activity Monitor is the same signal as the beachball: a report that the app has not answered recently, not a diagnosis.

Two more reasons to wait before you reach for the shortcut. First, some apps show a save dialog or a "this document has unsaved changes" sheet behind the frozen-looking window; Command + Tab to the app and check. Second, a slow Mac overall (every app beachballing in turn) is not an app problem but a system one, usually memory pressure or a background process eating the CPU, and force quitting the app in front just moves the beachball to the next one. The why is my Mac so slow guide covers that case.

App not responding: what to do first

Is it safe to force quit this one right now?

Answer the questions below and you get a plain yes, wait, or no. It is the same decision tree we use for every process in the lookup, boiled down to the three things that matter: is it saving, is it still working, and is it something macOS depends on.

If the answer is "wait", set a timer for a minute and do something else. Most apps that are saving or exporting come back well inside that. If the answer is "no", it is because what you have selected is a system process rather than an app, and the right move is to log out or restart instead of killing it.

What you lose, and how to get some of it back

What survives a force quit depends on the app, and it is worth knowing before you need it.

• Apple apps with Autosave (Pages, Numbers, Keynote, TextEdit, Preview, Notes, Reminders, Freeform) save continuously in the background. Reopen the document and you are normally back where you were, give or take the last few seconds. Notes and Reminders sync to iCloud as you type, so nothing is lost.
• Microsoft Office keeps AutoRecover copies, every 10 minutes by default. After a force quit, reopen Word, Excel or PowerPoint and look for the Document Recovery pane. Files stored in OneDrive with AutoSave on are saved as you type.
• Browsers (Safari, Chrome, Firefox, Arc, Edge) all restore windows and tabs after a forced exit, either automatically or through a "Restore" or "Reopen All Windows from Last Session" item in the History or File menu. Form text you had typed into a web page is usually gone.
• Creative and developer apps vary. Final Cut Pro and Logic save projects continuously; Photoshop has a configurable autosave (Preferences, File Handling, default every 10 minutes); Figma and other web-based tools save to the server; most code editors recover unsaved buffers on relaunch.
• Everything else: assume the last manual save is what you have.

Two habits make force quit painless. Save with Command + S before you start anything heavy (a large export, a big import, a font install), because that is exactly when freezes happen. And when an app has beachballed but you can still see a document behind it, try Command + S once before you force quit; if the app is merely slow rather than hung, the save queues up and runs when it recovers.

What to do, in order, when an app stops responding

This is the sequence that loses the least work. Each step is slightly more forceful than the one before it, and most freezes resolve at step one or two.

1. Wait 30 seconds

   Take your hands off the keyboard. If you just asked the app to save, export, open or import something big, it is probably busy rather than frozen. Watch the window title bar: a progress bar or a changing document name means it is working.

2. Check for a hidden dialog

   Press Command + Tab to switch to the app, then look for a sheet or alert that is waiting for an answer (a save prompt, a permissions request, a "file is in use" message). Press Return or Escape to clear it. Also check whether a different app has put up a modal dialog that is blocking everything.

3. Try a normal Quit

   Press Command + Q, or choose Quit from the app's menu. If the app is slow rather than hung, it will save and quit cleanly. Give it another 30 seconds.

4. Look at Activity Monitor

   Open Activity Monitor from Spotlight. Find the app in the CPU tab. High CPU or rising disk activity means it is working through something; leave it a few more minutes. Near-zero CPU, no change, and "(Not Responding)" for several minutes means it is hung.

5. Force quit with Option + Command + Esc

   Select the app in the Force Quit Applications window and click Force Quit. If the keyboard shortcut does not respond, use the Apple menu, or Option-right-click the app in the Dock, or the X button in Activity Monitor.

6. Reopen and recover

   Launch the app again. Check for a recovery pane, an autosaved version, or a restore-session option. If the app freezes again immediately on launch, the problem is a document or a cache it opens at startup: hold Shift while launching (many apps skip reopening windows), or open a different document first.

7. Restart the Mac if it keeps happening

   If several apps freeze in a row or the same app hangs every few minutes, something underneath is wrong: full memory, a full disk, a runaway background process. A restart clears all of it. Our guide on whether it is safe to restart a Mac explains what you lose and what you do not.

What if Finder is the thing that is frozen?

Finder draws the desktop, the Dock's file previews and every file window, and because it is always running, macOS treats it slightly differently. In the Force Quit Applications window its button says Relaunch, not Force Quit. Click it and Finder restarts in a second or two. The desktop goes blank briefly and comes back with the same windows. No files are affected; Finder does not hold your documents open the way an app does.

Finder most often hangs for three reasons, and each has a gentler fix than relaunching. A network volume or external drive has gone away mid-operation (eject it properly, or reconnect, and Finder wakes up). A folder with tens of thousands of items is being listed in icon view with previews on (switch to list view, or let it finish). Or a cloud folder (iCloud Drive, Dropbox, Google Drive) is syncing a large batch and fileproviderd is feeding Finder updates faster than it can draw them; that one settles on its own within minutes.

If Relaunch does nothing, open Activity Monitor, select Finder, click the X, and choose Force Quit. Finder relaunches automatically. If the Dock itself is stuck too (icons do not bounce, clicks do nothing), do the same for Dock; it also restarts itself. These two are the only system processes you should ever force quit by hand, and both are designed to come back.

What if the whole Mac is frozen?

There is a difference between one app being stuck and the Mac being stuck, and it is worth checking before you reach for the power button. Can you move the mouse? Does the clock in the menu bar still tick? Does Command + Tab switch apps, or Option + Command + Esc open the Force Quit window? If any of those work, the Mac is fine and one app is hogging the screen: force quit it from the keyboard and carry on.

If the pointer is frozen, the clock has stopped and no shortcut does anything for a full minute, the Mac itself has stopped. That is rare on modern macOS and is usually a kernel panic in progress, a graphics driver hang, or a Mac that is so short of memory and disk that it cannot schedule anything. There is only one way out:

1. Give it two minutes. A Mac that is swapping heavily can look dead and then recover. Unplug any external display or dock first; a misbehaving display connection is a surprisingly common cause of a "frozen" Mac that is actually fine.
2. Hold the power button for about 10 seconds. On a MacBook that is the Touch ID key at the top right of the keyboard; on a desktop it is the physical button on the back. Keep holding until the screen goes black. On an Apple silicon Mac, keep holding past the "Loading startup options" text if it appears, or release and hold again.
3. Wait a few seconds, then press it once to start up.

A forced shutdown is exactly like force quitting every app at once: unsaved work in every open app is lost, but the system itself is not damaged. APFS, the Mac's file system, is designed to survive a power cut without corruption. On the next start, macOS may show a "your computer was restarted because of a problem" dialog with a panic report; the Details button names the process or driver that caused it, which is useful if it keeps happening.

If the whole Mac freezes regularly, the usual suspects, in order: a third-party kernel extension or driver (audio interfaces, old VPNs, virtualization tools), a failing external drive or hub, memory pressure from too little RAM for the workload, and, on older Macs, hardware. Run Apple Diagnostics (hold D at startup on Intel, or hold the power button and choose Options on Apple silicon) if you suspect the last one.

When force quitting is a symptom, not a fix

Force quit is a tool for the occasional stuck app. If you are using it every day, the freezes are telling you something, and it is almost always one of these.

• One app freezes repeatedly. It is usually a specific document, plugin or extension. Open the app with a blank document; if that is fine, the document is the problem. Disable extensions or plugins one at a time. Update the app; freezes on the current macOS are often fixed in the next point release.
• Every app freezes in turn. That is the Mac running out of something. Open Activity Monitor's Memory tab and look at the Memory Pressure graph: yellow or red means apps are being swapped to disk, and the beachballs are the swapping. Close what you are not using, or see what memory pressure means. Check free disk space too: under about 10 GB, macOS struggles to swap and everything crawls.
• Freezes started after an update. Spotlight re-indexes, Photos re-analyzes, and iCloud re-syncs after a major update, and for a day or two the Mac is busy underneath. Apps that touch the disk heavily beachball while that runs. It passes. Our page on a Mac being slow after an update has the timeline.
• The freeze comes with heat and fan noise. A thermally throttled Mac drops its clock speed and apps stall. Move it to a hard surface, close the heavy app, and see why a MacBook overheats.

Safe to Quit sits in the menu bar and shows which process is actually stuck versus busy, so you can tell the difference before you lose work rather than after.