Independent MetaMask wallet support for browser extension checks, mobile app troubleshooting, login access, balance display, connected-site issues, and recovery phrase safety.
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
If you need MetaMask support or MetaMask wallet guidance, start by identifying whether the issue is browser extension state, mobile app access, local password/login, wallet import or restore, network/RPC display, transaction status, account visibility, or connected-site permissions.
Common wallet topics include browser extension issues, mobile app setup, wallet import or restore mismatch, balance not showing, token visibility, network/RPC display issues, account discovery, and wallet connection questions.
Never share your recovery phrase or private keys.
Wallet topics
Check browser profile, official extension source, permissions, popup behavior, connected sites, and conflicting extensions.
OpenCheck account, network, custom RPC, token visibility, transaction status, bridge state, and restore context.
OpenReview missing accounts after restore, local password confusion, imported accounts, hardware wallet accounts, and wrong network display.
OpenReview how recovery phrases work before importing, restoring, or backing up any self-custody wallet.
OpenUse token visibility checks for hidden tokens, contract imports, wrong networks, and RPC delays.
OpenAvoid fake extensions, fake update prompts, support DMs, and validation pages asking for seed words.
OpenMetaMask support is clearest when extension state, connected-site permissions, account discovery, network/RPC display, token visibility, and recovery phrase risk are checked separately.
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
Check browser profile, official extension source, permissions, connected sites, popup behavior, Brave shields or browser security settings, cache state, and competing extensions before reinstalling or restoring.
Step 2
Compare the active account, selected network, custom RPC, token contract, and public transaction status before treating a balance display as missing funds.
Step 3
If MetaMask mobile and the extension differ, compare the public address, account order, imported accounts, hardware wallet accounts, custom networks, and token imports.
Step 4
After a browser or MetaMask update, lock and unlock the wallet, reload the extension, review site permissions, reconnect trusted sites, and check RPC status before reinstalling.
Step 5
After restoring, add previously used accounts in order and reconnect hardware or imported accounts separately. A local password unlocks one installation; it does not restore the wallet by itself.
Step 6
Do not enter the Secret Recovery Phrase into a website, form, chat, support tool, or remote session to fix extension, token, or balance issues.
Work through the issue in this order before changing recovery settings, reinstalling apps, or opening official support channels.
Prepare non-private browser and wallet context before reinstalling the extension or importing the wallet again.
MetaMask issues often look like wallet loss when the actual cause is local browser state or display context.
Run these checks before removing MetaMask, clearing browser data, or importing the Secret Recovery Phrase again.
A MetaMask password, connected-site prompt, and recovery phrase each solve different problems.
Most extension issues involve Chrome or Brave profile, extension permissions, version state, cache, connected-site permissions, privacy shields, extension reload behavior, conflicting extensions, or custom RPC failures.
Mobile checks include app version, selected account, selected network, token list, local device state, and whether app data removal would force a restore.
The Secret Recovery Phrase restores deterministic accounts, but imported accounts, manually added networks or tokens, and connected hardware wallet accounts need separate handling.
Expected flow
Move from local browser or app checks into network, account, token, and restore context before contacting official MetaMask support.
Confirm the browser profile, extension source, extension version if known, mobile app state, permissions, and whether popups or connected sites are blocked.
After a browser or extension update, MetaMask may lock, reload, reset connected-site permissions, or show stale RPC/token data until the profile refreshes.
Check active account, selected network, custom RPC, token visibility, contract import, bridge status, and public transaction state.
A local password unlocks one installation. Restoring on a new device depends on the Secret Recovery Phrase, and imported or hardware accounts may need separate handling.
Reject support DMs, fake extensions, wallet validators, copied installers, and any request for seed words, private keys, or screen access.
Prepare browser or phone, extension/app version if known, network, public transaction hash if relevant, error text, and steps tried. Then wait for official support if a ticket is submitted.
Do not reinstall or clear app data until recovery readiness is clear or the same wallet remains accessible on another trusted device.
What users commonly report: MetaMask reports commonly resolve to extension reload behavior after updates, wrong network, failing RPC, hidden token display, missing re-added accounts after restore, or extension conflicts.
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 wallet guidance should ask for 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
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 official extension source, browser profile, conflicting extensions, and backup readiness.
Open helpCheck selected account, network/RPC state, token visibility, bridge status, and transaction context.
Open helpRe-add accounts and separately reconnect imported or hardware wallet accounts before assuming the phrase is wrong.
Open helpNo support chat should ask for seed words, private keys, or remote access.
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.
Check browser profile, official extension source, permissions, popup behavior, connected sites, and conflicting extensions.
OpenCheck account, network, custom RPC, token visibility, transaction status, bridge state, and restore context.
OpenReview missing accounts after restore, local password confusion, imported accounts, hardware wallet accounts, and wrong network display.
OpenUse token visibility checks for hidden tokens, contract imports, wrong networks, and RPC delays.
OpenFAQ
Start by identifying whether the issue is with the browser extension, mobile app, wallet access, network display, token visibility, or a connected site. Use official MetaMask channels for official support.
No. No legitimate wallet guidance should ask for your recovery phrase or private keys.
Identify the browser, extension version if known, wallet connection step, network selected, and what changed before using official MetaMask channels.
Prepare your device type, app version if known, issue type, and screenshots that do not show private information.
Compare browser extension use, mobile app experience, supported networks, wallet connection flow, and recovery phrase handling before choosing.
MetaMask is commonly described as a hot wallet because it is used through a browser extension or mobile app.
The wallet may be on the wrong network, using a different account, missing a custom token import, waiting on RPC refresh, or missing imported/hardware accounts that are not restored by the phrase alone.
The extension may reload, lock, reset site permissions, require reconnecting trusted sites, or show stale RPC/token data until the browser profile and network state refresh.
Compare wallet types, review beginner wallet help, and understand recovery phrase basics before choosing your next wallet.