Fixing the “app is damaged” warning on macOS
macOS will sometimes refuse a downloaded app with a line that sounds worse than the problem: the app “is damaged and can’t be opened.” I have watched people delete a perfectly ordinary utility because the sentence is scary. Sometimes the file really is damaged. Often the file is fine and the system is reacting to a quarantine flag it set when you downloaded it. This note is how I tell those two apart before I tell a reader to do anything permanent.
What the message means
Apple’s own support language treats the warning as Gatekeeper doing its job. Gatekeeper is the part of macOS that checks a downloaded app before the first open. When a browser saves a disk image, macOS attaches a quarantine attribute to the file. On first open, the system looks at the signature, the notarization, and that attribute. If something in that check fails, you get a short, unfriendly sentence. “Damaged” is the word it uses even when the more accurate word would be “not cleared.”
I am not saying every warning is a false alarm. I am saying the word is broader than a broken download. A half-written zip and a signed app with a quarantine flag can wear the same sentence. The next two sections are how I separate them. I do the cheap checks first. I do not start by turning security off, and I am not going to tell you to.
Check where the file came from
Before any Terminal command, I want the source. A developer’s own site, a vendor page you already pay, or a mirror this desk has listed on a program page are different from a forum attachment with a cheerful filename. If you cannot say where the file came from, stop. The warning is allowed to be the end of the story.
If you can name the source, check the size against the size the developer printed. A disk image that claims to be 11 MB and lands at 11 MB is not proof of anything noble, but a file that lands at a tenth of the stated size is an incomplete download. I trash those and fetch again. I do not run them “to see.”
Open the disk image and look at the app before you copy it. If the archive tool already said the archive was corrupt, believe the archive tool. That is the case where “damaged” means damaged. A second download is the fix, not a command.
Clear the quarantine flag
If the download is complete, the source is the one you meant, and macOS still says the app is damaged, the quarantine attribute is the usual culprit on utilities I cover. Apple documents the attribute as com.apple.quarantine. You can see it, and you can remove it, from Terminal. I am including the command because readers ask for the exact line, not because it is a personality.
Copy the app into Applications first, the ordinary way, by dragging it. Then, if the warning persists, this is the line I use, with the name swapped for the app in front of me:
xattr -d com.apple.quarantine /Applications/Compresto.appChange the name to match the bundle. Quotes go around the path if the name has a space. The command removes one attribute. It does not turn Gatekeeper off, it does not install a profile, and it does not make an unsigned app trustworthy. It tells the system you are taking responsibility for a file you already decided to trust. That is a smaller act than the warning makes it feel, and it is still an act. Do it on purpose.
If xattr replies that the attribute is not there, the quarantine flag is not your problem. Do not run the command a second time hoping for a different file. Go to the next section.
When Gatekeeper is right to refuse
A missing or broken code signature is a real refusal. A notarization check that fails on an app the developer claims is notarized is a real refusal. In those cases I do not “clear the flag and move on.” I write the developer, or I wait for a build that opens cleanly. The desk would rather file a late version than teach people to shrug at a bad signature.
I also stop if the app arrived through a channel the developer does not use. A mirror on this site is one the program page named. A link in a comment is not. Comments on RedTideNews are for notes about a build, not for alternate installers. If a comment offers you a “fixed” copy, ignore the comment.
System Settings still has a door for identified developers and for the App Store. I leave that door where Apple put it. This note is about one attribute on one app you meant to download. It is not a guide to loosening the Mac.
If the app still will not open
If the attribute is gone and the warning remains, I do three dull things. I restart the Mac once, because a stuck Gatekeeper decision sometimes clears on a fresh login. I download the image again from the same official source, in case the first copy was truncated in a way the size rounded past me. I check the developer’s note for a version that matches my macOS. A build aimed at a newer system can fail on an older one with a message that still says “damaged,” which is rude and also common.
If those three fail, the honest next step is the developer, not a fourth command from a stranger. Tell them the macOS version, the app version, and the exact sentence on the warning. That is the same information I would have wanted when I covered planning-board meetings: what happened, on what date, in whose words. Send it to them. If you send it here as well, I can say what the desk has already seen — and I will not pretend we have seen it if we have not.
Top