Hardware Wallet vs Exchange: Keys, Backups, Custody

A hardware wallet is a dedicated device that generates and stores the private keys controlling your crypto and signs transactions inside the device, so the key material never has to appear on your internet-connected computer or phone. It does not hold coins the way a USB stick holds files: balances are entries on a blockchain, and the device holds the cryptographic authority to move them. That distinction drives every practical decision below, including the one most readers arrive with — hardware wallet versus leaving assets on an exchange — where the real trade is between platform-assisted account recovery and sole control of keys with no reset path.

Quick answer

• Keys, not coins: the device stores private keys and produces signatures; the asset record lives on-chain, so a broken device is not a lost balance if the backup is intact.
• Two dimensions, not one: custodial versus self-custody describes who controls keys; hot versus cold describes whether signing keys ever touch an online device. A self-custody phone wallet is self-custody but not cold.
• Recovery is the real difference: Coinbase's own guidance says it can help you recover a lost password for a Coinbase-hosted wallet, but cannot help recover lost keys or seed phrases for a self-custody Coinbase Wallet.
• Backup format is model- and date-specific: Trezor documents 12- or 24-word BIP39 backups and a 20-word SLIP39 standard, and states that backups created before June 2024 on Model T or early Safe 3 cannot be upgraded to Multi-share.
• A genuine device does not make transactions safe: if you approve a malicious transfer or contract approval on the device screen, the signature is valid and the transfer is final.

How a hardware wallet works, and what the connected app actually does

Three things are separate in a hardware wallet setup, and mixing them up causes most of the confusion.

The blockchain holds the record of which addresses control which assets. The device holds the secret keys for those addresses and can produce a digital signature proving control. The companion app on your computer or phone — Trezor Suite, Ledger Live, a browser wallet, an exchange withdrawal form on the other end — reads the chain, shows balances, builds the unsigned transaction and broadcasts the signed result. The app is a convenience layer over public data plus an assembly line for transaction drafts. It never needs your key.

That is why verifying details on the device screen matters. The app proposes; the device's own display and buttons are the only part of the chain that malware on your laptop cannot repaint. If a compromised machine swaps the destination address after you paste it, the app may show what you expect while the device shows the attacker's address. Reading the recipient and amount on the device before confirming is the check that the architecture exists to enable.

A concrete scenario. Starting setup: a Trezor Safe device initialised after June 2024 with a 20-word single-share backup written on paper, Trezor Suite installed on a laptop, and 0.4 BTC received to an address derived from that device. Supported action: you send 0.1 BTC to an exchange deposit address. Suite builds the transaction and fee, the device displays the output address and amount, you confirm on the device, and the signature is generated inside it; the key never leaves. Outcome: the network records a transfer from your addresses, your remaining balance sits at roughly 0.3 BTC less the mining fee, and the laptop never saw the private key. Remaining limitation: nothing in that flow checks whether the deposit address was the right one. If you confirmed an address supplied by a phishing site, the device signed exactly what you approved, and there is no reversal, chargeback or support queue. Approval, not key theft, is the failure mode that survives a hardware wallet.

Custodial versus self-custody, hot versus cold: two questions, four combinations

Coinbase's education pages define hot wallets as software-based and typically connected to the internet, generating and storing keys online, and cold wallets as hardware-based and offline, held for longer-term storage. Custody is a different axis: Coinbase describes the wallet that comes with a Coinbase account as custodial, and Coinbase Wallet as a self-custody product where you control the keys. Ledger Academy goes further in its own framing, arguing a true cold wallet also never interacts with smart contracts — that is a vendor definition of the category, not an industry-wide standard, and it is worth reading as such.

The row that trips people up is the second one. Moving from an exchange to a self-custody mobile wallet changes who holds the keys. It does not put the keys offline.

Hardware wallet versus exchange: the six differences that decide it

This matrix is assembled from provider documentation rather than from any testing on our part. Exchange behaviour is scoped to Coinbase's published guidance; device behaviour is scoped to Trezor's documentation.

