tauri build: What Really Happens

"tauri build is two jobs wearing one command: compile a release binary, then wrap it in installers people can actually double-click."

The Two Phases

Running tauri build first executes your beforeBuildCommand to produce the static frontend, then compiles the Rust core in release mode (optimized, slow to compile, small and fast to run), embeds the frontend into the binary, and finally hands off to the bundler, which produces the OS-native installer formats. The result isn't a loose executable you email — it's proper installers under src-tauri/target/release/bundle/.

Release Is a Different Animal

Everything you measured in tauri dev was a debug build. Release applies real optimization: the binary shrinks dramatically and runs faster, which is where Tauri's 'tiny app' reputation actually lives. The flip side is compile time — a clean release build can take minutes. This is why people cache the Rust target/ directory in CI and why you only judge size/performance from release output, never dev.

Build Knobs You'll Use

Two flags matter early. --no-bundle compiles the binary without producing installers — perfect for a CI 'does it build?' check where you don't need the packaged output. --bundles <format> limits which installer formats are produced (e.g. just dmg) instead of everything configured. And --debug bundles a debug build when you need to package something for testing without full release optimization.

Code

The build command and its useful flags·bash

# Full release: optimized binary + all configured installers.
npm run tauri build

# CI 'does it compile?' check — skip the installers.
npm run tauri build -- --no-bundle

# Only build a specific installer format.
npm run tauri build -- --bundles dmg

# Package a DEBUG build (for testing, not release).
npm run tauri build -- --debug

Where the shippable output lands·text

src-tauri/target/release/
├─ my-app                       # the raw optimized binary
└─ bundle/
    ├─ macos/My App.app         # macOS app bundle
    ├─ dmg/My App_1.0.0_*.dmg   # macOS installer
    ├─ msi/ , nsis/             # (on Windows) installers
    └─ deb/ , appimage/         # (on Linux) installers

Exercise

Run tauri build on your app, then run it again with --bundles <your-os-format> (dmg on macOS, nsis on Windows, deb on Linux) and compare what appears in bundle/. Then run --no-bundle and note how much faster it is without the packaging phase. You now know what each phase of build costs and produces.

Hint

Full build produces every configured installer; --bundles narrows it; --no-bundle skips installers entirely (fastest). The raw binary is in target/release/; the installers are in target/release/bundle/<format>/.