简体中文
EnglishDoes electron-builder support code signing and notarization?
Updated
Yes. electron-builder supports code signing and notarization out of the box: macOS notarization and Windows Authenticode signing are both available, with the goal that users see trusted, verified apps on their platform. This means you can produce signed and notarized distribution builds without adding a separate signing toolchain to your project.
What is covered
| Platform | Capability | What it gives you |
|---|---|---|
| macOS | Notarization | Apps that pass Apple's notarization check so they open without being flagged as untrusted |
| Windows | Authenticode signing | Signed binaries that show a verified publisher identity instead of an unknown one |
Both are described as available out of the box, so signing and notarization are part of the normal build flow rather than an add-on you have to wire up yourself.
Why it matters for distribution
Unsigned or un-notarized builds create friction at the point of install:
- macOS may block or warn on an app that has not been notarized.
- Windows may show an unknown publisher warning for a binary without an Authenticode signature.
Signing and notarization are what let your users see a trusted, verified app, which is the stated outcome of these features.
How this fits the rest of the build
Signing and notarization sit alongside the other distribution features electron-builder provides:
- One command to ship — package your Electron app for macOS, Windows, and Linux with the
electron-buildercommand. - Installers and archives — it produces installers, portable builds, and distribution-ready archives.
- Auto-update —
electron-updaterhandles updates, including differential updates, staged rollouts, and multiple providers such as GitHub Releases and S3, with minimal configuration.
Because signing and notarization are built in, the same build that generates your installers can also produce the signed, notarized artifacts you ship.
What to check before you rely on it
- Credentials are still yours to supply. The feature is supported out of the box, but you need the relevant signing identity and notarization credentials for your platform accounts.
- Platform-specific requirements apply. macOS notarization and Windows Authenticode signing each have their own account and certificate prerequisites; confirm those before your first release build.
- Verify on the target platform. After building, install the artifact on macOS and Windows to confirm the app appears as trusted and verified rather than flagged.