Bridge your Trezor device to web apps with a secure, user-friendly connection
®Trezor® Bridge® provides a trusted local communication layer between your Trezor hardware wallet and browser-based applications. It keeps the device accessible while minimizing risk through origin checks, user confirmations, and strict host verification.
What is ®Trezor® Bridge®?
It is a small local application (service) that runs on your computer to enable secure communication between the browser and your Trezor device. This component lets web wallets and dApps request device operations while ensuring the Trezor device remains the source of truth for signing and confirmations.
Local HTTPS endpoints and origin verification for connected web apps.
Only accepts requests from known, authorized hosts when configured.
Keeps private keys on-device; Bridge only transports signed messages and public data.
Security model
Device-first verification
All signing requires explicit user confirmation on the Trezor device display.
Host attestation
Bridge validates requests originate from permitted web origins and can be configured to trust specific hosts.
Encrypted local transport
Communications between browser and Bridge use secure channels; Bridge does not expose private keys.
Install & setup
Download ®Trezor® Bridge® from the official Trezor site and install the appropriate package for your OS.
Start Bridge; the app will listen on a secure local port and show a small tray/menu indicator when running.
Open your browser and visit a recognized web wallet; allow Bridge access when prompted and confirm pairing on-device.
Tip: Only install Bridge from official sources and verify checksums when provided.
Common user flows
Connect device → Bridge detects device → Web app requests address → User confirms on Trezor → Address returned to app.
Sign transaction → Web app prepares transaction → User reviews details on Trezor → User approves → Signed transaction returned to app for broadcast.
Pairing: Web app requests persistent pairing token; user approves pairing on-device and Bridge stores minimal metadata locally.
Best practices for safety
Only grant Bridge access to trusted web applications and revoke pairing when no longer needed.
Verify transaction amounts and destination addresses on the Trezor device screen before approving.
Keep Bridge and device firmware up to date; read release notes and verify authenticity where possible.
Use OS-level firewall rules if you want to restrict which local hosts can connect to Bridge.
Troubleshooting
If Bridge cannot detect your device: check USB cables, ensure Bridge is running, confirm browser permissions, and try connecting the device directly to a different USB port. Restarting Bridge or the browser often resolves transient issues.
Disclaimer
Disclaimer: This presentation is informational only and not financial, legal, or tax advice. Install Bridge only from official Trezor channels. The authors are not responsible for losses from misuse. Always verify software integrity and never share your recovery seed.