MetaMask Wallet: Understanding Token Standards (ERC-20, ERC-721, ERC-1155)

A user receives what they think is a single digital asset, but when they open their MetaMask wallet, it appears twice with different icons and values. One shows a balance in a decimal format; the other displays a single item in an NFT section. The confusion reflects a real difference in how blockchain assets are structured. These are not variants of the same thing displayed differently—they are fundamentally distinct token types following different standards, each encoding information and transfer rights in a specific way.

Understanding token standards is essential for anyone managing assets on Ethereum-compatible networks. The standard determines how an asset behaves when sent, stored, received, and displayed. It affects whether your MetaMask wallet treats the item as a fungible token you can divide and send in fractional amounts, a unique NFT with individual characteristics, or something that combines both properties. Token standards also influence which decentralized applications can interact with your assets, how exchanges list them, and whether wallets recognize them at all.

ERC-20: The fungible token standard

ERC-20 is the oldest and most widely adopted token standard on Ethereum. It defines a set of rules for how fungible tokens—assets that are identical, divisible, and interchangeable—are created, transferred, and tracked. If you own one unit of a particular ERC-20 token and someone sends you another unit of the same token, the two units are equivalent in every meaningful way. This is functionally identical to how traditional money works: a dollar bill is a dollar bill, regardless of which physical bill you hold.

When you add an ERC-20 token to your MetaMask wallet, you see a balance displayed as a decimal number. That number represents your total holdings of that token. If you send 10 units to someone else, your balance decreases by 10, and theirs increases by 10. The transaction is atomic and immediate. ERC-20 tokens can represent stablecoins (like USDC or USDT), governance tokens, reward tokens, or any other asset designed to be divisible and fungible. The standard includes functions for checking balances, transferring tokens, and approving spending limits.

The ERC-20 standard is simple by design. It requires just a few core functions: transfer (move tokens to another address), approve (grant permission for another address to spend your tokens), and balanceOf (check an account’s token balance). Because this simplicity is predictable, most decentralized applications, exchanges, and services have built native support for ERC-20 tokens. Your MetaMask wallet automatically recognizes most ERC-20 tokens once they are added, displaying them in a consistent way regardless of the specific token’s purpose or origin.

However, simplicity also means ERC-20 has limitations. The standard does not handle batch operations efficiently, which can make minting or distributing large quantities of tokens expensive in gas fees. It also does not support the concept of unique items—each token is treated as identical to every other token of the same type. If you need to represent a digital collectible, a unique certificate of ownership, or any asset where individual units have distinct properties, ERC-20 is insufficient.

ERC-721: The NFT standard

ERC-721 emerged to solve the problem ERC-20 could not: representing unique, non-fungible assets on the blockchain. Each ERC-721 token is individually distinct, identified by a unique token ID, and cannot be split into smaller units. When you receive an ERC-721 NFT in your MetaMask wallet, you do not receive a fraction or a share; you receive the entire asset as a discrete item, or you receive nothing. The protocol enforces this atomicity at the blockchain level.

The most visible difference when using a MetaMask wallet is how NFTs are displayed. Instead of showing a numeric balance in a token list, NFTs typically appear in a separate NFT section within the wallet interface. Each NFT shows as a single card or tile with an image preview (if metadata is available), the asset name, and the collection it belongs to. You can see the token ID, which is the unique identifier proving ownership of that specific item within the contract.

ERC-721 is used for digital art, collectibles, gaming items, virtual real estate, domain names, and any application where individual ownership and uniqueness matter. The standard includes functions to query who owns a specific token ID, transfer ownership, and set metadata URIs that point to external data (image, description, attributes) about the NFT. That metadata is typically stored off-chain on systems like IPFS, while the blockchain maintains only the ownership record and a link to the metadata location.

The trade-off in ERC-721 is flexibility for specificity. The standard supports complex use cases—royalties, access control, conditional logic tied to ownership—but each NFT must be transferred whole. If you own a rare digital collectible represented as an ERC-721 token, you cannot sell 0.5 of it. You own it completely, or you sell the entire item. Your MetaMask wallet handles this limitation by design: you can send your NFT to someone else, but the protocol will not permit fractional transfers.

ERC-1155: The multi-token standard

