Trezor Bridge®

A lightweight, secure connectivity layer that lets your browser and Trezor Suite communicate with your hardware wallet. Install Bridge to enable direct, verified transactions and device management.

What is Trezor Bridge?

Trezor Bridge runs locally on your computer and acts as a secure messenger between your Trezor device and web-based apps or the Trezor Suite desktop client. It avoids insecure browser USB implementations and simplifies cross-platform device access.

When you need Bridge

  • Connecting a Trezor device to Trezor Suite (web or desktop).
  • Using browser-based cryptocurrency wallets that support Trezor.
  • When your operating system’s native USB stack or browser permissions block direct device access.

Quick install & verify

  1. Download Bridge from the official source (use the button on this page).
  2. Run the installer and allow it to run locally — Bridge installs a small local service.
  3. Open Trezor Suite (or your browser app) and connect your device. Confirm the connection on your Trezor screen.
  4. Only accept firmware or transaction prompts that match what you expect and are shown on your physical device.
Note: Bridge does not transmit your private keys or recovery seed — it only forwards signed messages and device prompts. All key operations remain inside your Trezor hardware.

Platform compatibility

Bridge supports Windows, macOS, and Linux. Some platforms may have slightly different installation flows — follow the prompts on-screen and the official documentation for your OS.

Security best practices

  • Always download Bridge from the official Trezor website or verified distribution channels.
  • Verify downloads with provided checksums/signatures if available.
  • Keep Bridge and Trezor Suite up to date to receive security improvements.
  • Confirm every transaction on the Trezor device display before approving.
Download Trezor Bridge

Developer notes

Trezor Bridge exposes a small local HTTP/WS interface for apps to communicate with attached devices. If you're integrating Bridge into a web app, follow the official developer documentation and only rely on trusted third-party libraries. Never prompt users to disclose recovery seeds or private keys — all signing must happen on the device.