What is Trezor Bridge and why do I need it?

Trezor Bridge is a secure local gateway that enables your browser or application to communicate with your Trezor hardware wallet. Install it to allow device pairing, account discovery and transaction signing when direct WebUSB/WebHID is unavailable or restricted.

How do I install Trezor Bridge safely?

Download Trezor Bridge only from the official Trezor website or your trusted distribution channel. Follow OS-specific installers for Windows, macOS and Linux and verify signatures if provided. Restart your browser after install for best results.

Can I use Trezor Bridge for automated testing or CI?

Yes — use the Bridge with a simulator or headless setup in test environments. Ensure you isolate test keys and never use production private keys in CI.

What security features does Trezor Bridge provide?

Trezor Bridge limits network exposure by acting as a local-only conduit between your app and the device, enforcing TLS on remote services, and forwarding only structured device requests. Private keys remain inside the hardware device at all times.

Troubleshooting: Bridge not detecting device — what should I check?

Confirm Bridge is running, check USB cables and ports, ensure browser restarts after install, enable WebUSB/WebHID permissions if needed, and update device firmware. Consult logs and run Bridge diagnostics for detailed errors.

Trezor Bridge — The Secure Gateway to Your Hardware Wallet®

Reliable local bridge, secure device communication, and easy integration for developers and users who connect to Trezor hardware wallets.

Bridge vX.Y.Z

Overview

Trezor Bridge serves as the secure gateway between your web browser or desktop application and your Trezor hardware wallet. When native WebUSB or WebHID access is limited, Trezor Bridge provides a local, trusted conduit to pair devices, enumerate accounts, push transaction payloads, and receive signatures — without exposing private keys. This page explains why Trezor Bridge matters, how to install it safely, integration tips, and troubleshooting guidance.

Why use Trezor Bridge?

Trezor Bridge improves compatibility across browsers and operating systems. It ensures secure device detection, consistent APIs for developers, and a predictable installation flow for end users. Use Bridge when WebUSB/WebHID is blocked, when you need a local daemon for automated flows, or when older browser versions require a helper process.

Download & Install

Obtain the Bridge installer for Windows, macOS or Linux from official sources and follow platform prompts. Restart your browser after install to ensure permissions are refreshed.

Connect & Authorize

Connect your Trezor via USB. The Bridge handles handshake and device enumeration. Authorize requests on-device to confirm accounts and operations.

Integrate — Developer Notes

Use the official Trezor Suite SDK or Bridge HTTP API endpoints. Always run input validation, check firmware versions, and keep user prompts clear for signing flows.

Developer integration example

Minimal sample: open a local Bridge session and request device features in JavaScript.

// Connect to local Bridge (pseudo-code)
fetch('http://127.0.0.1:21325/api/connect', {method:'POST'})
  .then(r=>r.json())
  .then(device => console.log('Device', device.features))
  .catch(err => console.error('Bridge error', err));

Tip: fall back to WebUSB/WebHID when available for direct browser support and disable Bridge only if users explicitly choose native access.

Security model

Trezor Bridge is intentionally local-only. It does not transmit private keys or transaction secrets to remote servers. The Bridge forwards structured JSON-RPC requests to the device and returns signed payloads only after explicit user approval on the hardware. Always verify firmware attestation and require user confirmation for sensitive operations.

Troubleshooting & tips

Restart your browser after installing Bridge.
Try a different USB cable/port and check OS permissions.
Ensure Bridge is running (check system tray / background services).
Update device firmware through official channels if prompts appear.
Run Bridge diagnostics (logs) to capture errors for support.

Frequently Asked Questions

Is Trezor Bridge required for all users?+

No — modern browsers with WebUSB/WebHID support may connect to Trezor devices directly. Bridge is recommended for broader compatibility and where native access is restricted.

How do I verify a Bridge download?+

Always download from the official site or verified channels. If signature hashes are published, compare checksums to ensure integrity before installing.

Can Bridge be used headless for automation?+

Yes, in controlled test environments you can run Bridge headless. Do not use production private keys in CI — use simulators and test vectors instead.

What ports/protocols does Bridge use?+

Bridge typically listens on a local HTTP endpoint and uses WebSocket/HTTP JSON-RPC patterns. Consult official docs for exact ports and firewall guidance.

Who do I contact for support?+

Use the community forum, official support channels, or open a ticket with logs and reproduction steps. Provide Bridge version, OS, browser, and device firmware details.