How to hide NFTs in MetaMask? (Interface Settings)

Understanding NFT Visibility in MetaMask

1. MetaMask does not natively support hiding individual NFTs from the main interface — it displays all NFTs associated with the connected wallet address across supported networks.

2. The wallet treats NFTs as tokens and relies on third-party APIs like OpenSea’s or Alchemy’s to fetch and render them in the collectibles tab.

3. There is no toggle, checkbox, or built-in “hide” button next to each NFT within the current MetaMask UI version.

4. Users often misinterpret token removal or network deactivation as “hiding”, but these actions affect visibility only indirectly and temporarily.

5. Any appearance of selective NFT filtering stems from external integrations or custom RPC configurations rather than native wallet functionality.

Disabling NFT Auto-Detection

1. Navigate to Settings → Preferences → toggle off “Show NFTs in activity feed” to suppress NFT-related notifications and timeline entries.

2. Go to Settings → Connected Sites → select a dApp → scroll to “NFT Permissions” and revoke access to prevent that site from triggering NFT metadata calls.

3. Disable automatic NFT detection by turning off “NFT detection” under Settings → Advanced — this stops MetaMask from querying NFT contracts when loading the wallet.

4. Clear cached NFT data manually via Settings → Advanced → “Reset Account” — this erases locally stored NFT thumbnails and metadata without affecting on-chain ownership.

5. Switching to a custom RPC endpoint that lacks NFT indexing (e.g., a private node without OpenRPC extensions) may result in incomplete or missing NFT listings.

Network-Level NFT Suppression

1. Remove unsupported or irrelevant EVM-compatible networks from the network list — NFTs minted exclusively on those chains will no longer appear.

2. Edit an existing network configuration and replace the default block explorer URL with a non-functional one to break metadata retrieval for NFTs tied to that chain.

3. Use MetaMask’s “Add Network” feature to register a testnet with intentionally incorrect contract addresses for popular NFT standards (e.g., ERC-721), causing failed detection.

4. Deactivate the Ethereum Mainnet or Polygon network if those contain most of your visible NFTs — the collectibles tab becomes empty or shows “No NFTs found”.

5. Import a wallet into a fresh MetaMask profile configured only for non-NFT-supporting chains such as Optimism Bedrock or Base Sepolia, limiting exposure surface.

Browser Extension Behavior and Cache Control

1. Right-click the MetaMask extension icon → “Manage Extensions” → click “Remove” then reinstall to eliminate persistent NFT rendering artifacts.

2. In Chrome or Edge, go to chrome://extensions → enable “Developer mode” → click “Inspect views background page” → clear localStorage entries containing “nft” or “collectible” keys.

3. Disable hardware acceleration in browser settings to prevent GPU-accelerated rendering glitches that sometimes cause duplicate or phantom NFT entries.

4. Block known NFT metadata domains (e.g., ipfs.io, cloudflare-ipfs.com, opensea.io) using browser-level content blockers — this prevents thumbnail loading and breaks display logic.

5. Launch MetaMask in incognito mode with all extensions disabled except MetaMask to verify whether third-party scripts interfere with NFT visibility.

Frequently Asked Questions

Q: Can I hide just one specific NFT while keeping others visible?MetaMask does not offer per-NFT visibility controls. All NFTs are rendered collectively based on detected contracts and API responses.

Q: Does resetting my MetaMask account delete my NFTs?No. Resetting only clears local cache and interface state. Your NFTs remain secured on-chain and accessible after reconnection.

Q: Why do some NFTs still show up after disabling NFT detection?Legacy metadata may persist in browser storage or be fetched directly from dApps you’ve interacted with, bypassing MetaMask’s detection layer.

Q: Is it safe to edit network RPC URLs to suppress NFTs?Yes, as long as the modified endpoint remains functional for transaction signing. Invalid endpoints may break balance updates but won’t compromise private keys.