Tauri Core Config

tauri-core-config

Quick Reference

Configuration File Location

The main configuration file lives at src-tauri/tauri.conf.json. Tauri auto-generates JSON schemas in src-tauri/gen/schemas/ for IDE autocompletion.

Top-Level Keys

Schema Reference

ALWAYS include the $schema key for IDE autocompletion and validation:

{
    "$schema": "./gen/schemas/desktop-schema.json"
}

Available schemas (auto-generated in src-tauri/gen/schemas/):

• desktop-schema.json -- desktop platform configuration
• mobile-schema.json -- mobile platform configuration
• remote-schema.json -- remote URL capabilities

Critical Warnings

NEVER omit the identifier field -- it is the ONLY required field. It MUST be unique reverse-domain notation (com.example.myapp). Using a non-unique identifier causes conflicts with other apps on the system.

NEVER use build.devUrl without build.beforeDevCommand -- the dev server will not start automatically, causing Tauri to connect to nothing.

NEVER omit build.beforeBuildCommand -- frontend assets will not be compiled before bundling, producing an app with missing or stale UI.

NEVER set app.security.csp to null in production -- this disables all Content Security Policy restrictions, leaving the app vulnerable to XSS attacks.

NEVER set app.security.dangerousDisableAssetCspModification to true unless you fully understand CSP nonce injection.

NEVER edit files in gen/schemas/ -- they are auto-generated and will be overwritten on the next build.

Build Section

The build section controls how the frontend is compiled and served during development and production.

Command Object Form

beforeDevCommand, beforeBuildCommand, and beforeBundleCommand support an object form:

{
    "beforeDevCommand": {
        "script": "npm run dev",
        "cwd": "../frontend",
        "wait": false
    }
}

Build Rules

• ALWAYS pair devUrl with beforeDevCommand -- the dev server must be running before Tauri connects
• ALWAYS set frontendDist to the output directory of your frontend build tool
• ALWAYS set beforeBuildCommand to compile frontend assets for production
• frontendDist is relative to src-tauri/, so ../dist points to project-root/dist

App Section

The app section configures runtime behavior including windows, security, and platform-specific features.

Window Configuration (app.windows[])

Window Rules

• ALWAYS set a unique label for each window -- labels are used for IPC targeting and window lookup
• Set create: false for windows you want to create programmatically from Rust
• The url property accepts relative paths (/settings.html) or custom protocol URLs
• Use minWidth/minHeight to prevent the window from being resized too small

Security Section (app.security)

Security Rules

• ALWAYS enable freezePrototype in production -- it prevents prototype pollution attacks
• ALWAYS define a restrictive CSP in production -- never leave it as null
• Use the isolation pattern for maximum security (adds an isolation layer between frontend and IPC)
• When specifying capabilities explicitly, auto-discovery of src-tauri/capabilities/ is disabled

Bundle Section

The bundle section controls application packaging and distribution.

Required Icon Sizes

ALWAYS include all required icon formats:

{
    "icon": [
        "icons/32x32.png",
        "icons/128x128.png",
        "icons/128x128@2x.png",
        "icons/icon.icns",
        "icons/icon.ico"
    ]
}

Use tauri icon CLI command to generate all sizes from a single source image.

Platform-Specific Bundle Configuration

Windows (bundle.windows)

macOS (bundle.macOS)

Linux (bundle.linux)

iOS (bundle.iOS)

Android (bundle.android)

Updater Rules

• ALWAYS set TAURI_SIGNING_PRIVATE_KEY environment variable before enabling createUpdaterArtifacts
• Use true for new projects, "v1Compatible" ONLY when migrating from Tauri v1 updater
• NEVER lose the updater private key -- it makes pushing updates to existing installations impossible

Plugins Section

The plugins section provides per-plugin configuration as key-value pairs:

{
    "plugins": {
        "fs": {
            "scope": {
                "allow": ["$APPDATA/**", "$HOME/Documents/**"],
                "deny": ["$HOME/.ssh/**"]
            }
        },
        "http": {
            "scope": {
                "allow": ["https://api.example.com/*"]
            }
        }
    }
}

Plugin configuration keys match the plugin name without the tauri-plugin- prefix.

Minimal Viable Config

The absolute minimum tauri.conf.json that works:

{
    "identifier": "com.example.myapp",
    "build": {
        "devUrl": "http://localhost:5173",
        "frontendDist": "../dist",
        "beforeDevCommand": "npm run dev",
        "beforeBuildCommand": "npm run build"
    },
    "app": {
        "windows": [
            {
                "title": "My App",
                "width": 800,
                "height": 600
            }
        ]
    },
    "bundle": {
        "active": true,
        "icon": [
            "icons/32x32.png",
            "icons/128x128.png",
            "icons/128x128@2x.png",
            "icons/icon.icns",
            "icons/icon.ico"
        ]
    }
}

Reference Links

• references/methods.md -- Complete tauri.conf.json schema reference with all properties
• references/examples.md -- Config examples: minimal, full, platform-specific
• references/anti-patterns.md -- Common config mistakes and how to avoid them

Official Sources

• https://v2.tauri.app/reference/config/
• https://v2.tauri.app/develop/configuration/
• https://v2.tauri.app/distribute/