Overview
Trezor Bridge acts as a local bridge between your browser (or a compatible app) and your Trezor hardware wallet. Because modern browsers restrict direct low-level USB access, Bridge provides a stable, local API so web and desktop clients can request device operations in a safe, auditable way. The hardware wallet — not Bridge — is the authority for private keys and signing.
Why Bridge matters
Without Bridge, some web-based wallet UIs can’t talk to the Trezor device reliably. Bridge ensures that the handshake, enumeration, and message exchange happen smoothly while enforcing an additional security boundary: every transaction or sensitive request still requires a physical confirmation on the Trezor unit.
Core features
- Local-only communication: runs on your machine and isolates device traffic from the web.
- Automatic device detection: Bridge watches for connected Trezor devices and makes them available to authorized web pages and apps.
- Small, focused binary: designed specifically for USB communication and local API handling.
- Update checks: optional update checks to ensure you have security fixes and compatibility improvements.
Installation — step-by-step
Follow the short steps below for the OS you use. Always verify you downloaded the installer from Trezor's official site or official releases page.
- Download the Windows installer (.exe) from the official source.
- Run the installer as an administrator if prompted.
- After installation, you might see a small icon in the system tray. Restart your browser.
- Plug in your Trezor using a data cable and follow the wallet website prompts.
- Download the macOS package (.dmg or .pkg).
- Open the DMG and drag the Bridge app to Applications or run the PKG installer.
- macOS may request permission to allow the app to access USB devices — allow it when prompted.
- Restart your browser and connect your Trezor.
- Check for a distribution-specific package (deb, rpm) or a tarball/binary on the official releases page.
- Follow the distribution instructions — you may need to add udev rules for device access.
- Run Bridge as a normal user after installation and restart your browser.
sudo dpkg -i trezor-bridge_
sudo apt-get install -f
Security & privacy
Bridge is designed to be a minimal conduit. The Trezor device itself holds the seed phrase and private keys. Bridge does not expose keys to the web. Best practices to maximize security:
- Always verify downloads via checksums or signatures if available.
- Use a trusted browser and consider a clean browser profile for crypto operations.
- Do not enter your seed phrase into any website or app — the seed should only be entered into the device during device setup and never shared.
- Confirm transaction details (address, amount) on the Trezor display before approving.
Troubleshooting — quick fixes
Common issues and immediate steps to resolve them:
- Device not detected: try a different USB cable/port (use a data cable); ensure Bridge is running and restart the browser.
- Browser permissions: some OSes require explicit permission for apps to access USB or the browser to allow the connection — allow when requested.
- Stale installation: uninstall and reinstall the latest Bridge release from the official source.
- Conflicting drivers or software: temporarily disable USB-monitoring or filtering software to test (security products sometimes interfere).
For developers & integrators
Bridge provides a local API that web apps and native clients can use to discover and communicate with a connected Trezor. If you're building integrations:
- Work with the official developer docs and test across firmware versions.
- Gracefully handle device disconnects and user-denied confirmations.
- Don’t rely on the web UI alone — always display the expected address and transaction details to the user and instruct them to verify on-device.
Using Trezor Suite vs Browser Flows
Trezor Suite (desktop) gives an all-in-one experience without browser permissions; however, many dapps require web flows. Both approaches are valid — choose the workflow you trust. If you prefer a simpler UI with fewer permission prompts, Suite may be the better choice. If you interact with decentralized apps, Bridge is essential.
Frequently asked questions
Do I need Bridge to use my Trezor?
For many browser-based wallets and dapps, yes. For Trezor Suite or other native apps, Bridge may not be required. Check the application’s instructions.
Does Bridge access my seed phrase or private keys?
No. The device stores keys; Bridge simply routes messages between the application and the Trezor hardware. Private keys never leave the device.
Can Bridge be used on headless servers?
Running Bridge on a headless server is not the typical use case and is discouraged for regular users. Hardware wallets are intended for interactive use where you can physically approve operations.
Where do I find logs for troubleshooting?
Bridge logs exist on the local machine. Refer to the official docs for the exact log path for your OS. Avoid sharing logs publicly if they contain personally identifying details.
When to contact support
If troubleshooting steps fail, contact official Trezor support with the following information: operating system and version, browser and version, Bridge version, Trezor model and firmware, a short description of the issue, and any relevant log excerpts (only non-sensitive parts).