Use this MetaMask restore support page when a restored wallet shows the wrong address, missing accounts, missing tokens, or a balance that does not match the wallet you expected.
Independent wallet security guidance. This site is not MetaMask.
MetaMask 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 MetaMask wallet restore issue often comes from using a different Secret Recovery Phrase, not re-adding accounts, viewing the wrong network, missing imported accounts, or expecting a local password to restore the wallet.
Common wallet topics include MetaMask wallet restore issue, missing account after restore, wrong wallet address, missing balance after restore, token visibility issue, or password confusion.
Never share your Secret Recovery Phrase, private keys, password, or screen access.
Wallet topics
Review seed phrase, password, and recovery boundaries before trying another restore.
OpenIf the address is correct but funds are missing, troubleshoot balance display.
OpenIf only tokens are missing, check visibility and custom token imports.
OpenReturn to the MetaMask support hub for broader recovery help.
OpenReview recovery phrase safety before any restore action.
OpenReport non-private restore symptoms to PhraseWallet.
OpenMetaMask troubleshooting is safest when you separate extension state, mobile app state, selected account, network/RPC display, token visibility, and recovery phrase concerns before reinstalling or restoring.
Use these checks to separate ordinary setup friction from wallet safety risk before you reset, restore, reinstall, or open wallet support portals.
Check the exact browser profile, phone, app version, permission state, selected account, and last update before reinstalling or restoring.
Chrome or Brave privacy settings, shields, popup blocking, stale cache, browser permission resets, and competing wallet extensions can block prompts.
Missing balances often come from wrong network, hidden token, NFT filter, custom contract, stale RPC, delayed indexing, or a pending bridge or transfer.
Extension, mobile, imported, hardware, and connected-site accounts can point to different public addresses. Compare the address before approving.
After browser, app, or extension updates, reload the wallet, reconnect trusted sites, and let balances refresh before treating the view as final.
Check backup readiness, official app source, active address, account/profile mismatch, network, token visibility, and sync state before clearing data.
Avoid fake support DMs, copied apps or extensions, wallet validators, remote access requests, and any request for recovery words or private keys.
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 browser profile, account order, mobile wallet, hardware account, or imported account may differ from the expected address.
Next safest step: Compare the active public address, browser profile, account list, and connected hardware/imported accounts before restoring.
Issue state
Browser updates, popup blocking, privacy shields, stale connected-site permissions, or extension conflicts can block prompts.
Next safest step: Reload MetaMask, review connected-site permissions, disable conflicting wallet extensions temporarily, and reconnect trusted sites.
Issue state
A correct account can still hide assets because of wrong network, custom RPC, missing token import, stale RPC, or bridge delay.
Next safest step: Check selected network, token contract, transaction status, and RPC state before assuming the token is gone.
Issue state
MetaMask may lock, reload, reset permissions, or show stale RPC/token data after browser or extension updates.
Next safest step: Lock and unlock, reload the extension, check network/RPC health, and wait for token data to refresh before reinstalling.
Issue state
Failed transactions, token display issues, and restore mismatch often attract fake support DMs and copied extensions.
Next safest step: Do not share Secret Recovery Phrase, private keys, screen access, or validation screenshots.
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
The extension can open normally while the browser profile, account order, mobile wallet, hardware account, or imported account differs.
Better step: Compare the active public address, browser profile, account list, connected sites, and imported or hardware accounts first.
Common mistake
Wrong network, stale RPC, missing contract import, bridge delay, or token visibility settings can hide assets without moving funds.
Better step: Check selected network, token contract, RPC status, and public transaction history before restoring again.
Common mistake
Chrome or Brave updates, privacy shields, popup blocking, stale cache, and competing wallet extensions can block prompts.
Better step: Reload MetaMask, review connected-site permissions, and temporarily disable conflicting wallet or privacy extensions.
Common mistake
Fake extensions and wallet validation DMs often appear after failed transactions, token display issues, or restore mismatch.
Better step: Use verified extension sources and never share the Secret Recovery Phrase, private keys, screen access, or validation screenshots.
Start with the most common causes before resetting the wallet, restoring from a recovery phrase, or trusting a support message.
Step 1
Compare the restored public address with a known address or transaction record. Do not share the recovery phrase to prove ownership.
Step 2
After restoring the phrase, add accounts in order until previously used addresses appear. Imported accounts and hardware wallet accounts may need separate re-import or reconnection.
Step 3
Switch to the network where activity occurred, verify custom RPC details if used, and import verified token contracts when needed.
Step 4
Do not use recovery helpers, synchronization pages, or live chats that ask for your phrase, private key, or remote access.
Step 5
After MetaMask or browser updates, reload the extension, unlock the wallet, review connected-site permissions, verify the selected network, and wait for RPC data to refresh.
Step 6
Compare a known public address or transaction record with the current wallet before restoring again, deleting app data, or entering the phrase anywhere else.
Step 7
If the address is correct, check network selection, hidden token or NFT filters, custom token imports, RPC or indexer delay, and stale app or extension state.
Make sure you are in the correct browser profile and official extension. Account names may reset even when addresses are restored.
Mobile restore should show the same addresses when the same phrase and account order are used. Check network and token visibility after restore.
Accounts imported by private key or connected from a hardware wallet are not recreated solely from the MetaMask recovery phrase.
Updates can reload apps, reset permissions, disconnect sites, or leave stale balance data. A restart, reconnect, or refresh can be normal before restore is relevant.
A missing token or blank account view may be display context. Public address, network, transaction status, and token settings are safer checks than repeated restores.
For official MetaMask help, downloads, updates, or contact options, use MetaMask's official portal and verified official channels. This page helps you prepare safe, non-private context before opening support portals.
No legitimate MetaMask help should need your Secret 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
MetaMask support reports often involve restore mismatch, missing balances or tokens, browser extension state, network context, and fake support warnings. These examples stay symptom-focused and avoid private wallet data.
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.
“MetaMask is open, but the balance, token, or transaction history does not match what I expected.”
Missing balances are often display or network issues first: selected account, chain, token visibility, RPC/server response, sync delay, and restore context should be checked before restoring again.
“The recovery phrase was accepted, but MetaMask shows different addresses or no funds.”
Some restores initially show empty wallets until account discovery, imported accounts, address verification, token visibility, and the correct network or derivation context are checked.
“MetaMask stopped loading or connecting after an update, browser change, or app refresh.”
Extension conflicts are commonly isolated by checking the browser profile, disabling competing extensions, then reconnecting sites only after account and network context are clear.
“A support page asked for my MetaMask seed phrase to fix the issue.”
Users often confuse the local extension password with the recovery phrase; the password unlocks one installation, while the phrase restores the wallet. No support path should ask for recovery words, private keys, remote access, or a wallet validation signature to fix a display or access problem.
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.
Re-add accounts after restore and separately reconnect imported or hardware wallet accounts.
Open helpA correct restore can still show missing balances on the wrong network.
Open helpDo not use validation pages or helpers asking for the recovery phrase.
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 MetaMask check only after the current issue type is clear.
Review seed phrase, password, and recovery boundaries before trying another restore.
OpenIf the address is correct but funds are missing, troubleshoot balance display.
OpenIf only tokens are missing, check visibility and custom token imports.
OpenUse this before reset, restore, reinstall, or responding to a request for seed words.
OpenFAQ
You may need to re-add accounts in MetaMask, reconnect hardware wallet accounts, re-import private-key accounts, or confirm you used the intended recovery phrase.
A different recovery phrase creates a different wallet. Also check whether the missing address was imported separately or came from a hardware wallet.
No. The local password unlocks one installation; wallet restore generally depends on the Secret Recovery Phrase or separate private-key imports.
No. Never send seed words, private keys, or screenshots of recovery data to support or issue-report forms.
Common causes include a different phrase or account, missing re-added accounts, imported accounts not restored by the phrase, wrong network, hidden token settings, delayed sync, or app/extension profile mismatch.
No. Token visibility, network selection, stale balance display, or app sync issues should not require entering recovery words into a website, support chat, validator, or remote session.
Updates can reload the app or extension, reset permissions, disconnect sites, refresh cache, change network state, or delay token display. Check those states before reinstalling or restoring.
Use the MetaMask support hub, report non-private symptoms, and keep official MetaMask access secondary until you know the issue type and recovery phrase risk.