Token Management: Add, Hide, and Track Tokens & NFTs

Why token management matters

Managing tokens in a software wallet (hot wallet) is more than cosmetic. Accurate token detection affects what you can send, how dApps read balances, and whether you accidentally approve a malicious contract. In my experience, the two most common user mistakes are: adding the wrong contract address and assuming "hidden" tokens are removed from approvals. Both can cost real money.

And yes, a cluttered token list slows down finding what you actually use daily.

This guide focuses on practical steps: add custom token MetaMask, fix token not showing in MetaMask, hide spam tokens MetaMask, and how to track balances and NFTs without exposing yourself to extra risk.

Which token standards MetaMask handles (ERC-20 / ERC-721 / ERC-1155)

MetaMask is built for EVM-compatible blockchains and recognizes common standards used on those chains. Here's a compact comparison I use when auditing a new token:

Standard	What it represents	How MetaMask typically handles it	Notes / when manual work is needed
ERC-20	Fungible tokens (same value per unit)	Auto-detects most; balance displayed as a number	New tokens or tokens on custom RPC often need the token contract address pasted manually
ERC-721	Unique NFTs (one token = one item)	Mobile apps commonly show collections; extension support is limited	Token metadata must be on-chain or via standardized metadata URL for display
ERC-1155	Semi-fungible (batchable items, token IDs)	Partial support; send/receive require token ID	Viewability depends on metadata and marketplace compatibility

If you see terms like "erc20 metamask", "erc721 metamask", or "erc1155 metamask" in searches, remember: the wallet supports the standards, but metadata and the active network determine whether assets appear cleanly.

How MetaMask detects tokens (automatic vs custom)

Under the hood, token detection uses two sources: public token lists and on-chain queries via your selected RPC node. When a token is listed in a well-known list, MetaMask will suggest it automatically. When it's not, you must provide the token contract address.

Why does that matter? Because the token contract address is the canonical identifier — symbols and names can be duplicated across chains. Paste the right token contract address into MetaMask and you avoid false tokens (a common scam).

If you need to find a token contract address, use the chain's block explorer (see Using Etherscan with MetaMask) and confirm the contract's verified source and total supply before adding.

How to add a custom token — Step by step (extension + mobile)

Step-by-step: extension (desktop browser)

Open the extension and confirm the correct network (top dropdown).
Go to the Assets tab and click "Import tokens".
Choose "Custom Token" and paste the token contract address. Token symbol and decimals often auto-fill.
Click "Add Custom Token", then "Import Tokens" to finish.

Step-by-step: mobile app (iOS / Android)

Open the mobile app and confirm the current network.
Tap "Assets" then the plus (+) or "Import Tokens" option.
Paste the token contract address (or search supported tokens) and confirm the token symbol/decimals.
Tap "Add" or "Import" to finish.

Practical checklist before hitting Import:

Confirm the network (ERC-20 tokens on Ethereum mainnet won't show if you are on Polygon).
Verify the token contract address against the official project site or the chain explorer. (And double-check; scammers copy names.)
Confirm decimals — wrong decimals will display wildly incorrect balances.

If you want a deeper guide for the full UI on mobile or desktop, see MetaMask mobile setup and install MetaMask chrome extension.

Hide spam tokens and clean your list

Seeing dozens of worthless tokens after interacting with a faucet or a suspicious dApp? You can hide them. Hiding removes them from view but does NOT remove on-chain token approvals.

But remember: hiding doesn't revoke approvals. If you approved an allowance to a dApp, hiding the token only cleans your UI — it doesn't stop that allowance. Use token approvals & revoke to audit and revoke allowances.

Quick steps to hide a token

Desktop: Assets → click the token → Manage → Hide token (varies by version).
Mobile: Assets → tap token → three‑dot menu → Hide.

Hiding is a convenience, not a security measure.

Track tokens & NFTs: portfolio and NFT support

MetaMask provides a built-in portfolio view that aggregates token balances and fiat valuations using price feeds. It's a lightweight crypto portfolio tracker MetaMask users rely on for quick checks. For tax reports or deep analytics, I pair it with an external tracker that connects via WalletConnect or by exporting transaction history.

NFT support varies by client: mobile apps show collections where metadata is present; the extension is more limited for NFTs. If an NFT is missing, confirm the token contract implements ERC-721 or ERC-1155 metadata endpoints and that you are on the chain the NFT was minted on.

If you need NFT-focused workflows, see NFT support & management for best practices on viewing and sending collectibles.

![Screenshot placeholder: MetaMask portfolio view and tokens list]

Advanced tips: decimals, networks, and gas considerations

Wrong decimals = wrong balances. ERC-20 uses a decimals field; if the wallet reads it incorrectly, your displayed balance can be off by orders of magnitude.
Wrong network = token not showing. Make sure you’re on the same chain as the token contract (Ethereum mainnet vs L2 vs Polygon).
For ERC-1155 transfers you need the token ID. MetaMask may require you to use a dApp or custom contract call for complex token transfers.

If you see "token contract address MetaMask" errors, the usual root cause is the address belongs to a different chain or is an unverified contract.

Troubleshooting: token not showing, wrong balance, transfer failures

Common checks when a token is missing or behaves oddly:

Confirm network/RPC. Switch to the exact chain where the token lives.
Verify the token contract address on the chain explorer. Copy/paste — do not type.
Add the token as a Custom Token and confirm decimals.
If balance is missing on-chain, check the block explorer and your account's transaction history.
For transfers that fail: inspect gas fees and whether the token has transfer hooks (some tokens require extra gas or fail with certain contracts).
If UI is stale, try Reset Account (Settings → Advanced → Reset Account) — this clears local transaction history but not your funds.

If you're stuck, see transaction errors and fixes and recovering missing funds.

Who this wallet is best for — and who should consider other options

Best for:

Users interacting with DeFi on EVM-compatible chains who want a simple, non-custodial interface for tokens and dApps.
People who need a quick crypto portfolio tracker for day-to-day checks.

Consider other options if:

You need built-in support for non-EVM chains (e.g., Solana) — this wallet focuses on EVM-compatible networks.
You prioritize cold-storage-level security for large balances; combine software wallet use with a hardware wallet (see Ledger with MetaMask guide).

I’ve been using this setup daily for months and still pair it with a hardware wallet for large transfers — a trade-off between convenience and security I think most active DeFi users will recognize.

FAQ

Q: Is it safe to keep crypto in a hot wallet?

A: Hot wallets are convenient for trading and interacting with dApps, but they carry higher exposure than hardware wallets. Use seed phrase backups, enable biometric locks on mobile, and keep only the funds you plan to use in the hot wallet.

Q: How do I revoke token approvals?

A: Audit and revoke token approvals via the token allowances & revoke guide. Revoke infinite approvals immediately when you detect suspicious activity.

Q: What happens if I lose my phone?

A: If you have your seed phrase backed up, you can restore the wallet on another device. If not, funds are effectively lost. See seed phrase backup & recovery for a step‑by‑step plan.

Q: Where do I find the contract address for BTT on MetaMask?

A: Always get the contract address from the correct chain’s block explorer or the token project's official channels and confirm the contract verification. Never trust a random forum post.

Conclusion & next steps (CTA)

Token management is mostly about two things: correct identification (contract addresses and networks) and ongoing security (approvals, hiding vs revoking). If you want hands-on practice: try adding a custom token using the steps above, then audit approvals for that token. For a focused walkthrough, see Add a custom token and if your tokens or NFTs aren’t appearing, check NFT support & management.

If you're ready to go deeper, check the linked how-to pages for step-by-step screenshots and prevention checklists.