Trezor Bridge — the secure gateway to your hardware wallet

Trezor Bridge provides a stable, local communication channel between your Trezor hardware wallet and the applications you use — from the Trezor Suite desktop app to web-based wallets and dApps. It’s designed to be lightweight, cross-platform, and secure: Bridge never has access to your private keys — signing always happens on-device.

Download Bridge Open Trezor Suite (Web)

Key resources: Downloads • Firmware • Support

Local-first

Bridge runs on your machine and exposes a localhost API — no external servers mediate the connection.

Cross-platform

Supports Windows, macOS, and Linux with platform-specific installers and package options.

Secure-by-design

Bridge only forwards messages — private keys remain on the Trezor device and signing requires physical approval.

Overview — what Bridge does

Trezor Bridge acts as a translator between applications and your hardware device. Web apps and desktop Suite send JSON-RPC or similar commands to Bridge on a localhost port; Bridge communicates with the Trezor over USB, relays responses back to the app, and ensures that sensitive operations are confirmed on the device itself.

Bridge is essential because it:

Enables web-based wallets to use hardware wallets reliably;

Handles platform-specific USB permission quirks;

Provides a stable API for applications to talk to devices;

Does not read or expose private keys — signing is performed on the hardware.

Install & configure Bridge (step-by-step)

Download from official sources: Start at trezor.io/bridge or the central Downloads page to choose your platform-specific installer.

Verify integrity: Where checksums or signatures are provided, verify them before running the installer so you can be confident the file hasn't been tampered with.

Install: Run the installer and follow OS prompts. Bridge runs as a background service and listens on a localhost port to accept connections from apps like Suite.

Restart apps: Restart your browser or open Trezor Suite so the application can detect Bridge. You may need to accept permission prompts for USB access.

Connect device: Plug in your Trezor and follow on-screen instructions. Always confirm transaction details on the device screen.

Notes: Desktop Suite includes native connectivity for some platforms, but installing Bridge ensures consistent behavior for web workflows across browsers and operating systems.

Security & best practices

Bridge is designed with minimal trust — it runs locally and only forwards messages. However, the overall security depends on your environment and behavior. Follow these best practices:

Install only official builds: Use trezor.io/bridge or trezor.io/downloads to avoid malicious copies.

Keep software updated: Update Bridge, Suite, and device firmware regularly. See Firmware updates and release notes.

Localhost only: Ensure Bridge listens only on localhost and is not exposed to the broader network or through port forwarding.

Trust app sources: Only grant connections to apps you trust. When in doubt, decline access and verify the app origin.

Phishing vigilance: Never enter your seed or passphrase into a website. Learn more at Anti-Phishing.

Troubleshooting — common issues & fixes

Bridge not running: Restart the Bridge service or your computer. On Windows or macOS check system services/processes.
Browser can't connect: Restart the browser, clear cache, or try a different browser. Ensure localhost is not blocked by security policies.
Permission prompts missing: Reconnect the device and check for OS-level USB permission dialogs. Some browsers require explicit site permissions.

Multiple versions: Uninstall older Bridge versions and reinstall the latest from official Bridge.
Firmware mismatch: Verify device firmware and update if needed — see Firmware.
Still stuck: Consult Support or community resources.

Developer notes & integrations

For developers building integrations, Bridge provides a predictable local API. Keep these points in mind:

Validate origins and prompt users for explicit confirmation for sensitive actions.

Use official SDKs and libraries where available — browse GitHub for code and examples.

Test across platforms and browser combinations to handle permission differences and driver behaviors.

Consider desktop Suite native connectivity for tighter integration in desktop applications.

Support & resources

Here are ten essential official links and resources for users and developers:

If you need personalized help, open a support ticket via the Support Center or consult community forums — never share your seed or passphrase when asking for help.