App Is Damaged and Can’t Be Opened on Mac: The Real Fix

You double-click the app, and instead of opening, macOS throws up a dialog: “App is damaged can’t be opened Mac. You should move it to the Trash.” There’s even a helpful little Trash button, practically daring you to delete something you just downloaded.

Before you do that — don’t. In the vast majority of cases, the app isn’t damaged at all.

Quick answer: This message almost always comes from Gatekeeper, macOS’s built-in security check, not from actual file corruption. It appears when an app hasn’t been notarized by Apple or carries a quarantine flag from being downloaded outside the App Store. The fix is usually a one-line Terminal command, not a redownload.

Why macOS Says an App Is “Damaged” (It Usually Isn’t)

Here’s what’s actually going on under the hood. Every file you download from a browser gets tagged with an extended attribute called com.apple.quarantine. When you try to open that file, Gatekeeper checks it: Is it code-signed by an identified developer? Has Apple notarized it? Does the signature match what was submitted?

If any of those checks fail — or if macOS simply can’t verify them — it doesn’t say “unsigned” or “not notarized.” It says “damaged.” That wording has confused Mac users for years, and honestly, it’s a poor choice on Apple’s part. The dialog is a security decision dressed up as a corruption warning.

The safe approach is to make a per-app trust decision rather than assume the download broke: confirm the app’s source first, then use the supported per-app override, and only then consider the targeted Terminal fix. That’s the order this guide follows too.

Newer macOS releases have tightened this further. On macOS Tahoe (26), Gatekeeper enforcement got stricter, and you might see slightly different wording — “damaged” in some cases, “Apple cannot check it for malicious software” in others. Same underlying mechanism, different phrasing.

Common triggers:

• Downloading directly from a developer’s website instead of the App Store
• Copying an app via USB drive, external disk, or network share (quarantine can travel with it)
• An older app that predates current code-signing requirements
• A 32-bit app trying to run on a modern 64-bit-only macOS
• A genuinely incomplete or corrupted download (rare, but it happens — more on that below)

Quick takeaway: If the app came from a source you trust — the developer’s real site, a colleague, your own backup — this is a trust prompt, not proof of a broken file.

Step 1: Try “Open Anyway” First

Before touching Terminal, check the supported, no-command path:

1. Open System Settings > Privacy & Security.
2. Scroll down to the Security section. If macOS blocked the app recently, you’ll see a line like “[App Name] was blocked from use because it is not from an identified developer” (or similar).
3. Click Open Anyway.
4. Try launching the app again — you’ll usually get one more confirmation dialog, then it opens normally.

This works for a lot of cases, especially apps downloaded straight from an App Store, but blocked once on first launch. If you never see this option, or the app still throws the “damaged” error afterward, move to the Terminal fix.

Step 2: Clear the Quarantine Flag With Terminal

If “Open Anyway” doesn’t appear or doesn’t help, the app almost certainly still has that quarantine attribute attached. You can remove it directly:

1. Open Terminal (Spotlight: Cmd + Space, type “Terminal”, hit Enter).
2. Type the command below, but don’t press Enter yet:

   sudo xattr -cr

(note the trailing space) 3. Drag the app icon from Finder directly into the Terminal window. This auto-fills the full path, so you don’t have to type it by hand — e.g., /Applications/YourApp.app. 4. Press Enter, then type your Mac login password when prompted. You won’t see characters appear as you type — that’s normal, just type it and press Enter. 5. Try opening the app again.

The -cr flags clear all extended attributes recursively, which removes the quarantine tag along with anything else that might be flagged. This is the single most effective fix reported across nearly every Mac troubleshooting source, and it works because you’re not disabling security — you’re just telling macOS “I’ve already vetted this specific app.”

Only do this for software whose origin you actually trust. If you’re not sure where an app really came from, clearing quarantine on it is not the move — see the next section.

The One Command You Should Never Run

You’ll occasionally see advice to run:

sudo spctl --master-disable

This turns off Gatekeeper system-wide, for every app, permanently — not just the one giving you trouble. Don’t do this. It removes a security layer for your entire Mac indefinitely, and there’s essentially never a good reason to trade blanket protection for convenience on one app.

