Table of contents
Overview: MetaMask and NFTs
MetaMask is a widely used software wallet for interacting with EVM‑compatible chains. It supports ERC‑721 and ERC‑1155 NFTs on networks that the wallet is connected to (Ethereum mainnet and many EVM chains). The mobile app includes an in‑app collectibles viewer; the browser extension often relies on marketplaces or manual imports to display artwork.
I use MetaMask daily for small NFT trades and wallet‑connected marketplaces. I’ve made mistakes (approved an operator I didn’t mean to, paid high gas on a busy block). Those are useful lessons.
(Image placeholder: image: mobile-collectibles-screenshot)
Key takeaways at a glance:
- NFTs on EVM chains can be viewed and managed in MetaMask mobile more easily than in the desktop extension.
- NFT metadata depends on the token contract’s tokenURI (IPFS or HTTP). If the metadata endpoint is missing or blocked, images won't show.
- Sending an NFT is a single on‑chain transfer; gas depends on network and congestion (L2s are typically cheaper).
Related reading: NFT support and management and MetaMask mobile setup.
How to add nft to metamask mobile (step-by-step)
- Open the MetaMask mobile app and unlock your account.
- Tap the "Collectibles" or "NFTs" tab (bottom bar on most versions).
- Tap Add / Import collectible.
- Paste the NFT contract address and the token ID. Choose the correct network (check the network dropdown first).
- Confirm. The app will read tokenURI and attempt to fetch metadata and image.
Tips:
- If the contract uses IPFS, MetaMask will try a gateway. If images don’t appear, try a public IPFS gateway (see troubleshooting below).
- Double‑check the account address before importing (you can only import NFTs on the account that actually owns them).
Why this matters: adding a collectible is a read operation; it does not change blockchain state. It’s a UI convenience to surface tokens you already own.
How to view nfts in metamask — mobile vs desktop
Mobile (built‑in viewer)
- Native collectibles tab: shows artwork, name, and token ID.
- Supports both ERC‑721 and ERC‑1155 on EVM‑compatible networks the app supports.
- Connects to marketplaces via the in‑app browser or WalletConnect.
Desktop extension (limitations)
- The extension historically offers limited native NFT display; many users view NFTs via marketplaces (Open interfaces) or by importing token contract + ID.
- The extension injects a provider so marketplaces detect ownership, but the extension UI may not list every collectible automatically.
Comparison table
| Feature |
MetaMask Mobile |
MetaMask Extension (Desktop) |
| Native NFT viewer |
Yes |
Limited / relies on import or marketplace |
| Add by contract + token ID |
Yes |
Often manual import required |
| In‑app dApp browser |
Yes |
No (use browser tabs + injected provider) |
| WalletConnect support |
Yes |
N/A |
In my experience the mobile viewer reduces the number of times I open a marketplace site to check ownership. But desktop is still useful when signing marketplace listings or using developer tools.
How to send nft from metamask (step-by-step)
- Open the collectibles/NFT you want to send.
- Tap Send (or Transfer).
- Enter the recipient address. Paste; don’t type. Confirm the address checksum if possible.
- Choose the correct network (the network your NFT lives on).
- Review gas fees (EIP‑1559: base fee + priority fee). Adjust priority fee for speed if needed.
- Confirm and sign the transaction.
Practical checklist before you send:
- Verify the recipient address is an externally owned address or a contract that accepts ERC‑721/ERC‑1155 transfers.
- Make sure the receiving wallet supports that network (e.g., don’t send an Ethereum NFT to a Solana address).
- If you see a warning about a contract interaction, read it. Approvals like setApprovalForAll are different from transfers — they grant permission, not transfer ownership directly.
And always double‑check; a wrong chain or address can be permanent.
How to hide spam nft metamask (practical options)
Spam mints and unsolicited NFTs are common. MetaMask does not automatically filter every unwanted collectible, but you have options:
- Hide or remove the collectible from view in the mobile app (open the NFT, choose Manage / Hide or Remove if available).
- Create a local viewing filter: only import collectibles you want to see (don't auto‑import all owned tokens).
- Use a separate account for marketplace interactions to keep your primary account clean (common operational security practice).
But hiding is a UI change only; it does not affect on‑chain ownership. If you need to prevent contracts from moving your NFTs, check approvals and revoke operators (see token‑approvals‑revoke).
Troubleshooting: metadata not showing MetaMask NFTs
Symptoms: the token appears but the image or metadata shows blank, generic placeholder, or "Unknown".
Checklist and fixes:
- Network mismatch: confirm you’re on the same network the NFT was minted on (mainnet vs L2 or a testnet).
- Ownership check: verify the account holds the token (use block explorer or the wallet address to confirm).
- tokenURI accessibility: fetch the tokenURI from a block explorer. Does it return JSON with image property? If it points to IPFS, try a public gateway.
- CORS or blocked endpoints: some metadata endpoints block client requests. In that case the wallet can’t fetch images. (You can view the JSON in a browser to confirm.)
- Indexing delays: some indexers take minutes or hours to index a new contract; wait or manually import contract + ID.
What if metadata still doesn't load? Try removing and re‑adding the collectible, clear app cache, or view the token on a marketplace (which may use its own indexing). If none of that works, the token's metadata may be malformed.
Related: sync and use on multiple devices.
Advanced: collection management, approvals, cross‑chain considerations
- Collection grouping: Mobile groups items by contract where metadata is consistent. If a contract uses on‑chain metadata or nonstandard fields, grouping may be inconsistent.
- Batch transfers: MetaMask does not offer native batch NFT transfer in the standard UI. For bulk moves, use a smart contract tool or a smart‑contract wallet that supports batched transactions (see account‑abstraction‑smart‑contract‑wallets).
- Cross‑chain NFTs: bridging NFTs is nontrivial. Bridges usually wrap and mint a representation on the destination chain. This introduces counterparty and custody risks. Read bridges‑cross‑chain‑security first.
- Approvals: setApprovalForAll grants operators permission to transfer all your NFTs for a contract. Check and revoke unsafe approvals (see token‑approvals‑revoke).
Security & recovery: what every NFT holder should know
- Seed phrase is the single recovery method. Back it up offline and redundantly. See seed‑phrase‑backup‑recovery.
- Hot wallet trade‑offs: software wallets are convenient for daily use but expose keys to a connected device. Consider a hardware wallet for high‑value NFTs.
- Phishing: dApp popups can request approvals. Read the transaction data before signing.
I once approved an operator that could transfer an ERC‑721. I revoked it immediately after spotting the error. Mistakes happen. Keep a revoke routine.
FAQ
Q: Is it safe to keep NFTs in a hot wallet?
A: Hot wallets are convenient for trading and interacting with dApps. They come with higher risk than hardware wallets. For long‑term custody of high‑value NFTs, consider hardware wallets or multisig arrangements.
Q: How do I revoke token approvals for NFTs?
A: Check operator approvals (setApprovalForAll) on a block explorer or use the wallet's revoke tool (see token‑approvals‑revoke). Revoke if you don’t recognize the operator.
Q: What happens if I lose my phone?
A: With a seed phrase you can restore the account on a new device. Without it, access is lost. Back up your seed phrase offline and store it securely (see seed‑phrase‑backup‑recovery).
Q: Why isn’t my NFT image showing?
A: See the troubleshooting checklist above under "metadata not showing". Most cases are network mismatch, inaccessible tokenURI, or indexing delays.
Who this wallet is best for / who should look elsewhere
Best for:
- Active DeFi and NFT users who need an EVM‑compatible software wallet on mobile and desktop.
- Users who value in‑app dApp access and WalletConnect support.
Look elsewhere if:
- You need native Solana NFT management (this wallet focuses on EVM chains).
- You require built‑in batch NFT transfers or a UI dedicated to large collection management — specialized custody or multisig tools are better suited.
Conclusion & next steps
MetaMask provides a practical set of features for viewing, sending, and managing NFTs on EVM chains. It balances convenience and control, but you should pair it with good backup and approval hygiene.
Want a deeper walkthrough? Read the mobile setup guide (MetaMask mobile) or the NFT support overview (NFT support and management). And if you frequently use dApps, check connect to dApps via WalletConnect.
If you're ready to manage a collection, try importing one test collectible first and practice a send with a small, low‑value token (test first). Good habits save money and grief later.