Use this MetaMask support page when the wallet is stuck loading, opens to a blank screen, freezes after unlock, or will not finish loading on extension or mobile.
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 not loading problem is commonly caused by browser profile state, extension conflicts, outdated app or browser versions, cache issues, network/RPC timeouts, or a corrupted local vault state.
Common wallet topics include MetaMask wallet not loading, blank extension screen, mobile app stuck, unlock freeze, browser profile issue, app cache problem, or network timeout.
Never share your Secret Recovery Phrase, private keys, password, or screen access.
Wallet topics
Use extension-specific checks for browser permissions, profiles, and conflicts.
OpenIf reinstall is required, prepare for safe restore and missing-account checks.
OpenReview recovery phrase safety before reset, reinstall, or restore steps.
OpenReturn to MetaMask wallet support for broader troubleshooting.
OpenAvoid fake update pages, remote access helpers, and support DMs.
OpenReport non-private app, browser, and loading 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
If MetaMask is still accessible anywhere, confirm the recovery phrase is safely backed up offline before removing the extension, clearing app data, or resetting a browser profile.
Step 2
Close and reopen the browser or mobile app, restart the device, update the browser or app, and retry without changing recovery settings.
Step 3
Disable conflicting browser extensions temporarily, try the correct browser profile, turn off unstable VPN/proxy settings, and switch away from a failing custom RPC if the wallet loads.
Step 4
If reinstall or restore becomes necessary, use the official MetaMask source and restore only on a trusted device. Never paste the phrase into a support site.
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.
Check the right browser profile, extension permissions, browser updates, and conflicting extensions before removing MetaMask.
Update the app from the official app store, check storage and network conditions, and avoid clearing app data unless recovery backup is confirmed.
A failing custom RPC can make the wallet feel stuck. If accessible, switch to a reliable network endpoint and retry.
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.
Check browser profile, extension conflicts, permissions, and update state before reinstalling.
Open helpDo not clear app data or remove the extension until recovery backup is understood.
Open helpUse official MetaMask sources only and avoid cloned download pages.
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.
Use extension-specific checks for browser permissions, profiles, and conflicts.
OpenIf reinstall is required, prepare for safe restore and missing-account checks.
OpenReview recovery phrase safety before reset, reinstall, or restore steps.
OpenUse this before reset, restore, reinstall, or responding to a request for seed words.
OpenFAQ
Common causes include extension conflicts, outdated browser or app versions, stuck cache, wrong browser profile, failing RPC endpoint, VPN/proxy interference, or local vault state issues.
Only after confirming your recovery phrase is safely backed up offline or the same wallet is accessible on another trusted device.
No. Legitimate support should not ask for seed words, private keys, remote access, or wallet validation.
Browser or phone model, app or extension version if known, selected network, error text, and steps tried. Do not include recovery words.
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.