How to restore MetaMask wallet on a new device

Recovery Phrase Verification

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

2. Enter the 12-word recovery phrase exactly as written—case-sensitive, space-separated, and in correct order.

3. Confirm the phrase by re-entering it manually in the verification field; copy-paste is disabled for security reasons.

4. Set a new password for the local wallet instance; this does not alter the blockchain identity or private key derivation.

5. Wait for the wallet to synchronize transaction history and token balances via the configured network RPC endpoint.

Network Configuration Consistency

1. Ensure the same Ethereum-compatible networks used on the original device are added to the new MetaMask instance.

2. Manually input custom RPC parameters if previously configured—network name, RPC URL, chain ID, currency symbol, and block explorer URL.

3. Verify chain ID alignment: Ethereum Mainnet uses 1, Polygon uses 137, and MapleChain uses 2024 as confirmed by official documentation.

4. Disable Privacy Mode in Settings → Advanced to allow proper dApp interaction and metadata fetching from third-party explorers.

5. Confirm “Allow custom chain” is enabled under Experimental Features to prevent “Invalid ChainID” errors during cross-chain asset binding.

Browser Extension Data Migration

1. Locate the extension’s Local Extension Settings directory using OS-specific paths: Windows at C:\Users\USER_NAME\AppData\Local\Google\Chrome\User Data\Default\Local Extension Settings\nkbihfbeogaeaoehlefnkodbefgpgknn or Mac at ~/Library/Application Support/Google/Chrome/Default/Local Extension Settings/nkbihfbeogaeaoehlefnkodbefgpgknn.

2. Identify the correct Profile folder if multiple Chrome profiles exist—paths may contain Profile 1, Profile 2, or Default depending on login context.

3. Copy the entire extension data folder from the old device’s local storage and overwrite the corresponding folder on the new device.

4. Restart Chrome after replacement; do not reinstall the extension unless the ID mismatch triggers an “invalid extension” warning.

5. Check for persistent account labels and transaction history—these persist only if IndexedDB and Local Storage directories were fully migrated.

Transaction Nonce Synchronization

1. Access MetaMask Advanced Settings and trigger “Reset Account” to reset the internal transaction counter to zero.

2. Clear browser site data specifically for metamask.io and associated dApps using Developer Tools → Application → Clear site data.

3. Reconnect wallet to all previously authorized dApps to refresh session tokens and permissions.

4. Monitor pending transactions in the activity tab—if stuck, manually adjust gas fee or replace-by-fee (RBF) where supported.

5. Confirm balance visibility across all ERC-20 and ERC-721 tokens by verifying contract addresses match those stored in the original wallet’s token list.

Antivirus Interference Mitigation

1. Before initiating wallet import, check antivirus quarantine logs for isolated MetaMask-related JavaScript files.

2. Restore any quarantined files and add MetaMask’s extension ID to the antivirus trust list to prevent future isolation.

3. Avoid uninstalling the extension—even when nonfunctional—as local keystore fragments may still reside in encrypted storage.

4. If recovery phrase import fails unexpectedly, inspect Chrome’s extension error console for “Keystore decryption failed” or “Invalid mnemonic” messages.

5. Use offline tools like Ian Coleman’s BIP39 tool only in air-gapped environments to validate phrase integrity without exposing seed to network.

Frequently Asked Questions

Q1: Can I restore MetaMask using only my public address?No. The public address alone cannot regenerate private keys or access funds. Restoration requires the full 12-word recovery phrase or encrypted private key backup.

Q2: What happens if I enter one word incorrectly in the recovery phrase?MetaMask will reject the phrase outright. Even a single misspelled or out-of-order word results in an invalid checksum and prevents wallet initialization.

Q3: Does restoring MetaMask on a new device affect the original installation?No. The original MetaMask instance remains fully functional and independent. Both devices share identical cryptographic identity but operate separately.

Q4: Why does my restored wallet show zero balance after successful import?This typically indicates incorrect network selection or missing custom RPC configuration. Switch to the correct chain and verify token contracts are manually added or auto-detected.