ERC-1155, sometimes called the multi-token standard, abstracts both fungible and non-fungible assets into a single contract framework. A single ERC-1155 contract can manage thousands of different tokens, some fungible (like currencies or resources), some non-fungible (like unique items), and some semi-fungible (limited editions, where multiple identical copies exist but with a capped supply). This flexibility comes from treating every token within the contract as having a unique token ID, but allowing any ID to have a supply greater than one.

In your MetaMask wallet, ERC-1155 tokens can appear in multiple ways depending on the supply of each token ID. A token ID with a supply of one might look similar to an ERC-721 NFT in the NFT section. A token ID with a supply of 1,000 might be displayed like an ERC-20 token with a balance. Some wallets may group them together, while others might split the display. The standard gives contract creators the flexibility to design how many copies of each asset exist, but it does not mandate a specific way wallets must present them to users.

ERC-1155 is particularly useful for games, virtual worlds, and decentralized platforms where you might own 50 identical resource tokens (fungible) alongside unique skins or artifacts (non-fungible) all within the same ecosystem. The standard is also more efficient than managing separate ERC-20 and ERC-721 contracts, which reduces deployment costs and simplifies interactions. When you approve spending on an ERC-1155 contract, you can grant permissions for specific token IDs, all token IDs, or fine-grained subsets, depending on how the contract implements access control.

The complexity of ERC-1155 is that wallet support is less consistent than ERC-20 or ERC-721. Your MetaMask wallet supports ERC-1155 assets, but the way they are displayed and organized may be less polished than for the more established standards. Some assets may not display metadata correctly, and interactions with games or dApps using ERC-1155 may require more manual contract interaction than with simpler standards.

How token standards affect MetaMask wallet operations

When you use your MetaMask wallet to interact with decentralized applications, the token standard matters more than you might realize. A contract expecting ERC-20 tokens cannot automatically work with ERC-721 NFTs, even if you own them. The functions they call are different, the data structures are incompatible, and the blockchain will reject a transaction that tries to force the wrong standard into a contract designed for another. This is a feature, not a bug: it prevents accidental use of assets in ways they were not designed for.

Token standards also affect gas costs and transaction efficiency. Adding an ERC-20 token to your MetaMask wallet is a simple contract interaction that costs minimal gas. Minting a large batch of ERC-721 NFTs, by contrast, can be expensive because each NFT transfer is an atomic operation. ERC-1155 can reduce this cost through batch operations, allowing multiple token transfers in a single transaction. If you are sending NFTs in bulk or managing a portfolio that involves many small transactions, the token standard influences both your costs and how efficiently you can execute.

Discovery and validation are also affected by the standard. Your MetaMask wallet can be configured to display ERC-20 tokens automatically if they are sent to your address, but it may not automatically display all NFTs, depending on wallet settings and whether the NFT contract metadata is complete and accessible. Some ERC-1155 tokens may not appear at all if the wallet software does not fully support the standard. If you receive an asset and it does not show up in your wallet, the problem may not be that the asset is missing—it may be that the wallet does not recognize the standard or the metadata is incorrect.

The security implications of token standards are also worth understanding. Because ERC-20 is so widely supported, it is often the target for token impersonation attacks where someone deploys a fake ERC-20 token with a similar name to a legitimate one and tries to trick users into interacting with it. Your MetaMask wallet helps by warning you when you interact with unverified tokens, but the security ultimately depends on your ability to verify contract addresses. When you add a custom ERC-20, ERC-721, or ERC-1155 token to your wallet, always confirm you are using the correct contract address from the official project website, never from a link in an email or social media post. You can find guidance on securing your recovery phrase and validating tokens in your metamask wallet documentation.

Managing different token types in a single wallet

One advantage of modern MetaMask wallet design is that it handles multiple token standards in a single interface. You can own ERC-20 tokens, ERC-721 NFTs, and ERC-1155 assets all in the same wallet on the same network, and the wallet will organize them appropriately. The token section typically shows your ERC-20 and semi-fungible ERC-1155 balances, while the NFT section displays unique or rare ERC-721 and ERC-1155 items.

