ERC-721
Last Updated: November 16, 2026
ERC-721 is a standard for creating non-fungible tokens (NFTs) on the Ethereum blockchain. Unlike fungible tokens such as ERC-20, each ERC-721 token is unique and represents a distinct asset. These tokens mostly prove ownership of unique digital items, such as art, collectibles and game assets. Each token in an ERC-721 contract carries a unique NFT ID that sets it apart from every other token.
Origin and Status
ERC-721 began as Ethereum Improvement Proposal 721, created on January 24, 2018, by William Entriken and three co-authors. The official EIP-721 page lists it as Final, so the interface is settled. The proposal calls NFTs “deeds.” It notes that CryptoKitties used an earlier draft, while the older CryptoPunks contract was only partly ERC-20 compatible.
How ERC-721 Works
Every ERC-721 contract shares the same basic interface. Each token has a tokenId number that is unique inside its contract, so a contract address plus a tokenId points to exactly one NFT. The ownerOf function returns a token’s owner, and balanceOf counts how many tokens an address holds.
Transfers use transferFrom or safeTransferFrom. The safe version checks that a receiving contract can accept NFTs, so tokens do not get stuck. Owners can approve one address for a single token, or use setApprovalForAll to let an operator, such as a marketplace, move every token they hold in that collection.
An optional metadata extension adds a name, a symbol and a tokenURI for each token. The tokenURI usually points to a JSON file with the title, description and image link, often stored on IPFS or a web server.
Features of ERC-721
- Uniqueness: Every ERC-721 token is unique, identified by its own token ID, which makes it ideal for digital collectibles and assets.
- Ownership & Transfer: ERC-721 tokens can be owned, transferred and traded like physical items.
- Interoperability: Wallets, marketplaces and dApps support the same interface, so one NFT works across many apps.
ERC-721 vs ERC-20 and ERC-1155
| Standard | Token type | Tokens per contract | Typical uses |
|---|---|---|---|
| ERC-20 | Fungible, every unit identical | One token | Currencies, stablecoins, governance tokens |
| ERC-721 | Non-fungible, each token unique | Many unique tokens | Art, collectibles, domain names, liquidity positions |
| ERC-1155 | Fungible, non-fungible or both | Many token types | Game items, editions, prediction market shares |
When a project needs many copies of one item, such as 1,000 identical game potions, ERC-1155 is often cheaper. One contract can track many token types and send them in a single batch.
On Bitcoin, the closest match to an ERC-721 NFT is an Ordinals inscription, which stores content on a single satoshi instead of in a token contract.
Use Cases
ERC-721 is widely used for digital art, virtual land, game items and collectibles, letting creators sell unique digital assets on the blockchain.
It also covers items that are not art. ENS documentation says .eth names such as ens.eth have ERC-721 NFTs behind them, so a web3 name can be moved or sold like any NFT. Uniswap’s v3 developer guide says each liquidity position is an NFT with its own tokenId in an ERC-721 contract.
Example: Uniswap Positions on November 16, 2026
At 19:01 UTC on November 16, 2026, Uniswap’s v3 position manager contract on Ethereum (0xC364…FE88) reported a totalSupply of 1,253,965 at block 26,429,546. In plain terms, about 1.25 million liquidity positions existed as ERC-721 tokens. Each one records a token pair, a fee tier, a price range and its liquidity, and it can be sent like any other NFT.
Where to Check an ERC-721 Token
A block explorer such as Etherscan shows a contract’s token standard, holders, transfers and the owner of any tokenId. Before buying, compare the contract address with the one the project publishes, because copycat collections often reuse the same name and art.
Limits and Risks
An NFT usually keeps only a link on-chain. If the metadata or image sits on a server that goes offline or changes, the token can lose its picture or traits. ERC-721 itself does not enforce royalties. The separate EIP-2981 royalty standard says it cannot force a payment on every transfer, so creator fees depend on each marketplace.
Approvals are the biggest everyday risk. A signed setApprovalForAll lets the approved address move every NFT you hold in that collection, and scam sites often ask for exactly this signature. Our guide on how to store crypto safely explains how to read signature requests and revoke old approvals.
Frequently Asked Questions
What is the difference between ERC-721 and ERC-20?
ERC-20 tokens are fungible, so every unit is identical and can be swapped for another, like dollars in a bank account. ERC-721 tokens are non-fungible: each has its own tokenId, owner and metadata, so one cannot simply replace another. ERC-20 suits currencies and stablecoins, while ERC-721 suits unique items such as art, domain names and liquidity positions.
What is the difference between ERC-721 and ERC-1155?
ERC-721 gives each token in a contract its own unique ID and owner, which fits one-of-one items and collections. ERC-1155 lets one contract manage many token types, fungible or not, and move several of them in a single batch transaction. Projects with many identical items, such as game assets, often choose ERC-1155 to save on transaction costs.
Is an ERC-721 NFT stored fully on the blockchain?
Usually not. The blockchain records the token ID, its owner and a tokenURI link. The image and traits normally sit in a JSON file on IPFS or a web server. Some projects store everything on-chain, but most do not, so it is worth checking where the metadata lives before relying on an NFT’s art or traits.
Who created the ERC-721 standard?
ERC-721 was written by William Entriken, Dieter Shirley, Jacob Evans and Nastassia Sachs. It was created as an Ethereum Improvement Proposal on January 24, 2018, and its official page now lists it as Final. The proposal grew out of early NFT projects and notes that CryptoKitties worked with an earlier version of the interface.
Data sources: EIP-721 and EIP-2981 on eips.ethereum.org; ENS and Uniswap developer documentation; Uniswap v3 position manager contract on Ethereum, read November 16, 2026.