How it works
You sign your software with a Developer ID certificate, upload it to Apple’s notary service, and wait for a verdict. The service scans for malicious content and checks code-signing requirements. If nothing is wrong, it returns a ticket and also publishes the ticket online where Gatekeeper, the macOS download check, can find it. You then staple the ticket to your file so it works even when the Mac is offline.
Apple’s requirements, as of November 2026: sign every executable with a Developer ID certificate, enable the hardened runtime, include a secure timestamp, and link against the macOS 10.9 or later SDK. Software built after 1 June 2019 and distributed with Developer ID must be notarized to run on macOS 10.15 and later.
The commands
These are the commands in Apple’s documentation, with MyApp.zip standing in for your file:
xcrun notarytool submit MyApp.zip --keychain-profile "notarytool-password" --wait
xcrun notarytool log <submission-id> --keychain-profile "notarytool-password" developer_log.json
xcrun stapler staple "MyApp.app"
With --wait, notarytool returns when the service finishes, with a status such as Accepted or Invalid. The log is JSON and lists each issue with a path and severity. Apple says to read it even when notarization succeeds, because it may hold warnings. Apple also says most software completes within 5 minutes and 98 percent within 15.
Edge cases that cost time
- You cannot staple a ZIP. Notarize the ZIP if you like, but staple each item inside it, then build a new ZIP from the stapled items.
- Standalone binaries cannot be stapled. The ticket exists online, but there is nothing to attach it to.
- Containers. The service accepts disk images (UDIF), signed flat installer packages and ZIP archives, and processes nested containers. A signed package inside a disk image gets its own ticket.
- Modified after signing. Changing anything in the bundle after signing makes notarization fail with an invalid signature.
- Wrong certificate. Only Developer ID certificates work. A Mac App Distribution or self-signed certificate fails.
Notarization versus code signing versus App Review
| Code signing | Notarization | App Review | |
|---|---|---|---|
| Done by | You, with a certificate | Apple’s automated notary service | Apple, for the Mac App Store |
| Proves | Who published it, unchanged since signing | Apple scanned this build | The app meets Store rules |
| Needed for | Everything | Developer ID software | Store distribution |
Code signing is a prerequisite for notarization, not a substitute.
How Clavem handles it
Clavem does not notarize or sign anything. It stores the files you upload to a release, up to 5 GiB each, and serves them to buyers as attachments through signed links. So notarize and staple first, then upload the .dmg or .pkg. If you upload a ZIP, staple the app inside before zipping. Platform labels such as macos are up to 40 characters and not a fixed list; the releases and downloads documentation covers the rest. For the full Mac distribution picture, see distributing Mac apps and notarization.
Questions
Is notarization the same as App Store review?
No. Apple's own documentation says notarization is not App Review. It is an automated service that scans for malicious content and code-signing problems, and it applies to software you distribute yourself.
Do I notarize every update?
Yes, every build you distribute. Each submission produces tickets for that build, so a new version needs its own notarization and stapling before you publish it.