Build native Linux desktop applications with Bini.js.
Bini.js allows you to build native Linux desktop applications using Tauri v2. Your React app is wrapped in a WebKitGTK binary, providing a native experience with full system access. The desktop target covers Windows, macOS and Linux from one src-tauri/.
Linux AppImage with optional signing
AppImage, .deb, and .rpm bundle support
Full access to Linux APIs via Tauri
Building Linux desktop apps requires different tools depending on your operating system. See the section for your OS below.
.AppImage directly from Windows or macOS. Tauri v2 has no supported local cross-compilation path for Linux. The recommended way is GitHub Actions on an ubuntu-latest runner, described in each section below.On Linux you can scaffold, develop, and build the app entirely on your own machine - no CI required.
Install Node.js 20.19.0 or higher, Rust via rustup, and the WebKitGTK development libraries. Pick your distribution:
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 AppImage:
create-bini-app sign desktop to set up GPG signing for your AppImage.A native Linux .AppImage can be produced on Windows, but only through CI - Tauri relies on Linux-only toolchains (WebKitGTK, GTK 3, AppImage tooling). The Tauri team's own recommendation is to build Linux apps on an ubuntu-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..AppImage from the Releases page).ubuntu-latest is the supported path.A native Linux .AppImage cannot be produced on macOS - Tauri relies on Linux-only toolchains (WebKitGTK, GTK 3, AppImage tooling). The Tauri team's own recommendation is to build Linux apps on an ubuntu-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..AppImage from the Releases page).ubuntu-latest is the supported path.Running tauri:dev opens your app in a native Linux window. This requires a Linux machine with the requirements installed (see the Linux section):
This launches your app in a native Linux window with:
tauri:dev runs the Windows/macOS desktop app, not the Linux one. Use web development while iterating, and let CI build the Linux binary.Build a distributable Linux application with tauri:build. On Linux this runs locally; on Windows and macOS it runs in GitHub Actions (see those sections):
The build outputs land in src-tauri/target/release/bundle/:
appimage/*.AppImage - Portable executable (recommended for distribution)deb/*.deb - Debian/Ubuntu packagerpm/*.rpm - Fedora/RHEL packageBini.js supports GPG signing for AppImage and RPM distribution. Create a GPG key and set it up with create-bini-app sign. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires a GPG key. If you do not have one, generate it with gpg --full-gen-key.
To sign the AppImage/RPM locally on your Linux machine, run:
If you want the GitHub Action runner to sign the AppImage/RPM automatically, you must provide the GPG key via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:
To sign the Linux build in GitHub Actions, you must add your GPG key as a repository secret. bini-deploy does not upload secrets automatically. You must add them manually:
GPG_PRIVATE_KEY with the base64-encoded string of your GPG private key.SIGN set to 1.SIGN_KEY with your GPG key ID.APPIMAGETOOL_FORCE_SIGN set to 1.TAURI_SIGNING_RPM_KEY with your ASCII-armored GPG key text..env.signing or your private key.Once you have a signed .AppImage, .deb, or .rpm, you can distribute it. Depending on your goals, you have four options:
.AppImage on your website or GitHub Releases. This is the most common option for desktop apps.To publish on Flathub, you need a Flatpak manifest. See the Flathub submission guide for the specific steps.
To publish on the Snap Store, you need a Snapcraft account and a snapcraft.yaml file. See the Snapcraft publishing guide for the specific steps.
If you are distributing directly, upload the signed .AppImage or .deb from src-tauri/target/release/bundle/ to your website or GitHub Releases. Users can then download and install the app manually.
Arch Linux users can install from the Arch User Repository (AUR). Create a PKGBUILD and submit it to the AUR.
Build a native Windows app with Authenticode signing and NSIS/MSI installers.
Build a native macOS app with Developer ID signing and notarization.
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 Linux desktop applications with Bini.js.
Bini.js allows you to build native Linux desktop applications using Tauri v2. Your React app is wrapped in a WebKitGTK binary, providing a native experience with full system access. The desktop target covers Windows, macOS and Linux from one src-tauri/.
Linux AppImage with optional signing
AppImage, .deb, and .rpm bundle support
Full access to Linux APIs via Tauri
Building Linux desktop apps requires different tools depending on your operating system. See the section for your OS below.
.AppImage directly from Windows or macOS. Tauri v2 has no supported local cross-compilation path for Linux. The recommended way is GitHub Actions on an ubuntu-latest runner, described in each section below.On Linux you can scaffold, develop, and build the app entirely on your own machine - no CI required.
Install Node.js 20.19.0 or higher, Rust via rustup, and the WebKitGTK development libraries. Pick your distribution:
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 AppImage:
create-bini-app sign desktop to set up GPG signing for your AppImage.A native Linux .AppImage can be produced on Windows, but only through CI - Tauri relies on Linux-only toolchains (WebKitGTK, GTK 3, AppImage tooling). The Tauri team's own recommendation is to build Linux apps on an ubuntu-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..AppImage from the Releases page).ubuntu-latest is the supported path.A native Linux .AppImage cannot be produced on macOS - Tauri relies on Linux-only toolchains (WebKitGTK, GTK 3, AppImage tooling). The Tauri team's own recommendation is to build Linux apps on an ubuntu-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..AppImage from the Releases page).ubuntu-latest is the supported path.Running tauri:dev opens your app in a native Linux window. This requires a Linux machine with the requirements installed (see the Linux section):
This launches your app in a native Linux window with:
tauri:dev runs the Windows/macOS desktop app, not the Linux one. Use web development while iterating, and let CI build the Linux binary.Build a distributable Linux application with tauri:build. On Linux this runs locally; on Windows and macOS it runs in GitHub Actions (see those sections):
The build outputs land in src-tauri/target/release/bundle/:
appimage/*.AppImage - Portable executable (recommended for distribution)deb/*.deb - Debian/Ubuntu packagerpm/*.rpm - Fedora/RHEL packageBini.js supports GPG signing for AppImage and RPM distribution. Create a GPG key and set it up with create-bini-app sign. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires a GPG key. If you do not have one, generate it with gpg --full-gen-key.
To sign the AppImage/RPM locally on your Linux machine, run:
If you want the GitHub Action runner to sign the AppImage/RPM automatically, you must provide the GPG key via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:
To sign the Linux build in GitHub Actions, you must add your GPG key as a repository secret. bini-deploy does not upload secrets automatically. You must add them manually:
GPG_PRIVATE_KEY with the base64-encoded string of your GPG private key.SIGN set to 1.SIGN_KEY with your GPG key ID.APPIMAGETOOL_FORCE_SIGN set to 1.TAURI_SIGNING_RPM_KEY with your ASCII-armored GPG key text..env.signing or your private key.Once you have a signed .AppImage, .deb, or .rpm, you can distribute it. Depending on your goals, you have four options:
.AppImage on your website or GitHub Releases. This is the most common option for desktop apps.To publish on Flathub, you need a Flatpak manifest. See the Flathub submission guide for the specific steps.
To publish on the Snap Store, you need a Snapcraft account and a snapcraft.yaml file. See the Snapcraft publishing guide for the specific steps.
If you are distributing directly, upload the signed .AppImage or .deb from src-tauri/target/release/bundle/ to your website or GitHub Releases. Users can then download and install the app manually.
Arch Linux users can install from the Arch User Repository (AUR). Create a PKGBUILD and submit it to the AUR.
Build a native Windows app with Authenticode signing and NSIS/MSI installers.
Build a native macOS app with Developer ID signing and notarization.
Build a native Android app with keystore signing and Play Store support.
Build a native iOS app with App Store distribution and TestFlight.