Trezor® Bridge

Secure Connection for Your Hardware Wallet — seamless, local, and privacy-preserving communication between Trezor devices and apps.

Bridge the gap — connect safely, transact with confidence

Trezor® Bridge is a small, dedicated piece of software that runs on your computer and securely mediates communication between your web browser or desktop app and your Trezor hardware wallet. It provides a stable, cross-platform transport layer so you can manage accounts, sign transactions, and verify actions on-device — all without exposing your private keys to the host machine.

Download Bridge Release notes

What it does

Acts as a secure local server on your machine. It translates requests from apps into messages your Trezor device can understand, and returns device responses back to the app — always requiring manual confirmation on-device for sensitive operations.

Why it exists

Browsers can't directly access USB or certain device APIs consistently across platforms. Bridge standardizes communication while giving users an auditable local component they control.

Cross-platform

Available for Windows, macOS, and Linux. Lightweight and fast — optimized to run in the background only while needed.

Security model

Bridge only proxies messages. Private keys never leave the Trezor device, and all transaction approvals require explicit confirmation on the hardware screen.

Features & benefits

Secure local transport

Bridge runs as a local service on your computer, providing a reliable channel for software to communicate with the Trezor device without exposing keys or passphrases to the host.

Consistent browser integration

Works with web-based wallet interfaces and decentralized apps — no browser extensions required. Your browser talks to Bridge, which then talks to the device.

Automatic device discovery

When Bridge is installed and running, it detects connected Trezor devices and makes them available to authorized apps on your computer.

Minimal footprint

Lightweight installer and low resource usage. Designed to start on demand and stop when idle, keeping your system tidy.

Privacy-first

Bridge only communicates locally and does not collect transaction data. Any cloud interactions come from the application you use (e.g., Suite), not Bridge itself.

Auditable & transparent

Logs and behaviors are local; advanced users can inspect communication for troubleshooting. Official builds are signed and distributed via the Official Site®.

Install & setup — step by step

Getting Bridge running

  1. Download the correct installer: Choose the build for your OS from the Official Site®. Prefer official releases — avoid third-party mirrors.
  2. Run the installer: On Windows, allow the installer to create a local service. On macOS, follow the package prompts. On Linux use the provided package or distribution instructions.
  3. Allow USB access: When the app asks for permission to access USB devices, allow it for Bridge to enumerate your Trezor.
  4. Verify operation: Open the desktop app or web interface; it should detect your device and prompt you for hardware confirmation on the Trezor display.

Troubleshooting & tips

Bridge not detected?

Restart the Bridge service, unplug and replug your Trezor, and ensure no other application is blocking USB. On macOS, check Security & Privacy settings if the installer was blocked. If problems persist, reinstall Bridge from the Official Site®.

Browser can't connect?

Ensure your browser is up-to-date and that Bridge is running. Some corporate or privacy-focused browsers may restrict localhost connections — try a mainstream browser (Chrome, Edge, Firefox) for diagnosis.

Permission errors on Linux?

Set correct udev rules (instructions provided with Bridge packages). Running the app with elevated privileges is not recommended; fix permissions instead to maintain a secure environment.

Security considerations

Understanding how Bridge fits into your security model is essential. Bridge is only a communication helper — it cannot sign transactions or reveal private keys. The Trezor device performs all critical cryptographic operations and displays transaction data for you to confirm. Still, follow these best practices:

Passphrase & PIN

Bridge does not handle PINs or passphrases. PIN entry is performed on the device; passphrases (if used) are managed by your chosen workflow. Losing these means losing access to funds — keep backups in secure, offline storage.

Frequently asked questions

Do I need Bridge to use Trezor?

For many browser-based apps and for some legacy desktop integrations, Bridge simplifies communication. Trezor Suite includes built-in transport options, but Bridge is often recommended for maximum compatibility across third-party web apps.

Does Bridge send my transaction data anywhere?

No. Bridge facilitates local communication only. Any transaction broadcast goes through the application you use (e.g., a wallet backend or node provider), not Bridge itself.

Can I uninstall Bridge safely?

Yes. Uninstalling Bridge removes the local service; your Trezor device and recovery seed remain unaffected. Reinstall whenever you need to reconnect to apps that require it.

Where can I find logs for debugging?

Bridge keeps local logs that advanced users can inspect. Use these when submitting a bug report to support; avoid sharing sensitive data publicly.