How to view your NFT collection in MetaMask Mobile? (Digital Gallery)

Accessing the Digital Gallery Interface

1. Open the MetaMask Mobile application on your iOS or Android device.

2. Ensure you are logged into the correct wallet account where your NFTs are stored or have been received.

3. Tap the 'Collectibles' tab located at the bottom navigation bar — this is the entry point to the built-in Digital Gallery.

4. If the Collectibles tab does not appear, verify that your wallet is connected to a supported network such as Ethereum Mainnet, Polygon, or BSC — NFT visibility depends on chain compatibility.

5. The interface displays thumbnails of all recognized NFTs, grouped by collection and sorted chronologically by receipt time.

Supported Standards and Chain Requirements

1. MetaMask Mobile natively supports ERC-721 and ERC-1155 tokens on EVM-compatible chains.

2. Collections deployed on non-EVM networks like Solana or Cardano will not render in the Digital Gallery — no bridge or adapter exists within the app for cross-architecture token parsing.

3. Custom RPC endpoints must expose the OpenSea API-compatible metadata endpoints for full asset rendering; missing or malformed URIs result in blank or generic placeholders.

4. Some NFTs minted via obscure contracts may lack standardized event logs or fail signature validation, causing them to remain invisible even if balance checks confirm ownership.

5. Wallet-level asset detection relies on on-chain transfer events indexed by MetaMask’s internal scanner — delays up to 15 minutes may occur after receipt.

Manual Addition of Hidden or Unrecognized NFTs

1. Navigate to the Collectibles tab and tap the '+' icon in the top-right corner.

2. Select “Add NFT manually” and input the exact contract address and token ID — case sensitivity matters.

3. Confirm chain selection matches the deployment network; entering an Ethereum contract ID while on Polygon will return an error.

4. MetaMask fetches metadata directly from the contract’s tokenURI function — if that function reverts or returns invalid JSON, the NFT appears with no image or name.

5. Users cannot override or edit fetched metadata locally; edits require contract-level changes executed by the collection’s deployer.

Metadata Rendering and Display Limitations

1. Image previews load only if the metadata contains a valid HTTP or IPFS URI pointing to a PNG, JPG, or GIF file under 10MB.

2. SVG files are unsupported and trigger fallback to placeholder icons; animated GIFs play inline but do not support looping controls.

3. Descriptions and attributes appear beneath each thumbnail only if the metadata includes a 'description' and 'attributes' field formatted per EIP-721 standard.

4. Localization is absent — all text renders exactly as returned by the tokenURI response, including unsupported Unicode or truncated strings.

5. No offline caching occurs; images and metadata reload every time the gallery is opened unless the device has persistent network access.

Frequently Asked Questions

Q: Why does my NFT show “Unknown Collection” even though it’s verified on Etherscan?A: MetaMask relies on its own registry of known contracts. If the collection isn’t whitelisted or lacks proper OpenSea-compatible metadata, it defaults to “Unknown Collection” regardless of on-chain verification status.

Q: Can I view NFTs sent to my wallet from a hardware wallet-connected account?A: Yes — provided the hardware wallet’s public address matches the one imported into MetaMask Mobile and the transaction was confirmed on a supported chain.

Q: Does MetaMask Mobile support layered NFTs or dynamic traits that change over time?A: No. The gallery displays static metadata retrieved at load time. Real-time trait updates, on-chain state changes, or off-chain logic-driven visuals are not reflected.

Q: Why do some NFTs appear duplicated across multiple collections?A: This occurs when a single token ID is registered under more than one contract address — often due to migration forks, proxy upgrades, or misconfigured multi-chain deployments.