Quick answer: what tokens does MetaMask support?
Short version: MetaMask is built for EVM-compatible tokens. That means native ETH and tokens that follow Ethereum-style standards (ERC-20, ERC-721, ERC-1155, and similar on other EVM chains) work out of the box once the correct network is selected. Add a Binance Smart Chain RPC and your BEP-20 tokens are visible and usable. But native Solana (SPL) and Tron (TRC20) tokens are not supported by MetaMask.
I've been using this daily for months across Ethereum mainnet, Polygon, and BSC. In my experience the flow for ERC-20 and BEP-20 tokens is seamless once networks are configured. And yes, that includes interacting with DEXs and DeFi apps that run on those chains.
(If you want walkthroughs for adding common networks, see Add BSC, Add Polygon, Add Avalanche, and Add Optimism & Arbitrum.)
Token standards explained (EVM first)
ERC-20 / EVM-compatible tokens
ERC-20 is the baseline token standard for Ethereum and any EVM-compatible chain. An ERC-20 token is an on-chain contract that keeps a ledger of balances. MetaMask connects to a network via RPC and reads those balances. Because BEP-20 on BSC is EVM-compatible, MetaMask can interact with BEP-20 tokens exactly like ERC-20s once BSC is added as a network.
How it works under the hood? MetaMask acts as a web3 provider (injected provider in a browser or internal provider on mobile). When you ask a dApp to read balances or send tokens, the dApp queries the token contract on the selected RPC.
NFTs: ERC-721 & ERC-1155
MetaMask can sign transfers and show token contract interactions for ERC-721 and ERC-1155 NFTs. The extension and mobile app have basic NFT visibility, but they are not full-featured gallery apps. For deeper NFT management use a specialized viewer or marketplace tool (see NFT management).
BEP-20 and other EVM-style forks
BEP-20 is effectively ERC-20 on Binance Smart Chain. MetaMask supports BEP-20 tokens once you add the BSC RPC. The same applies to any chain that speaks the Ethereum JSON-RPC interface.
Non-EVM standards: SPL, TRC20, etc.
MetaMask does not natively support Solana SPL tokens or Tron TRC20. Those blockchains use different runtime environments and transaction formats. You cannot import a Solana private key into MetaMask to control SPL tokens. There are wrappers and bridges that mint EVM-wrapped tokens representing SPL/TRC assets on an EVM chain, but that adds counterparty and smart-contract risk (see Bridges & cross-chain for more).
But there's a catch. Some third-party tools try to bridge or proxy non-EVM chains into MetaMask via extensions or bridges. Use extreme caution with those.
Supported chains & how MetaMask handles them
MetaMask ships with Ethereum mainnet by default and lets you add custom RPCs. On desktop this is done via settings; on mobile you can add networks too. Once a network is added, MetaMask reads balances and lets you send tokens on that chain.
Practical examples:
- Add BSC to hold BEP-20 tokens — works. (How-to: Add BSC)
- Add Polygon to hold ERC-20 tokens on Polygon — works. (Add Polygon)
- Want to use L2 or rollups? Add Optimism/Arbitrum networks. (Add Optimism & Arbitrum)
If a token doesn’t show automatically after switching networks, you can add it by contract address (steps below). For mobile dApps, WalletConnect is an alternative to the injected provider — see WalletConnect & mobile browser.
How to add a custom token (step-by-step)
- Switch MetaMask to the network that the token lives on (e.g., BSC for BEP-20).
- Click "Import Token" or "Add Token" in the UI.
- Paste the token contract address, and MetaMask will usually fill name and decimals.
- Confirm and add.
If you prefer screenshots or platform-specific notes, see Token management and How to import token.
DeFi, swaps, approvals: practical compatibility notes
MetaMask connects to dApps that accept an injected provider. That covers most EVM DeFi apps. MetaMask also has a built-in swap aggregator (see Built-in swap), which routes trades across on-chain liquidity. In my experience the aggregator saves time on frequent swaps, though slippage and routing should still be checked.
Token approvals are the biggest practical risk. I once approved an "infinite" allowance for a scam contract (rookie mistake). I revoked it afterward (you can use the guide at Revoke approvals). Always limit allowances when possible and inspect the spender address.
Gas fees behave differently across chains. EVM networks with EIP-1559 use base fee + priority fee mechanics, and MetaMask exposes those settings under gas options. For Layer 2 networks, gas costs are often lower but you may need native token balance (e.g., ETH on an L2) for fees.
NFTs and token visibility
MetaMask shows NFT assets in a basic list. It will read ERC-721/1155 metadata from the token contracts. But spam NFTs and broken metadata are common. You can hide collections in the UI and use a marketplace or gallery for serious collection management (see NFT management).
Security recommendations for token management
- Keep your seed phrase offline and only enter it in official restore flows.
- For large holdings use a hardware wallet connected to MetaMask (see Connect Ledger).
- Don’t add tokens just because someone tells you to. Check the contract address on a block explorer.
- Revoke unused token approvals regularly.
- Avoid third-party plugins that promise support for non-EVM tokens unless you verified their code.
In my experience, the convenience of a software wallet is worth it for daily DeFi. But high-value storage belongs in cold storage.
Compatibility quick-reference table
| Token standard |
Supported in MetaMask? |
Notes |
| ERC-20 |
Yes |
Native on Ethereum and EVM-compatible networks |
| ERC-721 / ERC-1155 |
Yes |
Basic viewing and transfers; use dedicated NFT tools for galleries |
| BEP-20 |
Yes (with BSC RPC) |
Add network via custom RPC (Add BSC) |
| SPL (Solana) |
No |
Use a Solana wallet; can bridge to EVM-wrapped tokens (risky) (Solana & Tron & Near) |
| TRC20 (Tron) |
No |
Tron requires a Tron wallet; bridges exist but are separate |
FAQ
Q: What token does MetaMask support?
A: MetaMask supports tokens that live on EVM-compatible chains (ERC-20, ERC-721, ERC-1155 and their equivalents). BEP-20 works when BSC is added. It does not support native Solana SPL or Tron TRC20 tokens.
Q: What crypto can I store on MetaMask?
A: Any crypto that the chain exposes via JSON-RPC and that your account controls: ETH, ERC-20 tokens, and tokens on added EVM networks (Polygon, BSC, Avalanche C-Chain, L2s). For Solana/TRON native assets use dedicated wallets or bridges. See bridges-cross-chain for trade-offs.
Q: Is a BEP20 MetaMask wallet a different product?
A: No — MetaMask is the same software. To hold BEP-20 tokens add the BSC RPC and you'll interact with BEP-20 contracts like ERC-20 ones. See Add BSC.
Q: Can MetaMask be a TRC20 MetaMask wallet?
A: No. MetaMask does not support the Tron protocol natively.
Q: Does MetaMask support SPL token MetaMask / Solana MetaMask support?
A: Not natively. SPL tokens live on Solana and are incompatible with the Ethereum JSON-RPC interface that MetaMask uses.
Who this wallet is best for — and who should look elsewhere
Best for:
- Users who use DeFi on Ethereum and EVM-compatible chains.
- People who value quick dApp integration and frequent swaps.
Look elsewhere if:
- You hold primarily Solana or Tron native assets and need full SPL/TRC20 support.
- You need enterprise multi-sig custody (consider dedicated multisig solutions — see multisig & Gnosis).
Conclusion & next steps
MetaMask handles EVM-based tokens well. It gives direct access to ERC standards and, with added networks, BEP-20 and other EVM variants. It does not support SPL or TRC20 natively; bridging introduces new risks.
If you want to get hands-on: try adding a network and import a known token contract (test with a small amount first). See setup guides: Install extension and Install mobile, and review Token management and Revoke approvals for safety steps.
Want a deeper walkthrough for adding a specific chain or importing tokens? Follow the linked how-to pages above and test on a small amount before moving larger balances. But remember: seed phrase safety always comes first.
