App Won’t Open on Mac? Here’s How to Fix It

You click the icon. It bounces in the Dock a few times. Then nothing. No window, no error, no app. When an app won’t open on Mac, you might also see a blunt message: “App can’t be opened because it is from an unidentified developer.” Either way, it’s annoying, and it usually isn’t a sign your Mac is dying.

Quick answer: Most apps that won’t open on Mac are blocked by macOS security (Gatekeeper), stuck on a corrupted preference file, low on system resources, or simply out of date. Force quit and restart the app first, then check Privacy & Security settings, update both the app and macOS, and reinstall if the problem persists.

Quick Takeaway

Before anything else: force quit the app (Cmd+Option+Esc), restart your Mac, and check for updates. That combination solves a surprising number of these cases in under two minutes.

Try the Quick Fixes First

Start simple. Most “won’t open” problems trace back to one of a handful of causes, and you can rule several out fast.

1. Force quit and relaunch. Press Command + Option + Escape to open Force Quit Applications. If the app is listed as “Not Responding,” select it and click Force Quit, then try opening it again.
2. Restart your Mac. This clears temporary system glitches, stuck background processes, and memory conflicts that can silently block an app from launching.
3. Check for updates — both the app and macOS. An app built for an older or newer system version than the one you’re running is a common cause of launch failures. If you got the app from the App Store, open the App Store and check Updates. If you got it elsewhere, check the developer’s site.
4. Close other apps. If your Mac has 8GB of RAM and you’re running several memory-heavy apps at once, a new app may fail to launch simply because there isn’t enough free memory. Open Activity Monitor (Applications > Utilities) and see what’s using the most memory before you troubleshoot further.

If none of that works, the cause is usually one of the more specific issues below.

“App Is Damaged and Can’t Be Opened” — the Gatekeeper Problem

This is one of the most common — and most misunderstood — errors. macOS uses a security system called Gatekeeper to check whether an app is code-signed and notarized by Apple before letting it run. If an app fails that check, or wasn’t downloaded through the App Store, macOS may refuse to open it and label it “damaged,” even when the file itself is perfectly fine.

To allow it manually:

1. Go to the Apple menu > System Settings > Privacy & Security.
2. Scroll to the Security section and set “Allow applications from” to App Store & Known Developers.
3. Try opening the app again. If macOS blocked it, you’ll usually see an option right there to open it anyway.

If that doesn’t clear it, the quarantine attribute attached to the downloaded file may be the real culprit. Open Terminal and run:

xattr -cr /path/to/YourApp.app

Replace the path with the actual location of the app (drag the app icon into Terminal after typing xattr -cr to auto-fill the path). This strips the quarantine flag macOS adds to files downloaded from the internet, and it resolves a large share of “app is damaged” errors that survive a first attempt.

If you manage a work Mac, note that an IT administrator may have locked down which apps can run at all — in that case, no local setting will fix it, and you’ll need to contact your organization’s IT support.

Corrupted Files? Reinstall the App (and Clear Its Preferences)

Sometimes the download itself is incomplete or corrupted, or a crash left behind a broken configuration file. Two things worth trying, in order:

1. Delete a corrupted preference file. Go to Finder > Go > Go to Folder, type ~/Library/Preferences/, and look for a .plist file matching the troubled app’s name (for example, com.developer.appname.plist). Move it to the Trash and relaunch the app — macOS will generate a fresh default preference file automatically.
2. Delete and reinstall the app. If the preference fix doesn’t help, delete the app entirely (note: you may lose data stored inside it), then redownload it from the App Store or the developer’s website.

This two-step order matters: reinstalling first can feel like the obvious move, but it won’t help if the actual problem is a stale preference file, and you’ll end up redoing the reinstall anyway.

Permissions and Admin Account Problems

If you’re not using an administrator account on the Mac, some apps simply won’t be allowed to launch — this is common on shared family Macs, work computers, or Macs set up with a “Standard” user account. Signs this is the cause:

• The app works fine for other users on the same Mac.
• You get a permissions or “cannot be opened” error but no Gatekeeper security prompt.
• You recently switched user accounts or the Mac was recently set up by someone else.

Fix: Ask whoever administers the Mac to grant the app permission, or log in with an admin account to test. On a personal Mac, check System Settings > Users & Groups to confirm your account type.

Apple Silicon, Rosetta 2, and Compatibility Problems

If you’re on an Apple Silicon Mac (M1, M2, M3, or later) and an older app won’t open, compatibility is worth checking before anything else. Some apps built only for Intel Macs need Rosetta 2, Apple’s translation layer, to run at all.

