Send & Receive Crypto with MetaMask

Quick summary

MetaMask is a non-custodial software wallet available as a browser extension and mobile app. Sending and receiving is simple most of the time: copy your address, choose the correct network on the sending platform, and confirm. But mistakes (wrong network, wrong token standard, or phishing dApps) regularly cost users money. I’ve made a costly approval mistake; learned fast. This guide gives practical, step-by-step directions for common scenarios like sending crypto from Coinbase to MetaMask, sending from Crypto.com to MetaMask, and sending BNB to MetaMask.

Before you send: checklist

Do these four things every time. Short and strict.

Confirm the network. (Is the token on Ethereum, BSC, Polygon, Avalanche, or another EVM-compatible chain?).
Copy the address from MetaMask — not from a message or browser autofill.
On the exchange or wallet, pick the same network (ERC-20 vs BEP-20 vs Polygon). Wrong choice can hide funds.
Keep enough native chain gas (ETH, BNB, MATIC, AVAX) in the receiving MetaMask account to pay future transactions.

And yes, double-check the address twice. Copy/paste mistakes happen.

Useful reads: add-bsc, add-polygon, add-avalanche, gas-fees-and-eip-1559.

Step-by-step: sending crypto from Coinbase to MetaMask

This is one of the most-searched flows (search terms: sending crypto from coinbase to metamask, transfering from coinbase to metamask). Follow these steps.

Open MetaMask (extension or mobile). Select the account you want to receive funds into. Copy the public address (starts with 0x).
On Coinbase, start a withdrawal. In the destination address field paste the MetaMask address.
Select the correct network. If you’re sending ETH choose "Ethereum" (ERC-20). If the exchange gives options like "BEP-20" or "Polygon", only use those if you added the corresponding network to MetaMask.
Confirm fees and expected arrival time, then send. Keep the tx hash.
After the transaction confirms on the sending platform, paste the tx hash into a block explorer (Etherscan, BscScan, SnowTrace depending on the chain) to track progress.

Common mistake: picking a network the wallet doesn’t have configured. If you transfering from coinbase to metamask and choose a chain that MetaMask doesn’t show yet, tokens might be "missing" until you add that network.

Other common flows: Crypto.com, Trust Wallet, BNB, AVAX, MATIC

Short, actionable notes for common search patterns.

Sending from Crypto.com to MetaMask (keyword: sending from crypto.com to metamask): same process as above. Crypto.com offers network options — pick the one that matches the token standard in MetaMask. See move-from-crypto-com.
Sending ETH from Crypto.com to MetaMask (keyword: sending eth from crypto.com to metamask): choose Ethereum (ERC-20). If the app prompts for a gas fee, expect it in ETH.
Sending ETH from Trust Wallet to MetaMask (keyword: sending eth from trust wallet to metamask): copy your MetaMask address on the receiving device. Trust Wallet can scan a QR code or paste the address.
Sending AVAX from Crypto.com to MetaMask (keyword: sending avax from crypto.com to metamask): AVAX has multiple chains; ensure you’re using the C-Chain (EVM) route, and add Avalanche to MetaMask first (add-avalanche).
Sending MATIC from Crypto.com to MetaMask (keyword: sending matic from crypto.com to metamask): choose the Polygon network (make sure Polygon is added to MetaMask — see add-polygon).
Sending BNB to MetaMask (keyword: sending bnb to metamask): BNB can exist on different chains (BEP-2 vs BEP-20). MetaMask supports BSC (BEP-20) when you add BSC network. If you send BEP-2 BNB (Binance Chain) to MetaMask you’ll likely lose access.

But remember: if an exchange doesn’t offer the network you need, don’t try creative workarounds. Use a bridge or swap service only after confirming contract-level compatibility.

Helpful: migrate-from-trust-or-coinbase.

Receiving tokens and adding custom tokens

To receive: public address only. Use the account address shown at the top of MetaMask.
If tokens don’t appear: add the token manually via token-management. You'll need the contract address, token symbol, and decimals (find these on the token project's website or a block explorer).
Hiding spam tokens: use the hide function in the token list; keep watching your balances for unknown approvals (see revoke-approvals).

Image:

Mobile vs extension: practical differences

Table: feature vs form factor

Feature	Browser extension	Mobile app	With hardware (Ledger/Trezor)
Copy/paste address	Easy	Easy (QR supported)	Works (requires device)
QR code receive	No	Yes	Depends
DApp browser	No (uses injected provider)	Yes (built-in dApp browser)	No
On-device tx approval	No	Yes (biometric lock)	Yes (hardware approval required)
Best for frequent swaps	Good	Best for on-the-go	Best for security

If you swap often on mobile, the dApp browser and QR flow are convenient. If you use MetaMask in a desktop browser for DeFi, the extension injects a provider into sites. Want hardware? See connect-ledger and connect-trezor.

Security and recovery: what can go wrong

MetaMask is non-custodial: you alone control private keys via a seed phrase. That’s both the power and the danger. If you lose your seed phrase or private key you lose funds. I’ve lost hours and a small balance when I once used a temporary cloud backup (don’t do that unless you understand the risk).

Back up your seed phrase and store it offline. Read backup-and-recovery-options.
Revoke unnecessary token approvals; see revoke-approvals.
Watch for phishing sites that copy DeFi UIs. MetaMask flags some malicious sites, but attackers adapt fast.

And never enter your seed phrase into a website or a form. Ever.

Quick troubleshooting checklist

If a transfer doesn’t show: don’t panic. Run these checks.

Confirm the transaction hash on the correct explorer.
Switch MetaMask to the correct network and refresh balances.
Add the token manually if it’s a custom ERC-20/BEP-20/Polygon token.
If the exchange shows completed and explorer shows success but MetaMask balance is zero, you likely used the wrong network — contact the sending platform support.

For step-by-step debugging see stuck-pending-transactions and transaction-troubleshooting.

FAQ

Q: Is it safe to keep crypto in a hot wallet? A: Hot wallets are convenient for DeFi interactions and daily use. They are less secure than hardware wallets. If you hold large long-term balances, consider splitting funds to a hardware wallet. (Yes, I use both.)

Q: How do I revoke token approvals? A: MetaMask shows connected sites; to revoke ERC-20 allowances you may need a dedicated revoke tool or the guide at revoke-approvals.

Q: What happens if I lose my phone? A: Restore using the seed phrase on a new device or desktop extension. If someone else has the seed phrase, your funds can be drained. See backup-and-recovery-options for safe practices.

Who MetaMask is for — and who should look elsewhere

Best for:

Active DeFi users who interact with DEXs, lending protocols, and L2s.
People who want a simple extension and mobile pairing.

Look elsewhere if:

You require native Solana support (MetaMask is EVM-focused). See solana-tron-near for alternatives.
You need built-in multisig as your primary wallet (consider multisig solutions; see multisig-and-gnosis).

Conclusion & next steps

Sending crypto from exchanges and other wallets to MetaMask is routine — until it's not. The difference between a smooth transfer and a lost deposit is usually the network choice and a careful address check. If your next move is transferring from Coinbase to MetaMask or sending from Crypto.com to MetaMask, follow the checklist here, add the proper network first (add-polygon, add-bsc, add-avalanche), and keep the seed phrase offline. Need a step-by-step for setup before you send? See setup-desktop and setup-mobile.

Ready to move a small test amount first? That’s the cleanest way to avoid a costly mistake. And remember — pause before you approve any contract or transfer.

More MetaMask how‑tos and troubleshooting