Trezör® Bridge®

Supported platforms

• Windows 10+ (64-bit)
• macOS (Intel & Apple Silicon)
• Linux (Debian/Ubuntu and other distributions)

Some web integrations may use a browser-native WebHID/WebUSB API that reduces the need for a separate Bridge installation; Bridge ensures broader compatibility across browsers and versions.

Installation summary

1. Visit the official download page on the Trezör website and select your platform.
2. Download the installer package and verify checksums or signatures when provided.
3. Run the installer and follow prompts; Bridge runs as a background helper and may require system permissions.
4. After installation, your browser and supported dApps will detect Bridge and request access when you connect your device.

Step 1 — Install and run Bridge

Install Bridge, then launch it. On first run, grant any OS prompt for network or device access as required. Bridge typically runs in the background and listens on a localhost port for browser connections.

Step 2 — Connect your Trezör device

Plug your Trezör hardware wallet into the computer and unlock it with your PIN. The device screen will show connection prompts which you must confirm to allow interactions.

Step 3 — Open a supported dApp

Visit a Web3 site (e.g., a decentralized exchange or wallet interface). The site will request a connection; approve the connection in Bridge and confirm on your device.

Step 4 — Approve signatures on-device

When the dApp asks to sign a transaction or message, Bridge forwards the request and your Trezör device will display the transaction details. Carefully verify amounts, recipient addresses, and any data before approving.

Minimal attack surface

Bridge only relays messages — private keys and signing are always performed on the Trezör device. The host computer never holds secrets, and Bridge is designed to be small and auditable.

Cross-browser compatibility

Bridge supports integrations with WebUSB, WebHID, and traditional localhost-based connectors to maximize compatibility across Chrome, Edge, Firefox (where supported), and other Chromium-based browsers.

Permissioned access

Bridge exposes a permission grant flow — you control which sites can request device interactions and can revoke permissions at any time for improved safety.

Local-first design

All communication occurs locally between your browser, Bridge, and the Trezör device. No sensitive data is sent to third-party servers by default as part of the signing process.

Auditable & open approach

Bridge components and signaling designs are intended to be transparent and reviewable by security-conscious users and auditors. This helps maintain trust in the connector between web and hardware.

Lightweight & low-overhead

Bridge runs with minimal system resources and can coexist with other wallet helpers or browser extensions you may use.

Always verify on the device

When prompted to sign, confirm transaction details directly on your Trezör device screen. Do not approve a signature based solely on what the browser shows — malware can alter displayed content on the computer.

Limit permissions

Grant dApps only the permissions they need. Revoke permissions for unfamiliar sites and periodically audit the list of authorized origins in Bridge's settings (if available).

Keep Bridge up to date

Install updates for Bridge and your Trezör device firmware promptly to benefit from security fixes and compatibility improvements.

Use official sources

Download Bridge and Suite only from official Trezör distribution points. Verify checksums/signatures when possible and avoid unofficial guides that direct you to alternative downloads.

Isolation for high-value operations

For very high-value transactions, consider using a dedicated, clean machine or an offline signing workflow and an air-gapped device to minimize exposure to threats on your primary workstation.

Wallet connectors

Bridge allows popular wallet connectors (WalletConnect, Web3 provider bridges) to use a hardware-backed account for signing, offering a seamless hybrid experience: a web UI with hardware-level security.

DeFi & DEX usage

When interacting with DeFi protocols, Bridge ensures signature requests are routed to your Trezör for explicit approval. Carefully review contract data and permissions before approving token allowances or complex transactions.

NFT storefronts

Purchasing, minting, or transferring NFTs will often trigger signatures; Bridge forwards these requests, letting you sign while verifying asset IDs and target addresses on-device.

Developer workflows

Developers can use Bridge for local testing and debugging of Web3 apps while ensuring integration with hardware wallet signing without exposing private keys during development.

Device not detected

Try a different USB cable or port, ensure device is unlocked, and check that Bridge is running. On macOS, grant WebUSB permissions or system prompts if required.

Connection refused

Restart Bridge and the browser, clear site data, and re-establish the connection. Ensure no other wallet connectors are conflicting with the same origin.

Transaction mismatches

If transaction details differ between the dApp and device, cancel and investigate. Malware can spoof browser content — always trust the Trezör device screen for final verification.

Update issues

If Bridge or firmware updates fail, follow official recovery steps and consult support. Avoid unofficial workarounds that ask for seeds or private keys.