Trezor Suite, the desktop and web app for managing a Trezor hardware wallet
Trezor Suite is the application that turns a Trezor hardware wallet from a locked box into something you can use day to day. The device stores private keys and signs transactions. Trezor Suite does everything around that: it reads balances from blockchain indexers, builds unsigned transactions, passes them to the device for approval, and broadcasts them once you confirm the details on the device screen. It ships as a downloadable program for Windows, macOS, and Linux, and as a browser version for machines where installing software is not an option.
This page explains what Trezor Suite does, where the trust boundary sits between the app and the hardware, which privacy controls are worth turning on, how coins and account types are organized, and what to do when something behaves oddly. If you have a device in front of you and want the short path, jump to the setup sequence.
- Form
- Desktop + web
- Platforms
- Win / macOS / Linux
- Key custody
- On device only
- Source code
- Open source
What Trezor Suite actually is
It helps to be precise about the vocabulary. A cryptocurrency wallet is a set of keys, and those keys live inside the hardware device. Trezor Suite is the interface layered on top of them. It knows your public keys, so it can derive addresses and show a full transaction history, but it never sees a private key, a recovery seed, or a passphrase in a form it could leak. That separation is the whole point of the product, and almost every design decision in Trezor Suite follows from it.
Trezor Suite consolidated a job that used to be spread across several tools. Older Trezor devices were driven by a browser-based wallet page plus a separate helper program for USB communication, with firmware updates and exchange services handled elsewhere. Trezor Suite pulled account management, firmware maintenance, device settings, privacy options, and third-party buy and swap services into one application with a single account model. The source code is published, so builds can be audited and reproduced by people who do not want to take the vendor's word for it.
Two kinds of user end up in Trezor Suite. The first wants a portfolio view and a safe send button, and is served well by the defaults. The second wants coin control, Taproot accounts, a custom backend pointed at a personal node, and hidden wallets behind passphrases. Trezor Suite tries to serve both by keeping the advanced controls present but out of the way, which is why the app can look deceptively simple on first launch.
How the app talks to the device and the blockchain
Communication runs over the USB cable. The desktop build of Trezor Suite includes the transport layer it needs, so there is nothing extra to install and no background helper to keep patched. The browser build depends on the browser's own USB access, which is why Chromium-based browsers tend to be the smoothest route and why a browser that blocks device access will simply never see the wallet. When Trezor Suite detects a device it reads the firmware version and public key material for the accounts you have enabled, and nothing more.
Balances and history come from blockchain indexers rather than from the device, because the hardware has no network connection of its own. By default Trezor Suite queries the vendor's public indexing servers, which is fast and requires no configuration but means those servers learn which addresses you are asking about. For Bitcoin and several other chains, Trezor Suite lets you replace that default with a backend you control, which is the standard answer for anyone who cares about that metadata.
A payment moves through a fixed sequence. Trezor Suite selects inputs, assembles an unsigned transaction, and sends it to the device. The device renders the destination address, the amount, and the fee on its own screen and waits for a physical confirmation. Only then does it return a signature, which Trezor Suite wraps into a final transaction and broadcasts. Nothing in that chain requires the computer to be trustworthy, which is precisely why the confirmation screen exists.
Firmware is handled in the same spirit. Trezor Suite offers updates, but the device itself verifies the cryptographic signature on any firmware image before running it, and it shows a fingerprint you can compare. Newer models add an authenticity check that uses a factory-provisioned secret to confirm the hardware is genuine, and Trezor Suite surfaces the result of that check as a plain pass or fail rather than burying it in a log.
Stays on device
Private keys, recovery seed, passphrase entry, PIN verification, signing, display confirmation.
Handled by the app
Address derivation from public keys, history lookup, fee estimation, coin selection, broadcast, labels.
Outside both
Exchange and staking partners, fiat rates, and any indexer you point Trezor Suite at.
Dashboard, accounts, and everyday actions
The first screen after unlocking is a portfolio dashboard: total value, a value-over-time chart, a breakdown by asset, and the most recent transactions across every enabled account. It is a summary, not a trading terminal, and the numbers depend on rate data pulled from the network, so treat them as a reference rather than an audit.
Below that sits the account structure, which is the part worth understanding properly. Trezor Suite organizes holdings into named accounts, each with its own derivation path and history, and you can add more accounts per coin as you need them. For Bitcoin the app exposes account types including Taproot, native SegWit, and legacy formats, because address type affects fees, compatibility with older senders, and which addresses a given exchange will accept. Coins are not all enabled by default, so the settings screen is where you switch on the ones you hold and hide the rest to keep the list readable.
Receiving is deliberately slightly slow. Trezor Suite generates a fresh address and asks you to display and verify it on the device before it will show the full string in the app, which is the defense against malware that swaps addresses in a browser window. Sending offers preset fee levels plus a custom rate, and for Bitcoin you can bump the fee on a stuck transaction using replace-by-fee. Users who care which coins they spend can open coin control and select individual unspent outputs by hand instead of letting the automatic selection mix histories together.
Small conveniences round out the interface. Labels let you annotate accounts, addresses, and transactions so a history is readable months later; the labeling data is encrypted with keys derived from your device and can be kept locally or synced through a third-party file storage account of your choice. Discreet mode blanks all amounts with a keystroke, which is genuinely useful in a café or on a shared screen, and Trezor Suite offers light and dark themes plus a choice of display currency.
Privacy and network controls worth changing
Hardware protects keys; it does not hide activity. Every time Trezor Suite refreshes an account it asks a server about a set of addresses, and that server can associate those addresses with your IP address. Nothing about that leaks funds, but it does leak a picture of your holdings to whoever operates the endpoint.
Two settings address this. The first is the built-in Tor option in the desktop build, which routes the app's requests through the Tor network so the indexer sees a relay rather than your connection. Expect slower syncing in exchange. The second, and stronger, is pointing Trezor Suite at a custom backend, meaning an indexing server you run yourself alongside your own full node. Then the only party learning your addresses is you.
Passphrases add a different kind of privacy. Because a passphrase produces an entirely separate wallet from the same recovery seed, Trezor Suite treats each one as its own hidden wallet with its own accounts and balances, invisible unless that exact passphrase is entered again. Combined with coin control, this gives you room to keep savings and spending genuinely apart. Do not confuse it with encryption of the app itself, though: any Trezor Suite installation with the right device and passphrase will show the same wallet.
Security model, backups, and the mistakes that cost money
The PIN is entered so that the computer cannot learn it, and repeated wrong guesses impose increasing delays. That means a stolen device is not an immediate loss, but it also means the PIN protects the hardware rather than the wallet: someone with your recovery seed does not need the device or the PIN at all. Trezor Suite will remind you of this during setup, and the reminder is worth taking literally.
Your backup is the wallet. Trezor Suite guides you through creating one during initialization, either as a single recovery seed written on paper or, on models that support it, as a Shamir-style split backup where several shares are generated and a defined subset is required to restore. Split backups suit people who want geographic separation without a single sheet of paper that unlocks everything. Whichever you choose, it happens once, offline, and Trezor Suite never displays those words on the computer screen.
The genuine failure modes are mundane. People photograph a seed, type a passphrase they cannot reproduce exactly, approve a transaction without reading the device screen, or install a wallet app that resembles Trezor Suite but was downloaded from a search advertisement. Trezor Suite mitigates the last of these with signed desktop builds and firmware signature checks, but the download step itself is on you: get the installer from the vendor's own domain and verify it if you know how.
Verification checklist
- 01Confirm the destination address on the device display, character groups included, not in the Trezor Suite window.
- 02Let the device show a receive address before you copy it out of Trezor Suite.
- 03Never enter a recovery seed into Trezor Suite, a browser, or any other software; recovery is done on the device.
- 04Run the device authenticity and firmware checks that Trezor Suite offers when you first connect new hardware.
device_check = firmware_signature_valid AND authenticity_pass AND on_screen_confirm
What you can hold and where the edges are
Trezor Suite manages major coins natively, including Bitcoin, Ethereum with its ERC-20 tokens, several Bitcoin-derived chains such as Litecoin and Bitcoin Cash, Cardano, XRP, and Solana. Exact coverage shifts with firmware releases and differs by device model, and there is a Bitcoin-only firmware option for people who want the smallest possible attack surface, so the coin list inside your own copy of Trezor Suite is the authoritative answer rather than any published summary.
Some assets the hardware can protect are not fully manageable inside the app. In those cases the device is used as a signer for a compatible third-party wallet, which keeps the keys on the hardware while another interface handles the chain-specific features. That is a normal arrangement, not a workaround, but it does mean you should confirm the workflow for an unusual asset before moving a meaningful amount.
| Asset family | Account types in the app | Notes |
|---|---|---|
| Bitcoin | Taproot, native SegWit, SegWit, legacy | Coin control, fee bumping, and custom backend support are most complete here. |
| Ethereum and ERC-20 tokens | Single account type, multiple accounts | Tokens appear under the account holding them; gas is paid in the native coin. |
| Bitcoin-derived chains | Varies by chain | Litecoin, Bitcoin Cash and similar chains follow the Bitcoin account model closely. |
| Cardano, XRP, Solana | Chain-specific | Supported on models with the required firmware; check availability in Trezor Suite settings. |
| Other supported coins | External wallet, device as signer | Keys stay on the hardware while a compatible third-party interface handles the chain. |
Buying, selling, swapping, and staking inside the app
Trezor Suite includes a trading section that aggregates offers from outside providers rather than operating an exchange itself. You pick a quote, and the provider handles payment, identity checks where required, and settlement, with the coins delivered to an address from your own account. The convenience is real, since the receiving address comes from the device rather than being typed by hand, but the terms, fees, and data collection belong to the provider you selected, not to Trezor Suite.
Selling and swapping work the same way. A swap moves value between two of your accounts through a partner service, which means it involves a real counterparty, a real spread, and a transaction you must approve on the device like any other. Rates shown in Trezor Suite are quotes at that moment, so a delay while you find the confirmation button can change what you receive.
Staking is offered for selected proof-of-stake assets through integrated providers, letting you delegate or stake without leaving the app while keys remain on the device. It is worth reading the specifics before committing funds: lock-up and unbonding periods, provider fees, and the mechanics of claiming rewards vary by chain, and Trezor Suite is the interface to those rules rather than the party setting them.
Desktop, browser, and the mobile companion compared
The desktop application is the reference implementation and the one to prefer when you have the choice. It carries the full feature set, including the Tor toggle, and it does not depend on a browser's permissions model or extensions. The browser version exists for locked-down or borrowed machines and behaves like the desktop app in most respects, but it inherits whatever the browser allows.
On phones, the companion app is a portfolio viewer built around public keys imported by scanning, not a full replacement for Trezor Suite. It lets you check balances and incoming payments while away from your computer, and it deliberately cannot spend, because spending requires the connected device and the confirmation step that only the hardware can provide.
| Capability | Desktop app | Browser version | Mobile companion |
|---|---|---|---|
| View balances and history | Yes | Yes | Yes |
| Send and sign transactions | Yes | Yes | No |
| Firmware updates and device settings | Yes | Yes | No |
| Built-in Tor routing | Yes | Browser dependent | No |
| Custom backend or own node | Yes | Yes | No |
How to get started with Trezor Suite
A first-time setup takes roughly twenty minutes, most of which is spent writing down a backup by hand. Work somewhere private, keep a pen ready, and do not rush the backup step; everything else in Trezor Suite can be redone later, and that step cannot.
-
Step 01
Install from the official source
Download the desktop build for your operating system from the vendor's own site, or open the browser version. Ignore search advertisements and app-store lookalikes; a fake copy of Trezor Suite is the most common way people lose funds.
-
Step 02
Connect and verify the device
Plug in the wallet with its cable. Trezor Suite will detect it, run the authenticity and firmware checks, and install firmware if the device shipped without it. Do not continue if a check reports a problem.
-
Step 03
Create the wallet and back it up
Choose a new wallet, then follow the backup process on the device screen and copy every word in order onto paper or metal. Trezor Suite never shows these words, so nothing is stored on the computer.
-
Step 04
Set a PIN and name the device
Set a PIN you will remember without writing it beside the seed, then give the device a name so Trezor Suite can tell it apart from any other wallet you connect.
-
Step 05
Enable your coins and make a test transfer
Switch on the assets you actually hold, then receive a small amount and send part of it back before moving anything substantial. That round trip proves the backup, the confirmation flow, and your own understanding of the interface. Afterwards, revisit the settings in Trezor Suite for Tor, a custom backend, or a passphrase-protected hidden wallet if those fit how you plan to store value.
Common problems and what usually causes them
A device that is not detected is almost always a cable, a port, or a permission issue rather than a broken wallet. Charge-only cables are the classic culprit, USB hubs are the second, and on Linux the udev rules that allow user access to the device may need installing. If the desktop app cannot see the hardware, try the browser version, or the reverse, since that quickly tells you whether the problem sits in Trezor Suite or below it.
Missing balances usually mean the wrong account rather than missing coins. A passphrase produces a distinct wallet, and a single wrong character silently produces a different empty one, so check that you opened the hidden wallet you meant to. On Bitcoin, funds sent to a legacy address will not appear in a Taproot or SegWit account; adding the matching account type in Trezor Suite brings them into view. Coins on a chain the app does not manage need the appropriate third-party interface.
Stalled syncing points at the backend. If the default servers are slow or unreachable, or if Tor is making requests time out, switching the connection settings is the fastest diagnostic. Users running a personal node should confirm the node is fully synchronized before blaming Trezor Suite for balances that look wrong, because the app can only report what the backend tells it.
Transactions that sit unconfirmed are a fee problem, not a bug. Bitcoin fee markets move quickly, and a rate that looked comfortable an hour ago can be too low now. Trezor Suite can bump the fee on an eligible transaction, and for the receiving side there is nothing to do but wait. If a firmware update interrupts mid-way, the device has recovery paths built in, and this is the moment when a correct backup turns a frightening evening into an inconvenience.
Frequently asked questions
Does Trezor Suite cost anything?
The application is free and open source; you pay for the hardware. Fees appear only when you use network transactions or a third-party buy, sell, swap, or staking service reached through the app.
Can I use it without a hardware wallet?
No. Trezor Suite is built around a connected device that holds the keys and confirms transactions, so there is no software-only wallet mode to fall back on.
What happens if my computer is infected?
Malware can lie to Trezor Suite about addresses and amounts, but it cannot extract keys or sign for you. Verifying every detail on the device display is what neutralizes that class of attack.
Do I lose access if the app disappears?
No. Your coins are controlled by the seed on the device, following open standards, so they can be recovered with other compatible wallets even without Trezor Suite installed.
Should I install the desktop app or use the browser?
Use the desktop build when you can. It has the complete feature set, including Tor, and avoids depending on browser permissions or extensions. The browser version of Trezor Suite is the fallback for restricted machines.
Can two devices share one installation?
Yes. Trezor Suite handles multiple devices, each with its own name and set of accounts, and it can hold several passphrase-protected hidden wallets per device.
Are my labels and settings private?
Labeling data is encrypted with keys derived from your device before it is stored, whether you keep it locally or sync it to third-party file storage. Balances themselves are still fetched from an indexer unless you change the backend.
Do firmware updates put funds at risk?
The device verifies firmware signatures before installing, and Trezor Suite walks you through the process. Still, have your backup present before starting an update, since that is the one thing that guarantees recovery.
The short version
Trezor Suite is a competent, unflashy control panel for hardware-secured coins. It reads the chain, composes transactions, keeps a legible history, and hands every consequential decision to the device in your hand. Learn where the confirmation screen is, keep the backup somewhere you would trust with the value it represents, and the rest of Trezor Suite becomes a matter of preference rather than risk.
If you want to go further, the two settings with the largest effect are the network backend and the passphrase. Both live in Trezor Suite, both take a few minutes to configure, and both change what other parties can learn about you far more than any other option in the app.