Build native Windows desktop applications with Bini.js.
Bini.js builds native Windows desktop applications using Tauri v2. Your React app is wrapped in a WebView2 binary, providing a native experience with full system access. The desktop target covers Windows, macOS and Linux from one src-tauri/.
Windows executable (.exe) with Authenticode signing
Authenticode signing support for trusted distribution
Full access to Windows APIs via Tauri
Building Windows desktop apps requires different tools depending on your operating system. See the section for your OS below.
.exe directly from macOS or Linux. Tauri v2 has no supported local cross-compilation path for Windows. The recommended way is GitHub Actions on a windows-latest runner, described in each section below.On Windows you can scaffold, develop, and build the app entirely on your own machine - no CI required.
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 tauri:dev to open your app in a native window, then tauri:build to produce the executable and installer:
npm run doctor to check your toolchain, and create-bini-app add desktop to add the desktop target to an existing project.A native Windows .exe cannot be produced on macOS - Tauri relies on Windows-only toolchains (MSVC, WebView2, WiX/NSIS), and bundles are not cross-compiled. The Tauri team's recommendation is to build Windows apps on a windows-latest runner in CI.
Install Node.js 20.19.0 or higher and Git. Git comes with the Xcode command line tools - run xcode-select --install if you do not have it yet.
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..exe / .msi from the Releases page).windows-latest is the supported path.A native Windows .exe cannot be produced on Linux - Tauri relies on Windows-only toolchains (MSVC, WebView2, WiX/NSIS), and bundles are not cross-compiled. The Tauri team's recommendation is to build Windows apps on a windows-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..exe / .msi from the Releases page).windows-latest is the supported path.Running tauri:dev opens your app in a native desktop window for the OS you are on. To develop the Windows app in a native window, run it on a Windows machine with the requirements installed (see the Windows section):
This launches your app in a native window with:
tauri:dev runs the macOS/Linux desktop app, not the Windows one. Use web development while iterating, and let CI build the Windows binary.Build a distributable desktop executable with tauri:build. On Windows this runs locally; on macOS and Linux, Windows builds run in GitHub Actions (see those sections).
The build outputs land in src-tauri/target/release/bundle/:
nsis/*.exe - NSIS installer (recommended for distribution)msi/*.msi - WiX MSI installerrelease/my-app.exe - The raw executable (before bundling)Bini.js supports Authenticode code signing for Windows binaries. Set it up or redo it at any time with create-bini-app sign - either interactively or with a single command. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires an Authenticode certificate. If you do not have one, purchase it from a trusted Certificate Authority (CA).
.pfx code signing certificate from a trusted CA such as DigiCert, Sectigo, or GlobalSign.To sign the .exe locally on your Windows machine, import your .pfx certificate into your local certificate store:
If you want the GitHub Action runner to sign the .exe automatically, you must provide the certificate 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.windows.conf.json, which Tauri merges automatically on Windows only, so the committed tauri.conf.json never points at a certificate that only exists on your machine:
To sign the Windows build in GitHub Actions, you must add your certificate as a repository secret. bini-deploy does not upload secrets automatically. You must add them manually:
WINDOWS_CERTIFICATE with the base64-encoded string of your .pfx file.WINDOWS_CERTIFICATE_PASSWORD with the password for your certificate..env.signing, the .pfx, or tauri.windows.conf.json.Once you have a signed installer (.exe or .msi), you can distribute it. Depending on your goals, you have three options:
.msi or .exe on your website or GitHub Releases. This is the most common option for desktop apps.To publish on the Microsoft Store, you need an MSIX package and a Partner Center account. See the Microsoft Store publishing guide for the specific steps.
If you are distributing directly, upload the signed .exe or .msi from src-tauri/target/release/bundle/ to your website or GitHub Releases. Users can then download and install the app manually.
For command-line installs, you can submit your installer to Winget (Microsoft's package manager) or Chocolatey (a community package manager). Users install your app with a command like winget install MyApp or choco install my-app.
Build a native macOS app with Developer ID signing and notarization.
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 Windows desktop applications with Bini.js.
Bini.js builds native Windows desktop applications using Tauri v2. Your React app is wrapped in a WebView2 binary, providing a native experience with full system access. The desktop target covers Windows, macOS and Linux from one src-tauri/.
Windows executable (.exe) with Authenticode signing
Authenticode signing support for trusted distribution
Full access to Windows APIs via Tauri
Building Windows desktop apps requires different tools depending on your operating system. See the section for your OS below.
.exe directly from macOS or Linux. Tauri v2 has no supported local cross-compilation path for Windows. The recommended way is GitHub Actions on a windows-latest runner, described in each section below.On Windows you can scaffold, develop, and build the app entirely on your own machine - no CI required.
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 tauri:dev to open your app in a native window, then tauri:build to produce the executable and installer:
npm run doctor to check your toolchain, and create-bini-app add desktop to add the desktop target to an existing project.A native Windows .exe cannot be produced on macOS - Tauri relies on Windows-only toolchains (MSVC, WebView2, WiX/NSIS), and bundles are not cross-compiled. The Tauri team's recommendation is to build Windows apps on a windows-latest runner in CI.
Install Node.js 20.19.0 or higher and Git. Git comes with the Xcode command line tools - run xcode-select --install if you do not have it yet.
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..exe / .msi from the Releases page).windows-latest is the supported path.A native Windows .exe cannot be produced on Linux - Tauri relies on Windows-only toolchains (MSVC, WebView2, WiX/NSIS), and bundles are not cross-compiled. The Tauri team's recommendation is to build Windows apps on a windows-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..exe / .msi from the Releases page).windows-latest is the supported path.Running tauri:dev opens your app in a native desktop window for the OS you are on. To develop the Windows app in a native window, run it on a Windows machine with the requirements installed (see the Windows section):
This launches your app in a native window with:
tauri:dev runs the macOS/Linux desktop app, not the Windows one. Use web development while iterating, and let CI build the Windows binary.Build a distributable desktop executable with tauri:build. On Windows this runs locally; on macOS and Linux, Windows builds run in GitHub Actions (see those sections).
The build outputs land in src-tauri/target/release/bundle/:
nsis/*.exe - NSIS installer (recommended for distribution)msi/*.msi - WiX MSI installerrelease/my-app.exe - The raw executable (before bundling)Bini.js supports Authenticode code signing for Windows binaries. Set it up or redo it at any time with create-bini-app sign - either interactively or with a single command. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires an Authenticode certificate. If you do not have one, purchase it from a trusted Certificate Authority (CA).
.pfx code signing certificate from a trusted CA such as DigiCert, Sectigo, or GlobalSign.To sign the .exe locally on your Windows machine, import your .pfx certificate into your local certificate store:
If you want the GitHub Action runner to sign the .exe automatically, you must provide the certificate 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.windows.conf.json, which Tauri merges automatically on Windows only, so the committed tauri.conf.json never points at a certificate that only exists on your machine:
To sign the Windows build in GitHub Actions, you must add your certificate as a repository secret. bini-deploy does not upload secrets automatically. You must add them manually:
WINDOWS_CERTIFICATE with the base64-encoded string of your .pfx file.WINDOWS_CERTIFICATE_PASSWORD with the password for your certificate..env.signing, the .pfx, or tauri.windows.conf.json.Once you have a signed installer (.exe or .msi), you can distribute it. Depending on your goals, you have three options:
.msi or .exe on your website or GitHub Releases. This is the most common option for desktop apps.To publish on the Microsoft Store, you need an MSIX package and a Partner Center account. See the Microsoft Store publishing guide for the specific steps.
If you are distributing directly, upload the signed .exe or .msi from src-tauri/target/release/bundle/ to your website or GitHub Releases. Users can then download and install the app manually.
For command-line installs, you can submit your installer to Winget (Microsoft's package manager) or Chocolatey (a community package manager). Users install your app with a command like winget install MyApp or choco install my-app.
Build a native macOS app with Developer ID signing and notarization.
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.