MetaMask is a non-custodial hot wallet with basic NFT support for common token standards (ERC-721 and ERC-1155 on EVM-compatible chains). It will hold the private keys locally and let you sign transactions, view token metadata, and transfer collectibles. I use it daily for small trades and test listings. For high-value collections I usually pair it with a hardware wallet.
MetaMask is practical for interacting with marketplaces, but the in-wallet NFT gallery is intentionally lightweight. Don't expect a full marketplace client inside the wallet. If you want more advanced collection management, check the nft-management guide.
NFTs are just smart contracts with on-chain pointers to metadata (tokenURI). MetaMask pulls that tokenURI, then fetches image files and traits from wherever the metadata points (HTTP gateway or IPFS). If the metadata uses a private gateway or a CORS-blocked host, thumbnails won't load. I've seen this several times when minting on testnets—images fail to show even though the token exists on-chain.
Common causes when a token doesn't display:
If an NFT isn't showing, try the steps in how-to-fix-nft-not-showing and the NFT troubleshooting section below.
Mobile and extension experiences differ. Big difference. The mobile app shows a collectibles section that fetches and displays many items. The browser extension supports NFTs too, but the UI is less polished and may not list every token (especially newly minted or layer-2 assets).
If you're primarily on phone, use the MetaMask mobile app or connect via WalletConnect when a marketplace prompts it. (See walletconnect-and-mobile-browser.) If you use multiple networks—Polygon, Arbitrum, or others—switch networks in the wallet before viewing or sending assets.
Tip: switching networks is like changing tabs. Do it before you try to list or transfer an NFT.
How to send NFTs MetaMask (short, actionable):
If the NFT doesn't appear in the wallet UI, you can still transfer by interacting directly with the contract's transfer function using a dApp or block explorer. See nft-management for a longer walkthrough.
And yes, check the recipient address twice. Short sentences. I once sent an NFT to the wrong chain because my wallet was on the wrong network. Costly mistake.
Search queries like "why is metamask not connecting to opensea", "why isn't metamask connecting to opensea", and "why is opensea not connecting to metamask" are common. Here are the usual reasons and fixes.
For a step-by-step guide to connecting OpenSea, read how-to-connect-opensea.
That message—"you declined the action in your wallet metamask opensea" or "you declined the action in your wallet opensea metamask"—means you rejected a signature or transaction inside MetaMask. There are two flavors:
If you declined by mistake, refresh the dApp and resend the request. If the dApp keeps failing, check connected sites in settings and revoke stale sessions, then reconnect.
Other frequent errors and fixes:
Marketplaces often ask for approvals like setApprovalForAll. Those allow a contract to move your NFTs. Approvals are powerful. Revoke them when you no longer trade on the marketplace (see revoke-approvals).
Phishing is common: fake marketplace URLs, spoofed wallet popups, and social-engineered email links. Always check the URL before approving a signature. If a site requests an unusually high gas or a contract interaction that looks unrelated, stop.
For high-value NFTs, connect your account with a hardware wallet (Ledger/Trezor). MetaMask supports hardware integrations—see connect-ledger. Hardware adds friction, but it reduces risk.
But don't assume hardware is a silver bullet. You still need to guard your seed phrase and firmware updates.
| Problem | Likely cause | Quick fix |
|---|---|---|
| "Why is MetaMask not connecting to OpenSea" | Wallet locked, site not permitted, wrong network | Unlock wallet, allow site, switch network, refresh |
| "You declined the action" error | Signature/tx was rejected in MetaMask | Re-initiate request and Confirm; check connected sites |
| NFT not showing | Metadata CORS/IPFS or wrong network | Add custom RPC, refresh, check tokenURI (see /how-to-fix-nft-not-showing) |
| Marketplace listing fails | Missing approval or insufficient gas | Approve contract (careful), top up native token for fees |
| Wallet not showing in a platform | Platform doesn't support injected wallets | Use WalletConnect or the platform's supported flow |
Who it's for:
Who should look elsewhere:
I believe MetaMask strikes a practical balance for daily crypto activity. In my experience the convenience is worth it for day-to-day tasks, but pair MetaMask with a hardware wallet for serious holdings.
Q: "why is metamask not connecting to opensea"? A: Usually site permission, network mismatch, or blocked popup. Unlock, allow site access, switch to the right chain, and refresh. See how-to-connect-opensea.
Q: "view nfts metamask" — how do I see my NFTs? A: Open the Collectibles/NFTs tab in mobile or extension, switch to the correct network, and refresh. If missing, follow how-to-fix-nft-not-showing.
Q: "send nfts metamask" — can I transfer from extension? A: Yes. Select the NFT, choose Transfer, paste recipient, set gas fees, and confirm. For large transfers, approve with a hardware wallet.
Q: "why is my metamask not connecting"? A: Common causes: locked wallet, blocked popup, multiple extensions, or mobile browser limitations. Try refresh, allow site, or WalletConnect.
Q: "why is metamask wallet not showing in blockfi"? A: Some custodial platforms don't support injected wallets. Use the platform's supported connection method or WalletConnect if available.
MetaMask handles NFTs and marketplace interactions well for routine tasks, but it requires attention: correct network, careful approval management, and basic phishing hygiene. If you want a step-by-step connection guide for marketplaces, follow how-to-connect-opensea. For deeper NFT display or transfer troubleshooting, see nft-management and how-to-fix-nft-not-showing.
If you run into a specific error while connecting or sending an NFT, copy the exact error and check the troubleshooting table above. Good luck—and double-check that address before you hit Confirm.