How to hide NFTs in MetaMask? (Privacy & gallery settings)

Understanding NFT Visibility in MetaMask

1. MetaMask does not store NFTs directly on the wallet interface but displays them by fetching data from blockchain explorers and third-party APIs like OpenSea or Rarible.

2. The wallet relies on token standards such as ERC-721 and ERC-1155 to detect and render NFTs in its built-in gallery view.

3. Visibility is determined by whether an NFT contract is whitelisted, supported by MetaMask’s asset detection service, or manually added via custom token configuration.

4. Users cannot “hide” NFTs at the protocol level since ownership is immutable and publicly verifiable on-chain.

5. What appears as hiding is actually a client-side filtering mechanism within the wallet’s UI layer.

Disabling Auto-Detection of NFTs

1. Navigate to MetaMask Settings → Preferences → toggle off “Show NFTs” under the “Privacy & Security” section.

2. This action disables automatic fetching and rendering of NFTs from known marketplaces and supported contracts.

3. Existing NFT entries may remain visible until the cache is cleared or the page is reloaded.

4. Disabling auto-detection prevents new NFTs from appearing unless explicitly imported using contract address and token ID.

5. This setting affects only the visual gallery — it does not alter on-chain ownership records or metadata accessibility.

Removing Individual NFTs from the Gallery

1. Open the NFT tab inside MetaMask and locate the specific item you wish to remove from view.

2. Click the three-dot menu icon next to the NFT and select “Remove from collection”.

3. Confirm the action; the NFT will disappear from the gallery but remains owned and transferable.

4. Removal does not revoke permissions or interact with smart contracts — it only deletes local UI references.

5. If the NFT belongs to a newly deployed or non-standard contract, manual removal may be required after initial detection failure.

Managing Contract-Level Visibility

1. MetaMask maintains an internal list of verified NFT contracts used for display optimization.

2. Unverified or low-traffic contracts often do not appear unless users manually add them through the “Add Token” flow.

3. Developers can influence visibility by submitting their contracts for verification via MetaMask’s GitHub repository or official partnership channels.

4. Contract-level filtering is handled server-side by MetaMask’s asset service and cannot be overridden by end users.

5. Some wallets integrate decentralized indexers like Covalent or Moralis, but MetaMask currently uses its own centralized asset API.

Frequently Asked Questions

Q: Does removing an NFT from MetaMask’s gallery affect my ability to send or sell it?A: No. Removal only affects UI rendering. You retain full control and can still interact with the NFT via contract calls or external marketplaces.

Q: Can someone see my hidden NFTs if they know my wallet address?A: Yes. All NFT holdings are publicly visible on blockchain explorers like Etherscan or Solscan regardless of MetaMask settings.

Q: Why do some NFTs reappear after I remove them?A: Auto-detection may reload cached assets during wallet sync or after network reconnection. Disabling “Show NFTs” prevents recurrence.

Q: Is there a way to hide NFTs from all dApps connected to MetaMask?A: No. Connected dApps query the blockchain directly or use their own indexing services. Wallet-level hiding has no effect on external applications.