Trezor Bridge

Secure local connectivity between your Trezor and apps — USB & supported transports

Official Local Connector

How Trezor Bridge works — a simple, secure relay

Trezor Bridge is a small local service that runs on your computer and enables web or desktop applications to communicate securely with your Trezor hardware wallet. It acts as a trusted relay on your machine — relaying encrypted requests between the browser and the physical device while ensuring private keys remain on the Trezor device itself.

Local-only communication

Bridge listens only on localhost and does not transmit keys or transaction data to remote servers — it simply channels requests between apps and the device.

Verified signing

Every cryptographic operation (signing a transaction) is shown on the device screen and requires physical confirmation — preventing remote signing without your consent.

Cross-platform

Available for Windows, macOS and Linux with lightweight installers and minimal overhead for background operation.

Developer-friendly

Exposes a documented local API for secure integrations; libraries exist for common languages and web contexts.

Typical flow (what happens when you use a web wallet)

  1. The web app asks the browser to reach the local Bridge service.
  2. Bridge verifies the origin and relays the request to your connected Trezor.
  3. The Trezor displays transaction details for you to verify on-device.
  4. After you approve, the device signs the transaction and Bridge forwards the signed payload back to the web app.
Privacy note: Bridge does not store or transmit your recovery phrase, private keys, or personal data — it only forwards encrypted requests locally.

Security considerations

Core guarantees

  • Keys never leave the device — Bridge only forwards requests, signing happens on-device.
  • Manual approval — every signature requires you to confirm on your Trezor.
  • Local operation — Bridge runs on your machine and does not upload secrets.

Best practices

  • Download Bridge only from the official Trezor website and verify checksums when available.
  • Keep firmware and Bridge updated to receive security fixes.
  • Use browser extensions or apps from trusted, well-known providers.
  • When approving transactions, read addresses and amounts on your device screen carefully.

Troubleshooting

  • If your browser doesn't detect the device: reconnect the USB cable, try a different port, or restart the Bridge service.
  • On Windows, ensure device drivers were installed during the Bridge setup.
  • Check Bridge logs (available via the app or installer) for errors and consult official support if needed.
  • Avoid third-party installers or unofficial forks of Bridge — they may compromise device connectivity and security.

For developers

Trezor Bridge exposes a local API for apps to communicate with devices safely. If you’re building integrations:

  • Request the minimum scopes needed and present clear UX explaining signature contents.
  • Use the official client libraries and handle errors gracefully (device disconnected, firmware incompatible).
  • Encourage users to verify everything on their device — never bypass on-device verification.

Privacy & support

Bridge is a local utility and does not transmit personal information as part of normal operation. For support, always use official documentation and community channels linked from the Trezor website. If you suspect tampering or unusual behavior, stop using the device and contact official support channels immediately.