Hardware wallet software
What Trezor Suite is and how it works
Trezor Suite is the software half of a Trezor hardware wallet. The device holds the private keys and signs transactions; Trezor Suite is the application that reads the blockchain, shows balances, assembles transactions, installs firmware, and gathers the privacy and backup settings in one place. It is made by SatoshiLabs, the Prague company that shipped the first Trezor device in 2014, and it costs nothing to use.
For years, owners managed their coins through a page in the browser called Trezor Wallet. Trezor Suite replaced that arrangement with a standalone desktop program, a browser version for people who would rather not install anything, and a watch-only mobile companion. The security model stayed the same, but the interface stopped being a website you had to trust your browser with and became an application you can install, verify, and run offline against your own node if you want to.
It helps to be precise about what the software actually does. Coins are not stored in Trezor Suite, and no balance lives inside it. Everything Trezor Suite shows is derived from public keys that the connected device shares with it, and every outgoing payment must be confirmed on the device screen with physical button presses or taps. Strip the app away and the funds are still recoverable from the recovery backup. In that sense Trezor Suite is a viewer, a transaction builder, and a broadcaster rather than a wallet in the everyday sense of the word.
The audience splits into two groups that rarely want the same thing. One group buys a hardware wallet, moves coins onto it twice a year, and needs the process to be short and unambiguous. The other runs a full node, cares about which coins are spent in a transaction, and wants nothing leaking to a third-party server. Trezor Suite tries to serve both by keeping the default path simple and pushing the harder options into settings menus that stay out of the way until they are needed.
What follows is a working description of Trezor Suite: the pieces it is built from, the platforms it runs on, how to set a device up with it, what daily sending and receiving looks like, the privacy and security controls worth knowing, and the questions people ask most often. Where a feature depends on a specific device model or an external service, that is noted rather than glossed over.
How Trezor Suite is put together
Three pieces cooperate every time you open Trezor Suite: the hardware device, the application on your computer, and a blockchain backend that supplies transaction data. Understanding which piece does what removes most of the confusion people have about where their coins live and why certain steps cannot be skipped.
The device does the signing
When you send a payment, Trezor Suite gathers the inputs, calculates the fee, and produces an unsigned transaction. That transaction is handed to the hardware wallet over USB. The device parses it, prints the amount and destination address on its own screen, and waits for you to approve. Only then does it produce a signature, which Trezor Suite passes back to the network. The seed and the private keys derived from it never cross the cable.
This split is why the device screen matters more than the computer screen. Malware on a PC can rewrite what an application displays, but it cannot change what the hardware shows or forge an approval. The habit worth building is simple: read the address and amount on the device, not in Trezor Suite, and cancel if anything looks unfamiliar.
Blockchain backends
A hardware wallet cannot scan a blockchain on its own, and neither can Trezor Suite by default. The app queries indexing servers that watch the chains and answer questions like which outputs belong to a given public key. Out of the box those servers are operated by Trezor, which means the operator can see which addresses one anonymous client is interested in, though never the keys themselves.
You are not stuck with that arrangement. In the per-coin advanced settings, Trezor Suite lets you point an account at a backend you control, such as your own Bitcoin full node with the matching indexer, or an Electrum server on your local network. Traffic then goes to a machine you trust and the default servers see nothing at all.
The connection layer
The Trezor Suite desktop build communicates with the device directly, so plugging in a cable is normally all that is required. The browser build depends on the WebUSB support of the browser you happen to be using, which is why some browsers work immediately and others do not. Running Trezor Suite as a desktop application removes that variability, which is one reason it is the version most owners end up keeping.
Where Trezor Suite runs
The Trezor Suite desktop build covers Windows, macOS, and Linux, and it is the most complete version. Features that need a local process, such as routing traffic through Tor, exist here and nowhere else. Updates arrive through the application itself.
The browser version of Trezor Suite offers the same core wallet functions without an install, which suits a borrowed machine or a quick balance check. It inherits whatever restrictions the browser imposes, and it cannot provide the network-level privacy options of the desktop app.
Trezor Suite Lite is a separate mobile app for Android and iOS. It is watch-only: you add accounts by scanning a public key from the desktop app, then track balances and incoming payments from your phone. It cannot sign or send, which is exactly the point, since a phone is not where signing should happen.
A common setup is the desktop version of Trezor Suite on one trusted computer for anything that moves money, plus the mobile app for glancing at a portfolio without unpacking hardware.
Comparison
Trezor Suite desktop, web, and Lite compared
The three Trezor Suite builds share a design language and much of the same code, but they are not interchangeable. The table below sets out what each one can do, so you can pick the right tool rather than discovering a missing feature halfway through a transfer.
One rule applies across all of them: signing always happens on the hardware. No version of Trezor Suite can move funds by itself, and any screen that claims otherwise is not the real application.
| Capability | Trezor Suite desktop | Trezor Suite for browsers | Trezor Suite Lite |
|---|---|---|---|
| Platforms | Windows, macOS, Linux | Desktop browsers with USB access | Android, iOS |
| Install required | Yes, signed installer | No | Yes, from the app stores |
| Sign and send | Yes, with device confirmation | Yes, with device confirmation | No, watch-only |
| Device setup and firmware | Yes | Yes | No |
| Tor routing | Built in | Not available | Not available |
| Your own node as backend | Yes | Yes, per coin | No |
| Best suited to | Main wallet management | Occasional access, other machines | Checking balances on the move |
In practice the choice is less about features than about where you are sitting. Trezor Suite on your own machine is the version to reach for when you are setting a device up, restoring a backup, or moving a meaningful amount. The browser version of Trezor Suite is the fallback for a computer you do not control, and the mobile companion is for the times you only want to look.
How to get started with Trezor Suite
Initial setup with Trezor Suite is a genuine sequence: each step depends on the one before it, and skipping the backup step is the single most common way people lose access later. Set aside twenty quiet minutes, have pen and the supplied backup card ready, and do this somewhere no camera can see the screen.
Trezor Suite guides the whole process with on-screen prompts, and the device echoes every critical step on its own display so you can verify what the computer claims is happening.
One caution before you begin: only ever download and install Trezor Suite from the official source, and treat any page, email, or chat message asking for your recovery words as an attack, no matter how convincingly it imitates the app.
Read the FAQ-
Step 01 / Check the package
Inspect the tamper-evident packaging before anything else. A device that arrives already set up, or with a recovery phrase printed on a card inside, is not safe to use. Buy new and from a source you trust.
-
Step 02 / Install and connect
Install Trezor Suite for your operating system, or open the browser version, then connect the device with the supplied cable. Trezor Suite detects the model and tells you what it needs.
-
Step 03 / Install firmware
Devices ship without firmware. Trezor Suite downloads the current release and installs it while the device verifies the manufacturer signature itself, so a tampered image is rejected by the hardware rather than by the app.
-
Step 04 / Create the wallet and write the backup
Generate a new wallet and copy the recovery words shown on the device, in order, onto the paper card. Never photograph them and never type them into a computer. Trezor Suite then asks you to confirm the backup on the device.
-
Step 05 / Set a PIN and start using it
Choose a PIN, give the device a name, and let Trezor Suite discover your accounts. From here you can enable coins you plan to use, turn on privacy options, and send yourself a small test amount before moving anything significant.
Everyday use in Trezor Suite
Receiving
To receive funds you open an account, request a fresh address, and press the button that shows it on the device. Trezor Suite deliberately hides part of the address until you have confirmed it on the hardware, because address-swapping malware is one of the few attacks that works against an otherwise careful user. A new address is offered for each payment, which is a privacy measure rather than a technical necessity.
Sending and fees
The send form takes a destination, an amount in crypto or in your chosen fiat currency, and a fee level. For Bitcoin and similar chains, Trezor Suite presents preset fee tiers plus a custom option in satoshis per virtual byte, and it shows the resulting transaction size so the tradeoff is visible. Ethereum-style accounts get gas controls instead.
If a Bitcoin payment sits unconfirmed because fees rose, Trezor Suite can bump it using replace-by-fee rather than leaving you to wait. The same screen supports adding an OP_RETURN message on Bitcoin and sending the full balance minus fees, which is handy when emptying an account.
Accounts
One seed produces many accounts, and Trezor Suite handles them as separate entries in the sidebar. For Bitcoin it can create legacy, SegWit, and Taproot accounts, each with its own address format and fee characteristics. New accounts appear only after the previous one has been used, which keeps the list from filling with empty entries.
Separating funds by purpose, for example savings in one account and spending in another, costs nothing in Trezor Suite and makes bookkeeping easier. Every account is still derived from the same backup, so nothing extra needs to be written down.
Labels and history
Blockchains record numbers, not context. The labeling feature in Trezor Suite lets you name accounts, addresses, and individual transactions so a payment reads as rent rather than a string of characters. Those labels are encrypted with a key derived from your device and can optionally be synced through a cloud storage account, in which case the provider stores only ciphertext.
The history view groups transactions by date, shows confirmations, and exports to CSV or PDF for tax season. Combined with labels, it turns Trezor Suite into a usable record of what actually happened, which is more than most wallet software bothers to offer.
Privacy
Privacy controls
Hardware wallets protect keys well and privacy only if configured for it. Trezor Suite gathers the relevant switches in one settings area instead of scattering them, which makes it realistic to review them once and be done.
The Trezor Suite desktop build can route all of its traffic through the Tor network. With it enabled, the servers answering balance queries see a Tor exit rather than your home connection, which breaks the link between your IP address and your addresses.
Stronger still is running your own node and telling Trezor Suite to use it. Then no outside party learns which addresses you watch, because the machine doing the watching is yours. This is the configuration most privacy-minded Bitcoin users end up with.
Coin control in Trezor Suite gives you say over which unspent outputs fund a payment. Selecting them by hand prevents accidentally merging coins from unrelated sources into one transaction, which is how chain analysis links identities together.
Smaller touches help in ordinary situations: discreet mode blurs balances so you can open Trezor Suite in a cafe, and product analytics are optional and can be switched off entirely. Using the app never requires an email address or an account.
One historical note, since it still causes confusion. A CoinJoin feature was available in Trezor Suite for a period through an external coordinator service. That coordinator shut down in 2024 and the feature was retired with it, so CoinJoin is no longer part of the application.
The security model behind Trezor Suite
Security here is a division of labor. The hardware guards the secret and demands physical confirmation; the application handles everything that does not require the secret. Assume the computer running Trezor Suite is compromised and ask what an attacker could still do, and the design starts to make sense.
PIN, passphrase, and hidden wallets
A PIN protects a device that falls into someone else's hands, with escalating delays between wrong guesses. On top of that sits the optional passphrase, an extra word or sentence that is combined with the seed to derive a completely separate wallet. Enter a different passphrase and Trezor Suite opens a different set of accounts, each with its own balances and history.
This is powerful and unforgiving in equal measure. A passphrase is never stored anywhere, not on the device and not in Trezor Suite, so there is no recovery if you forget it or mistype a character. Anyone using the feature should treat the passphrase as a second backup that needs its own safe storage.
Backups
The recovery backup that Trezor Suite has you create during setup is the real wallet. Depending on the model you get a single list of words, or a multi-share backup that splits the secret into several shares of which a chosen number are needed to restore. Multi-share suits people who want to store parts in different locations without any single card being enough.
Trezor Suite includes a check that lets you verify your written backup against the device without exposing it to the computer, which is worth running once a year. If a device is lost, a replacement restored from the same backup, plus the same passphrase if you used one, reproduces every account exactly.
Firmware and device authenticity
Firmware updates are delivered through Trezor Suite, and the device checks the signature on any image before installing it. Updates are worth applying: they carry security fixes and support for new coins and features. Trezor Suite will tell you when one is pending rather than updating silently behind your back.
Models built around a secure element can additionally run an authenticity check, where the chip proves cryptographically to Trezor Suite that it is a genuine unit. It is a useful defense against counterfeits, though it does not replace buying from a trustworthy channel in the first place.
No legitimate part of the application ever asks for your recovery words. If a screen, a support agent, or a website requests them, the request itself is the attack.
The remaining risk is you. Phishing sites that clone the interface, fake support accounts, and counterfeit installers are the realistic threats against hardware wallet owners, not cryptographic breaks. Verify what the device displays, download Trezor Suite only from the official source, and the model holds.
Coins and tokens
Trezor Suite handles the major chains natively: Bitcoin and the Bitcoin-derived coins such as Litecoin, Bitcoin Cash, Dogecoin, and Dash, plus Ethereum with its ERC-20 tokens and compatible networks, and accounts for Cardano, Solana, and XRP among others.
Coins are enabled per network in settings, so the sidebar shows only what you actually hold. Token balances appear inside the relevant account rather than as separate entries, which keeps a busy Ethereum account readable in Trezor Suite.
Support in Trezor Suite is narrower than the full list of assets the hardware can sign for. Anything not covered there is typically reached through a third-party wallet that speaks to the device using the Trezor Connect integration library, so the keys stay protected even when a different interface is driving.
Before buying an asset specifically to hold on hardware, check the current supported list, and check whether it is supported in Trezor Suite or only through an external wallet. The two answers have different day-to-day consequences.
Buying, swapping, and staking
Alongside the wallet functions, Trezor Suite includes a trade section that connects to third-party providers. You can compare offers to buy crypto with a card or bank transfer, sell back to fiat, or swap one asset for another, with the purchased coins delivered straight to an address on your own device.
It is important to read this correctly: the providers are outside companies, not the wallet vendor. Trezor Suite aggregates their quotes and hands you off to them, and their identity checks, fees, spreads, and regional availability are theirs. The advantage over using an exchange separately is that the coins land in self-custody by default rather than sitting on someone else's books.
Staking is offered for a few networks, currently including Ethereum and Solana, again through external validator services surfaced inside the interface. Delegating from Trezor Suite keeps the keys on the device while the stake earns rewards, and Trezor Suite shows the position alongside the ordinary balance.
Treat these as conveniences with their own risks. Staked funds may face unbonding periods, validators can underperform, and rates change. None of that is a fault of Trezor Suite, but none of it is removed by using it either.
Open source and releases
The source code for Trezor Suite is public, as is the firmware that runs on the devices. Anyone can read how a transaction is constructed, how the backup flow works, or what data the application sends. For security software this openness is not a marketing point but a precondition for informed trust, and it lets independent researchers examine the code rather than take claims on faith.
Development of Trezor Suite happens in the open too. Issues, discussions, and pull requests are visible, so a reported bug can be followed from report to fix to release. Users who want to understand a change do not have to wait for a summary written for them.
Releases arrive regularly and the desktop application checks for updates itself. Installers are signed, and published checksums and signatures allow a careful user to verify a download before running it, which is the last defense against a tampered copy of Trezor Suite obtained from the wrong place.
There is no account system and no subscription. You do not register, you are not asked for identity documents to use the wallet, and Trezor Suite works the same whether you hold a token amount or a large balance. Costs sit in the hardware and in the fees charged by the external services you choose to use.
Common problems and how to approach them
Most Trezor Suite support questions come down to a handful of situations, and nearly all of them are recoverable. The one rule that matters while troubleshooting is that no fix ever requires typing your recovery words into a computer. If a proposed solution asks for them, stop.
Work through causes in order of likelihood: cable and port first, then software, then the device itself. A surprising share of cases labelled as broken hardware turn out to be a charge-only USB cable that carries no data.
If a problem persists after the basics, the desktop version of Trezor Suite can export a log file that describes what the application attempted, which gives support something concrete to read instead of a description from memory.
-
Device not detected
Try a different data cable and a port directly on the machine rather than through a hub. On Linux, the udev rules that grant USB access may need to be installed. In a browser, switch to the desktop version of Trezor Suite, which avoids browser permission quirks altogether.
-
Accounts look empty
Almost always a passphrase issue. A different passphrase, including a stray space or a capital letter, opens a different wallet with a balance of zero. Reconnect and enter the exact passphrase to see the expected accounts return in Trezor Suite.
-
Balances will not load
Check the connection indicator in Trezor Suite. If Tor or a custom backend is enabled, a slow circuit or an offline node will stall data while the device itself is fine. Disable the option temporarily to isolate the cause.
-
Firmware update interrupted
A device left in bootloader mode can usually be reconnected and the update retried from Trezor Suite. Because the backup, not the device, holds your funds, even a failed unit does not mean lost coins.
-
Transaction stuck unconfirmed
For Bitcoin, use the fee bump option in Trezor Suite to rebroadcast at a higher rate. Waiting also works when the mempool clears, but bumping puts the timing back under your control.
Questions
Frequently asked questions about Trezor Suite
Does Trezor Suite cost anything?
No. Trezor Suite is free and there is no subscription tier. You pay for the hardware device once, and separately for any fees charged by the third-party buy, sell, or swap providers if you choose to use them inside Trezor Suite.
Do I have to use Trezor Suite with my device?
Not for everyday use. Various third-party wallets can drive the hardware for signing, which is how many people interact with networks or applications Trezor Suite does not cover. Setup and firmware updates, however, are handled through Trezor Suite, so most owners keep it installed regardless.
Can Trezor Suite or its maker access my coins?
No. Private keys are generated on the device and never leave it, so Trezor Suite only ever sees public data and signatures the device chose to produce. Every outgoing transaction requires physical confirmation on the hardware, which no remote party can supply.
Does Trezor Suite work without an internet connection?
Partly. The app opens offline and the device still works, but fetching balances and broadcasting transactions need a network path to a blockchain backend. If that backend is your own node on a local network, Trezor Suite can operate without reaching the public internet at all.
What happens to my funds if Trezor Suite is discontinued?
Nothing. Your coins are controlled by the seed in your recovery backup, which follows published standards, so a compatible wallet from another vendor can restore the same accounts. Trezor Suite is an interface to those keys, not a dependency for them, and the source code would remain public in any case.
Is the browser version as safe as the desktop app?
The signing guarantees are identical, since the device confirms everything either way. The desktop build of Trezor Suite is preferred because it sidesteps browser extensions and lookalike websites, and it is the only version with Tor routing. Whichever you use, verify the address on the device screen.
Can I send crypto from my phone?
Not with the mobile companion. Trezor Suite Lite is watch-only by design: it tracks balances and incoming payments using public keys and cannot construct or sign a transaction. Sending requires the desktop or browser version of Trezor Suite with the device connected.
Is CoinJoin still available in Trezor Suite?
No. The feature relied on an external coordinator that shut down in 2024, and it was removed with it. The privacy tools that remain in Trezor Suite are Tor routing, custom backends, coin control, and careful address reuse avoidance.
Where Trezor Suite fits
Judged as wallet software, Trezor Suite is deliberately conservative. It does not chase every chain, it does not bury the confirmation step, and it keeps the operations that matter, backups, firmware, and privacy settings, in plain sight rather than behind a friendly abstraction. That restraint is what makes Trezor Suite usable for a first-time owner and still acceptable to someone running their own node.
If you own a compatible device, the reasonable approach is to install the desktop application, write the recovery backup on paper, verify a receive address on the device once so the habit sticks, and revisit the privacy settings when you have time. Everything else in Trezor Suite can be learned as the need arises, and none of it changes the fact that the backup in your drawer, not the software on your screen, is what actually holds the keys.