Trezor Suite, the companion app for Trezor hardware wallets
Trezor Suite is the official desktop and web application that SatoshiLabs builds for its hardware wallets. It is where you set up a new device, install firmware, create and verify a backup, watch balances, and sign payments. The private keys never leave the hardware; Trezor Suite is the interface that talks to the device, assembles transactions for it to approve, and reads the blockchain on your behalf.
This page explains what Trezor Suite does, how the desktop build differs from the browser version and the watch-only mobile companion, which privacy and security controls are worth switching on, and what to check first when the app cannot see a connected device.
- Free to use
- Open source
- Windows / macOS / Linux
- Browser version
- No account, no email
What the application is and who builds it
Trezor Suite is a single application that took over from the older browser-only wallet interface. Instead of visiting a web page to manage coins, most owners install Trezor Suite on their computer as a normal desktop program. It brings device management, wallet management and market access into one window, and it works with the current hardware models as well as older ones.
A hardware wallet on its own cannot show you a balance. It holds keys and signs data, nothing more. Something has to ask the network what happened to your addresses, turn that into readable history, and hand unsigned transactions to the device for approval. In this ecosystem that job belongs to Trezor Suite.
The software is free, needs no registration, and is published as open source, so the code that builds your transactions can be read and audited by anyone. Trezor Suite also never asks for personal details: there is no cloud login, no email address, and no identity check to use the wallet functions themselves.
Because the same company makes both halves, Trezor Suite is also the channel through which firmware arrives. Firmware images are cryptographically signed, and Trezor Suite checks that signature before a device will accept an update, which is one reason firmware should never be installed from anywhere else.
Key takeaways
The short version: the device is the vault, and Trezor Suite is the control panel bolted to the front of it.
- Keys are generated and stored on the device. Trezor Suite never sees them.
- Every payment must be confirmed on the device screen, not in the app window.
- The app is free, open source and account-free.
- Buying, selling, swapping and staking are handled by third-party providers with their own rules.
How the keys stay off your computer
When you unlock a device in Trezor Suite, the hardware exports public account information, commonly called an extended public key, for each account you use. From that, Trezor Suite can derive every receiving address in the account and look up their history, but it cannot spend a single coin. Read more about the general idea of a cryptocurrency wallet if the terminology is new.
Spending works in three moves, and the middle one is the important one. Trezor Suite collects the recipient, amount and fee, builds an unsigned transaction, and passes it to the device. The device renders the details on its own screen. If you approve them there, it hands back a signed transaction, and Trezor Suite broadcasts it to the network.
That split is the entire security argument. A computer carrying malware could tamper with what Trezor Suite displays, but it cannot change what appears on the hardware screen or forge the button press on the device. This is why every piece of guidance insists on reading addresses and amounts from the device, never from the monitor.
Blockchain data itself has to come from somewhere. By default the app queries indexing servers run by the vendor, and advanced users can point Trezor Suite at their own node instead, so no outside party learns which addresses are being watched.
The device signs. The app asks. Nothing in between ever holds your recovery seed.
Compose
Trezor Suite gathers inputs, outputs and the fee, then serializes an unsigned transaction.
Confirm
The hardware displays the destination and amount. Approval happens with the device buttons or touchscreen.
Broadcast
The signed result returns to Trezor Suite, which relays it to the network and tracks confirmations.
Desktop app, browser version, and mobile companion
Trezor Suite ships as a desktop application for Windows, macOS and Linux. That build is the recommended way to work with the hardware, because Trezor Suite handles device communication itself, ships as a signed application, and does not depend on browser permissions or extensions that can change without warning.
There is also a browser version for situations where installing software is impossible, such as a locked-down work machine. It covers nearly the same ground, but it lives inside the browser security model, so page integrity depends on the browser and on the connection at that moment rather than on a program you installed once and verified.
The mobile companion, Trezor Suite Lite, is deliberately limited. It is a watch-only app for Android and iOS: you pair account information from Trezor Suite on the desktop, then check balances and generate receiving addresses from a phone. It cannot sign or send anything, and that restriction is exactly what makes it safe to carry.
All three share one design idea. Accounts, labels and preferences belong to the device and to your local Trezor Suite installation rather than to an online profile, so moving to a new computer means installing Trezor Suite again and plugging in the device, not recovering a password to some server.
Compared with other ways to use the device
The hardware is not locked to a single interface. It also works with third-party software such as browser wallet extensions and desktop Bitcoin clients, and that flexibility is genuinely useful. The table below sets out what changes when you step outside Trezor Suite.
| Capability | Trezor Suite desktop | Trezor Suite web | Trezor Suite Lite | Third-party wallets |
|---|---|---|---|---|
| Device setup and firmware | Yes | Yes | No | No |
| Balances and history | Yes | Yes | Yes | Varies |
| Sign and broadcast | Yes | Yes | No | Yes |
| Coin control for Bitcoin | Yes | Yes | No | Varies |
| Tor routing toggle | Yes | No | No | Varies |
| Own node as backend | Yes | Limited | No | Varies |
| Buy, sell, swap panel | Yes | Yes | No | Varies |
| Passphrase wallets | Yes | Yes | No | Varies |
A sensible rule follows from this: keep firmware, backup and device settings inside Trezor Suite, and treat third-party wallets as specialist tools for particular jobs rather than as replacements for it.
Setting up a new device step by step
The first run is scripted and hard to get wrong, but it deserves full attention, because two of its steps cannot be repaired later. When a new device is connected, Trezor Suite checks whether firmware is present, verifies the signature on the image it is about to write, and asks you to confirm the installation on the device itself.
Next comes wallet creation and backup. The device generates a recovery seed internally and shows the words on its own display. Trezor Suite paces the process and runs a quiz-style check afterwards, but the words never appear in the app window. Write them on paper or steel, keep them offline, and never type them into any computer, including into Trezor Suite.
Supported models can produce a multi-share backup instead of one continuous word list, splitting the secret into shares of which a threshold is needed to restore access. Trezor Suite walks through creating and verifying each share in turn, which takes longer but suits people who want geographic separation of their backup.
The last required step is a PIN, entered through a scrambled layout so that software watching the host learns nothing useful. After that, Trezor Suite offers the optional passphrase feature: any passphrase you enter opens a separate hidden wallet derived from the same seed. It is powerful and unforgiving, because a forgotten passphrase cannot be reset or recovered by anyone, the manufacturer included.
Recovery runs the same road backwards. Choose the recovery option in Trezor Suite, state how many words your backup holds, and follow the prompts, where entry happens on the device screen or through a protected input method depending on the model you own.
Accounts, assets, and address types
Trezor Suite organizes holdings into accounts rather than one undifferentiated pile. Each account is a separate branch of the key tree derived from your seed, with its own addresses, history and balance, and you can add more of them whenever you want to keep savings apart from spending money.
For Bitcoin, several account types sit side by side: legacy addresses, wrapped SegWit, native SegWit and Taproot. They differ in address format, fee efficiency and compatibility with older services. Coins held under one type do not appear under another, which is why a restored backup sometimes looks empty in Trezor Suite until the right account type is enabled.
Beyond Bitcoin, Trezor Suite handles Ethereum together with tokens on it and on further networks, plus a long list of other chains. Exactly what appears depends on the connected model, since older hardware cannot run every coin implementation, and Trezor Suite hides assets the device in front of you cannot sign for.
Naming things helps more than people expect. Trezor Suite lets you label accounts, addresses and individual transactions, and it can keep those labels encrypted and synchronized through a personal cloud storage account, so the same names show up on a second computer. The labels are metadata encrypted with a key derived from the device, and they have no effect on the funds themselves.
Sending, receiving, and fee control
To receive, open the account in Trezor Suite, request a fresh address, and confirm that the address shown on the device matches the one in the app before you share it. Trezor Suite issues a new address for each request, which stops a run of payments from being trivially tied together by anyone reading the chain.
Sending asks for a recipient, an amount and a fee level. Trezor Suite offers presets based on current network conditions plus a custom option for people who prefer to name their own rate. For Bitcoin it also supports replace-by-fee, so a transaction stuck in a busy mempool can be bumped rather than abandoned.
Coin control is the feature that brings experienced users in. A Bitcoin balance is really a set of separate unspent outputs, and Trezor Suite can list them individually and let you pick exactly which ones fund a payment. That matters for privacy, since careless spending merges coins from unrelated sources into one transaction that links them forever.
History views show confirmations, fees paid and the addresses involved, and a date range can be exported for bookkeeping. Balances can be displayed in a chosen national currency using rate data the app fetches, which is a display convenience rather than any form of custody or conversion.
Privacy controls worth knowing about
Owning a hardware wallet does not make your activity private by itself. Any wallet application has to ask some server about your addresses, and those questions reveal interest even when they reveal no keys. Trezor Suite gives you several ways to narrow that leak.
The desktop version can route its traffic through Tor with a single switch. Requests then reach the backend from an anonymous circuit rather than from your home connection, at some cost in speed. It is a per-installation setting and it covers the blockchain lookups Trezor Suite makes on your behalf.
For maximum separation, run your own node and tell Trezor Suite to use it as the backend. No external service then sees your addresses at all. This is the strongest privacy posture available in Trezor Suite, and also the one that asks for the most upkeep, so it suits people already running node software.
Two smaller controls finish the picture. Discreet mode blurs amounts so a screen is safe to show in a cafe or on a call, and the anonymous usage analytics offered during onboarding can be declined outright, either during initial setup or later in the settings.
Buying, selling, swapping, and staking
Trezor Suite includes an exchange area that connects to outside brokers and exchanges. You can compare offers to buy coins with a card or bank transfer, sell back into national currency, or swap one asset for another, with the coins arriving at or leaving addresses your own device controls.
Two points are worth understanding before using it. First, these providers are separate businesses, so their fees, limits, country coverage and identity requirements are theirs and not something Trezor Suite sets. Second, the identity verification some of them demand is the one place where using Trezor Suite involves handing personal data to a company, and that data goes to the provider rather than into the wallet.
Selected networks can also be staked from inside Trezor Suite through integrated partners, with rewards accruing to your own address while the keys stay on the hardware. Staked funds typically carry lock-up or unbonding periods set by the network, and Trezor Suite reports the state of a stake rather than controlling the schedule.
A useful mental model: Trezor Suite is the wallet, and the trading and staking panels are shop windows onto other companies. Read their terms, check their fees against the spot price, and start small the first time.
Security habits that matter most
Hardware protects keys from a compromised computer. It does not protect a user who is talked into approving the wrong thing, and most real losses in this field come from that direction rather than from broken cryptography.
Download discipline comes first. Obtain Trezor Suite only from official channels, verify signatures if you know how, and treat any search advertisement, chat message or email offering a Trezor Suite download, an urgent update, or a wallet validation as hostile until proven otherwise.
Confirmation discipline comes second. Read the address and the amount on the device screen every single time, including the middle of the address rather than only the first and last characters. Trezor Suite is built around the device being the source of truth precisely because a general purpose computer cannot be one.
Backup discipline comes third, and it is the one that decides whether a mistake is survivable. The recovery words are the wallet. No legitimate person, support agent or web page will ever need them, and no genuine feature of Trezor Suite requires typing them into a computer.
- Confirm every address and amount on the device, not in the app window.
- Keep the recovery backup offline, on paper or metal, in more than one location.
- Install firmware only through a prompt inside Trezor Suite that you started yourself.
- Add a passphrase only after you understand that a forgotten one is unrecoverable.
- Test a new setup with a small amount in and a small amount out before moving real value.
How to get started
Five steps take a boxed device to a working wallet. Set aside half an hour and do it somewhere you can write without anyone watching. Trezor Suite paces the sequence; you supply the patience.
-
01
Install the app
Download Trezor Suite for your operating system from the official source and install it like any other program, or open the browser version if installing is not allowed on that machine.
-
02
Connect and verify
Plug in the device and let Trezor Suite run its firmware and authenticity checks, approving each prompt on the device rather than assuming the screen on your desk is right.
-
03
Create and back up
Follow the backup flow and record the words offline, in order. Do not photograph them, do not store them in a password manager, and do not type them anywhere.
-
04
Set a PIN
Choose a PIN you will actually remember, then leave the passphrase feature alone until you have read how hidden wallets behave and decided you need one.
-
05
Add accounts and test small
Enable the coins you need in Trezor Suite, receive a small amount first, confirm it arrives and shows the expected history, then send a small amount back out before you move anything significant.
When the app cannot see your device
Most connection trouble is physical or driver-level rather than mysterious. Try a different cable, use a port directly on the machine instead of a hub, and unlock the device before expecting Trezor Suite to react to it. Cables that only carry power are a common culprit.
In the browser, communication depends on a helper component and on page permissions, which adds moving parts. The desktop build of Trezor Suite avoids that whole category of problem, so switching to it is the first thing to try when the web version stays stubborn.
An empty balance after a recovery is almost never lost money. Usually the relevant coin or Bitcoin account type has not been enabled yet, so adding the missing account in Trezor Suite brings the history straight back. If a transaction sits unconfirmed, compare its fee with current network conditions and consider bumping it instead of sending again.
If an update stalls or the device shows a screen you did not expect, stop clicking and read the device. Reconnecting, restarting Trezor Suite and beginning the update again from the app is safe as long as your recovery backup exists, which is the whole reason that backup is created before any funds arrive.