Import & Restore MetaMask Wallet (Seed Phrase, Private Key, JSON)

Quick summary: this guide explains how to import a MetaMask software wallet using a seed phrase (12 words), a private key, or a keystore JSON file. I walk through the extension and mobile flows, share hands-on tips I use every day, and point out common traps (like imported accounts not being recovered by a seed phrase).

I’ve restored wallets on both desktop and mobile many times. Some restorations were routine. Some taught me hard lessons about backups. You’ll get step-by-step checks and practical warnings below.

Quick overview

MetaMask supports three practical import paths:

Seed phrase (the common 12-word recovery phrase)
Single private key import (one account)
Keystore (UTC/JSON) file when available (password required)

Which should you use? Use the seed phrase when you want to recover all primary HD accounts created from that phrase. Use a private key if you only have a single account keypair. Use a keystore file if that’s what you exported from another wallet.

If you still need to install MetaMask before restoring, see the extension and mobile install guides: /install-metamask-extension and /install-metamask-mobile-app.

What you can import into MetaMask

Method	Recovers multiple accounts?	Scope	Notes
Seed phrase (12 words)	Yes	Full HD account set derived from that phrase	Preferred when available. Recreates deterministic accounts and associated public addresses.
Private key	No (single account)	One imported account	Imported accounts are stored separately and may not be recovered by restoring just the seed phrase later.
Keystore JSON	No (single account)	One imported account (file + password)	Use only when you have a trusted UTC/JSON file and the password.

(Placeholder image: screenshot of import options)

Step-by-step: Restore MetaMask from seed phrase (12 words)

This covers both extension and mobile. The words must be typed in the correct order and separated by spaces.

Open MetaMask extension or app. If you don’t have it yet, go to /install-metamask-extension or /install-metamask-mobile-app.
Choose “Import using seed phrase” or “Import wallet.”
Enter your 12 words in order. Don’t add punctuation. Use lowercase unless you know otherwise.
Create a strong local password for the app/extension and confirm it.
Complete any onboarding prompts.

What I do after a restore: I immediately check the main account address against a known address (from a previous export or block explorer). Short sentence. It verifies the import worked.

And yes, you will often need to re-add custom networks and tokens after a restore (those are local settings). See /add-custom-network and /tokens-portfolio for help.

Step-by-step: Import MetaMask using a private key

Open MetaMask and click the account icon (top-right on desktop) → "Import Account".
Choose "Private Key" and paste the private key string (do not include extra spaces).
Confirm. The account will appear as an "Imported Account".

A couple of important caveats: imported accounts are stored locally and will not be recovered by restoring a different seed phrase later (unless the private key belongs to a derived account of that seed). In my experience that confusion causes lost access more than anything else.

For a focused walkthrough on private key imports see /import-private-key.

Step-by-step: Import a keystore (JSON) file

Some wallets export a UTC/JSON keystore file you can import.

Choose "Import Account" → "JSON File" (or similar) in MetaMask.
Upload the JSON file.
Enter the password that encrypted the file.
Confirm and check the account address.

Only upload JSON files in the official extension or app. Do not paste JSON into random websites. But remember: if you lose the JSON or forget its password, recovery is difficult.

After you restore: quick checklist

Re-add custom networks (Polygon, BSC, L2s) — linking: /add-custom-network.
Re-add tokens you held that don’t auto-show. (Search by contract address.)
Check pending transactions and nonces. If a stuck txn exists, consider canceling or increasing gas.
Reconnect dApps you trust (via WalletConnect or injected provider) and re-check approvals. See /connect-dapps and /token-approvals-revoke.
If you use Ledger or Trezor as a second factor, reconnect them (they are hardware integrations, see /connect-ledger).

A practical tip: after restore I send a very small test transaction to confirm outgoing flows work. Small losses are better than big mistakes.

Security considerations & backup options

Seed phrase safety matters above all. Treat your seed phrase like the keys to a safe. Short sentence.

Paper backups are simple and resilient. Store them in separate physical locations.
Cloud backups (e.g., screenshots, note apps) are convenient but increase exposure to hacks. Use with care. See /backup-cloud-vs-paper.
Consider a hardware wallet for significant balances (hardware helps reduce hot wallet risk). See /hardware-wallets-overview.

I once lost access temporarily because I restored on a new device and later realized an imported private key wasn’t backed up. Learn from that: export and save any imported private keys if you intend to rely on them.

And a final security point: never paste your seed phrase into websites. If a dApp asks for your seed phrase, that’s a red flag.

Troubleshooting common issues

Seed phrase rejected? Check word order, remove extra spaces, and confirm it’s actually 12 words (some wallets use 24 words). If the phrase is 24 words, direct import may fail; export private keys from the original wallet instead.
Imported address doesn’t show tokens? Add the token by contract address or re-add the correct network.
Keystore JSON password not accepted? Try the original wallet app to verify the password (do not upload the JSON to unknown services).
Lost phone? See recovery options at /lost-phone-recovery and restore from your seed phrase on another device.

If a transaction is stuck, check gas settings (EIP-1559 priority fee) and nonce values. For more on gas see /gas-fees-eip1559.

Who this is best for — and who should look elsewhere

Who this is best for:

Daily DeFi users who need a flexible software wallet across browsers and mobile. I use this pattern daily for quick swaps and dApp connections.
People who understand seed phrase safety and can maintain backups.

Who should look elsewhere:

Users who want a fully custodial or exchange-managed experience.
People holding large sums who prefer hardware-only signing for every transaction.

But remember: the hot wallet trade-off is convenience vs security. If you’re swapping daily, a software wallet is practical. If you store large holdings long-term, pair it with a hardware wallet.

FAQ

Q: Is it safe to keep crypto in a hot wallet? A: Hot wallets are convenient for day-to-day DeFi. They are not as secure as hardware wallets for long-term storage. Use small operational balances in hot wallets and keep larger amounts offline.

Q: How do I revoke token approvals? A: Revoking approvals can be done with on-chain revoke tools or within some wallet UIs. See /token-approvals-revoke for step-by-step guidance.

Q: What happens if I lose my phone? A: If you have your seed phrase, you can restore on another device. Without the seed phrase or backed-up private keys, recovery is unlikely. See /lost-phone-recovery.

Conclusion & next steps

Restoring a MetaMask software wallet by seed phrase, private key, or keystore is straightforward if you follow the right steps and guard your backups. Recreate the wallet, re-add networks and tokens, and do a small test transaction before moving large amounts.

If you need a guided install or a restore on a specific platform, start here: /install-metamask-extension or /install-metamask-mobile-app. For backup strategy, see /backup-recovery-seed and read up on /security-best-practices.

Want a quick walkthrough for importing a single private key? Try /import-private-key next.

Thanks for reading. Safe restores—and remember to double-check addresses before sending funds.