A MetaMask installation can display accounts derived from several Secret Recovery Phrases, separately imported private keys, social-login wallets and hardware devices. They may look like one wallet, but they do not share one recovery method. This guide builds an account-by-account recovery map, explains what returns automatically and provides a controlled migration workflow for a new browser, phone or computer.

Last reviewed: October 20, 2026. MetaMask recovery, social-login, Backup and Sync, supported networks and account-import behavior can change. Confirm current instructions in the official MetaMask Help Center. Never enter a Secret Recovery Phrase or private key into a support form, website or message. This independent guide is educational and is not financial, legal or investment advice.

Quick answer: first inventory every address and identify whether it comes from an SRP, imported private key, social-login wallet or hardware device. Restoring one SRP returns accounts derived from that SRP, but imported private-key accounts, other SRPs and hardware accounts may require separate re-entry or reconnection. Exported wallet data can help rebuild names, contacts, settings and custom networks, but it is not a substitute for secret key material. Test the new installation and compare every address before deleting the old one.

1. A MetaMask installation is a container, not one recovery object

The account selector can combine several independent key sources in one interface. Convenience can hide the boundaries: Account 1 may come from the original SRP, a trading address may be imported by private key, and a vault address may be controlled by a Ledger.

Restoration succeeds only when each address is matched to its real key source. The wallet logo, account name and browser profile do not establish that relationship.

2. Separate blockchain state from wallet configuration

Balances, NFT ownership, approvals and transaction history live on blockchains. MetaMask displays and signs for them; reinstalling the application does not move or erase those assets. Access returns when the same address can be controlled again.

Account labels, contacts, custom networks, token display choices and connected-site records can be local or synchronized configuration. They may disappear even though onchain assets remain intact.

3. Build an address inventory first

Before migrating, list every address visible in MetaMask, its label, relevant networks and suspected key source. Verify addresses with a trusted explorer and record which contain assets, approvals, identities or dapp positions.

Address Key source Recovery requirement Test status
Public address only SRP-derived Correct SRP and account order Not tested / tested
Public address only Imported private key That account’s private key or JSON backup Not tested / tested
Public address only Hardware wallet Hardware backup, device and matching derivation path Not tested / tested

Do not place SRPs, private keys or device PINs in this ordinary inventory.

4. Understand the Secret Recovery Phrase boundary

An SRP is the root used to derive a family of accounts. Anyone who obtains it can reproduce those accounts without the original browser or password. Protect it offline and assume disclosure compromises every account derived from it.

One MetaMask instance can now manage multiple SRPs, but importing them into the same interface does not merge their cryptographic roots. Each phrase remains an independent recovery boundary.

5. Understand the MetaMask password boundary

For an SRP-based setup, the password protects local access to that MetaMask installation. It does not replace the SRP and is not normally a cross-device recovery credential. A new installation restored from an SRP receives a newly chosen local password.

Knowing only an old password is not a reliable backup after the browser profile or device data disappears.

6. Understand a private-key imported account

Importing one private key adds control of one account. That address is not transformed into a child of the original MetaMask SRP. Restoring the main SRP later may therefore omit it.

Back up the imported account through its original recovery method. Avoid exporting private keys unnecessarily, because each exposed copy can control the account.

7. Understand JSON-imported accounts

An encrypted JSON keystore can represent an individual account and needs its associated decryption password. It is different from MetaMask’s wallet-data export, which primarily documents configuration.

Label the file’s purpose without placing its password beside it. Test the supported import procedure before depending on it.

8. Understand hardware-wallet accounts

A Ledger or Trezor connected to MetaMask keeps the signing keys under the hardware wallet’s recovery system. MetaMask is an interface for those accounts; its SRP does not back them up.

After reinstalling MetaMask, reconnect the hardware device and select the same account and derivation path. Never type the hardware wallet’s recovery words into MetaMask to make the account appear.

9. Understand social-login recovery

Current MetaMask flows can create access using Google, Apple or Telegram together with a MetaMask password. MetaMask documents that the wallet still has an SRP, but its encrypted recovery material is handled through a different social-login model.

This makes the social account, its recovery routes and the MetaMask password part of the access chain. Protect the social account with strong phishing-resistant authentication.

10. Compare the recovery methods

Method Normally restores Does not automatically restore
One SRP Accounts derived from that phrase Other SRPs, imported private keys and hardware accounts
Social login and password Accounts associated and synchronized under that login Hardware-wallet accounts
Private key One account The rest of an SRP wallet
Hardware connection Accounts selected from that signer MetaMask hot-wallet accounts
Wallet-data export Reference data for manual configuration Ownership keys and signing capability

11. What an SRP restore does

On a fresh installation, choose the official existing-wallet flow and enter the words locally in their exact order. MetaMask derives accounts according to the supported path and creates a new local vault protected by the new password.

Use a clean device and verified extension or mobile application. No support agent needs to watch the process or receive the words.

12. Why only Account 1 may appear

