Table of contents
Overview and test methodology
This guide explains how to view, add, send, and verify NFTs and collectibles in MetaMask on both mobile and the Chrome extension. I describe the exact steps I used while testing so you can replicate them. I tested on a recent MetaMask mobile release on Android and the Chrome extension in Chrome on desktop, using a public Ethereum testnet (pick Goerli or Sepolia that your MetaMask shows). Tests covered: adding a collectible contract address, viewing metadata, sending via mobile UI, and sending via a contract write on desktop when extension UI did not list an NFT.
How to reproduce my tests (short version)
- Create a fresh software wallet in MetaMask or use a burner account (backup seed phrase first).
- Switch MetaMask to a public testnet like Goerli or Sepolia and grab test ETH from a faucet.
- Deploy or mint an ERC-721 test token via Remix or an existing test NFT minter, and note the contract address and token ID.
- Add the collectible in MetaMask mobile by contract address and token ID, then try sending it to another test account.
I avoided sending real-value NFTs while testing. That is a step you should always take too.
Quick checklist before you move an NFT
- Confirm the correct blockchain and network. MetaMask is EVM-focused, so NFTs minted on non-EVM chains like Solana will not appear (see solana-and-metamask-compatibility).
- Copy the collectible contract address and token ID from the marketplace or block explorer.
- Check metadata on a block explorer to confirm authenticity and token standard (ERC-721 vs ERC-1155).
- Have enough ETH for gas fees on the selected network.
- If you use a hardware wallet, connect it via integrate-hardware-ledger-trezor.
And one more thing: never connect MetaMask to a dApp you do not trust just to move an NFT.
How MetaMask handles NFTs: mobile vs Chrome extension
Short answer: the mobile app has a more polished NFTs/collectibles UX, while the Chrome extension can be more limited and sometimes requires using an NFT marketplace or direct contract interaction.
| Task |
MetaMask mobile |
MetaMask Chrome extension |
| View owned NFTs |
Yes, dedicated NFTs/collectibles tab |
Limited; may not auto-display all NFTs |
| Add collectible by contract + token ID |
Yes |
Sometimes; often requires marketplace or contract call |
| Send NFT from UI |
Yes |
Possible if NFT is listed; otherwise use contract write via block explorer |
| WalletConnect/dApp integration |
Supported |
N/A (extension injects web3) |
| Hardware wallet signing |
Supported via USB/Bluetooth + integration |
Supported via Ledger or Trezor connection |
In my experience the mobile app shows metadata faster (images, names). But the extension remains useful for marketplace workflows where the marketplace site handles transfers.
Add a collectible to MetaMask (step by step)
Mobile (typical)
- Open MetaMask mobile and switch to the correct network.
- Tap Assets, then the NFTs or Collectibles tab.
- Choose Add collectible or Add NFT, paste the collectible contract address and token ID, then confirm.
- Wait a minute for metadata to load (IPFS-hosted images take longer).
Chrome extension (when UI does not list the NFT)
- Option A: Visit the NFT marketplace page for that token and connect MetaMask. The marketplace often triggers the wallet to detect and let you transfer.
- Option B: Use a block explorer like Etherscan, connect MetaMask, open the contract page and use the Read methods to confirm ownership, then use Write -> transferFrom or safeTransferFrom to move the token while MetaMask signs the transaction.
For verifying contract addresses, see the section below and the add-custom-token-contract guide.
Send an NFT from MetaMask (step by step)
Mobile
- From the NFT in MetaMask, tap Send.
- Paste the recipient address and confirm. Adjust gas fee if needed.
- Approve the transaction when the MetaMask signature sheet appears.
Extension (if NFT not shown in UI)
- Connect to the NFT marketplace dApp and use its Transfer UI, or
- On a block explorer, call the contract write method transferFrom or safeTransferFrom to your recipient address, then confirm with MetaMask.
But be careful: if you use a contract write, confirm the method, token ID, and recipient address twice. I once mistyped an address and learned why this double-check matters.
Verify collectible contract address and metadata
- Always copy the contract address from a trusted source (marketplace listing or block explorer). Then verify the source on the explorer to ensure the contract is verified and matches the metadata schema.
- Check whether the token is ERC-721 or ERC-1155. ERC-1155 tokens may bundle multiple balances and behave differently when transferring.
- If metadata does not show in MetaMask, check the tokenURI on the explorer and open it directly (it may point to IPFS or a CDN). Some marketplaces cache images differently.
See the related guide on verify-contract-address for more.
Security, backups, and hardware wallets
- Keep your seed phrase offline. Treat your seed phrase and private keys like cash.
- If you handle high-value NFTs, use a hardware wallet via integrate-hardware-ledger-trezor for signing transfers.
- Revoke unnecessary approvals and token allowances regularly (see token-approvals-and-revoke).
- Cloud backups are tempting but add custodial risk. I prefer local encrypted backups or hardware security for collectibles I care about.
Troubleshooting common NFT problems
- NFT not showing: Verify network and token ID, then re-add collectible in mobile. IPFS-hosted images can take minutes to appear.
- Transfer failing: Check gas fees, nonce, and that you own the token using a block explorer. If using a hardware wallet, ensure the device is unlocked.
- Wrong network errors: Switch the network in MetaMask or follow the wrong-network-recovery guide.
If you need step-by-step recovery or wallet import options, see import-wallets-overview and backup-and-recovery-seed-phrase.
Who MetaMask NFT flows are good for (and who should look elsewhere)
Good for
- Users who interact with NFT marketplaces and want a single, mobile-friendly software wallet to view and move collectibles.
- People who use EVM-compatible collections and prefer direct control of seed phrase and private keys.
Who should look elsewhere
- Users who need native support for non-EVM chains for NFTs (for example, Solana collectors should consider a wallet built for that chain; see solana-and-metamask-compatibility).
- Users who need built-in multi-sig custody or advanced NFT custody features without hardware keys.
FAQ
Q: Is it safe to keep crypto in a hot wallet like MetaMask?
A: Hot wallets trade convenience for increased exposure. For everyday swaps and short-term NFT moves they are practical. For long-term or high-value holdings, consider hardware wallets or cold storage. See security-and-safety.
Q: How do I revoke token approvals that may affect NFTs or marketplaces?
A: Use the token-approvals-and-revoke tool to audit and revoke unlimited allowances. I revoked a bad approval once and avoided a bigger loss.
Q: What happens if I lose my phone?
A: Restore with your seed phrase into MetaMask on a new device or import into another compatible wallet. Follow backup-and-recovery-seed-phrase for secure recovery steps.
Q: Can MetaMask show NFTs from non-EVM chains like Solana?
A: No. MetaMask is focused on EVM-compatible chains. For Solana NFTs use a wallet built for that chain (see solana-and-metamask-compatibility for more notes).
Conclusion and next steps
MetaMask offers practical NFT management on mobile and workable options on the Chrome extension, but behavior varies by network and by how the NFT metadata is hosted. I believe testing on a public testnet before moving real assets will save you headaches. If you want hands-on walkthroughs next, check view-and-manage-nfts, learn how to add custom token contracts at add-custom-token-contract, or secure your setup with integrate-hardware-ledger-trezor.
Want a step-by-step for a specific NFT transfer scenario? Ask and I will write a tailored walkthrough you can run on a testnet first.