You download an app, double-click it, and instead of opening, your Mac throws up a wall: “can’t be opened because it is from an unidentified developer.” No install button, no obvious way around it — just Done or Move to Trash. It’s one of the most common macOS headaches, and it trips up longtime Mac users just as often as people switching over from Windows.

The good news: your Mac isn’t broken, and the app probably isn’t dangerous. This is Apple’s Gatekeeper doing exactly what it’s designed to do.

Quick answer: To allow apps from unidentified developers Mac, try opening it once, click Done on the warning, then go to System Settings > Privacy & Security, scroll to the Security section, and click Open Anyway next to the blocked app’s name. Confirm with your password if asked, then open the app again.

What “Unidentified Developer” Actually Means

Gatekeeper is the built-in macOS feature that checks every app the first time you try to run it. It’s not scanning for viruses in real time — it’s checking whether the app carries a valid Developer ID signature and whether it’s been through Apple’s notarization process, where Apple screens the software for known malicious code before letting it circulate.

When an app is unsigned, or signed by a developer who hasn’t enrolled in Apple’s paid developer program, macOS labels it “unidentified” and refuses to launch it without your explicit override. That label gets applied to a huge range of software — indie tools, open-source utilities, internal company apps, older abandoned projects — most of which is completely fine. It also, occasionally, catches genuinely malicious software, which is the whole point of the friction.

It’s worth separating two different warnings people often lump together. “Unidentified developer” means Apple simply doesn’t recognize who made it. A separate message — “this app is damaged and can’t be opened” — usually means something else: a broken download, or a quarantine flag that needs clearing, which we’ll cover in the Terminal section below.

How to Allow Apps From Unidentified Developers Mac

Apple has tightened this workflow gradually over the past several macOS releases, and starting with macOS Sequoia, the old right-click shortcut mostly stopped working as a way to bypass the warning. Here’s the method that works across current macOS versions:

1. Double-click the app to try opening it normally.
2. When the warning appears saying the app “cannot be opened because it can’t be verified” or “is from an unidentified developer,” click Done (not Move to Trash).
3. Open the Apple menu and choose System Settings.
4. Click Privacy & Security in the sidebar.
5. Scroll down to the Security section. You should see a message like “‘App Name’ was blocked to protect your Mac,” with an Open Anyway button next to it.
6. Click Open Anyway.
7. You may be asked to confirm again or enter your Mac’s admin password — do so, then the app will launch.

One detail that surprises a lot of people: the Open Anyway button only appears after you’ve tried and failed to open the app at least once. Going straight to Privacy & Security without that first launch attempt often shows nothing there.

Quick takeaway: Try to open the app first, dismiss the warning, then go find the Open Anyway button in Security settings. Skipping the first step is the most common reason people can’t find the option.

Method Differences by macOS Version

The steps above work for current macOS releases, but the exact UI has shifted more than once, and older guides floating around the web can send you looking for buttons that no longer exist. Here’s how it breaks down:

macOS Version	Method
Sierra and earlier	System Preferences > Security & Privacy > General tab had a visible “Anywhere” radio button
Sierra through Sonoma	Right-click (Control-click) the app, choose Open, confirm in the dialog — no need to visit Settings
Sequoia and later	Right-click no longer bypasses the warning reliably; you must dismiss the initial alert, then click Open Anyway inside System Settings > Privacy & Security > Security
Sequoia 15.1.1 and later, Tahoe	Same Open Anyway flow, but the button now only shows up for the most recently blocked app — if you tried opening several unsigned apps, only the last one gets a button

If you’re on an older Mac still running Sierra through Sonoma, the right-click method is still faster and worth trying first. On Sequoia or Tahoe, skip straight to the System Settings method above.

Using Terminal to Allow Unsigned Apps

For people who install a lot of unsigned software — developers, IT admins, power users — clicking through System Settings for every single app gets old fast. Terminal offers two different approaches, and they solve two different problems.

Removing the quarantine flag from a specific app. Every file downloaded from the internet gets tagged with a quarantine attribute, which is what triggers the Gatekeeper warning in the first place. You can strip that tag from a single app:

1. Open Terminal (Spotlight search, then type Terminal).
2. Type xattr -cr (with a trailing space) but don’t press Return yet.
3. Drag the app from Finder directly into the Terminal window — this pastes its file path.
4. Press Return.
5. Try opening the app again.

This is a targeted fix: it clears the flag on that one app without touching your Mac’s overall security posture.

Disabling Gatekeeper system-wide. This is the blunter option, and on Sequoia and later it doesn’t work the same way it used to.

1. Open Terminal.
2. Type sudo spctl --master-disable and press Return.
3. Enter your admin password (you won’t see characters as you type — that’s normal).

On macOS Sequoia and newer, running this command alone won’t finish the job — you’ll get a message saying the change “needs to be confirmed in System Settings.” After running the command, go to System Settings > Privacy & Security > Security, and you’ll now see an Anywhere option under “Allow applications from,” which wasn’t visible before. Select it to complete the change.

