Trezor Bridge® — Connect Your Trezor to Web Browsers

Trezor Bridge is the secure local connector that lets web browsers and web wallets communicate with your Trezor hardware device. This guide covers what it does, how to install it, best security practices, and tips for developers.

What is Trezor Bridge?

Trezor Bridge is a small, trusted background application that runs on your computer and provides a controlled communication channel between web-based wallet interfaces (like Trezor Suite web client or third-party dApps) and your Trezor hardware wallet. Bridge avoids the need for browser extensions and exposes a secure local API that web clients can use to send requests to connected devices.

Why Bridge matters

Modern browsers intentionally restrict raw USB access to protect users from malicious pages. Bridge solves this by acting locally: it performs device discovery and proxying, prompts the user for permission, and ensures that only approved origins can interact with the hardware device. The result is a safer, more predictable experience when interacting with hardware wallets from the browser.

01

Compatibility

Bridge supports major desktop platforms — Windows, macOS, and Linux — and works across popular browsers such as Chrome, Edge, Firefox, and others that abide by modern WebUSB and security models.

02

Security model

Private keys never leave the Trezor device. Bridge only forwards approved commands from a browser to the device; signing and key management happen exclusively on the hardware. Bridge also enforces origin checks so untrusted web pages can't silently access your device.

Key features

  • Cross-browser support: works with Chrome, Firefox, Edge, and more.
  • Lightweight background service: minimal system resource usage.
  • Origin whitelisting: only approved web pages can send requests.
  • Automatic updates: optional updates keep Bridge current.
  • Developer-friendly: integrates with Trezor Connect and provides diagnostics.

Installation guide

Important: Always download installers from the official Trezor website and verify checksums if you are in a high-risk environment.

  1. Visit the official Trezor download page and choose the correct installer for your operating system.
  2. Run the installer and follow prompts. On Windows, you'll need administrator permissions to install the service. On macOS, allow the app to be added to Applications. Linux users may need to install udev rules — the installer can usually add them for you.
  3. After installation, start your browser and open the web wallet or dApp you want to use. Connect your Trezor device via a data-capable USB cable.
  4. Your browser will display a prompt to connect to a local Bridge service. Confirm the prompt on your computer and follow the device's on-screen instructions to authorize access.
// macOS: manually start Bridge if it does not auto-launch
open /Applications/Trezor\ Bridge.app

// Linux (example): ensure udev rules are applied and re-log if needed
sudo udevadm control --reload-rules && sudo udevadm trigger

Troubleshooting tips

If your browser can't find the device, try these steps before contacting support — most issues are simple to fix.

  • Check your cable: Use the original or a known data-capable cable. Many cheap cables are power-only.
  • Try another port: Switch USB ports; some front-panel or hub ports behave poorly.
  • Restart Bridge: Quit and restart the Bridge service or app. On Windows, use the Services panel; on macOS, stop the app and relaunch.
  • Disable extensions: Privacy and security extensions can block the browser prompt — temporarily disable them while connecting.
  • Update software: Ensure your OS, browser, and Bridge are up to date.

Advanced: Linux notes

Linux users may need to add udev rules to grant non-root access to USB devices. The installer typically places a rule file in /etc/udev/rules.d/. If you install Bridge manually, make sure rules are present and that you've reloaded udev rules and reconnected the device or logged out and back in.

Developer integration

Developers building web apps that talk to Trezor should use the official Trezor Connect library. Bridge exposes a stable API and logs that make it easier to diagnose connection problems. Follow these best practices:

  • Always perform origin checks — only interact with approved hostnames.
  • Gracefully handle multiple devices attached to the same system.
  • Surface clear UI instructions to ask users to authorize device access.
// Example pattern: check for TrezorConnect global and request device
if (window.TrezorConnect) {
  TrezorConnect.getFeatures().then(response => console.log(response));
}

Security & best practices

Your Trezor's security depends not only on the hardware but also on how you interact with web software. Follow these guidelines:

  • Never share your recovery seed or PIN with anyone.
  • Verify download checksums for installers when possible.
  • Only approve device access for websites you trust.
  • Keep your device firmware, OS, and browser updated.

FAQ

Do I need Bridge to use the desktop Trezor Suite?
No. The desktop Trezor Suite communicates directly with your device and doesn't require Bridge. Bridge is intended for browser-based clients and web apps.
Can Bridge run on startup?
Yes — Bridge can run as a background service for convenience. If you prefer, you can disable auto-start and launch it only when needed.
Is my private key ever transmitted through the Bridge?
No. Signing and key operations remain on the device. Bridge merely forwards approved requests from the browser to the hardware.

Where to get help

If you're stuck, check the official Trezor knowledge base and community forums for step-by-step guides and troubleshooting articles. For critical security concerns, consult Trezor's official support channels.

© Trezor. This guide is provided for general information. For downloads, firmware updates, and official support, always visit the Trezor website.