Use this Trezor balance issue page when Trezor Suite shows a missing balance, stale account, zero value, wrong account, or tokens that do not match what you expected.
Independent wallet security guidance. This site is not Trezor.
Trezor help topics
Wallet security
Quick issue summary
Ledger and Trezor support teams should never ask for a recovery phrase, seed phrase, private key, or remote access to a wallet.
Recently Reported Issues
A Trezor balance not showing issue usually points to Suite sync, selected coin or network, account type, hidden wallet passphrase, token display, pending transaction, or a restore using a different recovery phrase. Check display and account context before resetting.
Common wallet topics include Trezor balance issue, missing balance, zero balance, hidden wallet confusion, account type mismatch, token display, sync state, or restore context.
Never share your recovery phrase, seed phrase, private keys, or PIN.
Wallet topics
If Suite itself is stuck, fix app loading before balance checks.
OpenSome balance and account updates need the device to be recognized.
OpenReturn to Trezor support for connection, firmware, recovery, and balance issue routing.
OpenUse the older zero-balance page for another view of hidden wallet and sync causes.
OpenFake balance recovery pages commonly target hardware wallet users.
OpenReport non-private account display symptoms to PhraseWallet.
OpenTrezor Suite troubleshooting is safest when you separate display, sync, device, firmware, and recovery phrase concerns before changing wallet settings. Use official Trezor support links for device-specific instructions.
Use these checks to separate ordinary setup friction from wallet safety risk before you reset, restore, reinstall, or open wallet support portals.
A cable can power a hardware wallet without carrying data. Test a known data-capable cable, direct port, and stable connector before changing wallet settings.
Windows device recognition and macOS accessory permission prompts can block detection until approved, completed, or followed by an app restart.
Close competing wallet apps, browser wallet tabs, and stale update windows before reconnecting so Suite or Bridge can own the device session.
After firmware or app updates, bootloader or update mode can be normal. Reconnect, approve prompts, reopen the trusted app, and let account discovery finish before restoring.
Standard wallet versus hidden passphrase wallet is a common mismatch. Compare a known public address before repeating restore steps.
A missing balance can be selected account, network, token visibility, app sync, passphrase, or restore context rather than fund movement.
Verify backup readiness, official app source, firmware state, public address, account context, and reconnect steps before wiping the device.
Fake support DMs, copied installers, fake firmware downloads, remote-access offers, and recovery phrase requests are not valid fixes.
Match what you are seeing to the closest state first. The next safest step is usually a visibility, connection, or context check before reset or restore.
Issue state
The device can receive power while Suite, Bridge, browser permissions, OS prompts, cable data, or another app blocks communication.
Next safest step: Try a direct data-capable cable, approve browser or OS prompts, restart Suite or Bridge, and close competing wallet apps.
Issue state
Suite may be showing a different coin, account type, token view, hidden wallet passphrase, or sync state.
Next safest step: Compare standard versus hidden wallet, selected coin, account type, token view, and a known public address.
Issue state
Update-mode handling, browser permission resets, Bridge state, reconnect prompts, and account discovery can make the wallet look incomplete temporarily.
Next safest step: Restart Suite or the browser, reconnect, approve prompts, and let account discovery finish before restoring.
Issue state
A missing or different passphrase opens a different hidden wallet. A blank hidden wallet is not the same as confirmed fund loss.
Next safest step: Check the expected public address and passphrase context before trying another restore.
Issue state
Copied Suite installers, firmware mirrors, support DMs, and remote helpers often target users during restore or update confusion.
Next safest step: Use official Trezor sources and keep recovery words, PINs, and passphrases out of chats and forms.
Avoid these common shortcuts while you are narrowing the issue. Most wallet problems are clearer after connection, account, network, token, and update state are separated.
Common mistake
A different hidden wallet passphrase can show a different wallet view even when the Trezor and seed words are valid.
Better step: Compare standard wallet versus hidden wallet, expected public address, selected coin, and account type before restoring again.
Common mistake
Bridge state, browser permissions, OS prompts, hubs, docks, and another wallet app can make detection look worse than it is.
Better step: Restart Suite or the browser, approve prompts, test a data-capable cable, and close competing apps first.
Common mistake
Firmware work can temporarily change how the device appears before Suite finishes reconnecting and rediscovering accounts.
Better step: Follow official instructions for the exact screen, reconnect, approve prompts, and wait for account discovery.
Common mistake
Copied installers, firmware mirrors, search ads, and remote helpers are unsafe places to troubleshoot recovery issues.
Better step: Use official Trezor sources and never enter recovery words, PINs, or passphrases into support forms or chats.
Start with the most common causes before resetting the wallet, restoring from a recovery phrase, or trusting a support message.
Step 1
Confirm the exact coin, network, account type, token, and receiving address before assuming funds are gone.
Step 2
Restart Trezor Suite, check network access, reconnect the device if needed, and let accounts sync before restoring, resetting, or entering recovery words anywhere.
Step 3
If you use a hidden wallet, the passphrase must match exactly. A different passphrase opens a different wallet view.
Step 4
When appropriate, compare a public address on a trusted explorer. Never share recovery words or private keys to prove ownership.
Step 5
Confirm backup readiness offline, verify the update source inside official software, keep USB stable, close competing wallet apps, and avoid copied installers or remote helpers.
Step 6
After firmware or app updates, restarting the app, reconnecting the device, approving prompts, and waiting for account discovery can be normal before balance checks are reliable.
Step 7
Compare a known public address, account type, derivation or passphrase context, selected network, and app sync state before entering the recovery phrase again.
Step 8
A zero balance, hidden token, stale account view, or delayed sync is a visibility problem until public address or transaction evidence shows funds moved.
Trezor passphrase settings can create separate wallet views. Standard and hidden wallets can show different balances.
Different account types or address formats can make expected funds appear missing until the correct account is added.
Suite may need accounts re-added and synced. A different recovery phrase or passphrase will not show the same wallet.
Bootloader or update mode can change how a hardware wallet appears to the computer. Follow official on-screen state instructions before reset or restore decisions.
After firmware, app updates, or restore work, re-open the app, approve device prompts, let account discovery finish, and check network or token display before reset steps.
For official Trezor help, downloads, updates, or contact options, use Trezor's official portal and verified official channels. This page helps you prepare safe, non-private context before opening support portals.
No legitimate wallet guidance should need your recovery phrase.
A recovery phrase controls wallet restoration. Treat it as private self-custody information and review how phrases work before using any wallet.
Community reports
Trezor troubleshooting reports often involve Suite detection, Bridge or browser state, USB connection, firmware prompts, balance display, and recovery phrase safety. These examples avoid private wallet data and focus on the support pattern.
These examples are informational and reflect common user-reported wallet issues. Never share your recovery phrase, seed phrase, private keys, PIN, or wallet backup with anyone. Official wallet support should never ask for your recovery phrase.
“Trezor Suite shows zero balance after setup, but I used this wallet before.”
Zero balance issues may happen when a different recovery phrase, passphrase, account type, coin network, or hidden wallet setting is being used.
“Trezor Suite will not open or keeps loading on my computer.”
Trezor Suite issues may involve app updates, browser conflicts, operating system permissions, cached sessions, or temporary connectivity problems.
“My Trezor is connected by USB, but Trezor Suite does not recognize it.”
Connection issues may involve USB cable type, bridge or web permissions, outdated firmware, browser support, or device authorization prompts.
“I am not sure if my recovery phrase is correct and I do not want to lose access.”
Recovery phrases should never be typed into unofficial portals or shared with anyone. Users should only use official device-based recovery processes.
Report wallet issue
Submit a non-secret wallet problem for moderated review and safer routing. PhraseWallet is independent and this is not official wallet support or emergency recovery assistance.
Never enter your recovery phrase, private key, password, PIN, or payment details.
Common wallet issues
Use these maintained support paths to move from a symptom to the right setup, recovery, troubleshooting, or security help without sharing private wallet data.
Related problems
If this page is close but not exact, check these nearby support topics so the next step matches the failure pattern.
Hidden wallet passphrase, account type, or restore context can show a different Trezor wallet view.
Open helpBridge state, browser permissions, USB data, and device prompts should be checked before reset steps.
Open helpUse official Suite prompts and keep recovery words offline while checking cable and bootloader state.
Open helpAvoid remote helpers and anyone asking for recovery words, private keys, PIN, or wallet validation.
Open helpOfficial wallet support should never ask for your recovery phrase, seed phrase, private keys, PIN, wallet backup, screen sharing, or remote access. Verify downloads, QR tools, and update prompts on the official wallet site before acting.
Related troubleshooting
Move to the next closest Trezor check only after the current issue type is clear.
If Suite itself is stuck, fix app loading before balance checks.
OpenSome balance and account updates need the device to be recognized.
OpenUse the older zero-balance page for another view of hidden wallet and sync causes.
OpenReturn to the Trezor hub for setup, recovery, balance, app, and safety paths.
OpenFAQ
Common causes include wrong coin or network, stale Suite sync, hidden wallet passphrase mismatch, account type mismatch, missing account after restore, or a different recovery phrase context.
Not necessarily. Check public address, network, account type, hidden wallet context, and Suite sync state before assuming funds moved.
No. Fake balance recovery and wallet validation pages often steal recovery phrases.
Asset, network, device model, Suite version if known, account type, error text, and public address only if you are comfortable sharing it. Never include seed words or private keys.
Common causes include phrase mismatch, passphrase or hidden-wallet context, derivation or account path, selected network, hidden tokens, stale sync, or imported accounts that need separate handling.
Updates can put the device in update mode, require reconnecting, reset app or browser permissions, delay account discovery, or leave balance data stale until the official app refreshes.
Use official Trezor support links for device-specific support, and keep private wallet recovery data offline while you troubleshoot.