How to restore MetaMask on a new device?

Recovery Phrase Verification

1. Launch MetaMask on the new device and select “Import wallet” instead of “Create a new wallet”.

2. Enter the full 12-word recovery phrase exactly as written—case-insensitive but order-sensitive.

3. Input a strong new password for local encryption; this password does not affect fund access, only local unlocking.

4. Confirm phrase entry by selecting words in correct sequence if prompted by visual verification step.

5. Wait for balance synchronization; balances appear once the wallet connects to the correct network and scans relevant blocks.

Network Configuration Consistency

1. Ensure the same networks used on the prior device are manually enabled or added—MetaMask does not auto-sync custom RPCs.

2. Toggle “Show test networks” in Settings → Advanced to expose Sepolia, Holesky, or other test environments previously accessed.

3. For non-Ethereum chains like BSC or Avalanche, re-enter all five required parameters: network name, RPC URL, chain ID, currency symbol, and block explorer URL.

4. Validate each network’s status using its native block explorer by pasting the restored address and confirming transaction history visibility.

5. Disable any conflicting third-party RPC providers that may override default endpoints during initialization.

Local Data Migration (Advanced)

1. Locate the extension’s Local Extension Settings folder on the old device using OS-specific paths: Windows uses AppData\Local\Google\Chrome\User Data\Default\Local Extension Settings\nkbihfbeogaeaoehlefnkodbefgpgknn.

2. Copy the entire folder contents—not individual files—and transfer via encrypted USB or air-gapped medium.

3. On the new device, close Chrome completely, then paste the folder into the corresponding path under the target Chrome profile.

4. Restart Chrome and load the unpacked extension from chrome://extensions in Developer Mode.

5. Observe whether account labels, transaction nonce counters, and custom token lists reappear without re-importing.

Token and Contract Recognition

1. Manually add ERC-20 tokens using contract addresses—even if balances were visible before, they won’t auto-load without explicit registration.

2. Re-enable hidden tokens by navigating to Assets → Manage Assets → Search by contract address or symbol.

3. For NFTs, reconfigure the NFT detection service: Settings → NFTs → toggle “Enable NFT detection” and confirm wallet connection to OpenSea or LooksRare API endpoints.

4. Verify custom contract interactions by revisiting dApp interfaces and re-authorizing permissions via WalletConnect or injected provider prompts.

5. Check pending transaction queue in Activity tab—if stuck, manually adjust gas price or speed up/cancel using the transaction hash from Etherscan.

Frequently Asked Questions

Q1: Can I restore MetaMask without the 12-word phrase? No. The recovery phrase is the sole deterministic source for private key derivation. Browser backups, cloud sync, or exported JSON files without the phrase are insufficient for full restoration.

Q2: Why do my testnet balances not show after restoring? Testnet assets require explicit network activation and separate faucet claims. Restoring the phrase does not auto-claim Sepolia ETH or Mumbai MATIC—you must revisit each faucet and submit your restored address.

Q3: Does restoring overwrite existing accounts on the new device? Importing a recovery phrase creates a new wallet instance. It does not merge with or delete pre-existing accounts unless you explicitly choose to replace them during setup.

Q4: What happens if I enter one word incorrectly? MetaMask will display “Invalid mnemonic” and refuse to proceed. No keys are generated. The phrase must match the original byte encoding—typos, misspellings, or swapped words invalidate the entire set.