MetaMask can scan derived accounts in ascending order and use Ethereum-mainnet ETH activity as a discovery signal. Official guidance notes that automatic discovery can stop at an account with zero ETH even when a later account holds tokens on another network.

This does not mean the later account vanished. Recreate additional Ethereum accounts under the same SRP in their original order and compare the resulting addresses.

13. Re-add derived accounts in sequence

Select the option to add an Ethereum account repeatedly. Deterministic derivation should reproduce Account 2, Account 3 and later addresses in order when the correct SRP and supported path are used.

Names do not control derivation. A former label such as “DeFi” may return with a generic name, but the address should match exactly.

14. Diagnose an address that does not match

Stop before sending funds. Check whether the phrase is correct, whether the old account belonged to another SRP, whether it was imported by private key or whether it came from hardware. A derivation-path difference can also produce another address.

Do not keep entering recovery phrases into random wallets or recovery websites hoping that one displays the expected account.

15. Multiple SRPs require multiple records

MetaMask supports managing multiple SRPs in one installation. This can separate personal, professional and experimental activity while keeping one interface, but every phrase needs its own protected backup and address map.

If the installation is restored using only SRP A, addresses from SRP B should not be expected until SRP B is imported separately.

16. Imported accounts need their own backup

Mark every imported account in the inventory. Retain its original SRP, private key or encrypted keystore through a deliberate offline process. Confirm which method was used rather than assuming the main phrase covers it.

Moving all assets from an old imported account to a correctly backed-up destination may simplify the system, but that is an onchain operation with fees and risk, not a mandatory recovery step.

17. Hardware accounts must be reconnected

Install the supported hardware-wallet integration, unlock the device locally, open the appropriate app if required and select the same account. Compare the full address before trusting the restored label.

If the expected address is absent, verify the device’s seed, passphrase wallet and derivation path. An optional passphrase produces a distinct wallet; a nearly identical phrase does not produce the old accounts.

18. Derivation paths can explain missing hardware accounts

MetaMask documentation describes specific path options for supported hardware integrations, including Ledger choices and BIP-44 behavior. The same seed under another path can display different addresses.

Use the original device and documented path when possible. Do not change paths blindly while holding assets at risk.

19. Social login changes automatic restoration

MetaMask states that signing into a new instance with the same supported social account and MetaMask password can restore associated accounts, including synchronized imported wallets, while hardware accounts still require reconnection.

If avoiding a permanent association with a social account matters, understand the current import behavior before adding another wallet. Use a separate MetaMask instance when the desired trust boundary requires it.

20. Protect the social account as a recovery dependency

Review its recovery email, phone, passkeys or security keys, trusted devices and sessions. A strong MetaMask password cannot compensate for an easily recovered or already compromised social identity.

Document the dependency without recording authentication secrets together. Test legitimate recovery while access still works.

21. Back up wallet configuration separately

MetaMask Extension provides a wallet-data export under privacy settings. Official documentation says it can include account addresses and names, contacts, many settings and custom networks.

This file is a rebuilding reference. It should be protected because it maps wallet relationships, but it is not a signing-key backup and does not replace SRPs or imported private keys.

22. Do not confuse two kinds of JSON

A MetaMask wallet-data export documents configuration. An encrypted account keystore can contain key material for a particular account. File extension alone does not tell the user which one is present.

Label backups by function, creation date and originating application without putting secret passwords in the filename.

23. Custom networks may need rebuilding

Record the chain ID, RPC source, currency symbol and explorer through authoritative network documentation. A missing custom network changes what MetaMask displays; it does not erase assets on that chain.

Reject RPC details sent by unsolicited support accounts. A malicious endpoint can misrepresent data or create privacy exposure even though it cannot directly derive the wallet keys.

24. Custom tokens may need to be added again

A restored wallet may control the correct address while omitting a token from its interface. Verify the balance on the correct explorer, obtain the real contract from an authoritative source and add it to the display.

Never swap again merely because a portfolio screen shows zero. First verify the onchain address, network and token contract.

25. Contacts and labels are not authority

Names make addresses easier to recognize but do not change ownership or validate the recipient. Restore or recreate contacts carefully and verify each destination through an independent trusted channel.

Do not allow a convenient restored label to override an address-poisoning warning or a mismatch on the final confirmation screen.

26. Connected sites and approvals are different

Reinstalling MetaMask may remove local connected-site records. It does not automatically revoke token allowances or permissions recorded onchain. Those remain associated with the address until changed through the relevant contract process.

After migration, review connected sites, allowances and active dapp positions separately.

27. Pending transactions require network-specific review

A transaction submitted before migration can remain pending because the nonce belongs to the blockchain account, not the old interface. Search the address and transaction hash on the correct explorer.

Do not submit a conflicting transfer until the nonce and replacement behavior are understood. A restored wallet can still sign for the same account.

28. Prepare a migration package

  • Public address inventory with key-source classification.
  • Offline backups for every SRP.
  • Independent backups for imported accounts.
  • Hardware-wallet recovery and passphrase plan.
  • Protected configuration export and custom-network references.
  • List of important dapps, approvals and pending activity.
  • Official installation links saved independently.

