A user creates a MetaMask wallet on their desktop browser, secures the Secret Recovery Phrase, and transfers assets to the first account. Later, they install MetaMask on their phone and import the same Secret Recovery Phrase. They expect to see the same wallet with the same funds. Instead, they see a new, empty account. This is not a loss or a security failure. It is the intended behavior of hierarchical deterministic (HD) wallet derivation. The Secret Recovery Phrase is the seed, but the actual account address depends on the derivation path—a mathematical sequence that transforms that seed into a specific account.

Understanding why this happens requires clarity about what a Secret Recovery Phrase actually controls and how MetaMask uses it. The phrase is a compact representation of cryptographic entropy that can generate an unlimited number of accounts and addresses, but it does not automatically generate all of them at once. MetaMask follows a specific standard for deriving accounts from the seed. When you import that seed on a new device, MetaMask starts at the beginning of its derivation sequence unless you tell it otherwise. The first device may have already created accounts further along the path, but the new device has no way to know that without additional instructions.

The distinction between the seed and the account

A Secret Recovery Phrase is a 12- or 24-word mnemonic code that represents entropy—random data. This entropy, when processed through a cryptographic function, becomes a master private key. From that master key, derivation functions generate child keys, and from those, individual account addresses. The phrase itself is not the wallet; it is the key to a vault containing infinite potential wallets. The actual wallet you use is determined by which child key is selected and activated.

MetaMask uses BIP44 derivation, a standard that specifies a deterministic path for generating accounts. The path includes parameters for the coin type (Ethereum, for instance), the account index (usually starting at 0), and the address index within that account. When you first set up MetaMask on a device, it derives the account at path m/44’/60’/0’/0/0 and creates the first account. If you then create additional accounts in MetaMask, the software increments the account index: m/44’/60’/1’/0/0 for the second account, m/44’/60’/2’/0/0 for the third, and so on.

The critical point is that each device maintains its own account index counter. When you import a Secret Recovery Phrase on a new device, MetaMask initializes that counter at zero and derives the account at the first position in the path. It has no record that another device has already created accounts at positions 1, 2, or 10. Unless the new device reads that information from a server (which MetaMask does not do, as it maintains non-custodial, local-only account tracking), it cannot know which accounts already exist.

This design preserves security and self-custody. MetaMask does not upload your account list to its servers, and it does not sync accounts across devices through a central authority. That independence is valuable because it means no third party controls your recovery process. It also means recovery is your responsibility. If you move to a new device and import your Secret Recovery Phrase, you must manually navigate to the correct account or recreate the accounts you had before.

Why the same seed produces different accounts on different devices

Consider a concrete scenario. On your laptop, you create a MetaMask wallet with a fresh Secret Recovery Phrase. MetaMask automatically creates account 0. You receive some Ethereum and approve a token swap. You then create account 1, and account 2. You now have three active accounts on your laptop, with funds and transaction history in account 0.

You then install MetaMask on your phone and import the same Secret Recovery Phrase. The software reads the phrase, reconstructs the master private key from the entropy, and begins deriving accounts. The phone’s MetaMask instance has no knowledge of what accounts the laptop created. It starts fresh, derives the account at the first derivation path (m/44’/60’/0’/0/0), and presents that as “Account 1” on the phone. This address happens to be mathematically derived from the same master key as your laptop’s account 0, so the private key is identical. The address is identical. But the phone’s MetaMask is not automatically connected to the laptop’s transaction history or account label.

If you send funds to your laptop’s account 1 (derived at m/44’/60’/1’/0/0) and then open MetaMask on your phone, those funds will not appear in the phone’s “Account 1” because the phone is displaying the account at m/44’/60’/0’/0/0. The phone would need to advance its account counter to index 1 to display the correct account. MetaMask provides a mechanism to do this: you can manually add accounts on the phone until you reach the account number that holds your funds. This is not automatic because MetaMask cannot predict how many accounts you had on other devices.

Blockchain networks and custom derivation paths complicate recovery

The scenario becomes more complex when multiple blockchain networks enter the picture. MetaMask is now a multichain wallet, supporting not only Ethereum but also Polygon, Arbitrum, Optimism, and other EVM-compatible networks. The Secret Recovery Phrase is the same across all networks, but the account addresses are different for each network.

When you import your Secret Recovery Phrase on a new device, the default behavior is to display account 0 on the currently selected network. If you had been using account 1 on Ethereum and account 0 on Polygon on your original device, the new device shows account 0 on both networks by default. The funds on your original device’s Ethereum account 1 and Polygon account 0 require you to navigate to the correct accounts manually on the new device, which may mean adding accounts, switching networks, and confirming addresses.

Some users also customize their derivation paths, either through advanced settings or by using hardware wallets that follow different standards. For example, some Ledger devices use a different path structure or allow users to choose between account and change address derivation. If you have been using a custom derivation path and then import your Secret Recovery Phrase into standard MetaMask, the recovered accounts will not match. Standard MetaMask always follows BIP44; if you used a non-standard path elsewhere, you may need to use the same hardware wallet or tools to recover those accounts.

The recovery process and account reconstruction

When importing a Secret Recovery Phrase into MetaMask on a new device, the wallet guides you through a setup process. After confirming the phrase word by word, MetaMask displays your first account and its balance. If you had multiple accounts on your original device, you must manually add them on the new device. This is done through the “Add Account” option in the account menu, which increments the account index and derives the next account in the BIP44 sequence.

