How To Force Quit An App On Mac

Tips
1

My Mac keeps freezing whenever I open a specific app and the usual close button doesn’t respond. I’m worried about losing unsaved work or damaging the system, but I need to shut this app down so I can keep working. What’s the safest, most reliable way to force quit a stuck application on macOS, and are there any keyboard shortcuts or settings I should know about to prevent this from happening so often?

2

Quick ways to kill a frozen app on Mac:

  1. Force Quit menu
  • Press Command + Option + Esc
  • A window pops up with running apps
  • Select the frozen app
  • Click Force Quit
  • Confirm
  1. Dock method
  • Right click the app icon in the Dock
  • Hold Option key
  • “Quit” changes to “Force Quit”
  • Click Force Quit
  1. Apple menu
  • Click the Apple logo top left
  • Choose “Force Quit…”
  • Same window as Command + Option + Esc
  • Pick the app and Force Quit
  1. Activity Monitor
  • Open Spotlight with Command + Space
  • Type Activity Monitor, hit Enter
  • Find the app in the list
  • Click it once
  • Click the stop sign icon at top
  • Choose “Force Quit”

About your unsaved work

  • If the app supports auto save (Pages, Numbers, many editors) your data often survives a force quit
  • If it does not, unsaved stuff is usually gone after a hard kill

To avoid freezing again

  • Update the app and macOS
  • Check free disk space, try to keep at least 10–20 GB free
  • Restart your Mac if you have not done it in a while
  • If only this one app hangs, try reinstalling it

If the whole Mac stops responding

  • Hold the power button until it shuts off
  • Wait a few seconds
  • Turn it back on
  • Do this only if keyboard shortcuts and mouse do nothing

Try Command + Option + Esc first. It is the least messy and fastest in most cases.

3

Couple extra angles on top of what @yozora already covered, since sometimes the usual tricks just don’t cut it.

1. Try to save something before killing it
If the app is half‑frozen but menus still respond, try this before force quitting:

  • Hit Command + S to brute‑save.
  • If that does nothing, try File → Save As… and change the filename/location.
    Sometimes the regular save hangs but “Save As” sneaks through.

2. Lower the pressure on your Mac first
Sometimes the app looks frozen because your whole system is choking. Before force quitting it, try:

  • Close other heavy apps first (browser with 50 tabs, looking at you).
  • Unplug extra monitors or drives if the system just spazzed out after connecting them.
  • Wait 30–60 seconds. I know, sounds dumb, but apps doing huge imports / renders often look dead but recover if you leave them.

3. Use Terminal for a more “surgical” kill
If Activity Monitor is laggy or not responding well:

  1. Open Terminal (Command + Space, type “Terminal”).
  2. Type:
    ps aux | grep -i 'appname'
    Replace appname with part of the app’s name.
  3. Note the PID number (first number after your username).
  4. Then run:
    kill PID
    If it refuses to die, use:
    kill -9 PID

This is the nuclear option. Almost no chance of unsaved work surviving, but it won’t “damage” macOS itself.

4. Check if the app is the real villain
If only this app always freezes:

  • Create a new macOS user account and launch the same app there.
    • If it runs fine in the new account, the issue is probably with prefs / caches / plugins in your main profile.
  • Try launching it in “Safe Mode”:
    • Shut down Mac.
    • Turn it on and hold the Shift key until you see the login window.
    • Open the app in Safe Mode.
      If it works in Safe Mode but not normal, some extension or background process is conflicting.

5. Reset the app’s preferences instead of reinstalling first
I slightly disagree with the “reinstall first” approach. That can be overkill. I usually try:

  • Quit the app completely (or force quit it).
  • In Finder, press Command + Shift + G and go to:
    • ~/Library/Preferences/
  • Look for files that clearly match the app name and move them out to a folder on the Desktop.
  • Relaunch the app. It will behave like a fresh install, but faster than actually reinstalling.

6. Avoid hard power‑offs unless nothing responds
Holding the power button is fine if literally everything is frozen, but:

  • Try Control + Command + Power first for a forced restart.
  • If keyboard and mouse still respond even a little, keep trying the softer options above.
    Power‑button shutdowns are unlikely to “break” your Mac, but they increase the chances of minor disk / file system issues and corrupting open files.

