Table of contents
Quick summary
This guide explains how to import Coinbase Wallet into MetaMask and practical alternatives for moving assets. I show three approaches: importing the recovery (seed) phrase, importing a single private key, and simply sending tokens from one wallet address to another. You’ll get step-by-step instructions, a small comparison table, and a clear security checklist so you can replicate the steps safely.
I’ve done these flows on both desktop (MetaMask extension on Chrome) and on mobile (MetaMask mobile app), and I’ll explain exactly what I tested so you can reproduce the checks yourself. And yes—there are trade-offs between convenience and exposure of private keys.
Which scenarios this covers
- You want to have the same Coinbase Wallet accounts available inside your MetaMask extension or mobile app.
- You prefer to keep Coinbase Wallet as a separate recovery but move selected tokens to an address managed in MetaMask.
- You need to confirm that token balances and NFTs transferred correctly after import or transfer.
If your assets live on non-EVM chains (Solana, for example), stop and check compatibility first (see solana-and-metamask-compatibility). Sending a token to the wrong chain can mean permanent loss.
Options: import seed phrase vs import private key vs send crypto
| Method |
What it restores |
Pros |
Cons |
When to use |
| Import seed phrase |
Full HD wallet (all derived accounts) |
Restores entire wallet in one step |
You expose the full recovery phrase to the importing device |
When you want identical accounts in MetaMask |
| Import private key |
Single account/address |
Only exposes one private key; quick for one address |
Only that address is available; you must export private key from source wallet |
When you only need one address in MetaMask |
| Send tokens (transfer) |
Only assets you move |
No key exposure; keeps wallets separate |
Pay gas per transfer; manual for each token |
When you want to keep original wallet as backup |
(Placeholder image: screenshot-import-menu.png)
Step-by-step: how to import Coinbase Wallet to MetaMask (seed phrase)
This is the straightforward route if your aim is to have MetaMask manage the very same accounts used by Coinbase Wallet.
- Open MetaMask on the device you want to use (extension or mobile). If you already have a MetaMask wallet you use, consider whether you want to merge accounts—importing a recovery phrase will replace the current MetaMask vault unless you use a different browser profile or a second browser. Read the on-screen warnings.
- Choose "Import using seed phrase" (or during onboarding select "Import wallet").
- Enter the Coinbase Wallet recovery phrase exactly (12 or 24 words, space-separated). Type carefully. Create a strong local password for MetaMask when prompted.
- After import, check the public address that appears in MetaMask by clicking the account name and comparing it to the address shown in Coinbase Wallet (copy/paste or scan QR). They should match.
- If you used multiple accounts in Coinbase Wallet and don’t see them in MetaMask, use MetaMask’s "Create account" button repeatedly—it advances the derivation index and will reveal the next addresses (this is how HD wallets derive multiple addresses).
- Add any custom tokens that don’t automatically show up (use add-custom-token-contract or add-tokens-mobile).
Important: only import a seed phrase on a machine you trust. But don’t rush—test with a tiny transfer first if you’re uncertain.
Step-by-step: how to move crypto from Coinbase Wallet to MetaMask (send tokens)
If you prefer to avoid giving MetaMask the full recovery phrase, this is the safer route.
- Open MetaMask and copy the receiving address (click account name → "Copy to clipboard").
- Open Coinbase Wallet (mobile) and choose the token to send. Paste the MetaMask address or scan its QR code.
- Set a low test amount (for example a small amount of ETH or token) and send it first. Wait for confirmation on-chain and verify the balance in MetaMask.
- Once you confirm the test transfer arrived, send the remainder. For ERC-20 tokens, make sure you have enough ETH in Coinbase Wallet to pay gas.
- For NFTs, some wallets require special steps to transfer metadata; check view-and-manage-nfts for tips.
This flow keeps both wallets separate and avoids exporting private keys.
How I tested this (replicable methodology)
I performed both import and send flows on a clean browser profile (Chrome) and on MetaMask mobile. Testing steps you can replicate:
- Create a throwaway wallet in Coinbase Wallet mobile.
- Send a small amount of ETH and an ERC-20 token to that wallet.
- On a clean browser profile, install MetaMask extension (or open MetaMask mobile), choose import using seed phrase, and enter the recovery phrase.
- Verify the address matches the Coinbase Wallet address in both UI and a block explorer (copy address → check on explorer).
- For transfer testing, copy the MetaMask address and send a 0.001 ETH test from Coinbase Wallet mobile to MetaMask. Wait for 1 confirmation and verify balance.
I repeated these steps on both desktop and mobile to check UI differences. And I intentionally tested token transfers after import to confirm token visibility and the need to add token contracts manually.
Security checklist and risks
- Never share your seed phrase. Exporting a seed phrase to copy/paste on an internet-connected machine increases exposure.
- If you export a private key for a single address, treat clipboard data as sensitive (clear clipboard after use).
- Revoke old token approvals after moving large balances (see token-approvals-and-revoke).
- For cross-chain assets (Bridges, Solana, etc.), confirm compatibility before sending (see cross-chain-bridges-and-risks).
- Consider using a hardware wallet for long-term holdings. But remember, hardware wallets require integration steps (see integrate-hardware-ledger-trezor).
Troubleshooting common issues
- Address mismatch after import: create additional accounts in MetaMask (MetaMask advances the derivation path with each account). If still different, double-check the recovery phrase source and spelling.
- Missing tokens: add custom token contract manually (add-custom-token-contract).
- I don’t see NFTs: some NFT metadata loads slowly; try the "Add NFT" flow or check the collection on a block explorer.
- Accidentally imported to the wrong MetaMask: use a clean browser profile or reinstall and import the correct phrase (see remove-uninstall and backup-and-recovery-seed-phrase).
If you hit an error you can’t resolve, consult the troubleshooting hub (troubleshooting) or the page on recover-lost-wallets.
Who this workflow is for (and who should look elsewhere)
Best fit: active DeFi users who want identical addresses in a desktop browser for easier dApp access, or users consolidating mobile-only wallets into a single MetaMask instance.
Not for: users who want to keep two completely separate seed phrases for redundancy, or people uncomfortable typing recovery phrases into any device (you should avoid seed imports in that case and instead send assets between addresses).
Related guides and next steps
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient for daily DeFi activity but come with more exposure than cold storage. Use small balances for daily swaps and consider hardware wallets for large holdings.
Q: How do I revoke token approvals after moving balances?
A: Use a contract-approval management tool or the revoke feature in your wallet. See token-approvals-and-revoke for a step-by-step.
Q: What happens if I lose my phone?
A: If you have your seed phrase backed up securely, you can restore the same accounts in MetaMask or any compatible non-custodial wallet. See lost-phone-reset-recovery and backup-and-recovery-seed-phrase.
Conclusion and CTA
Importing Coinbase Wallet into MetaMask can be quick, but choose the method that matches your threat model: seed phrase import for full parity, private-key import for single addresses, or transfers to avoid exposing keys. I walked through reproducible tests and practical checks so you can repeat the steps safely. Want a follow-up on adding Layer 2 networks or managing approvals after the move? Check these guides next: add-networks-custom-rpc and token-approvals-and-revoke.