It’s also worth remembering that “trusted” isn’t the same as “safe by default.” Even legitimate, well-known apps have been compromised in the past — a widely cited example is the Transmission BitTorrent client, which shipped a malware-infected version in 2016 despite being a long-trusted, legitimate app. The lesson isn’t “never trust anything” — it’s “verify the source before you override a security check, every time,” even for apps you’ve used before.

When the App Is Actually Corrupted

Sometimes — less often than people assume, but it does happen — the file really is broken, and no Terminal command will fix it. Signs of a genuinely bad download:

• The installer or app file size is noticeably smaller than what the developer lists
• The quarantine-removal command runs successfully but the app still crashes or refuses to launch
• Multiple, unrelated errors appear (not just the “damaged” dialog)

This typically happens from an interrupted download: a dropped Wi-Fi connection, a server timeout mid-transfer, or a browser hiccup. macOS receives a partial file, and no attribute change will complete a file that isn’t actually whole.

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

What to do:

1. Delete the incomplete copy.
2. Re-download from the original, official source — ideally over a stable connection.
3. If a checksum (SHA-256 or similar) is published by the developer, compare it against your downloaded file before installing.
4. If the same “damaged” error reappears after a clean re-download, it’s back to a Gatekeeper/quarantine issue, not corruption — go back to Step 2.

Apple Silicon, Old Apps, and Other Edge Cases

A few situations that look like the same error but have slightly different roots:

• Old, unmaintained apps. Software last updated years ago may predate current code-signing and notarization requirements entirely. The quarantine fix still usually works, but if the developer never resumed updating it, you may hit this every time you re-download.
• 32-bit software. macOS Catalina (2019) and every version since dropped 32-bit app support completely. If that’s the real issue, no amount of xattr or “Open Anyway” will help — the app needs a 64-bit update from the developer, or it simply won’t run on modern macOS.
• Apple Silicon (M-series) vs. Intel builds. Occasionally an Intel-only app run through Rosetta throws confusing errors that get misread as “damaged.” Check Activity Monitor or the app’s “Get Info” panel for architecture details if this pattern shows up.

---

Quick recap: try Open Anyway → if that fails, clear quarantine with sudo xattr -cr → never run spctl --master-disable → if it’s still broken after a clean re-download, it’s a real compatibility or corruption issue, not Gatekeeper.

If you’ve gone through all of this and the app still won’t launch, the safest next step is contacting the developer directly — a persistent failure after a verified clean download usually points to something on their end, not yours.

WANT MORE TIPS LIKE THIS? SEE MORE SOFTWARE TIPS TO DISCOVER MORE.

FAQ Section of App Is Damaged Can’t Be Opened Mac

Q1: Is my Mac app actually corrupted when it says “damaged”?

Usually not. The message almost always comes from Gatekeeper flagging an unsigned, non-notarized, or quarantined file — not from real file corruption. Genuine corruption is possible but far less common than the wording suggests.

Q2: How do I remove the “damaged” warning without deleting the app?

Open Terminal and run sudo xattr -cr /path/to/App.app, entering your Mac password when prompted. This clears the quarantine attribute so macOS stops blocking the app, without touching the file itself.

Q3: Why does this happen more on M1/Apple Silicon Macs?

Apple Silicon Macs enforce notarization and code-signing checks more strictly than older Intel Macs did, so apps that skated by before are now more likely to get flagged, especially if they haven’t been updated recently.

Q4: Is it safe to run the quarantine-removal command?

Yes, if you trust the app’s source — the developer’s official site, the App Store, or someone you personally know. It’s not safe to apply blindly to software from an unknown or suspicious source.

Q5: Should I ever disable Gatekeeper completely?

No. Running sudo spctl --master-disable turns off app verification for your entire Mac indefinitely. Fix the specific app instead; don’t remove protection for everything else on your system.

Q6: What if the app still won’t open after clearing quarantine?

Delete it and re-download from the original source — the download itself may have been incomplete. If it fails again with the same error after a clean download, the app may be genuinely outdated or incompatible with your macOS version.

Q7: Does this affect apps from the Mac App Store too?

Occasionally, yes — usually right after a macOS update changes verification requirements. The “Open Anyway” option in System Settings > Privacy & Security resolves most App Store cases without needing Terminal.

Q8: What does the quarantine attribute actually do?

It’s a small tag (com.apple.quarantine) macOS attaches to files downloaded from the internet, email, or external drives, prompting Gatekeeper to verify them before they’re allowed to run. It’s a safety check, not a sign of a bad file.