What is a Tauri v2 capability configuration?

In Tauri v2, capabilities define what permissions are granted to individual window groups, targeting specific platforms and security scopes.

Where do capability files live in a Tauri project?

They are typically defined in JSON or TOML files within the src-tauri/capabilities/ directory.

How do scoped permissions work in Tauri v2?

Certain plugins (like filesystem or shell) require a defined scope list (e.g. allowed paths or execute targets) to limit system exposure and prevent vulnerabilities.

Tauri v2 Capability Builder | Generate Custom Permissions

1. Capability Metadata

Identifierkebab-case pattern

Description

Target Windows

main

Target Platforms

2. Core Plugins Permissions Matrix

Toggle specific security permissions for each core Tauri plug-in. Adding a scoped permission (like fs:allow-read) will prompt you to configure custom scope parameters.

fs:defaultAllows basic safe file system operations

fs:allow-readNeeds ScopeAllows reading files (Requires Scope)

fs:allow-writeNeeds ScopeAllows writing/updating files (Requires Scope)

fs:allow-existsNeeds ScopeAllows checking if paths exist (Requires Scope)

fs:allow-mkdirNeeds ScopeAllows creating directories (Requires Scope)

fs:allow-removeNeeds ScopeAllows deleting files/directories (Requires Scope)

3. Dynamic Scope Rules Engine

Active Rules Table

Type	Scope Path Target	Action
No filesystem scope rules added. Scoped permissions will generate warnings.

src-tauri/capabilities/default.jsonREAD-ONLY

{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "default-capability",
  "description": "Capability for the main application windows",
  "windows": [
    "main"
  ],
  "platforms": [
    "macOS",
    "windows",
    "linux",
    "android",
    "iOS"
  ],
  "permissions": [
    "core:default"
  ]
}

Visual Validation & Safety Checklist

Everything looks secure! Zero warnings or syntax anomalies detected.