How to Fix ‘App Cannot Be Opened Because It Is from an Unidentified Developer’ on Mac

Downloading an open-source utility, specialized development tool, or third-party executable on macOS only to have Finder halt you with a security alert reading: “[App Name] cannot be opened because it is from an unidentified developer” or “macOS cannot verify that this app is free from malware” prevents application launch. On macOS Sequoia, Sonoma, and Ventura, this protective barrier is enforced by Apple’s Gatekeeper subsystem. Gatekeeper verifies that applications distributed outside the Mac App Store possess a valid cryptographic signature from an Apple-registered developer and have passed Apple’s automated cloud notarization check. When an independent developer does not pay for an Apple Developer subscription or distributes unnotarized binaries, Gatekeeper quarantines the file. This guide explains how Gatekeeper works and provides safe, verified methods to bypass or resolve the warning.

Why Does macOS Block Unidentified Developer Applications?

Apple implements multiple security layers to protect macOS from malicious payloads:

  • Missing Developer ID Certificate: The application binary is completely unsigned or signed with an ad-hoc, self-generated certificate unrecognized by Apple’s trust store.
  • Lack of Apple Notarization: Even if signed, the developer has not submitted the software package to Apple’s automated notary service for malware scanning.
  • Finder Extended Quarantine Attributes: When files are downloaded via browsers like Safari or Chrome, the operating system attaches a security attribute (com.apple.quarantine) that forces Gatekeeper checks upon initial launch.
  • Gatekeeper Strict Mode Enforcement: Recent macOS updates (including macOS 15 Sequoia) removed the simple “Open Anyway” button from certain contextual dialogues, requiring explicit authorization in System Settings.

Method 1: Open via Right-Click Contextual Menu

The fastest manual override method instructs macOS to create an explicit security exception for that specific executable.

  1. Open Finder and navigate to your Applications folder (or the folder containing the downloaded application).
  2. Do not double-click the app. Instead, hold down the Control key on your keyboard and click the application icon (or right-click the icon).
  3. Select Open from the contextual menu.
  4. A new dialogue box will appear with the app icon and a warning, but this time an explicit Open button will be visible alongside Cancel.
  5. Click Open. Enter your macOS administrator password or Touch ID if prompted.
  6. macOS records this application as trusted, and subsequent launches will execute seamlessly upon normal double-clicking.

Method 2: Authorize the App in macOS System Settings

If the right-click method fails or the app was already blocked during a previous launch attempt, you can grant permission via System Settings.

  1. Attempt to launch the application once so macOS logs the security event. When the warning modal appears, click OK or Done.
  2. Click the Apple menu in the top-left corner and select System Settings.
  3. In the left-hand navigation pane, select Privacy & Security.
  4. Scroll down to the Security section.
  5. Under “Allow applications downloaded from:”, you will see a notice reading: “[App Name] was blocked from use because it is not from an identified developer.”
  6. Click the Open Anyway button directly next to this notice.
  7. Enter your administrator password or authenticate with Touch ID, then click Open in the confirmation dialogue.

Method 3: Remove the Quarantine Flag via Terminal

If an open-source development tool (such as tools installed via manual tarballs or GitHub releases) refuses to launch due to persistent quarantine metadata, removing the extended attribute resolves the blockage permanently.

  1. Open Terminal on your Mac (Cmd + Space, type Terminal, and press Return).
  2. Inspect whether the application has the quarantine flag attached:
    xattr -l /Applications/ExampleApp.app
  3. If the output displays com.apple.quarantine, execute the following command to strip the attribute recursively:
    xattr -d com.apple.quarantine /Applications/ExampleApp.app
    (Replace /Applications/ExampleApp.app with the exact path to your application).
  4. If the command returns a permission denied error, prepend sudo:
    sudo xattr -rd com.apple.quarantine /Applications/ExampleApp.app
  5. Press Return and input your administrator password. Launch the application normally from Finder.

Method 4: Verify App Integrity with codesign

Before bypassing Gatekeeper for unfamiliar utilities, verify the cryptographic integrity of the package to ensure it has not been modified or corrupted.

  1. In Terminal, check the code signature of the binary:
    codesign -dv --verbose=4 /Applications/ExampleApp.app
  2. Inspect the Authority lines to verify whether the developer name matches the expected source.
  3. Check the Gatekeeper assessment status using the spctl tool:
    spctl -a -vvv /Applications/ExampleApp.app
  4. If the tool returns rejected because it is unsigned, but you verified the source code from a trusted GitHub repository, you can proceed safely with Method 1 or Method 3.

Gatekeeper Override Comparison Matrix

Override Method Suitability Security Impact
Control-Click > Open One-off consumer apps Safe (evaluates individual file)
Privacy & Security Settings Standard GUI override Safe (requires admin password)
xattr -d com.apple.quarantine Developer tools & command-line utilities Targeted (strips download quarantine)
spctl –master-disable Never recommended Dangerous (turns off Gatekeeper completely)

Using selective Gatekeeper overrides allows you to run essential open-source and independent developer software without disabling macOS system security protections.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.