Lost Access to MetaMask: Restore Your Wallet and Missing Accounts

If you have lost access to MetaMask, preserve the old installation before resetting it. A Secret Recovery Phrase can restore accounts derived from that phrase, but a separately imported account may need its own key or original wallet. If MetaMask opens with a different address, compare account origins before concluding that the funds are gone. The checklist below separates a login failure from a missing account and a missing balance.
First steps: preserve what still works
- Record the device, browser profile, MetaMask version and exact error without photographing any recovery words.
- Check whether the old phone or browser profile still opens the wallet. Keep that installation intact.
- Find a previously used public address in a withdrawal receipt or transaction record. Compare full addresses, not account names.
- Identify the original setup: phrase-only wallet, configured social login, private-key import or connected hardware wallet.
- If you have verified recovery material, use the official MetaMask restoration flow on a trusted device.
- If you lack that material, stop before deleting the extension, clearing its storage or resetting the phone.
A password unlocks local wallet data; it does not replace the Secret Recovery Phrase on a fresh installation. A forgotten password with a retained phrase has a different route from a forgotten password with only an old browser profile. See forgotten wallet passwords.
MetaMask's documented desktop vault procedure can help in some cases where local data survives. It depends on the browser, retained files and password. It is not a universal mobile recovery tool. Describe the device and backup first; do not upload vault files to a search result or send them to an unsolicited support account.
Which accounts does your recovery material cover?
| Original account | Recovery route | What does not substitute for it |
|---|---|---|
| Created under the restored phrase | Restore that phrase and re-add derived accounts as needed | A matching display name |
| Imported with a separate private key or encrypted JSON | Reimport the original account using its retained material | The main MetaMask phrase alone |
| Imported from another phrase | Restore that separate wallet | Adding more accounts under the first phrase |
| Connected hardware wallet | Reconnect the appropriate device and select the correct account | The software wallet's phrase |
| Previously configured Google, Apple or Telegram login | Use the same linked login and MetaMask password | A different social account |
For a configured social-login wallet, MetaMask currently documents restoration of associated imported accounts as well, with hardware wallets excluded. This does not mean any Google, Apple or Telegram account can recover any MetaMask wallet. The method must already have been connected, and its required credentials must be available.
An imported account is missing after restoring MetaMask
Start with the missing public address. If it was created under the restored phrase, use the account selector to add accounts in their original sequence. Automatic discovery may miss an account holding tokens on another network without ETH on Ethereum mainnet. The address is the reliable comparison; a custom name may need to be set again.
If the account was imported by private key, adding more derived accounts cannot recreate it. Find the original wallet, its separate backup or an old installation that still contains that account. A JSON keystore also needs its own encryption password, which may differ from the MetaMask password. The official JSON import option is documented for Extension.
Educational example: your main phrase restores the address used for everyday transfers, but an account named Savings is absent. Records show Savings was imported from another wallet. Repeatedly adding accounts under the everyday phrase tests the wrong recovery route. The next useful check is whether the source wallet or its backup still exists. This is a diagnostic example, not a recovery result.
For hardware accounts, use the hardware connection flow and confirm the address on the device where supported. Do not type the hardware wallet's recovery words into MetaMask merely to make its account appear. The Ledger access guide explains the distinction between reconnecting a device and recovering it.
The address is correct, but the balance is not
Once the address matches, compare the network and transaction history. A missing token display does not prove a missing private key. Check the exact token contract on the correct chain and whether the original transfer reached this address. Use the empty balance after recovery checklist for this branch.
An unfamiliar outgoing transaction changes the problem: restoring an interface does not reverse an on-chain transfer. Record its network, time and transaction hash, then follow the hacked wallet response. Do not fund an address again until you have assessed whether its keys were exposed.
What to include in a recovery assessment
For a MetaMask recovery assessment, describe the original setup, which device or profile survives, whether the wallet opens, whether the expected public address appears, and whether a phrase, key backup or password hints exist. Say what you have already reset or reinstalled. Do not submit the phrase, private key, vault contents or password in the contact form.
The useful outcome of an initial review is a specific next check: account discovery, locating a separate import, examining retained local data or assessing a bounded password search. A public address alone cannot recreate its private key. If no matching secret material, usable old installation or configured recovery method survives, a support ticket cannot manufacture access.
Risks and limitations
- Resetting or uninstalling can erase the only remaining local copy of an imported key.
- Restoring one Secret Recovery Phrase does not cover every wallet previously shown in the same interface.
- Anyone given a private key or recovery phrase can control the corresponding assets.
- Vault recovery depends on retained data, browser support and password feasibility; success is not guaranteed.