Reliable desktop connectivity for your Trezor
Trezor Bridge runs locally on your machine and exposes a safe API for authorized desktop apps and web browsers to talk to your Trezor hardware device. It minimizes attack surface by strictly mediating requests and never sending private keys or secrets anywhere.
Strong security model
Only authorized applications can request operations; every sensitive action requires device confirmation.
Cross-platform
Available on Windows, macOS, and Linux — with installers and packages tailored for each OS.
Lightweight & fast
Small footprint, low CPU use, and quick response times when interacting with your Trezor device.
Privacy-preserving
Bridge runs locally; no account, telemetry or cloud storage is required to use it.
How it works — short
Installed as a small native helper, Bridge listens on a local loopback address. Your browser or desktop application sends requests to Bridge, which then forwards approved commands to your Trezor device via USB. The Trezor device always displays the final transaction details for manual confirmation.
Quick FAQ
Is my seed exposed to Bridge?
No. Trezor Bridge never accesses or transmits private seeds or keys. All private keys remain on the device and cryptographic operations are performed there.
Do I need to keep Bridge running?
Bridge only needs to run when a compatible desktop app or web page needs to communicate with your Trezor. You can quit it when not in use.
Detailed features
Trezor Bridge acts as a secure mediator between the browser ecosystem and hardware wallet. Core capabilities include:
- Strict request origin validation — Bridge accepts calls only from whitelisted or user-approved applications.
- Automatic updates option — keep Bridge up-to-date with security fixes and improvements.
- Diagnostic logging (user-controlled) — simplifies troubleshooting while protecting sensitive data.
- Compatibility with major web wallets and desktop apps that support Trezor.
Developer notes
Developers integrating Trezor Bridge should follow the official API specifications and request only the permissions necessary for their workflows. Use HTTPS for web apps and always prompt users for explicit device interactions.