Overview
Trézór Bridge® is an official helper application that securely connects your Trezor hardware wallet to web services and decentralized applications. It acts as a local, authenticated proxy so that web pages can communicate with your device without exposing sensitive secrets. This guide explains how to install Bridge, configure permissions, and perform trusted transfers with confidence.
Step 1 — Download & verify
Download the Bridge installer from the official Trézor website. Whenever possible, verify the file using the provided checksum or signature. Verifying ensures the binary hasn't been tampered with and is the first line of defense against supply-chain threats.
Step 2 — Install Bridge
Run the installer for your operating system and follow the prompts. Bridge runs as a background application and listens locally for authorized connections. During installation you'll be asked to allow network access to localhost — this is intentional and safe: Bridge only accepts connections from the local machine by default.
Step 3 — Pair with Trezor Wallet or dApp
Launch the official Trezor Wallet or a supported dApp. When the web app requests access, Bridge will show a pairing prompt. Confirm the connection on your computer and on the Trezor hardware device if prompted. Always check the origin (URL) of the request before approving.
Step 4 — Enable trusted transfers
Once paired, use the dApp to prepare a transfer. The transaction details — destination address, amount, and fee — will be shown in the web UI but must also be verified on the Trezor hardware display. Reject any transaction where the on-device details don't match your intentions.
On-device verification is mandatory. It prevents host-side malware from silently changing transaction values or destinations.
Advanced: Permissions and ACL
Bridge maintains an access control list (ACL) of previously approved origins. You can revoke permissions for a site through the Bridge settings or via the official Suite. Regularly prune unused approvals to minimize risk. For high-security setups, grant permissions only when needed and revoke after the session ends.
Security best practices
- Keep Bridge and Suite updated via official releases
- Always verify transaction details on the device screen
- Use a dedicated machine for high-value transfers
- Revoke Bridge access for unknown or unused sites
Troubleshooting
If Bridge fails to start, check OS firewall or antivirus settings and allow localhost connections. If the browser cannot detect Bridge, ensure it is running and try restarting the browser. For persistent issues, reinstall Bridge from the verified installer.