Connecting Trezor links the hardware wallet to Trezor Suite, MetaMask, or WalletConnect so transactions can be signed without exposing private keys to internet-connected software.
Two distinct paths exist: first-time device initialization (firmware install → seed backup → PIN setup), and third-party pairing for DeFi access. Total initialization time is roughly 15 minutes.
| Connection Path | Use Case | Tool Required | iOS Support |
|---|---|---|---|
| First-time setup | Initialize new cold wallet | Trezor Suite desktop or Android | Safe 7 (BT) only |
| MetaMask pairing | EVM DeFi, custom networks | MetaMask browser extension | No |
| WalletConnect | Direct dApp authentication | Trezor Suite (built-in) | Safe 7 (BT) only |
| Electrum / Exodus / Rabby | Bitcoin advanced, multi-chain | Third-party app | Limited |
Trezor requires firmware installation during first setup to prevent supply-chain tampering — the device ships as a blank signer with no pre-loaded software. Every transaction is approved by physical button confirmation on the device — MetaMask, WalletConnect, and any third-party app can initiate but never authorize a transaction on their own.
Browser CompatibilityWebUSB handles browser-based device communication in most Chromium browsers. Safari does not support WebUSB, limiting web-app connections on macOS to Firefox or Chrome.
| Model | Price | Connection | iOS Full Access | Backup Standard |
|---|---|---|---|---|
| Safe 3 | ~$79 | USB-C | View-only | SLIP-39 (12-word default) |
| Safe 5 | ~$129 | USB-C | View-only | SLIP-39 (20-word Shamir) |
| Safe 7 | ~$169+ | USB-C + Bluetooth | Full (Bluetooth) | SLIP-39 Shamir |
| Model One | ~$49–69 | Micro-USB | View-only | BIP-39 (24-word only) |
Model One lacks an EAL6+ certified Secure Element, relying instead on software-enforced memory separation. Safe 3/5/7 implement EAL6+ chips with a secure boot chain — every firmware update is cryptographically signed and verified before loading. Safe 7’s encrypted Bluetooth is the only model providing full iOS functionality, since USB-C hardware wallet operations aren’t supported on iPhone.
From suite.trezor.io only — WebUSB browser connections work in Chrome and Firefox but not Safari.
The device powers on and Suite detects it through the HID protocol layer.
A challenge-response verification confirms the device responds correctly before you click Set up my Trezor.
Choose Standard (all coins) or Bitcoin-only, then verify the firmware fingerprint matches on both Suite and the device screen.
Write every recovery seed word in exact numbered order on paper — never photograph, type, or copy it digitally. Confirm by re-entering random words when prompted.
4 to 50 digits, entered on a randomized number grid to prevent keystroke logging. Setup is complete and Suite loads the portfolio dashboard.
Model One setup requires Trezor Suite Desktop only — the web app and all iOS devices can’t complete Model One initialization.
Shipping firmware-free eliminates a supply-chain attack vector: a device with pre-installed firmware could contain modified code that exfiltrates key material. Requiring user-initiated installation from Trezor’s servers removes that risk. Each firmware binary is signed with Trezor’s private key, and the Secure Element verifies the signature before executing any new version — rollback protection also blocks downgrading to older, vulnerable builds.
| Firmware Type | Supported Assets | Best For |
|---|---|---|
| Standard | BTC, ETH, SOL, ADA, XRP, 9,000+ | Multi-chain portfolio |
| Bitcoin-only | Bitcoin exclusively | Bitcoin-focused, minimal attack surface |
Switching between firmware types is possible through Device Settings — the device wipes during the switch, but the recovery seed restores all accounts immediately.
| Backup Format | Word Count | Threshold Recovery | Model Support |
|---|---|---|---|
| Standard BIP-39 | 12 or 24 words | Single share — all-or-nothing | Model One |
| Shamir Backup (SLIP-39) | 20 words per share | Multi-share threshold (e.g. 2-of-3) | Safe 3/5/7 |
SLIP-39 splits the master seed into independent shares using threshold cryptography — a 2-of-3 scheme means any two of three share locations reconstruct the wallet, and a single stolen share alone is worthless.
Connect the device via USB and enter the PIN, then open the MetaMask extension.
Account selector → Add account or hardware wallet → Hardware wallet → Trezor.
MetaMask receives only the extended public key (xpub) and derives addresses locally — no private key access.
Choose one or more Ethereum accounts and click Unlock — every transaction from these accounts still requires physical device confirmation.
Can MetaMask control Trezor funds?No. MetaMask only receives the extended public key — it can derive addresses and display balances but cannot sign transactions without hardware approval.
WalletConnect integration inside Trezor Suite enables direct dApp authentication by scanning a QR code, removing the need for a browser extension entirely.
Connect and unlock the device, then click the WalletConnect icon in Trezor Suite.
On the target dApp, click Connect Wallet → WalletConnect to generate a code, then scan it in Suite.
Approve the connection — all dApp transactions then route to the device for physical confirmation.
| Feature | WalletConnect | MetaMask |
|---|---|---|
| Browser extension required | No | Yes |
| Custom EVM RPC configuration | Limited | Full |
| Best for | Quick authentication, no extension | Advanced network configs |
A passphrase extends the seed into a separate derivation path, producing a hidden wallet accessible only when the exact passphrase is entered. It’s case-sensitive and character-exact — “Trezor” and “trezor” derive completely unrelated wallets with no error indication, and it’s never stored on the device.
Forgotten Passphrase RiskEntering the wrong passphrase opens a different, valid, empty wallet with no error message. A forgotten passphrase means permanent loss of the hidden wallet — no service can reconstruct it.
| Feature | Safe 3/5/Model One on iPhone | Safe 7 on iPhone |
|---|---|---|
| Check balance | Yes | Yes |
| Send crypto | No | Yes |
| Device setup | No | Yes |
Safe 7 is the only model with full iPhone support, connecting via Bluetooth. This is an Apple platform restriction — iOS doesn’t support USB-C hardware wallet connections — not a Trezor design choice. Android supports all models over USB-C fully.
| Issue | Cause | Fix |
|---|---|---|
| Device not recognized in Suite | Data-only USB cable | Replace with data-capable cable, try another port |
| WebUSB error in browser | Safari doesn’t support WebUSB | Use Chrome or Firefox |
| PIN entry loops | 16 wrong attempts wipe the device | Recount attempts carefully |
| Trezor not detected in MetaMask | Outdated MetaMask or blocked popup | Update MetaMask, allow the popup |
| Safe 7 Bluetooth not pairing | iOS Bluetooth permission not granted | Settings → Bluetooth → grant access |
Connect via USB cable and open Trezor Suite from suite.trezor.io. Suite detects the device via the HID protocol and shows the dashboard for initialized devices, or guides first-time firmware installation, seed backup, and PIN creation. Chrome and Firefox support WebUSB — Safari does not.
Connect via USB, let Suite detect the device, install firmware, verify the fingerprint on both Suite and the device screen, create a wallet, write down the recovery seed in numbered order, confirm it, and set a PIN. Total time is about 15 minutes. Model One requires Suite Desktop only.
Unlock the device, then in MetaMask go to account selector → Add hardware wallet → Trezor → approve public key export on the device → select accounts → Unlock. MetaMask only receives the public key; every transaction still needs physical confirmation.
Safe 3, Safe 5, and Model One are view-only on iPhone — balance checking and receiving work, but sending and setup require desktop or Android. Safe 7 provides full iPhone functionality via Bluetooth.
About 15 minutes for Safe 3 and Safe 5, including firmware installation, the Secure Element authenticity check, seed creation and confirmation, and PIN setup. The seed backup step shouldn’t be rushed — incomplete recording is the leading cause of permanent access loss.
