MetaMask Recovery: Why an Imported Account Is Missing

A correct MetaMask Secret Recovery Phrase does not always restore imported accounts. Distinguish derived accounts, other phrases, private keys and hardware wallets.

MetaMask Recovery: Why an Imported Account Is Missing

A correct Secret Recovery Phrase (SRP) does not guarantee that MetaMask will show every account you saw before. An SRP restores accounts derived from that root; an account imported with a private key or JSON file, an account from another SRP and a hardware-wallet account have a different origin. Identify that origin and follow the official process to add or reconnect it. Never enter a phrase, private key or JSON file into a website or support chat.

The phrase restores a root, not every visible account

MetaMask distinguishes a wallet—the set governed by one key source—from the accounts shown in the selector. When you restore with the original SRP, MetaMask can recover accounts created under that same SRP. Accounts imported from another SRP, a private key or a JSON file do not become part of the first root automatically.

The official guide to adding missing accounts after restoring an SRP confirms that separation: when recovering through an SRP alone, accounts derived from that phrase may reappear, while accounts imported by private key or JSON, and accounts connected through a hardware wallet, must be added or connected again. “The phrase works but my account is missing” therefore does not by itself prove that the phrase is wrong.

There are four common cases:

  • An account derived from the same SRP. It was created inside that wallet. In an SRP-only wallet, MetaMask may discover Ethereum Mainnet accounts in ascending order while they have a non-zero ETH balance; discovery can stop at the first account without that balance. An account from the same source can be added through the official flow, but a token or another network may require selecting the correct network and asset.
  • An account derived from another SRP. A different phrase produces a different root. Restoring SRP A does not add accounts from SRP B. Keep and restore both phrases separately.
  • An account imported by private key or JSON. The account is not derived from the SRP used to open MetaMask. You need the same import material and the official import flow, only in the legitimate app and with a safe backup.
  • An account connected through a hardware wallet. The key remains under the external device's control. MetaMask cannot reconstruct it from a local SRP; connect the original device or a compatible replacement restored through the manufacturer's procedure, then approve the connection according to both sets of documentation. Do not export a hardware wallet's seed into MetaMask.

Diagnose without exposing secrets

Start with the public address you expected to see. Compare it with a trusted record or known transaction without publishing screenshots that reveal unnecessary balances or metadata. A different address often means another account, another phrase, another derivation path or an imported account; do not try to “correct” words at random.

Then rebuild your inventory without copying secrets into online tools:

  1. Record which device or wallet created the account and whether it was added by SRP, private key, JSON or hardware wallet.
  2. Check which SRP you restored, without entering it into any form outside the official application.
  3. Look on the correct network and chain, and verify that you are not viewing an equivalent address on another network.
  4. If it is derived from the same SRP, use the official add-account option and compare the resulting public address.
  5. If it was imported, locate the original backup and import it into MetaMask only. If it was hardware, connect the physical device; do not replace that step with an exported key.

MetaMask describes importing a wallet with an SRP as a different operation from importing one account with a private key. The official guide to connecting or importing an existing wallet also explains that a JSON file is used on Extension. The JSON file's password protects that file; the MetaMask password protects its own access. Use the password that belongs to the file, without confusing it with the SRP.

Restoring on another device is not the same as importing

Synchronisation can copy some data between installations, but it does not turn every key origin into one wallet. MetaMask's official backup and sync documentation says that accounts associated with the relevant SRP are synchronised, while accounts imported through private keys, JSON or hardware wallets do not currently sync in that way.

If you reset an SRP-only installation, local accounts can be removed and you may need to import the SRPs and private keys again. MetaMask's official guide to restoring a wallet with an SRP warns that resetting removes local data and describes which derived accounts it attempts to discover. Before deleting an installation, verify that a backup for every source exists and that you can access the correct account. Turning off a sync feature also does not automatically mean that all remote data is deleted; review the provider's current policy and controls if that privacy question matters.

MetaMask also documents sign-in flows with Google, Apple or Telegram. In those wallets, the MetaMask password used with the linked social account may allow some imported wallets to reappear, except hardware wallets. The import guide warns that importing a wallet into a linked installation associates it with that social identity and does not allow unlinking it. Review that choice before importing. This access does not change which keys each SRP derives. For independent recovery, keep the SRPs and backups for every root.

Do not mix an SRP with a passphrase or SeedAddress

An optional BIP39 passphrase can derive another valid wallet from the same mnemonic; omitting or changing it can make the result look like an empty account. The difference between a seed phrase, passphrase and passwords helps separate those values. Typing a passphrase into MetaMask's password field does not reproduce that derivation. Recovery must preserve the original wallet's format and configuration.

SeedAddress is another case: its deterministic method runs in the browser from coordinates, password, language and length; the place or address used is public and the method adds no random entropy. If a SeedAddress phrase was imported into MetaMask, MetaMask does not know those inputs and cannot recover them from the SRP. An offline copy of the phrase can recover the imported account; the exact inputs are only needed if you try to regenerate it, with no regeneration guarantee if they are missing. Do not treat 24 words as a guarantee of 256 bits of random entropy. If you need a new wallet, use the wallet's random-generation process and verify the migration; the guide to connecting a hardware wallet versus importing a phrase explains why these are not equivalent operations.

A safer checklist

  • Do not share the SRP, private keys, JSON passwords or screenshots containing codes or balances.
  • Confirm whether the expected account came from the restored SRP, another SRP, an import or hardware.
  • Verify the public address on the correct network before moving funds.
  • Import or reconnect only from the official application and keep an independent offline backup.
  • Keep each root and its metadata separate; do not assume one SRP can recover accounts it never derived.

The key signal is the origin of the keys. A correct SRP can restore its own family of accounts perfectly and still not show an imported account. Identifying the source avoids repeated restores, exposed secrets and transfers to an address you do not control.