29. Test without deleting the working installation

Use a clean separate browser profile or spare trusted device. Install MetaMask through the official route, restore the intended source and compare public addresses. Do not transact merely to prove that an address appears.

Keep the old installation intact until every relevant account has been identified and independently recovered.

30. Validate control, not only visibility

An address can be watched without its private key. Confirm that MetaMask identifies the account as controllable and that the corresponding signer is available. For hardware wallets, verify the address on the trusted device screen where supported.

A harmless message-signing or minimal-value test may be appropriate, but never sign an opaque request from an unknown site as a recovery test.

31. Compare balances with explorers

Check each address on every relevant chain. The same EVM-formatted address can have different balances and activity across networks. Record non-EVM accounts separately when supported by the current MetaMask version.

Explorer verification distinguishes a display/configuration problem from an incorrect address.

32. Rebuild names only after address matching

Assign the old labels after the full address matches the inventory. This prevents a familiar name from being attached accidentally to a different derived account.

Use labels describing purpose rather than exposing balances or identity if screenshots or screen sharing might reveal them.

33. Remove the old installation carefully

Only after validation should the old browser profile, phone or computer be retired. Sign out of device accounts, remove storage according to the platform’s process and consider whether the device will be sold, repaired or reassigned.

Uninstalling MetaMask is not a blockchain revocation. Anyone who already obtained an SRP or private key remains capable of controlling its accounts.

34. Troubleshoot a zero balance

Confirm the full address, network and token contract. Check whether the asset was bridged, wrapped or deposited into a dapp. Add the correct network and token display only after verifying official parameters.

If the explorer also shows zero, compare the old transaction history and determine whether a different address or network held the asset.

35. Troubleshoot a missing imported account

Restoring the primary SRP will not recreate an unrelated private-key account. Locate its independent backup or the original wallet from which it came. If the old MetaMask instance still opens, identify the account type before making changes.

Never send a vault file or screenshot of a private key to someone offering remote extraction.

36. Troubleshoot a missing hardware account

Reconnect the device rather than entering its words. Confirm firmware/application compatibility, wallet passphrase state and derivation path. Compare candidate addresses with the inventory and historical explorer activity.

If the hardware device was replaced, restore it through the manufacturer’s verified process before connecting it to MetaMask.

37. If the old installation still unlocks

Use that opportunity to complete the address map, identify imported accounts, verify SRP backups and export configuration data. Work offline or in a controlled environment when revealing secrets.

Do not delay until a browser update, disk failure or accidental uninstall removes the last accessible local vault.

38. If the SRP is lost

If MetaMask still unlocks, follow the official local reveal procedure and create a secure backup. If only the password remains but the installation data is gone, the password alone generally cannot reconstruct an SRP-based wallet.

Official vault-recovery methods apply only to specific local-data scenarios and platforms. Treat third-party recovery tools as high risk and never upload vault material to an unverified website.

39. If a secret may be compromised

Restoration confirms access; it does not make an exposed SRP safe again. On a clean environment, create a new independently backed-up wallet and plan asset migration, allowance review and dapp-position handling.

Do not import a compromised phrase into a hardware wallet and call it cold storage. The attacker can still derive the same keys.

40. Recovery-map checklist

  • Every public address has a documented key source.
  • Each SRP is backed up independently and offline.
  • Imported accounts have separate verified recovery material.
  • Hardware accounts are mapped to the correct device, passphrase state and path.
  • Social-login dependencies have strong account recovery.
  • Configuration exports are not mistaken for key backups.
  • Custom networks and tokens come from authoritative sources.
  • The new installation reproduces every important address.
  • Balances are confirmed across all relevant chains.
  • The old installation remains available until validation is complete.

Frequently asked questions

Will one MetaMask SRP restore every account I previously saw?

No. It restores accounts derived from that phrase. Other SRPs, imported private keys and hardware-wallet accounts have separate recovery requirements.

Why did only the first account return?

Automatic discovery can stop before later accounts. Add accounts under the same SRP in their original sequence and compare addresses.

Does the MetaMask password restore my wallet?

For an ordinary SRP setup, it primarily unlocks local encrypted data. The SRP is the portable recovery root.

Does exporting MetaMask data include my SRP?

The documented wallet-data export is a configuration reference, not a substitute for SRPs or private keys.

Should I enter Ledger recovery words into MetaMask?

No. Reconnect the hardware wallet. Typing its recovery phrase into a hot-wallet interface destroys the hardware isolation.

Why are tokens missing when the address is correct?

The network or token may need to be added to the display. Verify the balance and contract through the correct explorer first.

Related One Crypto Library guides

Key takeaway: recovery must be designed per address, not per application. An SRP, imported private key, social login and hardware signer are different control systems even when MetaMask displays them in one account list.

Official MetaMask backup and recovery resources

Visit MetaMask ↗Official website