At a glance

Trezor Bridge runs locally on your computer and mediates USB/WebUSB communication between your browser and the Trezor device. It replaces the need for browser plugins and provides a consistent, secure API for web wallets and decentralized applications.

Key features

• Cross-platform support: installers for Windows, macOS, and Linux.
• Browser compatibility: works with Chrome, Firefox, Edge, and other modern browsers.
• Origin whitelisting: only pre-approved web pages can make device requests.
• Lightweight background service: runs with minimal impact and can be disabled when not needed.
• Developer tools: integration with Trezor Connect and optional debug logs for diagnostics.

Installation — quick steps

Security reminder: Always download Bridge from the official Trezor website and verify the installer checksum if possible.

1. Download the correct installer for your operating system from the official site.
2. Run the installer and follow on-screen instructions. Administrator rights are required on Windows; macOS users should allow the app in Applications.
3. Open your browser and load a compatible web wallet. Connect your Trezor device with a data-capable USB cable and follow the authorization prompts.

// macOS: launch Bridge manually if needed
open /Applications/Trezor\ Bridge.app

// Linux: reload udev rules after installing
sudo udevadm control --reload-rules && sudo udevadm trigger

Troubleshooting

Here are quick fixes for common problems. Most issues stem from cables, permissions, or blocked browser prompts.

• Not detected: swap USB cables/ports and avoid hubs. Use a known data-capable cable.
• No browser prompt: disable strict privacy extensions temporarily and check that Bridge is running.
• Service errors: restart the Bridge service or reboot your machine. On Windows, try re-running the installer as admin.
• Linux permissions: ensure udev rules exist at /etc/udev/rules.d/ and reload rules.

Security model

Bridge acts only as a local proxy. All cryptographic operations and private key storage remain on the Trezor device. When a web page requests an operation (for example, signing a transaction), Bridge forwards the request to the device. The device displays transaction details for you to confirm, preventing remote sites from signing without your explicit approval.

Additional safety tips:

• Keep your recovery seed offline and secure; never enter it into a computer or website.
• Only authorize known and trusted web applications. Revoke permissions if a site no longer needs access.
• Enable automatic updates for Bridge if you want seamless security patches; otherwise, check release notes periodically.

Developer notes

Developers should use the official Trezor Connect library to interact with Bridge. Follow these guidelines:

• Validate origin and use strict Content Security Policies.
• Handle multiple device connections gracefully and provide clear UI messages to users when authorization is required.
• Use the debug mode sparingly — logs can contain metadata useful for troubleshooting but avoid storing sensitive outputs.

// Sample detection pattern
if (window.TrezorConnect) {
  TrezorConnect.getFeatures().then(r => console.log(r));
}

FAQ

Do I need Bridge for Trezor Suite?

No — the desktop Trezor Suite talks to devices directly. Bridge is primarily for browser-based clients and third-party web apps.

Can I run Bridge only when I need it?

Yes — Bridge can be disabled from auto-start and launched manually when required.

Can a website get my private keys via Bridge?

No. Private keys never leave the hardware device. Bridge forwards requests, but the device performs all signing and key operations.

Support & resources

If you run into a problem, the official Trezor knowledge base and community forums are helpful first stops. For security-sensitive issues, contact official Trezor support directly and follow their guidance.