The process is straightforward if you remember how many accounts you had and in what order. It becomes more difficult if you had many accounts with unclear purposes or if you used accounts on several different networks. A practical approach is to document your account setup before you switch devices: note the account number, the primary network, the balance or purpose, and any custom settings. This information is locally stored on your original device and not automatically transferred.

For users getting started with MetaMask wallet, the first device setup is straightforward because there is nothing to recover. You create one account, secure your Secret Recovery Phrase, and proceed. The complexity arises only when you need to recover or migrate. At that point, understanding derivation paths becomes essential. The Secret Recovery Phrase is sufficient to recover every account you ever created, but only if you follow the correct derivation sequence on the new device.

Why MetaMask does not sync accounts across devices automatically

A natural question is whether MetaMask could store a list of accounts on its servers and automatically retrieve them when you import on a new device. This would simplify recovery. It would also introduce a trust assumption that contradicts MetaMask’s non-custodial design. If MetaMask maintained a central record of which accounts each user owns, it would know which Ethereum addresses belong to you. This information could be valuable for surveillance, regulatory pressure, or a data breach.

MetaMask’s design instead prioritizes independence. The wallet software itself contains no account tracking beyond what is stored locally on your device. Recovery depends only on the Secret Recovery Phrase and the derivation standard, both of which are under your control. This means recovery is possible without MetaMask’s infrastructure, using any compatible HD wallet software that implements BIP44. It also means recovery is your responsibility, not a service MetaMask provides.

The trade-off is acknowledged. Users on multiple devices must manually manage their account recovery. This is more friction than a cloud-synced wallet, but it eliminates a layer of institutional dependency. If you lose access to your original device, you can still recover every account using only your Secret Recovery Phrase and any standard Ethereum wallet, not just MetaMask. The phrase itself is portable in a way that a proprietary account list never could be.

Common pitfalls and how to avoid them

The most frequent mistake is importing a Secret Recovery Phrase on a new device, seeing an empty or partially populated account list, and assuming something is wrong. The account exists; it is simply not displayed yet. Before concluding that funds are lost, check whether you are on the correct blockchain network. MetaMask displays balances on the active network only. If you had funds on Polygon but the new device is set to Ethereum, the balance will appear as zero.

A second mistake is forgetting which account held which funds. If you had account 0 with Ethereum and account 1 with a token, and you recover on a new device where account 0 displays the token balance, you have recovered the correct account (the addresses are identical); you have simply not yet navigated to the Ethereum-holding account. Open the account menu and add additional accounts until you reach the one you need.

A third mistake is using the same Secret Recovery Phrase on multiple devices simultaneously without tracking which accounts are on which device. If account 0 has 10 ETH on your phone and you create account 3 on your laptop, the balances are split. The addresses are different, and you may accidentally send funds to the wrong account. Documenting your account allocation across devices reduces this risk. A spreadsheet with device name, account number, network, and primary purpose is sufficient.

Planning for multi-device setups and hardware wallet integration

Users who plan to use MetaMask on multiple devices should establish a clear account strategy before creating the first account. Designating account 0 for primary holdings and higher-numbered accounts for specific purposes or networks reduces confusion. Writing down the account allocation and storing it in a physically secure location (not a file on a synced device) provides a reference when you recover on a new device.

Hardware wallet integration adds another layer. If you connect a hardware wallet such as a Ledger or Trezor to MetaMask, the device itself performs the key derivation and signing. MetaMask displays accounts from the hardware wallet without storing the private keys locally. The Secret Recovery Phrase for the hardware wallet is stored only on the hardware device. If you later import that phrase into MetaMask directly (on a phone, for example), the accounts will not match the hardware wallet’s accounts unless you are using the same derivation path settings. This is another reason to test recovery procedures: confirm that your phrase restores the accounts you expect before you rely on it in an emergency.

For the highest-value holdings, a hardware wallet with a separate backup of the Secret Recovery Phrase stored offline is appropriate. For smaller amounts or more frequent trading, a phone or desktop MetaMask installation is sufficient if the backup is secure. The right setup depends on your assets, your transaction frequency, and your backup discipline. The key principle is consistency: if you use a specific derivation path or account structure on one device, document it so you can replicate it elsewhere if needed.

The path forward and best practices

As blockchain adoption broadens and wallet software becomes more complex, the gap between novice and expert users will likely persist. Basic account derivation is an implementation detail that most users need not understand to send and receive assets. But anyone moving to a new device, setting up a second wallet, or managing multiple accounts benefits from understanding the distinction between the Secret Recovery Phrase and the accounts it derives.

Best practice is to treat the Secret Recovery Phrase as a master key and each device as a separate interface to that key. Before importing on a new device, plan your account structure and test recovery if possible. Keep a written record of account allocations, networks, and purposes. Store the Secret Recovery Phrase and the account record separately and securely. If a device is lost, you have all the information needed to recover without contacting MetaMask or relying on a backup file.

Finally, recognize that MetaMask’s non-custodial design is both a strength and a source of user responsibility. The same independence that prevents MetaMask from locking you out also prevents it from automatically finding your accounts across devices. This is a deliberate choice to keep you in control. Understanding why that choice was made helps you use MetaMask more effectively and avoid mistaking derivation mechanics for lost funds.