Force Quit

On this page 7

Force Quit is the macOS command that terminates an application immediately, without waiting for the app to finish its own orderly shutdown. It belongs to the core toolkit of macOS fundamentals because it is the standard recovery step when an app stops responding to input, shows the spinning wait cursor for a long time or refuses a normal Quit command.

A normal Quit asks the app to close itself, which gives it a chance to save documents, write preferences and release resources. Force Quit skips that conversation: the operating system ends the process directly, so any unsaved changes held only in memory are lost. The command is available from the Apple menu, from the keyboard shortcut Command-Option-Escape, from the Dock and from tools such as Activity Monitor and Terminal.

How Force Quit ends a process

Force Quit works by having the system deliver a termination signal to the app’s process instead of a polite quit request. When a user chooses Quit, macOS sends the app an Apple Event asking it to quit, and the app decides how to respond, which may include showing a save dialog. A hung app cannot process that event, because its main thread is blocked and its event loop no longer runs.

Underneath the graphical interface, macOS runs on the Darwin layer and the XNU kernel, which use standard Unix process signals. Force Quit from the user interface typically results in the process being killed outright, comparable to the SIGKILL signal, which a process cannot catch, block or ignore. The kernel then reclaims the process’s memory, closes its open file descriptors and removes it from the scheduler, while launchd, the parent of user processes, notes that the process has exited.

The following table summarizes the main signals and quit requests that apply when an app is closed on a Mac.

MechanismCan the app intercept itChance to save dataTypical use
Quit (Apple Event)YesYes, through save dialogsEveryday closing of apps
SIGTERMYes, if it installs a handlerLimited, depends on the appScripted or service shutdown
SIGINTYesLimitedInterrupting a Terminal program with Control-C
SIGKILL (force quit)NoNoneEnding a hung or runaway process
Ways macOS can ask a process to stop

The key point is that Force Quit acts at the process level. It does not repair the app, clear its caches or fix the underlying cause. It simply removes the stuck process so that the rest of the system and other apps can continue normally.

Ways to force quit an app on a Mac

macOS offers several entry points to Force Quit, and the right one depends on how responsive the rest of the system still is. The Force Quit Applications window lists open apps and marks hung ones as not responding, while Activity Monitor shows every process, including background helpers that do not appear in the Dock.

MethodHow to invoke itScopeBest suited for
Apple menuApple menu, then Force QuitVisible appsGeneral use when the pointer still works
Keyboard shortcutCommand-Option-EscapeVisible appsA frozen app that has keyboard focus
Dock menuOption-click or Control-click the Dock iconOne appQuickly ending a single app
Activity MonitorSelect process, then the stop buttonAll processesHelpers, background agents, extensions
Terminalkill -9 with the process ID, or killallAll processes the user may signalRemote sessions and scripted recovery
Methods for forcing an app to quit

In Terminal, kill -9 PID sends SIGKILL to one process, while killall AppName targets processes by name. Ending system processes owned by root requires administrator privileges through sudo, and that step carries far higher risk than ending an ordinary user app.

The Finder is a special case. It cannot be quit in the usual way, so the Force Quit Applications window offers a Relaunch button for it instead, which restarts the Finder and restores the desktop, windows and sidebar.

Force Quit is one rung on a ladder of recovery actions, and an experienced administrator chooses the least disruptive step that resolves the problem. A normal Quit should always come first, and a full restart or macOS Recovery should be kept for faults that affect the whole system rather than one app.

ActionWhat it affectsData riskWhen to choose it
Normal QuitOne app, orderlyLowThe app still responds to commands
Force QuitOne process, immediateUnsaved work in that appThe app is hung for more than a minute or two
Log outAll apps in the user sessionUnsaved work in all appsSeveral apps or the Finder misbehave
RestartEntire systemUnsaved work everywhereThe system itself is sluggish or frozen
Forced shutdownEntire system, abruptHighest, including disk writes in progressNothing responds, including the pointer
Recovery actions from least to most disruptive

A forced shutdown by holding the power button is not the same as Force Quit. It cuts every process at once, including the file system’s pending writes, so it should be a last resort when even Command-Option-Escape produces no window.

What happens to data and system state

The direct cost of Force Quit is loss of unsaved in-memory changes. Many modern Mac apps reduce that cost through Auto Save and Versions, which periodically write document state to disk, so a document may reopen close to its last state. Apps that do not adopt these frameworks may lose everything since the last manual save.

  • Document files usually survive intact, because the file on disk is only replaced during a save operation.
  • Preference files stored as a property list may miss recent setting changes that the app had not yet written.
  • Databases and caches inside an app can be left partially written, which some apps detect and rebuild on the next launch.
  • Saved application state may cause the app to reopen its previous windows, which can repeat the hang if a window triggers it.

After a forced termination, macOS may record a crash or hang report that is visible in the Console app under diagnostic reports. These reports show which thread was blocked and are the most useful evidence when the same app keeps freezing.

Common mistakes and better practice

Force Quit is safe for ordinary apps, yet several habits turn it into a source of new problems. The table below links frequent mistakes with their consequences and the better approach.

MistakeConsequenceBetter approach
Forcing quit after only a few secondsLost work during a normal busy periodWait one to two minutes while an app processes a heavy task
Ending unknown system processesLogout, crash loops or a frozen interfaceOnly end processes you can identify
Forcing quit during an update or installDamaged app bundle or incomplete updateLet installers and macOS update tasks finish
Repeating Force Quit on the same app dailyUnderlying fault stays unresolvedUpdate the app, check reports, remove faulty extensions
Using it as routine memory managementSlower relaunches and no real gainTrust macOS memory compression and swap
Force Quit mistakes and how to avoid them

A frequent misconception is that apps must be force quit to free memory. macOS manages memory through compression and paging, and idle apps cost little. Force Quit is a fault recovery tool, not a performance routine.

A plain-language summary

Force Quit is the emergency off switch for a single app on a Mac. Normally, when you close an app, it gets a moment to tidy up and ask whether you want to save. When an app freezes, it can no longer hear that request.

Force Quit stops the frozen app at once, a bit like pulling the plug on one appliance while the rest of the house keeps its power. The rest of the Mac continues working. The price is that anything you had not saved in that app is gone, so it is worth waiting a little before using it.

An example from practice

A video editor on a MacBook is exporting a long project when the editing app stops responding and the spinning cursor stays for over five minutes. The export progress bar has not moved, and clicking Quit in the menu does nothing.

She presses Command-Option-Escape, sees the editing app marked as not responding in the Force Quit Applications window and ends it. Activity Monitor then shows that a third-party rendering plug-in helper is still using full CPU, so she ends that helper as well.

On relaunch, the app restores the project from its automatic backup, losing about ten minutes of edits. She opens the hang report in Console, sees the plug-in named in the blocked thread, updates it and completes the export without another freeze.