7. For the unsaved work paranoia
Real talk:

  • If the app is older or badly written and has no autosave, any hard kill means that unsaved work is basically gone.
  • For future sanity, switch to apps that support autosave / versioning where you can.
    • In macOS apps like Pages / TextEdit, the system quietly autosaves versions, so force quit is usually not a total disaster.
  • If this is a pro app (video / audio / design), check its autosave settings and make them more aggressive (like every 1–2 min).

Bottom line: try a quick manual save, reduce system load, then kill it as cleanly as you can. If this same app keeps freezing after a reboot and a fresh prefs reset, the problem isn’t you, the app’s just trash or broken on your setup and you’re better off replacing it than wrestling with it every day.

4

Couple of extra “force quit on Mac” tricks that haven’t been covered yet, plus some nuance where I slightly disagree with @yozora.

1. Try isolating the freeze with a second display / app layout tweak
If the app locks your whole Mac whenever a specific window or panel is open (common with design / DAW / 3D tools):

  • Disconnect external monitors, then reopen the app.
  • Change the workspace/layout to the simplest view possible and quit normally.
    Next launch, it may stop triggering the same GPU‑related freeze.

2. Use Dock & Mission Control more aggressively
If the app window is dead but macOS still responds:

  • Use Control + Up Arrow to trigger Mission Control.
  • Hover over the frozen app’s thumbnail, then click the small close icon if it shows.
  • Or right‑click the app in the Dock and choose “Force Quit”.
    This sometimes works when Command + Option + Esc takes ages to appear.

3. Disable automatic window restore for repeat offenders
If every relaunch of that app instantly re-freezes your Mac, it might be restoring a bad window/state:

  • Go to System Settings → Desktop & Dock → turn off “Close windows when quitting an application” (on older macOS: System Preferences → General → uncheck “Restore windows when quitting and re-opening apps”).
  • Then manually quit the app once when it is stable.
    After that, macOS stops trying to restore the exact last session that killed it.

4. Use Safe Boot selectively, then return to normal fast
I slightly disagree with using Safe Mode for a lot of normal work. It is great for diagnosis but not a place to stay:

  • Boot to Safe Mode, open only the problematic app.
  • If it behaves, you know some login item, extension, or helper app is the trigger.
  • Restart normally right after testing and start disabling login items one by one in System Settings → General → Login Items.
    You do not want to work long in Safe Mode since performance and drivers are limited.

5. Check crash logs to see what is actually choking
Instead of only killing the app, figure out why it is freezing:

  • Open “Console”.
  • On the left, click “Crash Reports” or search the app name.
    Look for repeating crashes that mention plugins, GPU, or specific frameworks. That is your hint which feature to avoid or remove. This is more work up front but saves you from constantly force quitting later.

6. Think about file size & corruption too
If the app only freezes on one document or project:

  • Try opening a small, new file in the same app.
    • If that is fine, the original file may be corrupt or just massive.
  • Save a copy of the big file to an external drive, then try opening it on another Mac or a different version of the app.
    Sometimes the best “force quit strategy” is not on the app but on that one cursed file.

7. About hard shutdowns vs data risk
I am a bit more relaxed than @yozora here:
If your cursor does not move, keyboard shortcuts do nothing, and even Control + Command + Power fails after 15 to 20 seconds, I would hold the physical power button rather than sit for 10 minutes hoping it recovers.
The filesystem on modern macOS is journaled and pretty resilient. The real risk is the open file, not the OS. So accept that the current unsaved work is probably gone and focus on getting back to a stable desktop fast.

8. Pros & cons of this “force quit an app on Mac” approach

Pros

  • Minimal system damage since you try gentle exits first and only escalate when necessary.
  • Helps you identify patterns (GPU / plugin / file corruption) instead of endlessly repeating force quits.
  • Works even when common tools like Activity Monitor are laggy or hidden behind full-screen frozen windows.

Cons

  • Time consuming compared to simply nuking the app every time.
  • Requires digging into settings, Console, and login items, which is more technical than a basic user might like.
  • Does not guarantee you can save unsaved work; some freezes are just fatal no matter what.

@yozora covered a lot of the “save first, kill second” and Terminal-based methods, which are solid. The above is more about making sure you do not keep ending up in the same frozen state, so you can stop living in the force quit menu and actually get work done.