Build native macOS desktop applications with Bini.js.
Bini.js allows you to build native macOS desktop applications using Tauri v2. Your React app is wrapped in a WKWebView binary, providing a native experience with full system access. The desktop target covers Windows, macOS and Linux from one src-tauri/.
macOS app bundle (.app) with Developer ID signing
Developer ID and notarization support
Full access to macOS APIs via Tauri
Building macOS desktop apps requires different tools depending on your operating system. See the section for your OS below.
.app directly from Windows or Linux. Tauri v2 has no supported local cross-compilation path for macOS. The recommended way is GitHub Actions on a macos-latest runner, described in each section below.On macOS you can scaffold, develop, and build the app entirely on your own machine - no CI required.
xcode-select --installCreate a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:
Or run the interactive prompt and select Desktop (Windows, macOS, Linux):
--app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.Run tauri:dev to open your app in a native window, then tauri:build to produce the app bundle:
create-bini-app sign desktop to set up Developer ID signing and notarization.A native macOS .app cannot be produced on Windows - Tauri relies on macOS-only toolchains (Xcode, code signing, notarization). The Tauri team's own recommendation is to build macOS apps on a macos-latest runner in CI.
Install Node.js 20.19.0 or higher and Git for Windows - Download.
Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:
Or run the interactive prompt and select Desktop (Windows, macOS, Linux):
--app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.Run npm run deploy and choose Desktop. bini-deploy writes .github/workflows/desktop.yml — a matrix job that builds Windows, macOS and Linux on their own GitHub runners — stages everything, and pushes to your repository:
Once pushed, the workflow runs on real windows-latest, macos-latest and ubuntu-latest runners and uploads the installers as run artifacts.
Desktop workflow run..dmg from the Releases page).macos-latest is the supported path.A native macOS .app cannot be produced on Linux - Tauri relies on macOS-only toolchains (Xcode, code signing, notarization). The Tauri team's own recommendation is to build macOS apps on a macos-latest runner in CI.
Install Node.js 20.19.0 or higher and Git with your package manager, for example sudo apt install git on Debian and Ubuntu.
Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:
Or run the interactive prompt and select Desktop (Windows, macOS, Linux):
--app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.Run npm run deploy and choose Desktop. bini-deploy writes .github/workflows/desktop.yml — a matrix job that builds Windows, macOS and Linux on their own GitHub runners — stages everything, and pushes to your repository:
Once pushed, the workflow runs on real windows-latest, macos-latest and ubuntu-latest runners and uploads the installers as run artifacts.
Desktop workflow run..dmg from the Releases page).macos-latest is the supported path.Running tauri:dev opens your app in a native macOS window. This requires a Mac with the requirements installed (see the macOS section):
This launches your app in a native macOS window with:
tauri:dev runs the Windows/Linux desktop app, not the macOS one. Use web development while iterating, and let CI build the macOS binary.Build a distributable macOS application with tauri:build. On macOS this runs locally; on Windows and Linux it runs in GitHub Actions (see those sections):
The build outputs land in src-tauri/target/release/bundle/:
macos/my-app.app - The app bundledmg/*.dmg - Disk image for distribution (recommended)my-app.pkg - Installer package (if configured)Bini.js supports Developer ID signing and notarization for macOS binaries. Set it up or redo it at any time with create-bini-app sign. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires an Apple Developer account. If you do not have one, enroll in the Apple Developer Program.
.p12 file..p12 file..p8 file) or your Apple ID and app-specific password.To sign the .app locally on your Mac, import your .p12 certificate into your login keychain:
If you want the GitHub Action runner to sign the .app automatically, you must provide the certificate and notarization credentials via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:
Signing values go into the git-ignored src-tauri/tauri.macos.conf.json, which Tauri merges automatically on macOS only, so the committed tauri.conf.json never points at a certificate that only exists on your machine:
To sign and notarize the macOS build in GitHub Actions, you must add your credentials as repository secrets. bini-deploy does not upload secrets automatically. You must add them manually:
APPLE_CERTIFICATE with the base64-encoded string of your .p12 file.APPLE_CERTIFICATE_PASSWORD with the password for your certificate.APPLE_SIGNING_IDENTITY with your identity string.KEYCHAIN_PASSWORD with a random password for the temporary keychain.APPLE_API_ISSUER, APPLE_API_KEY, and APPLE_API_KEY_P8 (or use APPLE_ID, APPLE_PASSWORD, APPLE_TEAM_ID)..env.signing, the .p12, or tauri.macos.conf.json.Once you have a signed and notarized .app or .dmg, you can distribute it. Depending on your goals, you have three options:
.dmg on your website or GitHub Releases. This is the most common option for desktop apps.To publish on the Mac App Store, you need an Apple Developer account, an App Store distribution provisioning profile, and to upload your app using Xcode or Transporter. See the App Store submission guide for the specific steps.
If you are distributing directly, upload the signed and notarized .dmg from src-tauri/target/release/bundle/dmg/ to your website or GitHub Releases. Users can then download and install the app manually.
For command-line installs, you can submit a Cask to Homebrew. Users install your app with a command like brew install --cask my-app.
Build a native Windows app with Authenticode signing and NSIS/MSI installers.
Build a native Linux app with AppImage, .deb, and .rpm bundles.
Build a native Android app with keystore signing and Play Store support.
Build a native iOS app with App Store distribution and TestFlight.
Build native macOS desktop applications with Bini.js.
Bini.js allows you to build native macOS desktop applications using Tauri v2. Your React app is wrapped in a WKWebView binary, providing a native experience with full system access. The desktop target covers Windows, macOS and Linux from one src-tauri/.
macOS app bundle (.app) with Developer ID signing
Developer ID and notarization support
Full access to macOS APIs via Tauri
Building macOS desktop apps requires different tools depending on your operating system. See the section for your OS below.
.app directly from Windows or Linux. Tauri v2 has no supported local cross-compilation path for macOS. The recommended way is GitHub Actions on a macos-latest runner, described in each section below.On macOS you can scaffold, develop, and build the app entirely on your own machine - no CI required.
xcode-select --installCreate a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:
Or run the interactive prompt and select Desktop (Windows, macOS, Linux):
--app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.Run tauri:dev to open your app in a native window, then tauri:build to produce the app bundle:
create-bini-app sign desktop to set up Developer ID signing and notarization.A native macOS .app cannot be produced on Windows - Tauri relies on macOS-only toolchains (Xcode, code signing, notarization). The Tauri team's own recommendation is to build macOS apps on a macos-latest runner in CI.
Install Node.js 20.19.0 or higher and Git for Windows - Download.
Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:
Or run the interactive prompt and select Desktop (Windows, macOS, Linux):
--app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.Run npm run deploy and choose Desktop. bini-deploy writes .github/workflows/desktop.yml — a matrix job that builds Windows, macOS and Linux on their own GitHub runners — stages everything, and pushes to your repository:
Once pushed, the workflow runs on real windows-latest, macos-latest and ubuntu-latest runners and uploads the installers as run artifacts.
Desktop workflow run..dmg from the Releases page).macos-latest is the supported path.A native macOS .app cannot be produced on Linux - Tauri relies on macOS-only toolchains (Xcode, code signing, notarization). The Tauri team's own recommendation is to build macOS apps on a macos-latest runner in CI.
Install Node.js 20.19.0 or higher and Git with your package manager, for example sudo apt install git on Debian and Ubuntu.
Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:
Or run the interactive prompt and select Desktop (Windows, macOS, Linux):
--app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.Run npm run deploy and choose Desktop. bini-deploy writes .github/workflows/desktop.yml — a matrix job that builds Windows, macOS and Linux on their own GitHub runners — stages everything, and pushes to your repository:
Once pushed, the workflow runs on real windows-latest, macos-latest and ubuntu-latest runners and uploads the installers as run artifacts.
Desktop workflow run..dmg from the Releases page).macos-latest is the supported path.Running tauri:dev opens your app in a native macOS window. This requires a Mac with the requirements installed (see the macOS section):
This launches your app in a native macOS window with:
tauri:dev runs the Windows/Linux desktop app, not the macOS one. Use web development while iterating, and let CI build the macOS binary.Build a distributable macOS application with tauri:build. On macOS this runs locally; on Windows and Linux it runs in GitHub Actions (see those sections):
The build outputs land in src-tauri/target/release/bundle/:
macos/my-app.app - The app bundledmg/*.dmg - Disk image for distribution (recommended)my-app.pkg - Installer package (if configured)Bini.js supports Developer ID signing and notarization for macOS binaries. Set it up or redo it at any time with create-bini-app sign. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires an Apple Developer account. If you do not have one, enroll in the Apple Developer Program.
.p12 file..p12 file..p8 file) or your Apple ID and app-specific password.To sign the .app locally on your Mac, import your .p12 certificate into your login keychain:
If you want the GitHub Action runner to sign the .app automatically, you must provide the certificate and notarization credentials via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:
Signing values go into the git-ignored src-tauri/tauri.macos.conf.json, which Tauri merges automatically on macOS only, so the committed tauri.conf.json never points at a certificate that only exists on your machine:
To sign and notarize the macOS build in GitHub Actions, you must add your credentials as repository secrets. bini-deploy does not upload secrets automatically. You must add them manually:
APPLE_CERTIFICATE with the base64-encoded string of your .p12 file.APPLE_CERTIFICATE_PASSWORD with the password for your certificate.APPLE_SIGNING_IDENTITY with your identity string.KEYCHAIN_PASSWORD with a random password for the temporary keychain.APPLE_API_ISSUER, APPLE_API_KEY, and APPLE_API_KEY_P8 (or use APPLE_ID, APPLE_PASSWORD, APPLE_TEAM_ID)..env.signing, the .p12, or tauri.macos.conf.json.Once you have a signed and notarized .app or .dmg, you can distribute it. Depending on your goals, you have three options:
.dmg on your website or GitHub Releases. This is the most common option for desktop apps.To publish on the Mac App Store, you need an Apple Developer account, an App Store distribution provisioning profile, and to upload your app using Xcode or Transporter. See the App Store submission guide for the specific steps.
If you are distributing directly, upload the signed and notarized .dmg from src-tauri/target/release/bundle/dmg/ to your website or GitHub Releases. Users can then download and install the app manually.
For command-line installs, you can submit a Cask to Homebrew. Users install your app with a command like brew install --cask my-app.
Build a native Windows app with Authenticode signing and NSIS/MSI installers.
Build a native Linux app with AppImage, .deb, and .rpm bundles.
Build a native Android app with keystore signing and Play Store support.
Build a native iOS app with App Store distribution and TestFlight.