App Is Damaged And Can't Be Opened

On macOS, the “app is damaged and can’t be opened” alert usually means Gatekeeper blocked it; reinstall from a trusted source.

You click an app, and macOS throws the same line again and again. It feels odd, because the app worked on your last Mac, or it ran yesterday. This page walks you through the clean fixes that solve the message without turning off Mac security.

The goal is simple. Find out whether the app is truly broken, flagged, or just tagged as “downloaded,” then take the safest step that gets you back to work.

App Is Damaged And Can’t Be Opened Meaning On Mac

That alert is Gatekeeper talking. Gatekeeper checks apps you download from outside the Mac App Store. It looks for a valid Developer ID signature, and on modern macOS it also expects notarization. Apple says that if macOS detects an app was modified, damaged, or linked to known malware, your Mac may block it and may even move it to the Trash.

So the word “damaged” can mean two different things. The app might be corrupted in transit, like a half-finished download. Or the app might be fine, but macOS can’t confirm it matches what the developer signed. That mismatch is enough to stop the launch.

You can see the same wording when you open an app, an installer package, or a disk image that contains an app.

App Developer Cannot Be Verified — macOS can’t validate the developer identity, so it blocks the first launch unless you approve it.
Apple Cannot Check The App — Apple’s automated checks did not clear it, so you need a safer copy or a different app.
App Will Damage Your Computer — macOS detected known malware or a revoked signing certificate, so the app should not run.

If you see this after downloading from a random mirror site, treat it as a red flag. If you see it after pulling a fresh copy from the developer’s own site, it can still happen, usually due to quarantine flags, stale copies, or a packaging slip.

Fast Checks Before You Change Settings

Do these quick checks first. They fix a lot of cases in under five minutes, and they keep the rest of your Mac locked down.

Confirm The Source — Go back to where you got the app. Prefer the Mac App Store or the developer’s official download page.
Reboot Your Mac — A restart clears hung install helpers and refreshes security caches.
Check Your macOS Version — Older apps can fail after a major update if they rely on old components.
Check Free Disk Space — Low space can break app extraction from a .dmg or .zip.
Move The App To Applications — Drag the app into the Applications folder before you open it.

Test In Safe Mode

Safe Mode can help you spot interference from login items and security tools. If the app opens in Safe Mode but fails in a normal boot, remove recent login items and retry.

Start In Safe Mode — Shut down, then start up while holding the startup shortcut for your Mac type.
Try One Trusted App — Download, copy into Applications, then open it.
Restart Normally — If it worked in Safe Mode, remove recent login items and test again.

If the app is still blocked, don’t jump straight to Terminal tricks. Start by re-downloading the app, because a clean copy solves both real corruption and a surprising number of security-tag issues.

Fixing The Damaged App Warning After Download

This section handles the most common situation. You downloaded an app, dragged it onto your Mac, and macOS refuses to launch it.

Many “damaged” reports come from the way the app was copied. Copy the full .app into Applications before you open it.

Copy The Whole App Bundle

Drag The .app Icon — Copy the app icon, not a folder next to it.
Wait For The Copy — Let the copy finish before you eject the disk image.
Eject The Disk Image — After the copy completes, eject the .dmg so you don’t run the app from it.

If the app came in a .zip, unzip it with Finder, not a third-party extractor. Some tools rewrite permissions inside the bundle. After unzipping, move the app to Applications, then eject any disk image. Try again before you run any commands. That change fixes a lot of cases.

Fix Permissions When Installs Keep Failing

If clean downloads still fail on one Mac, check disk and folder health.

Run Disk Utility First Aid — Select your startup disk and run First Aid.
Test A New User Account — Download the app there and try opening it.

Redownload The Right Way

Delete The Old Copy — Move the app to Trash, then empty Trash so macOS won’t reuse the same bundle.
Download Again — Use Safari or the developer’s in-app downloader, not a third-party mirror.
Unzip Or Mount Once — If it’s a .zip, unzip it once. If it’s a .dmg, open it once and copy the app out.
Drag Into Applications — Place the app in Applications, not Desktop or Downloads.
Open From Applications — Double-click it there, then approve the prompt if you trust it.

Use The Built-In “Open Anyway” Path

