How to view your NFTs in MetaMask? Why are my NFTs not showing up?

Accessing NFT Collections in MetaMask

1. Open the MetaMask browser extension or mobile app and ensure you are logged into the correct wallet address.

2. Navigate to the Assets tab — this is where tokens, including NFTs, are displayed by default.

3. Scroll down past the token balances until you reach the section labeled NFTs. If NFTs are present and supported, they will appear as cards with thumbnails and metadata.

4. Tap or click on any NFT card to view its details, including contract address, token ID, and associated blockchain explorer link.

5. On desktop, hover over the NFT image to reveal quick actions such as View on OpenSea or Send, depending on network compatibility.

Supported Blockchains for NFT Display

1. MetaMask natively supports NFT visibility on Ethereum, Polygon, BNB Smart Chain, Avalanche C-Chain, and Optimism.

2. Each chain must be manually added or pre-configured in your MetaMask settings before NFTs minted there can render properly.

3. NFTs deployed on unsupported networks like Solana, Cardano, or Tezos will not appear — MetaMask does not parse non-EVM-compatible token standards.

4. Even within EVM chains, some custom implementations of ERC-721 or ERC-1155 may omit required interface functions, causing detection failure.

5. Contract-level verification status on block explorers affects whether MetaMask can fetch name, symbol, and image URI reliably.

Manual NFT Import Process

1. Go to the NFTs section and select Import NFT at the bottom of the list.

2. Enter the exact contract address of the NFT collection — this must match the deployment address on the target network.

3. Input the specific token ID — a numeric value unique to that NFT instance within the contract.

4. Confirm the network selection matches where the NFT resides; importing on the wrong chain yields empty or broken previews.

5. After submission, MetaMask attempts to fetch metadata from the contract’s tokenURI function or an IPFS gateway if configured.

Common Metadata Loading Failures

1. Broken or inaccessible image URLs embedded in tokenURI responses prevent thumbnail rendering even when ownership is verified.

2. Centralized metadata hosts going offline cause persistent “Loading…” states or blank cards despite valid on-chain ownership.

3. CORS restrictions on certain gateways block MetaMask from retrieving JSON payloads, especially with non-standard headers.

4. Rate-limited API endpoints from services like Pinata or Cloudflare IPFS may return 429 errors silently during asset sync.

5. Incorrectly formatted JSON in metadata — missing fields like name, description, or image — results in partial or no display.

Frequently Asked Questions

Q: Can I see NFTs from a wallet I don’t control?A: No. MetaMask only displays assets tied to private keys it manages. Imported watch-only addresses do not trigger NFT scanning.

Q: Why does my NFT show “Unknown Asset” instead of a name?A: The contract either lacks a compliant name() function or returns empty/undefined, forcing MetaMask to fall back to generic labeling.

Q: Do I need to hold ETH or gas tokens on the same chain to view NFTs?A: No. Viewing does not require native gas tokens, but importing or interacting with contracts may fail without sufficient balance for RPC calls.

Q: Will deleting and re-adding a network restore missing NFTs?A: Yes. Resetting network configuration triggers a full asset rescan, which may recover NFTs previously missed due to cached RPC response failures.