Trezor Bridge is a lightweight background service that securely connects your Trezor hardware wallet to Trezor Suite and trusted web apps. It runs locally, keeps communication isolated, and dramatically simplifies interaction with your device while preserving maximum security.
Bridge sits between your browser/desktop app and the Trezor device. It manages USB/HTTPS communication, negotiates secure sessions, and exposes a tiny API that apps use to talk to your wallet—no keys ever leave your hardware.
Bridge runs on your computer as a trusted local helper. It does not forward data to remote servers—communication happens on your machine.
Bridge establishes a secure, authenticated channel between Suite/web apps and your device. Each transaction is shown and approved on the device screen.
No complex browser extensions or plugins — Bridge uses safe, modern browser APIs to enable direct device workflows for web apps.
Small, well-scoped, and easy to install — Bridge is designed to be unobtrusive while providing essential connectivity.
If you prefer not to use Bridge, advanced users may connect via other supported low-level methods — but Bridge offers the best combination of security and usability for most people.
Bridge is built with the same security-first principles as the Trezor ecosystem. It never handles private keys, does not store seed phrases, and requires device confirmation for signing operations.
Bridge mediates local connections; no remote server proxies transactions for you.
Installers and Bridge updates are signed and verifiable so you can confirm authenticity before installing.
Designed to request only the OS permissions it needs to access USB devices safely.
For most desktop/web workflows, Bridge simplifies and secures connectivity. Some advanced flows can use other tools, but Bridge is the recommended option.
Key components are open for auditing; check the official documentation for repositories and verification instructions.
Bridge provides installers for Windows, macOS and Linux — including packaged easy-installs and CLI options for advanced users.
Use published checksums/signatures and follow reproducible-build guidance where available to ensure installer integrity.