ERC-721 is the Ethereum token standard that defines a common interface for non-fungible tokens. Each token is identified separately, so wallets, marketplaces and applications can track and transfer unique assets through consistent functions and events.
The standard records token ownership; it does not guarantee that linked media will remain available, that an asset is authentic, or that copyright transfers with the token. This explains the core interface, optional metadata, minting and transfer flow, and the security checks that users and developers should apply.
Key Takeaways
- ERC-721 standardizes ownership, transfer and approval functions for individually identified tokens.
- A token is uniquely identified by its contract address and token ID on a particular chain.
- Metadata and enumeration are optional; media may be stored on-chain, on decentralized storage or on a conventional server.
- Owning an NFT does not automatically grant copyright, commercial rights or ownership of a physical asset.
What Is ERC-721?
ERC-721 is a standards-track Ethereum interface for non-fungible tokens. “Non-fungible” means the ledger tracks each token as a distinct item rather than as an interchangeable quantity. Ten units of one ERC-20 token are accounted for as a balance; ten ERC-721 tokens are ten separate token IDs.
The final specification lists William Entriken, Dieter Shirley, Jacob Evans and Nastassia Sachs as authors and records a creation date of January 24, 2018. Earlier NFT projects, including CryptoKitties, helped demonstrate the need for a shared interface.
The standard lets compatible smart contracts, wallets and marketplaces use the same basic calls. An implementation can add features, but it must preserve the required ERC-721 behavior if it claims compatibility.
How Does ERC-721 Work?
Token Identity
Every ERC-721 token has a uint256 token ID inside its contract. The fully qualified identifier is the combination of chain, contract address and token ID.
Token ID 42 in one contract is unrelated to token ID 42 in another. A collection name or ticker is not a reliable identifier because different contracts can use the same text.
Ownership and Balances
The ownerOf(tokenId) function returns the address recorded as the owner of a valid token. The balanceOf(owner) function returns how many tokens from that contract the address owns.
These functions record on-chain control of the token. They do not establish the identity of the person controlling the address or independently prove a claim about an off-chain object.
Transfers
transferFrom moves a token from one address to another when the caller is authorized. safeTransferFrom adds a check when the recipient is a contract: the recipient must implement the expected receiver interface or the transfer reverts.
The safe function helps prevent transfers to incompatible contracts, but it does not protect a user who approves a malicious operator or sends to the wrong externally owned address.
Approvals
An owner can approve one address to manage a specific token with approve. The owner can also grant an operator authority over every ERC-721 token from that contract through setApprovalForAll.
Operator approval is powerful. A malicious marketplace or phishing site can transfer all covered tokens. Users should verify the spender and revoke permissions they no longer need.
Events
The standard defines Transfer, Approval and ApprovalForAll events. Indexers and applications use these logs to follow ownership and permission changes.
A Transfer event from the zero address commonly signals minting, while a transfer to the zero address commonly signals burning. The specification describes event responsibilities but does not itself standardize public mint and burn functions.
How Does ERC-721 Metadata Work?
The optional metadata extension provides name, symbol and tokenURI. The URI may point to a JSON document containing a name, description, image and other attributes.
The JSON or media can be stored in several ways:
- Fully on-chain: Data is encoded in the contract or returned as a data URI. This improves self-containment but can be expensive.
- Content-addressed storage: A URI uses IPFS or a similar network. Integrity can be checked from the content identifier, but availability still requires hosting or pinning.
- Conventional web hosting: An HTTPS server returns the data. It is easy to update, but the operator can change or remove it unless the contract or URI is immutable.
The ERC-721 specification allows metadata URIs to be mutable. Buyers should check the contract, reveal process and any freeze mechanism rather than assume permanence.
What Can an ERC-721 Token Represent?
An ERC-721 can represent digital art, a game item, a membership pass, a domain registration, a ticket or a claim connected to a physical asset. The token standard supplies a ledger interface; it does not define the legal terms of the represented item.
This distinction is important for tokenized real-world assets. A deed, contract, issuer record or applicable law may determine the enforceable right. Merely linking a photo of a house to a token does not transfer the house.
Copyright works the same way. Buying an NFT generally transfers the token, while copyright or commercial-use rights depend on a separate license or agreement.
What Are the Benefits of ERC-721?
- Interoperability: Compatible wallets and applications can call the same core interface.
- Distinct ownership: Each token can have its own owner, history and metadata reference.
- Programmability: Developers can add royalties, access controls, rentals or game logic, subject to other standards and contract design.
- Composability: Other contracts can hold, transfer or use ERC-721 tokens as inputs.
- Transparent provenance: On-chain transfers can be inspected, although provenance does not prove authorship or legal authenticity by itself.
What Are the Risks and Limitations of ERC-721?
Approval and Phishing Risk
A deceptive signature can grant an operator broad transfer rights. Use a separate low-value wallet for unfamiliar applications, read the transaction on a trusted device and apply UEEx’s wallet security guidance.
Contract Risk
Mint logic, access controls and upgrade mechanisms can contain defects. An administrator may be able to pause transfers, change metadata or mint additional tokens. “ERC-721 compatible” is not a security audit.
Metadata and Availability Risk
The token can remain on-chain while its image or description disappears. Content-addressed storage improves integrity, but it does not guarantee hosting.
Authenticity and Intellectual-Property Risk
Anyone can deploy a lookalike contract or mint media they do not own. Verify the contract through official project channels and review the license.
Liquidity and Valuation Risk
NFTs are not interchangeable, so each asset may have a thin market. A collection’s floor price does not guarantee that a particular token can be sold at that price.
How Do You Verify an ERC-721 NFT?
- Confirm the chain and contract address through an official source.
- Inspect the token ID, current owner and transfer history in a block explorer.
- Check whether the contract is verified and whether it is upgradeable.
- Review owner, minter, pauser and metadata-administrator privileges.
- Open the token URI and identify where the JSON and media are stored.
- Read the license and any terms connected to physical access, membership or intellectual property.
- Verify marketplace approvals before signing and revoke unused operators.
- Never treat a screenshot, collection name or “verified” interface badge as sufficient proof.
How Does ERC-721 Compare With ERC-20 and ERC-1155?
| Standard | Asset model | Typical use | Notable feature |
|---|---|---|---|
| ERC-20 | Fungible balances | Currency, governance or utility tokens | Units are interchangeable within one contract |
| ERC-721 | Individually identified tokens | Unique collectibles, names and rights | Each token has a distinct ID and owner |
| ERC-1155 | Multiple token types in one contract | Games and mixed asset systems | Supports fungible and non-fungible IDs with batch transfers |
Conclusion
ERC-721 gives Ethereum applications a shared way to track and transfer unique tokens. Its value is interoperability, not a guarantee of authenticity, permanence or legal ownership. Users should verify the chain, contract, token ID, metadata storage, permissions and license. Developers should implement the standard carefully, minimize administrator power and make metadata behavior explicit.
Related Terms
- Token URI – The function and returned link that points to an ERC-721 token’s metadata JSON.
- ERC-1155 – The Ethereum standard supporting both fungible and non-fungible token types in one contract with batch transfers.
- IPFS – A content-addressed, peer-to-peer storage network commonly used to host NFT metadata and media.
- Floor Price – The lowest current asking price among listed tokens in an NFT collection.
- Metadata – The name, description, image and attributes associated with an individual token.
- Royalties – A percentage of secondary sales a creator may receive, enforced by marketplace convention or contract logic rather than by the core ERC-721 standard.
Sources
- ERC-721 Specification – The formal Ethereum Improvement Proposal defining the ERC-721 interface and events.
- OpenZeppelin ERC-721 Implementation Guide – Reference implementation and library commonly used to build ERC-721 contracts.
- Ethereum.org Overview of Non-Fungible Tokens – Plain-language explanation of NFTs and their common use cases.
- IPFS Documentation for NFT Data – Technical reference for storing and pinning NFT metadata and media on IPFS.
Frequently Asked Questions
Is every NFT an ERC-721 token? No. NFTs exist on many networks and can use other Ethereum standards, including ERC-1155. ERC-721 is one widely used interface, not the definition of every NFT.
Does ERC-721 store the image on Ethereum? Not necessarily. The contract often stores or returns a URI, while the JSON and image live elsewhere. Review the token URI and hosting method.
Does owning an ERC-721 token grant copyright? Not automatically. Copyright and commercial rights depend on the creator’s license or another legal agreement.
Can an ERC-721 token be copied? The on-chain token ID cannot be duplicated within the same contract, but the media can be copied and another contract can mint a lookalike token. Authenticity depends on the contract and issuer, not visual appearance alone.
Can ERC-721 tokens be burned? Yes, if the implementation provides a permitted burn method. The core standard does not require a public burn function.
