Trezor Bridge runs on your computer to enable secure, browser-based communication with your Trezor device. It creates a trusted, local channel between your web applications (wallets, portfolio managers, and explorers) and the hardware wallet, ensuring all signing requests are handled safely.
Local-first connection
Bridge never uploads your keys — it simply relays encrypted requests between your browser and the device on your machine.
Verified signing
Every transaction is previewed and approved on the physical Trezor device, keeping private keys offline and secure.
Automatic updates
Opt-in to updates to keep the Bridge client compatible with modern browsers and device firmware.
Cross-platform
Available for Windows, macOS, and Linux with a lightweight installer and minimal system requirements.
How it works
- Your browser sends a request to the Bridge local service to access a Trezor device.
- Bridge verifies the request origin and prompts the user for consent if required.
- The request is forwarded to the connected Trezor device over USB (or supported transport).
- The device displays transaction details for manual confirmation and signs only when you approve.
Bridge acts strictly as a relay — private keys remain inside the device at all times.
Security best practices
- Install Bridge only from official sources and verify code signatures where provided.
- Keep your firmware and Bridge client up to date to receive security fixes.
- Never share your seed phrase — Bridge does not and should never request it.
- Use the physical confirmation on the device for every transaction to prevent remote tampering.
Troubleshooting
If your browser cannot detect the device, try reconnecting the USB cable, restarting the Bridge service, or checking permissions in your system settings. For persistent issues, consult the official support documentation or community forums.