Wallet interface // hardware signing
Trezor Suite, the desktop and web app for Trezor hardware wallets
Trezor Suite is the official application that turns a Trezor hardware wallet into something you can actually use day to day. It runs as a downloadable desktop program on Windows, macOS and Linux, as a web app in a browser, and as a lighter mobile companion. Balances, accounts, sending, receiving, history, firmware updates, privacy switches and device checks all live in one place. The part that matters most is what Trezor Suite does not do: it never holds your private keys. It builds transactions, then hands them to the device for approval and signing.
This page explains how Trezor Suite is put together, what each screen is for, how the privacy and security controls behave, and where the app stops and third-party services begin. It is written for someone who has just unboxed a device as well as for someone who has used Trezor Suite for years and wants to understand the machinery underneath.
Trezor Suite comes from SatoshiLabs, the Prague company that shipped the first commercial Trezor hardware wallet in 2014. It replaced the older browser-based wallet interface and became the default way to manage a device. The code is published openly, so the app can be read, built and audited by anyone, and Trezor Suite is free to download and use with no account or registration.
- Editions
- Desktop / Web / Mobile
- Price
- Free
- Source code
- Public / auditable
- Key custody
- On device only
What the app is
A hardware wallet on its own shows very little. It has a small screen, a couple of buttons or a touch panel, and no idea what the current state of any blockchain is. Trezor Suite fills that gap. It watches the networks, works out what your accounts contain, drafts transactions when you ask for them, and shows the results in a readable interface. The device supplies the one thing software cannot be trusted with: the private keys and the physical confirmation step.
Because of that split, Trezor Suite is best understood as a client rather than a wallet in the custodial sense. There is no login, no password reset, no support desk that can move funds. If you delete Trezor Suite and reinstall it, nothing is lost; the app rebuilds its view of your accounts from the blockchain and from the public keys the device provides. Your recovery backup, not the software, is the thing that must survive.
Trezor Suite also absorbs jobs that used to be scattered across separate tools. Firmware installation, device authenticity checks, PIN and passphrase settings, backup verification, coin control for Bitcoin, Tor routing, portfolio charts and CSV exports all sit in the same window. That consolidation is deliberate, since every extra tool in the chain is another place where an address could be swapped or a download tampered with.
Development happens in public. Release notes, issue trackers and source code are open, and the app ships translations for many languages. Anyone worried about what Trezor Suite sends over the network can read the relevant code or simply watch the traffic, which is a meaningfully different position from auditing a closed exchange app.
Download check. Fake wallet software is one of the most common ways people lose coins. Only install Trezor Suite from the official vendor download page, and where signed checksums are published, verify them before running the installer. Trezor Suite will never ask you to type your recovery seed into a computer, and neither will any legitimate support channel.
Desktop, web and mobile
The desktop edition is the recommended one. It is a signed application you install on Windows, macOS or Linux, it bundles the communication layer that talks to the device over USB, and it includes the extras that a browser cannot offer, such as built-in Tor routing and the ability to point the app at your own blockchain backend. Because the code sits on your disk rather than being fetched on every visit, the desktop build of Trezor Suite is also harder to attack through a hijacked domain or a poisoned CDN.
The web edition covers the case where installing software is not an option, for example on a locked-down work machine or a borrowed computer. It offers the same core wallet functions in a modern browser that supports direct USB access to the device. The trade-off is that you are trusting the page you loaded, so the web version of Trezor Suite deserves a careful look at the address bar every single time.
On phones, the companion app leans towards watching rather than spending. It is designed to track balances and portfolio value from public account data, so you can check holdings without carrying the device. Support for connecting hardware directly to a phone depends on the model, the operating system and the cable, and mobile capabilities have been expanding over time; treat the phone app as a viewer first and check current device compatibility before relying on it for signing.
All editions read the same blockchains and derive the same addresses, because the derivation happens on the device. You can start an account on desktop, look at it on your phone, and later open the same wallet in a browser without any migration step. Nothing is stored in a Trezor Suite cloud, so the only state that moves between editions is what the blockchain already knows plus any labels you choose to sync.
Most people settle on a pattern quickly: desktop for anything involving spending, mobile for glancing at balances, web only as a fallback. Trezor Suite is deliberately consistent across the three, so switching costs almost nothing once you know where the settings live.
Edition comparison
| Capability | Desktop | Web | Mobile |
|---|---|---|---|
| Install required | Yes | No | Yes |
| Send and sign | Full | Full | Model dependent |
| Built-in Tor | Yes | No | No |
| Custom backend | Yes | Limited | No |
| Firmware updates | Yes | Yes | No |
| Portfolio tracking | Yes | Yes | Yes |
| Best for | Daily use | Fallback | Checking |
Exact mobile behaviour depends on your device model and phone. Confirm current support in the app before planning around it.
How it works under the hood
Three parts do the work. The hardware wallet stores the seed and signs. Trezor Suite runs on your computer and handles the interface, transaction construction and coin logic. A blockchain indexer sits between the app and the networks, answering questions like which outputs belong to this public key and what the recent history looks like. Asking a full node those questions directly would be slow, so an indexing layer does the heavy lifting.
When you connect the device, Trezor Suite requests extended public keys for each account it wants to display. From an extended public key the app can generate every receiving and change address in that account without ever touching a private key. It then asks the indexer for the balances and transactions of those addresses and assembles the account view you see. This is why Trezor Suite can show you a full history in seconds while the device itself remains a sealed signer.
Signing runs in the other direction. You fill in a recipient and amount, Trezor Suite selects inputs, calculates the fee and change, then sends the unsigned transaction to the device. The device parses it and displays the destination and amount on its own screen. If the malware-infected computer had rewritten the address, the screen would show the wrong one, which is the whole point of confirming on hardware. Once you approve, the signed transaction goes back to Trezor Suite, which broadcasts it.
By default the indexer is operated by the vendor, and that has a privacy consequence worth understanding: whoever runs it learns which addresses were queried together and from which network connection. Trezor Suite offers two answers. Route traffic through Tor so the requests are not tied to your IP address, or configure your own node and indexer so the queries never leave your infrastructure at all. The second option takes some work but removes the third party completely.
Device communication is another layer people ask about. Older browser setups needed a separate bridge process installed on the system; the desktop build of Trezor Suite includes what it needs, and browsers now use direct USB permissions. Practically, this means the desktop app works right after install, while the web app asks your browser for permission to access the connected device.
Layer 01
Hardware wallet
Holds the seed. Derives keys. Displays and confirms. Signs.
Layer 02
Trezor Suite
Interface, account discovery, fee and input selection, broadcast, labels, settings.
Layer 03
Indexer and node
Answers balance and history queries. Vendor-hosted by default, self-hostable by choice.
Layer 04
Public networks
Where signed transactions end up and where the truth lives.
First run and device setup
A new device arrives without firmware or with a minimal loader, so the first thing Trezor Suite does is offer to install the official firmware and verify what it is talking to. On models with a secure element, the app also performs an authenticity check that asks the chip to prove it is genuine. If that check fails or the packaging looks tampered with, stop and contact the vendor rather than continuing.
Next comes the backup, and this is the single most consequential step in the whole process. The device generates a recovery seed and shows the words on its own screen, never on the computer. Trezor Suite guides the pacing and then offers a verification step, but the words themselves are a hardware matter by design. Write them on the supplied cards, store them offline, and never photograph them or type them into any app, including Trezor Suite.
Some models support a multi-share backup instead of a single word list, splitting the secret into several shares where a defined threshold is needed to restore. Trezor Suite walks through the share creation and explains the threshold you have chosen. It suits people who want geographic separation without a single fatal point of loss, at the cost of a more complicated inventory to manage.
Then you set a PIN. The PIN protects against someone who physically holds the device, and the entry method depends on the model: a touchscreen keypad on touch devices, or a scrambled grid shown in Trezor Suite where the number positions are only visible on the device screen. Wrong guesses trigger increasing delays, so brute force is impractical rather than merely slow.
Finally, Trezor Suite asks which coins you plan to use and gives the device a name so multiple wallets are easy to tell apart. It then runs account discovery, scanning standard derivation paths for existing history. On a brand new wallet there is nothing to find; on a restored one, this is the step that makes your old accounts reappear. When discovery finishes, Trezor Suite drops you on the dashboard.
Setup checklist
- Installer downloaded from the official page
- Firmware installed through Trezor Suite
- Device authenticity check passed
- Seed written on paper, stored offline
- PIN set and memorised
- Small test transaction completed
Seed rule. Any screen, message or person asking you to enter your recovery words into software is an attack. Trezor Suite only ever needs them during an on-device recovery, where the words are handled by the hardware.
Dashboard and accounts
The dashboard is the summary view: total value in your chosen fiat currency, a chart of how that value moved, a breakdown by asset, and the most recent transactions across every account. Trezor Suite pulls exchange rates to render fiat figures, which is worth knowing if you are trying to keep network requests to a minimum.
Below the summary sits the account list, grouped by coin. An account in Trezor Suite is not an address but a branch of the key tree with its own history and its own stream of fresh addresses. You can hold several accounts per coin and use them as separate books, for instance one for savings and one for spending, without any relationship between them being obvious on chain.
For Bitcoin, Trezor Suite exposes multiple account types matching the common address standards, from legacy through nested and native segwit to taproot. Newer types generally mean lower fees; older ones mean broader compatibility with services that have not updated. If a restored wallet appears empty, the usual cause is that the coins live under an account type Trezor Suite has not added yet, and adding it brings them back into view.
Each account page carries tabs for its transaction history, receive addresses, sending, and details such as the extended public key and the account's derivation path. History entries can be searched and filtered, and Trezor Suite can export them to CSV or PDF, which is what most people reach for at tax time.
Discreet mode is the small feature people end up using constantly. One toggle blurs every balance and amount in Trezor Suite until you hover over it, so opening the app in a cafe or on a shared screen does not broadcast your net worth. Numbers stay blurred across the dashboard and all account views.
Bitcoin account types
| Type | Address starts | Notes |
|---|---|---|
| Taproot | bc1p | Newest, efficient, less widely accepted |
| Native segwit | bc1q | Default in Trezor Suite, low fees |
| Nested segwit | 3 | Compatibility with older services |
| Legacy | 1 | Oldest, highest fees |
Coins are tied to the account type that received them. Moving between types is an ordinary on-chain transaction, not a setting.
Sending and receiving
Receiving starts with a fresh address. Trezor Suite generates the next unused one and, crucially, asks you to compare it against the device screen before you use it. That comparison is not a formality. Address-swapping malware is a real and long-running category of attack, and confirming on hardware is what defeats it. Trezor Suite deliberately makes the address awkward to copy until you have looked.
The app also keeps handing you new addresses rather than reusing old ones. Previously used addresses stay listed and functional, but Trezor Suite nudges you towards fresh ones because address reuse makes chain analysis trivially easy. For account-based chains like Ethereum, the model is different and a single address is normal.
Sending is a short form: recipient, amount, fee. Trezor Suite offers preset fee tiers derived from current network conditions plus a custom option in satoshis per virtual byte for Bitcoin or gas settings for Ethereum. It shows the estimated total before anything is signed, and you can enter amounts in fiat and let the app convert. Bitcoin sends can include several outputs in one transaction, which is cheaper than sending them separately.
Coin control is where Trezor Suite gets genuinely powerful for Bitcoin users. Open it and you see every unspent output in the account, with the option to choose exactly which ones fund a payment. That lets you keep coins from different sources apart, avoid merging outputs that would link identities, and control the size of the change you create. It is optional, and most people ignore it until they have a reason to care.
If a Bitcoin transaction sits unconfirmed because the fee was too low, Trezor Suite can bump it using replace-by-fee, or in some cases replace it with one that returns the funds to you. Both are ordinary replacement transactions and both need a fresh confirmation on the device. Ethereum transactions can similarly be resubmitted with a higher fee.
Beyond payments, Trezor Suite can sign and verify plain text messages with an account key, which is how you prove control of an address to a service without moving funds. Every one of these actions follows the same rhythm: the app prepares, the device displays, you approve, the app broadcasts.
Verify
Compare receive addresses on the device screen, not in the browser window.
Choose
Use coin control when the origin of specific outputs matters to you.
Adjust
Bump a stuck fee from the history view rather than sending twice.
Privacy controls
Self-custody stops your funds from being someone else's liability, but it does not automatically make your activity private. Public blockchains are permanent ledgers, and the software you use to read them sees what you are asking about. Trezor Suite treats this as a first-class concern instead of an afterthought.
The Tor switch in the desktop app routes network traffic through the Tor network so the indexer sees a relay rather than your home connection. Turning it on in Trezor Suite is a single toggle and syncing will feel slower, which is the honest cost of that separation. It matters most on networks you do not control, or where you would rather not create a record linking your address book to your ISP.
The stronger option is running your own infrastructure. Trezor Suite lets you enter a custom backend for supported coins, so account queries go to a node and indexer you operate. Nobody outside your network learns which extended public keys you asked about. It requires maintaining that stack, but for people who take privacy seriously this is the setting that actually closes the gap.
On-chain hygiene is supported too. Fresh addresses by default, coin control for keeping unrelated funds unmerged, and multiple accounts to separate purposes all help. Trezor Suite cannot undo linkage you created in the past, but it gives you the tools to stop adding to it.
Anonymous usage analytics are optional and can be switched off in settings. Fiat rate lookups and any third-party trading widgets also generate requests, so a privacy-conscious setup usually means Tor or a custom backend on, analytics off, and the exchange features left alone. Trezor Suite lists these switches in one place rather than burying them.
Who sees what
| Setup | Third party learns |
|---|---|
| Default | Your addresses and your IP |
| Tor on | Your addresses, not your IP |
| Own backend | Nothing |
In every configuration, private keys stay on the hardware. These rows are about metadata only.
metadata matters
Security model
The design assumption behind Trezor Suite is that your computer might already be compromised. Everything follows from that. Keys are generated and kept on the device, transactions are displayed on hardware you trust more than the screen in front of you, and no operation that moves value happens without a button press or a touch on the device itself.
The PIN guards physical access. Repeated wrong entries make each attempt slower, so a stolen device is not a quick prize. It does not protect the seed if the seed itself is exposed, which is why backup storage and PIN choice are separate problems that both need solving.
The passphrase feature is the most powerful and the most easily misused. A passphrase entered on top of your seed produces a completely different wallet, with its own accounts and its own balance. Trezor Suite calls these hidden wallets, and there is no list of them anywhere: type a different passphrase and you land in a different wallet, including ones you created by typo. Nothing recovers a forgotten passphrase, so it must be backed up with the same care as the seed.
Used well, this gives you plausible deniability under coercion, because the wallet reachable with the PIN alone can hold a modest amount while the real balance sits behind a passphrase. Trezor Suite treats each passphrase as a separate wallet in the interface, with its own labels and its own account set.
Firmware integrity is checked by the device, and the device's own authenticity is checked by the app on models that support it. Trezor Suite will warn you loudly about unofficial firmware or a failed authenticity response. Update prompts appear in the app, and each install requires physical confirmation, so nothing can be flashed silently while you are away from the desk.
Finally, Trezor Suite includes a way to verify your backup without exposing it: a dry-run recovery where you enter your words on the device and the firmware confirms whether they match the seed already installed, without ever revealing the seed. Running that check once, shortly after setup, is the cheapest insurance available, since discovering a bad backup years later during a real recovery is the scenario nobody wants.
Threat model in one sentence. Trezor Suite assumes the host is hostile, so trust only what appears on the device display; if the app and the device disagree about an address or an amount, the device is right and you should cancel.
Coins and tokens
Trezor Suite supports the major networks natively, including Bitcoin and the main Bitcoin forks, Ethereum with its ERC-20 tokens, and a number of other established chains, plus their test networks for anyone who wants to rehearse. Support is added and adjusted over time, so the built-in coin list in the app is the authoritative answer for today.
Coins you do not use can be switched off in settings, which shortens account discovery and keeps the dashboard readable. Tokens with no meaningful balance can be hidden as well. This is housekeeping rather than security, but it makes a long-lived wallet in Trezor Suite far easier to read.
For chains outside the built-in list, the device can still be used through compatible third-party wallets that support hardware signing. In that arrangement, the other application handles the interface and the network while your keys stay on the hardware. You lose the verification and privacy features that Trezor Suite provides, and you inherit whatever the third-party app does, so it is worth knowing which one you are trusting.
There is also a Bitcoin-only firmware option for people who want a smaller attack surface. Installing it removes support for other coins entirely, and Trezor Suite adapts to show only Bitcoin. It is a reasonable choice for a long-term store where nothing else will ever be held.
Where assets are managed
| Asset class | Handled by |
|---|---|
| Bitcoin and forks | Trezor Suite, natively |
| Ethereum and ERC-20 | Trezor Suite, natively |
| Other supported chains | See coin list in the app |
| Unsupported chains | Third-party wallet, device signs |
| NFTs and dapps | External interface, device signs |
Signing always happens on the hardware, whichever interface asks for it.
Buy, sell, swap and stake
Trezor Suite includes a trading section that compares offers from external providers for buying, selling and exchanging crypto. The value is that a purchase can land directly on an address held by your own device instead of sitting on an exchange account, which removes a step where a lot of coins have historically been lost.
These are third-party services, not Trezor Suite functions. Each provider sets its own rates, fees, limits, supported countries and payment methods, and most will run identity verification because they are regulated financial businesses. Read the offer before accepting it, and understand that any complaint about a trade belongs to the provider that executed it.
Staking is available for some networks through integrated partners, letting you delegate holdings while the keys remain on your device. Rewards, lock-up behaviour and unbonding periods depend entirely on the network and the provider. Trezor Suite shows the position and the current state, but the economics and the risks are the network's, not the app's.
If you would rather not touch any of it, you do not have to. Everything in this section is optional, and a Trezor Suite installation used purely for holding and self-custodied transfers never needs to contact a trading provider at all. Privacy-focused users often leave the whole section untouched for exactly that reason.
Labels and record keeping
Raw transaction history is unreadable after a few months. Trezor Suite therefore lets you attach your own names to accounts, addresses and individual transactions, so a payment reads as rent or a client invoice rather than a string of characters. For anyone doing bookkeeping later, this is the difference between an hour and an afternoon.
Labels are sensitive data, since they describe who you pay and why. Trezor Suite encrypts them with a key derived from your device, and optional syncing through a personal cloud drive stores only that encrypted blob. The provider hosting the file cannot read it, and the labels stay tied to the wallet, including per-passphrase wallets, which each keep their own set.
For records that need to leave the app, Trezor Suite exports account history to CSV or PDF with dates, amounts, addresses and fiat values at the time. That covers most accounting and tax reporting workflows without giving a third-party tool access to your accounts.
A wallet you cannot read is a wallet you cannot audit. Labels in Trezor Suite are encrypted precisely because they are the most descriptive data in the whole app.
Compared to other ways of using the device
A Trezor device works with plenty of software besides its own app, so the honest comparison is not about who holds the keys, since the hardware always does. It is about which interface you are trusting, what it can see, and which safety features it gives you. Trezor Suite is the first-party option, built alongside the firmware and shipped with the verification and privacy tools described above.
Third-party wallets earn their place when you need a chain or a feature Trezor Suite does not cover, such as interacting with a smart contract application. A sensible arrangement for many people is Trezor Suite as the home base for holdings and transfers, with a browser wallet used narrowly for the specific thing it exists to do.
| Criterion | Trezor Suite | Third-party wallet with device | Custodial exchange app |
|---|---|---|---|
| Key custody | You, on device | You, on device | The company |
| Firmware management | Built in | Not usually | Not applicable |
| Tor routing | Built in on desktop | Varies | No |
| Own node support | Yes | Varies | No |
| Coin control | Yes, for Bitcoin | Varies | No |
| Smart contract apps | Not the focus | Common strength | No |
| Account required | No | Usually no | Yes |
Updates and firmware maintenance
Two things get updated: the app and the device. Trezor Suite on desktop notifies you when a new version is available, while the web edition is simply always current. Firmware updates are offered inside the app and are worth reading about before installing, since release notes explain what changed and whether the update matters for the coins you hold.
Before any firmware update, make sure your recovery backup is present and correct. Updates are not supposed to erase anything, but a wallet whose backup is unverified should not be gambled on. Trezor Suite reminds you of this, and it is one reminder worth taking literally.
Device management lives in the app as well. Trezor Suite can hold several devices and several passphrase wallets, letting you name them, switch between them and eject one so its data stops appearing. Wiping a device is also done here, which is the step before selling or repurposing hardware; with a verified backup in hand, a wiped device is recoverable, and without one it is not.
Older Trezor Suite versions keep working for a while, but running current software is the sensible default. Fixes to fee estimation, coin support and interface bugs all arrive through updates, and the app and firmware are developed to work together.
Troubleshooting the common cases
A device that is not detected is almost always a cable, a port or a permission problem. Try a different data-capable cable, connect directly rather than through a hub, and close any other wallet software that might be holding the connection. On Linux, device access rules may need installing before Trezor Suite can see the hardware. In the browser, check that you granted the USB permission prompt.
Balances that look wrong usually are not. On a restored wallet, the missing coins are typically in an account type that has not been added yet, so add the other Bitcoin account types in Trezor Suite and look again. If an entire wallet appears empty after a restore, the likely cause is a passphrase: the same seed with a different passphrase is a different wallet, and a single typo produces an empty one.
Slow or failed syncing points at the network layer. Tor makes syncing slower by nature, a custom backend may be behind or offline, and restrictive corporate networks sometimes block the connections Trezor Suite needs. Switching Tor off temporarily is a fast way to tell whether the problem is routing or something else.
A transaction stuck in the mempool is a fee problem, not a bug, and Trezor Suite has the fix built in: bump the fee from the history entry. Ethereum transfers that fail for insufficient gas need the fee raised and resubmitted. If something looks genuinely inconsistent, closing Trezor Suite and reopening it forces a fresh sync, and nothing about your funds depends on the app's local cache.
Symptom and first check
| Symptom | First check |
|---|---|
| Device not found | Cable, direct port, other apps closed |
| Wallet looks empty | Passphrase entry |
| Some coins missing | Add other account types |
| Sync stalls | Tor off, backend reachable |
| Transaction pending | Bump the fee |
| Update warning | Backup verified before flashing |
How to get started
The order below matters, because each step assumes the previous one is done. Set aside half an hour for a clean start, somewhere private, with a pen and the recovery cards from the box in front of you.
-
Step 01
Install the app
Get Trezor Suite for your operating system from the official download page, verify the signature or checksum if one is published, then install and launch it before plugging anything in.
-
Step 02
Connect and set up
Connect the device and follow the guided setup in Trezor Suite: install firmware, let the authenticity check run, create the wallet, write down the recovery words shown on the device, and set a PIN.
-
Step 03
Test with a small amount
Generate a receive address in Trezor Suite, confirm it on the device screen, send a small amount, and watch it confirm. Then send a little back out so you have practised both directions.
-
Step 04
Verify and tune
Run the dry-run backup check, then set your preferences in Trezor Suite: fiat currency, Tor or a custom backend, analytics off if you prefer, unused coins hidden, and labels for the accounts you will actually use.
Everyday habits that keep it safe
Confirm on the device, every time. It takes a few seconds to compare an address on the hardware screen with what Trezor Suite displays, and it is the one habit that neutralises the most common class of attack against self-custody.
Keep the backup offline and the passphrase separate. Paper or metal, stored where fire and flooding are not the same event, with no photographs and no cloud copies. If you use a passphrase, record it somewhere independent of the seed, because Trezor Suite cannot help you reconstruct either one.
Be skeptical of anything urgent. Fake support accounts, fake update prompts and fake wallet downloads all rely on hurry. Real updates appear inside Trezor Suite itself, and no legitimate message will ever ask for your recovery words, your PIN or your passphrase.
Practise the recovery before you need it. Do a dry-run check in Trezor Suite, know where your shares or cards live, and make sure whoever needs to find them in an emergency can. Self-custody works when the plan survives contact with real life, not just when the software is configured correctly.
Frequently asked questions
Does Trezor Suite cost anything?
No. Trezor Suite is free to download and use. You pay for the hardware device, and third-party trading or staking providers charge their own fees if you choose to use them.
Can I use it without a hardware wallet?
Not for managing coins. Trezor Suite is built around a connected device that holds the keys and signs, so a device is required for accounts, sending and receiving.
What happens if my computer is stolen?
Your coins are unaffected. Trezor Suite stores no keys, so a thief with the computer gets an app that cannot move anything without the device and its PIN. Reinstall elsewhere, connect the device, and your accounts reappear.
Do I have to use the vendor's servers?
No. Trezor Suite lets you route traffic over Tor or point supported coins at your own node and indexer, so account queries never reach a third party.
Why is my restored wallet empty?
Usually a passphrase. Each passphrase produces a distinct wallet from the same seed, so one wrong character opens a different, empty one. Also try adding the other Bitcoin account types in Trezor Suite before assuming something is lost.
Can two people share one wallet?
Only in the sense that whoever holds the device and knows the PIN can spend. Trezor Suite has no user accounts or roles, so shared use means shared physical control of the hardware.
Is the mobile app enough on its own?
Treat it as a viewer. The mobile side of Trezor Suite is aimed at checking balances and portfolio value, while setup, firmware and most signing belong on the desktop app.
Can I hold coins it does not list?
Sometimes, through a compatible third-party wallet that supports hardware signing. The keys stay on the device, but you give up the verification and privacy features that Trezor Suite provides.
Glossary
These terms appear throughout Trezor Suite and across this page. Knowing them makes the app's settings screens far less intimidating.
| Term | Meaning |
|---|---|
| Recovery seed | The word list that represents your keys. The only true backup of a wallet. |
| Passphrase | An extra secret that turns one seed into many separate wallets. Not recoverable if forgotten. |
| Extended public key | Lets an app derive all addresses in an account without any spending power. |
| Account discovery | The scan Trezor Suite runs to find accounts with existing history after a restore. |
| UTXO | An unspent Bitcoin output. Coin control is the practice of choosing which ones to spend. |
| Replace-by-fee | Replacing an unconfirmed Bitcoin transaction with a higher-fee version to speed it up. |
| Indexer | The service that answers balance and history queries for the app. Self-hostable. |
| Discreet mode | A Trezor Suite toggle that blurs all amounts on screen. |