To reverse this later, run sudo spctl --master-enable in Terminal.

Is It Actually Safe to Do This?

Here’s the honest answer: it depends entirely on where the app came from, not on the fact that it’s unsigned.

An unidentified developer label doesn’t mean malware. Plenty of legitimate software falls into this category — command-line tools distributed on GitHub, niche utilities from solo developers who don’t want to pay Apple’s $99/year developer fee, in-house corporate apps, or older software whose signing certificate expired years ago. None of that is inherently risky.

What actually matters is the source. If you downloaded the app from the developer’s own website, a well-known open-source repository, or a link someone you trust sent you, allowing it is usually low-risk. If it came from a random ad, a torrent, or an email attachment you weren’t expecting, the unidentified-developer warning is exactly the moment to stop and reconsider — this is precisely the scenario Gatekeeper exists to flag.

Two safety habits worth keeping regardless: use the per-app Open Anyway method rather than disabling Gatekeeper system-wide whenever possible, since it limits your exposure to just the one app you’ve vetted. And if you do disable Gatekeeper globally for a specific install, re-enable it afterward rather than leaving your Mac permanently open to unsigned software.

Troubleshooting: No “Open Anyway” Button, or Still Blocked

A few things trip people up here:

• No Open Anyway button appears. This almost always means you haven’t tried opening the app yet in this session, or too much time has passed since you tried. Double-click the app again first, dismiss the alert, then go straight to Privacy & Security without navigating away.
• The button disappears after you open a different app. On current macOS versions, only the most recently blocked app gets an Open Anyway button. If you’re trying to allow several unsigned apps, do them one at a time, fully completing each before moving to the next.
• The app says it’s “damaged” instead of “unidentified.” This is a different problem, usually caused by quarantine metadata Apple’s process didn’t like, or a corrupted download. Try the xattr -cr Terminal method above, or re-download the app from the source.
• Terminal says “operation not permitted.” This can happen if System Integrity Protection is blocking the command on certain protected system paths. It generally doesn’t affect apps in your Applications or Downloads folder, so double-check you’re targeting the right file.

Turning Gatekeeper Protection Back On

If you disabled Gatekeeper system-wide using the Terminal method, it’s worth switching it back once you’re done installing whatever you needed:

1. Open Terminal.
2. Run sudo spctl --master-enable and enter your password.
3. Open System Settings > Privacy & Security > Security and confirm “Allow applications from” is set back to App Store or App Store and Identified Developers.

This restores the default protection level without affecting any apps you’ve already allowed individually — those exceptions stay in place.

Bottom Line

The “unidentified developer” warning is a speed bump, not a verdict. For a one-off app you trust, the System Settings > Privacy & Security route is the safest and fastest fix on any current Mac. Reach for Terminal only if you’re regularly installing unsigned tools and want a faster workflow — and if you do disable Gatekeeper globally, make a habit of turning it back on once you’re finished.

WANT MORE TIPS LIKE THIS? OUR FULL GUIDE HUB TO DISCOVER MORE.

FAQ Section

Is it safe to open apps from unidentified developers on Mac?

It depends on the source, not the label itself. Apps from a developer’s own site or a trusted repository are usually fine. Apps from unexpected downloads, ads, or unfamiliar links deserve more caution before you override the warning.

Why can’t I right-click and choose Open anymore?

Starting with macOS Sequoia, Apple removed the right-click bypass for most unsigned apps. You now need to dismiss the initial warning, then click Open Anyway inside System Settings > Privacy & Security.

How do I permanently allow apps from anywhere on my Mac?

Run sudo spctl --master-disable in Terminal, then go to System Settings > Privacy & Security > Security and select Anywhere under “Allow applications from.” This disables Gatekeeper system-wide.

How do I re-enable Gatekeeper after allowing an app?

Run sudo spctl --master-enable in Terminal, then confirm the setting has reverted to App Store or App Store and Identified Developers in System Settings.

Why is there no Open Anyway button in my Security settings?

You likely haven’t tried opening the app in the current session, or too much time passed since your last attempt. Double-click the app, dismiss the warning, then check Security settings immediately.

What’s the difference between “unidentified developer” and “app is damaged”?

“Unidentified developer” means the app lacks Apple’s Developer ID signature. “Damaged” usually points to a corrupted download or quarantine metadata issue, which the xattr -cr Terminal command can often resolve.

Does allowing one unsigned app weaken my Mac’s overall security?

No — using Open Anyway for a single app creates an exception only for that app. Your Mac’s default Gatekeeper protection stays active for everything else, unlike the system-wide Terminal disable.

Do I need a developer account to get around this warning?

No, that’s only relevant if you’re the one distributing software. As a user, you don’t need any developer account to allow an app you’ve downloaded — just admin access to your own Mac.