Trezor Bridge — Secure Your Hardware Wallet®
A lightweight, secure communication layer that lets your browser and desktop apps talk to your Trezor device safely. Install Bridge to use Trezor Suite, web apps, and browser integrations.
Overview
Trezor Bridge runs locally on your computer and provides a secure, cross-platform API for web and desktop applications to communicate with Trezor hardware wallets. It replaces older browser plugins and simplifies connectivity while enforcing origin checks and device verification.
Why Bridge?
- Secure local proxy: isolates device communication from the browser environment.
- Cross-platform: installers available for Windows, macOS and Linux.
- Automatic updates: optional, keeps Bridge patched against vulnerabilities.
- Compatibility: used by Trezor Suite and supported third-party wallets that integrate with Trezor.
Install & setup
- Download the Bridge installer for your OS from the official site:
trezor.io/start(replace with your distribution link in production). - Run the installer and follow on-screen instructions. Administrator privileges may be required.
- After installation, Bridge runs in the background and listens on a local port for authorized requests.
- Open Trezor Suite or a compatible web app — the app will detect Bridge and prompt you to connect your device.
Security model
Bridge enforces origin checks and requires explicit user interaction on the device for sensitive operations (PIN entry, transaction confirmation, firmware actions). Private keys never leave your hardware device — Bridge only transmits signed messages and metadata needed by the app.
Verifying the installer
Always verify downloads. The recommended steps:
- Download the installer and associated checksum or signature from the official source.
- Verify the checksum or detached signature locally using
sha256sumor GPG tools before running the installer. - If the verification fails, do not run the installer and report the issue to official support.
Unattended & headless setups
Bridge can be installed on headless servers for advanced setups (e.g., offline signing via remote procedures). Use the CLI options included with the distribution and follow best practices for firewall rules and port restrictions.