Trezor Bridge used to be the recommended transport layer for communicating with Trezor hardware devices from browsers and third-party wallets. It operated as a lightweight, cross-platform background application that abstracted USB quirks across operating systems and browsers. When WebUSB support was inconsistent across platforms, Bridge provided a reliable way for websites and wallets to connect to your Trezor device without complex driver installations.
Bridge's design focused on stability: it managed device permissions and maintained a local HTTP-style transport that web pages could call into. For several years it helped make web-based wallet experiences usable for both Trezor One and Model T users. But as browsers improved native USB support and Trezor consolidated connectivity into the official Trezor Suite, the role of the standalone Bridge changed.
Current status — short
Standalone Trezor Bridge is no longer the recommended path. Modern users should rely on Trezor Suite (desktop or web) and native browser WebUSB flows. Bridge is effectively deprecated for the majority of users and keeping an old Bridge installation can cause conflicts with newer Suite transports.
When Bridge might still be seen
Bridge can appear in three contexts today: legacy systems that haven't adopted modern WebUSB, very old device firmware that required Bridge for certain flows, or niche third-party wallets that haven't migrated away from Bridge. Even in those rare cases, the better approach is to upgrade the host environment or use Suite where possible.