macOS "The application can't be opened" fix that works

macOS Errors Beginner 👁 1 views 📅 May 28, 2026

Your Mac says an app can't be opened because it's damaged or from an unidentified developer. Here's the actual fix that takes 30 seconds.

Yeah, that message is annoying. You download something—maybe a legit tool like HandBrake or a little utility from GitHub—and macOS throws up a dialog that says "The application can't be opened." Or maybe it says "… is damaged and can't be opened. You should move it to the Trash." Either way, you're sitting there wondering why your computer is treating you like a criminal.

The real fix isn't digging through System Settings or disabling Gatekeeper entirely. It's a single Terminal command that clears the quarantine flag Apple stamped on the app when you downloaded it. Here's exactly what to do.

Step-by-step fix

  1. Open Terminal. You can find it in Applications > Utilities, or just hit Cmd+Space and type "Terminal."
  2. Type this command — don't hit Enter yet:
    xattr -d com.apple.quarantine 
    Make sure there's a space after 'quarantine'.
  3. Drag the app from your Applications folder (or wherever you saved it) into the Terminal window. That pastes the full path to the app. Your command should look something like:
    xattr -d com.apple.quarantine /Applications/SomeApp.app
  4. Press Enter. You won't see any success message—that's normal. If the command ran without an error, it worked.
  5. Launch the app from Finder (or Spotlight). It should open normally now.

What to expect: After you press Enter, the Terminal cursor just drops to the next line. No fireworks. If you get an error like "No such xattr", it means the app didn't have the quarantine flag—so something else is wrong (we'll cover that below). Otherwise, double-click the app and it should start right up.

Why this works

macOS has a feature called Gatekeeper. When you download an app from the internet—any internet, not just Safari—Apple stamps a hidden attribute on that file called com.apple.quarantine. This flag tells macOS: "This file came from outside the App Store, check it."

If the app isn't signed with an Apple Developer ID (or if Apple's notary service flagged it), Gatekeeper blocks it with that scary message. The xattr -d command simply deletes that flag. That's it. You're not disabling security—you're telling macOS "I've seen this app, I trust it, don't bother me again."

This works on every macOS version from Catalina through Sequoia. I've used it on dozens of machines. It's the same fix Apple's own support docs recommend for apps you downloaded yourself.

Variations and edge cases

"The application can't be opened" with no explanation

Sometimes the dialog just says that, no mention of damage or unidentified developer. Same fix. Run the xattr command above. Still blocked? Try this instead:

sudo spctl --master-disable

That turns off Gatekeeper entirely. Only do this temporarily. After you launch the app, re-enable it with:

sudo spctl --master-enable

I don't love this approach—it's a sledgehammer. But some really old or unsigned apps need it.

"The application is damaged and can't be opened"

This one's trickier. It often means the app was built for an older macOS architecture (like PowerPC) or the download was corrupted. Try the xattr command first. If it still won't open, check the app's file size in Finder. If it's suspiciously small (like under 1 MB), download it again. Corrupted downloads cause this message constantly.

Another possibility: The app is 32-bit. macOS Catalina and later do not support 32-bit apps at all. If it's a really old app, you're out of luck unless you find a 64-bit version or use a virtual machine.

Right-click > Open bypass stopped working

You might remember the old trick: right-click the app, select Open, then click Open in the dialog. That used to bypass the Gatekeeper warning once. On recent macOS versions (Ventura, Sonoma, Sequoia), this method sometimes fails—the dialog appears but doesn't let you open the app. That's when the Terminal fix becomes your only option.

Prevention

The easiest way to avoid this: download apps from the Mac App Store whenever possible. Those are pre-approved and never get flagged.

If you have to download from the web, avoid old or obscure sources. Stick to the developer's official site. Some sites re-package apps with malware, and those will trigger the damaged message because they literally are damaged (or altered).

Also, use a tool like SilentKnight or BlockBlock to monitor what's running on your machine. I'm not saying you should trust every random app—just that the quarantine flag is a blunt instrument. If you know the app is legitimate, removing that flag is safe and fast.

One last thing: if you're a developer distributing apps, get them notarized by Apple. It costs nothing and saves your users this headache. Here's Apple's guide: Notarizing macOS software.

That's the fix. No System Settings hunting, no reinstalling, no disabling security permanently. One Terminal command, and you're done.

Was this solution helpful?