If your NFT is in your address but the MetaMask UI doesn't show it (search terms: "nft not showing metamask", "nft not appearing metamask"), the problem is almost always one of visibility, network mismatch, metadata, or a transfer error. I've run into this several times — usually because I was viewing the wrong network or because contract metadata was slow to load. Short answer: verify ownership on a block explorer first, then confirm MetaMask is pointed at the correct network and account.
Before you spend an hour troubleshooting, run this checklist.
| Symptom | Fast fix |
|---|---|
| NFT not listed in UI | Switch to the correct network and refresh MetaMask/mobile app |
| Image missing but token exists | Check tokenURI (IPFS or HTTP); try a public IPFS gateway |
| Transfer pending | Find tx hash, speed up or wait for miner confirmation |
| Received but balance is 0 | Verify address — HD account index or wrong wallet |
Below I explain each common failure mode and what to do about it.
Why doesn't my NFT show? Often because MetaMask is on the wrong network. NFTs live on a blockchain; if your wallet is set to an L2 or testnet, the extension won't display assets from mainnet (and vice versa).
Fix: switch MetaMask to the correct network, or add the custom RPC if you use an EVM-compatible chain. After switching, refresh the UI. And double-check you copied the right receiving address (copy/paste errors happen).
(If you want step-by-step help with network switching, see network-switching-multi-chain.)
MetaMask is a software wallet for EVM-compatible accounts. NFTs on non-EVM blockchains (Solana, Flow, Tezos) won't appear in MetaMask. So if your NFT lives on Solana, you need a Solana-compatible wallet to view or interact with it.
The token itself may be present but the image is missing because metadata is hosted on IPFS or a slow server. The NFT contract points to a tokenURI, which returns a JSON that points to an image. If that host is down, the image won't load.
How to check: open the tokenURI in a browser or through an IPFS gateway. If the JSON or image is missing, the issue is with the metadata host — not MetaMask.
Some wallets display ERC-1155s differently (they can be semi-fungible). If a collectible uses a custom implementation, the wallet UI may not render it. Check ownership on the chain (transfer events) and use a dedicated NFT viewer or marketplace that knows how to read that contract.
A transfer can appear to succeed in the sender UI but remain pending or revert on-chain. Always copy the tx hash and check a block explorer. If it failed, you’ll see a revert reason or no transfer event.
Tip: if a tx is pending due to low gas, you can often replace it (same nonce, higher gas). MetaMask supports "speed up" in many cases.
Sometimes the NFT is in a different account derived from your seed phrase (different account index or hardware wallet path). If you restored a seed phrase and don't see the NFT, try creating extra derived accounts in MetaMask (Account → Create Account) or reconnecting your Ledger/hardware wallet with the recommended path.
If you use WalletConnect, remember that some dApps show or cache NFTs differently than MetaMask’s UI. Try a full refresh or view the token on-chain.
This is a common question: "how to transfer nft from coinbase wallet to metamask". Below is a clear step-by-step I use when moving collectibles between two non-custodial wallets.
If you prefer detailed visuals, see the internal guide: Transfer from Coinbase Wallet to MetaMask.
If none of the above works, search the transaction for "Transfer" events and follow the chain of custody. That usually tells you whether the token was burned, moved to another address, or simply never transferred.
Never sign approval requests blindly. A single click on a setApprovalForAll can let a marketplace or malicious contract move all your NFTs. What I've found is this: always review which contract you're approving and revoke untrusted approvals afterwards (see revoke-approvals).
If you're ever asked to sign a message with no clear reason (especially during a transfer troubleshooting flow), pause. Phishing screens can look identical to legitimate dApps.
For recovery: back up your seed phrase securely (write it on paper, store in a safe). If you lose your phone, follow the steps in lost-phone and restore to a new device using your seed phrase.
Who this wallet works well for:
Who should look elsewhere:
Q: Is it safe to keep NFTs in a hot wallet?
A: Hot wallets are convenient for daily use but carry more risk than hardware storage. If you hold high-value NFTs, consider a hardware wallet or multi-sig for long-term custody. Also, revoke unnecessary approvals from marketplaces.
Q: How do I revoke token approvals for NFTs?
A: Use a revoke tool or inspect allowed operators for your NFT contract (see revoke-approvals). Revoke any setApprovalForAll or unlimited approvals you don't need.
Q: What happens if I lose my phone?
A: If you have your seed phrase, you can restore access on a new device. Without the seed phrase, a hot wallet cannot be recovered. See lost-phone and seed-phrase-backup-and-recovery for secure recovery tips.
If an NFT is missing from MetaMask, start by confirming ownership on-chain, then check network, metadata, and account derivation. Simple fixes (switch network, refresh, check tokenURI) solve most cases. But if a transfer failed or funds were sent to the wrong address, the block explorer record is your single source of truth.
If you still need guided help, try the step-by-step transfer walkthroughs (for example, transfer-from-coinbase-wallet-to-metamask) or the NFT overview page (nft-overview). And if you're worried about approvals or phishing, read revoke-approvals and phishing-alerts.
If you'd like, I can walk through a specific tx hash or error message — paste the hash and I'll explain what the chain shows. But remember: never share your seed phrase or private keys.