Neither column is safe in general. An exchange concentrates counterparty and policy risk and gives you a reset button; a hardware wallet removes the counterparty and removes the reset button. If a large share of your balance is stablecoins, note that neither choice touches issuer, reserve or redemption risk — that sits with the token, and our stablecoin risks guide covers it separately.

Backups and passphrases: three different losses with three different outcomes

Backup formats are product-specific, so treat the following as Trezor's documented behaviour rather than a universal rule. Trezor's backups page states that depending on the model, the backup contains 12, 20 or 24 words, and that the company uses the BIP39 and SLIP39 standards. It lists 12-word BIP39 as the default for Model T and for Safe 3 devices set up before June 2024, and 24-word BIP39 as the default for Model One; the 20-word format is the newer SLIP39 single-share standard introduced with the Safe 5 line. Trezor says BIP39 backups are widely supported by other wallets, and describes both BIP39 and SLIP39 as open standards — but compatibility should be confirmed against the specific wallet and the specific format you hold, because support for 12- and 24-word BIP39 phrases is far more common than support for SLIP39 shares.

Trezor also documents an upgrade boundary: backups created before June 2024 on Model T or an early Safe 3 use a format that cannot be converted to Multi-share, and switching would require creating a new wallet and moving funds. To identify a newer 20-word single-share backup, its guidance is to check words three and four of the physical card — both reading ACADEMIC indicates the newer format. Multi-share splits the backup into shares with a threshold; in Trezor's own example, a finder of one share cannot access the wallet because at least three are required.

A backup alone therefore does not restore every arrangement. Trezor's Suite documentation is explicit that the wallet backup recovers the standard wallet and that adding a passphrase opens a separate passphrase wallet; it advises checking the standard wallet's backup before adding a passphrase on top, and using Suite's check-wallet-backup simulated recovery to confirm you can reproduce access. Other self-custody products use different mechanisms — Coinbase's self-custody wallet centres on a recovery phrase, and some smart-contract wallet designs use passkeys rather than a word list — so do not assume one product's recovery steps transfer to another.

Mistakes that cost people money even with a genuine device

• Typing the backup into software. Trezor's guidance is to never enter your wallet backup anywhere unless prompted by the Trezor device itself, and states the company will never ask for it, including in support conversations. Any site, chat or app offering to "validate" or "restore" a phrase is the attack.
• Keeping a digital copy. Trezor explicitly advises against screenshots, photographs, email and cloud storage of the backup.
• Setting a passphrase you have not tested. An untested passphrase is a single typo away from an empty wallet you cannot distinguish from a wrong entry.
• Approving without reading the device screen. The device's display is the only trustworthy surface; skipping it discards most of the protection you paid for.
• Assuming asset and network support. A device that supports a coin does not necessarily support every chain, token standard or staking action for it, and sending to the wrong network can be unrecoverable.

Checklist before you buy, and the first thing to do after

1. Supported assets and networks. Check the manufacturer's current support list for every asset you actually hold, including the specific network variant, and for the app you intend to use with the device.
2. Recovery compatibility. Decide the backup format before setup, and confirm which other wallets can restore it. If you want the option of restoring without that brand's hardware, a widely supported BIP39 phrase behaves differently from SLIP39 shares.
3. Purchase source. Buy from the manufacturer or an authorised reseller and run the device's own authenticity and firmware checks during setup. A device that arrives pre-initialised with a printed "backup" is a scam, not a shortcut.
4. Accessibility and household reality. Small screens, button confirmations and PIN entry are part of daily use. Whoever may need to reach these funds after you should be able to operate the process you chose, including any passphrase.
5. Total cost. Count the device, shipping and any duties, durable backup storage, a second device or spare backup location if you want redundancy, and the on-chain fees to move funds into the new addresses. Prices change, so take current figures from the vendor's store page on the day you buy.

Your first step after setup is not funding the wallet. It is running the device's backup verification — on Trezor, the check-wallet-backup simulated recovery in Suite settings — and then sending a small test amount and moving it back out, so you have proven both the backup and the signing flow before any meaningful balance depends on them.