Quick overview
If your NFT not showing in MetaMask wallet, this guide gives practical checks you can run in 10–20 minutes. I’ll walk through ownership verification, metadata checks, network problems, OpenSea connection quirks, and hardware-wallet edge cases. I use MetaMask daily for small mints and marketplace interactions; these are fixes that worked for me when tokens or thumbnails vanished.
Whoever minted the NFT (or the marketplace) influences the fix. Sometimes it’s a wallet problem. Sometimes metadata is broken. And sometimes marketplaces cache old data.
Who this guide is for (and who should look elsewhere)
- For owners: you transferred or minted an NFT and it doesn’t appear in MetaMask.
- For buyers: you see a successful tx but OpenSea or MetaMask shows nothing.
- For mobile users: your NFT tab is empty or thumbnails are placeholders.
If you hold high-value collectibles, consider using a hardware wallet and follow hardware-specific guides like connect-ledger and ledger-troubleshooting. If you need a general MetaMask setup refresher, see install-mobile and install-extension.
Why an NFT might not show in MetaMask (common causes)
- Wrong account or wrong network selected. Short, sharp: the token is bound to an address on a specific chain. Switch accounts and networks first.
- NFT not yet indexed by MetaMask or marketplace caching. Many wallets don’t index every contract instantly.
- Metadata missing or pointing to a dead URL (broken HTTP link or unresolved IPFS/Arweave CID).
- The token standard or collection uses a non-standard implementation (some collections use custom metadata logic).
- Hardware-wallet account mismatch (using the wrong account in MetaMask for your Ledger/Trezor).
- You’re looking at the extension UI which may show fewer NFTs than the mobile app.
Technically: most NFTs expose a tokenURI via the ERC-721/1155 contract. If that URI returns bad JSON (or HTML), wallets will show placeholders. Want proof? Check the tokenURI yourself (see next section).
Step-by-step: Find the missing NFT
- Confirm the receiving address. Copy your address from MetaMask and compare with the transaction 'to' address in your block explorer entry. Don’t assume the active account is the receiving one.
- Confirm the network. Is the NFT on Ethereum mainnet, Polygon, or another EVM-compatible chain? If it’s on Polygon, switch networks (see how-to-add-polygon).
- Check the transaction on a block explorer for that chain. Look for 'success' and the token ID in the logs.
- Confirm ownership. Use the contract's read functions on the explorer (ownerOf for ERC-721) to confirm the token is assigned to your address.
- Inspect tokenURI. Copy the tokenURI returned and open it in a browser (replace ipfs:// with https://ipfs.io/ipfs/ or use a preferred gateway).
- If everything on-chain looks fine but MetaMask still hides it, try the UI fixes below.
If the tx is pending or failed, MetaMask won’t show the NFT. Resolve the tx first (see stuck-pending-transactions).
Check the metadata (tokenURI) yourself
- Look for a valid JSON object with fields like name, description, image (or image_url). If image contains an ipfs:// CID, use a gateway.
If the image field points to an HTML page or returns 404, the wallet can’t render a thumbnail. That’s a metadata issue the collection devs need to fix.
Fixes inside MetaMask (mobile & extension)
Short checklist (try these before reinstalling or logging out):
- Make sure the correct account and network are active.
- Lock and unlock the wallet (MetaMask -> menu -> Lock/Unlock) — this re-injects the provider on desktop.
- On desktop, disable strict third-party cookie or tracker blocks for the marketplace site if OpenSea won’t connect.
- On mobile, close the app and reopen it. Sometimes local cache needs a soft reset.
- If the NFT was minted very recently, wait 10–30 minutes for indexing.
Advantages and disadvantages of MetaMask NFT handling (practical):
- Advantage: Easy account switching and quick check on-chain. Bad: MetaMask does not index every collection instantly and relies on external metadata sources.
If you want in-depth token UI controls, see nft-management and token-management.
Refresh metadata MetaMask mobile — practical tips
Users search “refresh metadata MetaMask mobile” because mobile is often the place they check NFTs. Try these steps:
- Open the MetaMask mobile app and go to the NFT/Collectibles tab (if present).
- Pull down on the list to refresh (or close and reopen the app if pull-to-refresh is not present).
- If images are missing, open the token’s tokenURI via a browser to confirm metadata is live.
- If the marketplace (OpenSea) is the canonical viewer, use OpenSea’s 'Refresh metadata' for that token (see next section).
If pull-to-refresh doesn’t exist on your version, don’t log out to force a re-index unless you can restore your seed phrase securely.
OpenSea connection problems: connecting OpenSea to MetaMask
OpenSea connection issues are common: opensea not connecting to metamask, opensea mobile not connecting to metamask, and opensea metamask deeplink not supported are all common search queries. Connection modes are:
- Injected provider (desktop extension).
- WalletConnect (mobile pairing).
- MetaMask mobile in-app browser direct connect.
- Deep link flows (less reliable on iOS).
If OpenSea reports “wallet not detected,” make sure MetaMask is unlocked and the correct account is selected. On desktop, browser privacy settings or a blocked extension can prevent site detection (try another browser). On mobile, use WalletConnect from OpenSea and approve the connection inside MetaMask.
Quick comparison: OpenSea connection methods
| Method |
Works with hardware wallet? |
Common failure mode |
Fixes to try |
| Injected provider (desktop extension) |
Yes (via MetaMask account connected to hardware) |
Extension locked or blocked by browser |
Unlock MetaMask, allow site, disable strict cookie blocking |
| WalletConnect (pair mobile) |
No direct hardware via pairing (hardware depends on app support) |
Deep-link failures on iOS/Android |
Use QR pairing or MetaMask mobile app browser |
| MetaMask mobile in-app browser |
Limited, but direct |
Some marketplaces don’t accept deep-links |
Open OpenSea inside MetaMask browser and connect there |
| Deep link |
Varies |
opensea metamask deeplink not supported errors |
Use WalletConnect or in-app browser |
If you specifically see "opensea metamask deeplink not supported," switch to WalletConnect or open OpenSea in MetaMask’s built-in browser.
Hardware-wallet edge cases (OpenSea + Ledger via MetaMask)
Connecting a Ledger through MetaMask to OpenSea works, but there are extra steps: unlock the Ledger, open the correct app (Ethereum), and make sure contract data is enabled on the device. If OpenSea fails to detect your hardware-backed account, re-check which account index was used when you first added the Ledger to MetaMask (see connect-ledger and ledger-troubleshooting).
Don’t sign anything unexpected. Signing a marketplace message is normal for login, but never sign transactions you don’t understand.
Prevention and best practices
- Keep a copy of every mint tx hash and token ID.
- For high-value NFTs use a hardware wallet for approvals and transfers.
- Prefer collections that pin metadata to IPFS or Arweave to reduce broken-image risk.
- Revoke marketplace approvals if you stop using them (see revoke-approvals).
FAQ (real questions people search for)
Q: Is it safe to keep NFTs in a hot wallet?
A: For small-value collectibles yes, but for high-value items use a hardware wallet. Hot wallets are convenient but expose private keys and transactions to the web environment.
Q: How do I refresh metadata in MetaMask mobile?
A: Try pull-to-refresh in the NFT tab or restart the app. If the metadata is stale on the marketplace, use OpenSea’s refresh on the item page.
Q: OpenSea not connecting to MetaMask — what should I try?
A: Unlock MetaMask, try WalletConnect on mobile, or open OpenSea inside the MetaMask mobile browser. If you see deep-link errors, switch connection method.
Q: What happens if I lose my phone?
A: Recover MetaMask with your seed phrase on a new device only. See backup-and-recovery-options for secure recovery steps.
Q: How do I revoke approvals for an NFT marketplace?
A: Use a token-approval tool or follow the guide at revoke-approvals.
Conclusion & next steps
If your OpenSea NFT not in MetaMask wallet after these checks, the most reliable path is: verify ownership on-chain, inspect tokenURI metadata, then use marketplace refresh tools or contact the collection team. What I found over months of troubleshooting is that 80% of missing-NFT issues were metadata or wrong-network problems — not lost tokens.
Next steps: follow how-to-fix-nft-not-showing for guided fixes, or read how-to-connect-opensea if the marketplace won’t pair with your wallet. For hardware support, check connect-ledger and ledger-troubleshooting.
If you want hands-on walkthroughs for transferring or migrating collectibles, see migrate-nfts-between-wallets and nft-management.
Good luck — and don’t sign anything you don’t understand.