Adding tokens to your MetaMask wallet is straightforward for ERC-20. You can search for the token by contract address, and if it is already registered with popular token lists, it may appear with the correct icon, name, and decimal places. For less common tokens, you may need to manually enter the contract address, token symbol, and decimal count. This information should always come from the official project website, never from user forums or unverified sources.

NFTs and ERC-1155 assets are typically added automatically when you receive them, but you can also import them by contract address and token ID if needed. Some NFT marketplaces show token details directly, while others require you to find the contract on a blockchain explorer. Because NFT metadata can be hosted on IPFS, centralized servers, or other systems, metadata availability and display can vary. If an NFT does not show an image in your wallet, the issue is often that the metadata URI is broken or the hosting service is unavailable, not that the NFT itself is invalid.

Transferring tokens between standards is not directly possible—you cannot convert an ERC-20 token into an ERC-721 NFT through a wallet transfer. However, some projects create paired systems where an ERC-20 token can be wrapped or converted into an NFT (or vice versa) through a bridge contract. This is a deliberate choice by the project, implemented at the application level, not at the wallet level. Your MetaMask wallet simply shows you the result of the transaction: if the bridge succeeded, you will see the new asset appear and the old one disappear.

Common issues and troubleshooting token visibility

The most frequent problem is that a token appears to disappear from your MetaMask wallet after an apparent loss or transfer. Usually, the asset is still there—it has just been moved to a different account, sent to the wrong network, or is not displaying due to a metadata issue. If you sent an ERC-721 NFT from the Ethereum network to a Polygon address but your wallet is set to the Ethereum network, the NFT will not be visible until you switch to the Polygon network.

Another common issue is token decimals. ERC-20 tokens can define different decimal values, which affects how balances are displayed. A token with 18 decimals is the Ethereum standard (matching Ether’s precision), but some tokens use 6, 8, or other values. If you add a custom ERC-20 token with the wrong decimal count, your balance will display incorrectly, though the underlying token quantity on the blockchain remains accurate. Correcting the decimal value in your wallet settings will fix the display.

NFT metadata issues are often invisible at first. If you receive an ERC-721 NFT but see only a placeholder image or no image at all, the metadata URI might be pointing to a broken link or a server that is temporarily unavailable. The NFT itself is valid and yours; it is just not displaying its intended appearance. Refreshing the wallet or waiting for the metadata provider to recover can resolve this. Some wallets also allow you to manually set metadata, though this is an advanced operation.

If a token does not appear in your MetaMask wallet after you are certain you received it, verify the contract address and token ID (for NFTs) using a blockchain explorer. Check which network the token is on, ensure your wallet is set to the correct network, and confirm that the contract address in your wallet settings matches exactly. Contract addresses are case-sensitive at the application level, though Ethereum addresses are case-insensitive on-chain. A typo in a single character will cause the wallet to show the wrong (or no) token.

The relationship between standards and interoperability

Token standards exist because they create a common language for blockchain applications. If every token creator invented their own transfer mechanism, decentralized exchanges could not list them, wallets could not display them consistently, and users would need custom tools for each asset. By adhering to ERC-20, ERC-721, or ERC-1155, a token creator ensures that their asset works with thousands of existing services without custom integration work.

However, standards do have limitations. They define the technical rules but not the economic or social rules. A token following the ERC-20 standard could be a legitimate governance token, a scam, a test token with no real value, or a honeypot designed to trap users who try to sell. Your MetaMask wallet can verify that a token follows the correct standard, but it cannot verify legitimacy. You must research the project, check social media and official websites, and be suspicious of tokens that appear to have value but come from unknown sources.

The standards also evolve. Ethereum has proposed new standards like ERC-4626 (tokenized vaults), ERC-4855 (federated token standards), and others addressing specific use cases. As these gain adoption, wallets like MetaMask will add support, but it takes time for new standards to reach widespread use. If you encounter a token or NFT that your wallet does not recognize, it may be using a newer or specialized standard that is not yet universally supported.

Looking forward, the expansion of MetaMask wallet functionality to Bitcoin, Solana, and TRON networks will introduce different token standards specific to those blockchains. Bitcoin’s layer-two networks have their own token conventions, Solana uses a different token program architecture, and TRON has its own standards. Understanding token standards at the Ethereum level gives you the mental model to learn other ecosystems, but the specifics will differ based on each blockchain’s design and history.