• Right-click the app in Finder, choose Get Info, and check whether it lists as “Application (Intel)” or requires Rosetta.
• If macOS prompts you to install Rosetta 2 the first time you launch an Intel-only app and you decline, the app simply won’t open until you install it.
• If the app hasn’t been updated in years and shows no sign of Apple Silicon support, it may genuinely no longer be compatible with current macOS — check the developer’s site for a supported alternative.

When It’s Actually a Resource Problem (RAM, CPU, Disk Space)

Sometimes an app “won’t open” because your Mac is too busy to open it. The telltale sign is the spinning rainbow wheel (the beachball) instead of an outright failure to launch.

Open Activity Monitor and check two things:

• CPU tab: if system load sits above roughly 50% with nothing demanding running, something is misbehaving in the background.
• Memory tab: if memory pressure reads in the red or yellow consistently, you’re short on RAM for what you’re trying to run.

Also check available disk space (Apple menu > About This Mac > Storage). A nearly full startup disk can prevent apps from launching correctly, since macOS needs free space for virtual memory and temporary files.

Give a slow-to-open app 10 to 15 seconds before assuming it’s stuck — some apps take a moment to load large libraries or check for updates on launch. If it still hasn’t opened after that, force quit and try again after freeing up memory or disk space.

READ MORE: Website Won’t Load in Your Browser? Here’s How to Actually Fix It

System-Level Repairs: Disk Utility and Safe Mode

If quick fixes and app-specific troubleshooting haven’t worked, the problem may sit deeper in the system.

1. Run Disk Utility First Aid. Open Spotlight (Command + Space), type Disk Utility, select your startup disk, and click First Aid to check for and repair disk errors.
2. Boot into Safe Mode. Restart your Mac and hold Shift during startup (Intel Macs) or hold the power button and select Safe Mode from the startup options (Apple Silicon Macs). Safe Mode disables non-essential software and can confirm whether a third-party extension or login item is the real cause.
3. Consider an NVRAM/PRAM or SMC reset on Intel Macs if you’re seeing broader system oddities alongside the app issue — these clear low-level settings that occasionally interfere with app launches.

When to Reinstall macOS or Contact the Developer

If you’ve worked through the steps above and the app still won’t open:

• Check the developer’s support page or contact them directly — especially for niche or specialized software, where the fix may be app-specific.
• If you bought the app recently from the App Store and no longer want it, you can request a refund through Apple.
• As a last resort, back up your data and consider reinstalling macOS. This should only be necessary if multiple apps are affected, not just one.

FOR MORE HELPFUL GUIDES LIKE THIS, OUR FULL GUIDE HUB AND EXPLORE MORE.

FAQ Section of App Won’t Open on Mac

Why does my Mac say an app can’t be opened because it’s from an unidentified developer?

macOS blocks apps that aren’t notarized by Apple through its Gatekeeper security system. Go to System Settings > Privacy & Security, and set “Allow applications from” to App Store & Known Developers, then try opening the app again.

How do I force an app to open on Mac?

Right-click (or Control-click) the app icon and choose Open, instead of double-clicking. This gives you a one-time override option that a normal double-click won’t show for unidentified-developer apps.

Why won’t apps open after I updated macOS?

Some apps aren’t compatible with a new macOS version until the developer releases an update. Check the App Store or the developer’s website for the latest version before assuming anything else is wrong.

What does “app is damaged and can’t be opened” actually mean?

It usually doesn’t mean the file is broken — it means macOS’s quarantine or Gatekeeper check failed. Running xattr -cr /path/to/App.app in Terminal clears the quarantine flag and resolves this in most cases.

Why is my Mac app frozen but won’t close?

This is typically a resource problem — the app’s main thread is stuck waiting on something. Force quit with Command + Option + Escape, then check Activity Monitor for high CPU or memory pressure.

Do I need Rosetta 2 for apps to open on Apple Silicon Macs?

Only if the app was built exclusively for Intel Macs. macOS will prompt you to install Rosetta 2 automatically the first time you try to launch such an app.

Should I reinstall the app or delete its preferences first?

Delete the preference (.plist) file first — it’s faster and often fixes the same problems a reinstall would, without losing any app data.

When should I just give up and contact the developer?

If you’ve tried force quitting, restarting, updating, reinstalling, and checking permissions without success, and the issue is isolated to one specific app, it’s time to check the developer’s support page or request help directly.