Trezor Bridge is a small, secure background application that acts as a local gateway between your Trezor hardware wallet and web or desktop applications. It is intentionally lightweight and privacy-preserving: it never sends your private keys or secrets to the internet, and only facilitates signed interactions between software on your computer and your device. This page explains exactly how Bridge works, how to install and troubleshoot it, and why it remains an essential component for anyone who wants a safe, seamless hardware wallet experience.
Why Bridge?
Bridge isolates hardware-level communication and provides a stable API so apps don’t need direct USB access to your wallet. This minimizes attack surface and standardizes the experience across browsers and platforms.
Privacy-First
All communication is local. Bridge does not collect telemetry by default and is designed so sensitive operations remain offline on the device.
How it works
When you interact with a web wallet or desktop client, that software sends requests to Bridge through a secure local port. Bridge then relays the request to your Trezor device (via USB or WebUSB), waits for you to confirm the action on the hardware, and returns the signed response. This flow ensures that keys never leave the hardware. In network terms: app <> Bridge (local) <> Device (USB) — the internet never sees your private material.
Core features
- Local-only operations: Bridge performs requests on your machine — nothing is transmitted to Trezor servers.
- Cross-platform support: Official packages for Windows, macOS, and Linux.
- Automatic updates (optional): You can opt to allow Bridge to update itself; otherwise manual updates are supported.
- Robust compatibility: Works with major browsers and desktop wallets through a consistent API.
Security considerations
Bridge focuses on reducing complexity. Use only official downloads or verified package repositories. Keep your operating system and device firmware up to date. Treat Bridge like a conductor: it coordinates actions but cannot sign on your behalf — physical confirmation on the device is required for all critical operations (sending funds, exporting public keys, or changing settings).
Troubleshooting & tips
- Check device state: Ensure your Trezor is unlocked and at the home screen. If the device shows a firmware update prompt, follow the official instructions.
- Restart Bridge: Quit the Bridge application and relaunch it. On many OSes you can restart the background service from your system tray / menu bar.
- Browser permission: If using WebUSB, your browser may ask for permission to access the device. Granting this is required for in-browser apps.
- Reinstall: If problems persist, reinstall the latest Bridge package from the official site.
Compatibility
Bridge supports current versions of Windows 10/11, macOS (also Apple silicon), and mainstream Linux distributions. For advanced users, Bridge binaries and package manager instructions are provided for headless or scripted environments. If you are using a privacy-focused distro or strict firewall rules, ensure local loopback access between browser/app and Bridge is permitted.