If the app is from a developer you trust, macOS offers an approved exception flow. Try to open the app once. Then go to System Settings, open Privacy & Security, scroll, and use the Open Anyway button for that blocked app. That saves an exception for that one app, not a broad change.

Match The Symptom To The Fix

What You See	Likely Reason	Fix To Try
App was moved to Trash	Known malware flag or revoked signature	Get a fresh copy from the official developer
Same alert for one app	Corrupt download or modified bundle	Redownload, then copy into Applications
Same alert for many downloads	Quarantine or permissions issue on the Mac	Try a new user account and test there

Terminal Fixes For Apps You Trust

Sometimes the app is clean, and the block comes from a quarantine tag on the app bundle. Browsers and many download tools add a quarantine attribute so macOS can ask you before first launch. If that tag gets stuck or the bundle was copied in a weird way, you can remove the quarantine attribute on that one app.

Only do this when you are sure the app is from the developer and you checked the download location. If you’re not sure, stop and get a new copy from the Mac App Store or the developer’s site.

Quit The App — If it is half-open, force quit it.
Open Terminal — Use Spotlight, type Terminal, and open it.
Run A Quarantine Clear — Type xattr -dr com.apple.quarantine then drag the app from Applications into the Terminal window and press Return.
Try Opening Again — Launch the app from Applications.

If the command says “No such file,” the drag step likely pulled a shortcut, not the app bundle. Drag the .app itself from Applications.

Check Apple Silicon Compatibility

On Apple silicon Macs, some older apps are Intel-only. That alone can trigger odd launch errors after an update. If the developer offers a universal build, grab that. If the app is Intel-only and still maintained, install Rosetta when macOS prompts you, then retry.

When macOS Flags Malware And Blocks The App From Opening Again

Sometimes macOS blocks an app because Apple’s checks say the signing certificate is revoked, the app matches known malware, or the app bundle has been altered since signing. Apple notes that in these cases you might see a warning that the app will damage your computer or that the app is damaged, and macOS may move the app to Trash.

If you hit this path, the fix is not a bypass. The fix is a clean source and a clean version. Start over with a safe download.

A random “fix” script can hide the warning while leaving a risky app in place. If macOS moved the app to Trash, replace it with a clean build.

Get The Latest Build — Visit the developer’s official site and download the current macOS build.
Check For A Mac App Store Version — Some developers ship safer builds through the store.
Ask The Developer — If the developer can’t reproduce it, ask if their signing certificate changed.

If you need to share the error with the developer, include your macOS version, Mac model, and where you downloaded the app. Skip screenshots that show private data.

When Work Macs Or Security Tools Block The App

On a managed Mac, your company can restrict what apps can run. You might see the same “damaged” alert, even with a clean app, because the policy blocks apps that are not allowed by the device profile.

Try this simple test. Create a new user account on the Mac and download the same app there. If it runs there but not in your main account, the issue is local to your profile or permissions. If it fails for every user, a device policy or a security tool is a likely cause.

If you must run the app for work, ask for an approved installer or a signed package from your IT team. A managed Mac can block unsigned apps even when you personally trust them.

Check Privacy & Security — If the Open Anyway button is missing, a management profile may be locking it.
Check Antivirus Logs — Some tools quarantine apps right after download, which can trigger the alert.
Use An Approved Install Method — Your IT team may offer a package portal for allowed apps.

Keep The Error From Coming Back

This message is frustrating, but it’s also a signal that macOS is doing its job. A few habits cut the odds that you see it again.

Prefer Official Downloads — Get apps from the Mac App Store or the developer’s site.
Avoid Repacking Apps — Copy the app as-is. Don’t rename internal files inside the .app bundle.
Store Apps In Applications — Running apps from Downloads can trigger extra checks and odd path issues.
Update macOS — Security updates can fix false blocks and improve checks.
Keep A Clean Backup — Time Machine lets you roll back if an install breaks other apps.

If you came here because your Mac shows “app is damaged and can’t be opened” for one app, start with a fresh download and the Open Anyway path. If you see it for many files, test a new user account and then check for device restrictions.

Use the Terminal quarantine clear only for apps you trust. It can get you unstuck, but it should never be the first move when the download source is unknown.