Performance guide

Mac app not responding: preserve work, quit carefully, then investigate

By LearnHubPlay · Built-in Mac tools first

Handle a frozen app with the least disruptive available action and collect a repeatable report if it happens again.

Protect what still responds

Try switching to another app. If it responds, save work there and note the frozen app’s name, document type and operation. A beachball during a known long task is different from an app that repeatedly fails at the same click. Avoid sending more commands into an app that is already struggling.

If the frozen app offers a working Save command, use it. Otherwise note the last known saved version; do not assume autosave has preserved every edit.

Try a normal quit first

Apple recommends Command-Q or the app’s Quit menu before a forced quit. A normal quit gives the application a chance to finish saving and closing resources. If it will not respond, decide whether the unsaved work justifies waiting or getting app-specific support before proceeding.

Force only the affected app when necessary

Press Option-Command-Escape, select the unresponsive app and choose Force Quit. Finder has a Relaunch option in that window. Confirm the app name carefully; closing a different app can lose unrelated work.

If the app cannot be forced to quit, Apple suggests a normal Mac restart next. A forced power-off is a last resort when the Mac cannot restart; it can interrupt other work as well. Follow Apple’s linked instructions rather than treating a forced shutdown as routine maintenance.

Reopen cautiously and check recovery

Look for the application’s document-recovery or version controls. Preserve any recovered copy before resuming edits. If a particular file triggers the freeze, test with a small non-sensitive sample instead of repeatedly opening the only working original.

When the problem returns

1. Record the app and macOS versions.
2. Write the shortest sequence that reproduces the problem.
3. Note whether it affects one document or a new test document too.
4. Check the vendor’s supported update and troubleshooting path.
5. Share a redacted report without private documents or full logs.

Use the memory and performance guides if multiple apps struggle during the same workload. Tend’s direct edition has process controls; the Mac App Store edition does not. Both editions’ boundaries are separate from the built-in macOS Force Quit workflow.

Follow new guides with RSS · Suggest a correction or topic