NFT Royalty Standards (EIP-2981)

What Are NFT Royalty Standards (EIP-2981)?

NFT Royalty Standards, also known as EIP-2981 or ERC-2981, define a common way for a smart contract to tell marketplaces, wallets, and other crypto applications how much royalty should be paid when a non-fungible token is sold or resold.

The official EIP-2981 specification describes the standard as a way to retrieve royalty payment information for NFTs so that royalty support can work across different marketplaces and ecosystem tools.

In simple terms, EIP-2981 does not move money by itself, but it answers two important questions: who should receive the royalty and how much should be paid based on a given sale price.

This matters because NFTs are traded across many different applications, and a shared royalty standard helps creators avoid setting royalty information separately on every platform.

For crypto users, EIP-2981 is best understood as a signaling standard rather than an enforcement standard.

It signals royalty information on-chain, but the buyer, seller, marketplace, or settlement contract must still choose to honor and pay that royalty.

Why EIP-2981 Exists in the NFT Market

Before EIP-2981, NFT royalty systems were often fragmented, meaning one marketplace could use one royalty method while another marketplace used a different method.

That made creator payments hard to track, hard to support, and hard to standardize across the wider NFT ecosystem.

The goal of EIP-2981 is to give NFT contracts a predictable interface that any marketplace or application can call when it needs royalty information.

This is similar to how common token standards make crypto assets easier to integrate across wallets, decentralized applications, analytics tools, and smart contract systems.

EIP-2981 is especially useful for NFT creators, gaming projects, digital art collections, music NFTs, membership NFTs, and brand collectibles that want a clear royalty rule attached to each token.

It also helps developers build NFT infrastructure because they can check one standard function instead of supporting many custom royalty formats.

How EIP-2981 Works

EIP-2981 uses a function called

to return royalty data for a specific NFT and a specific sale price.

The function receives a token ID and a sale price, then returns a receiver address and a royalty amount.

The receiver address is the wallet or smart contract that should receive the royalty payment.

The royalty amount is calculated as a percentage of the sale price, not as a fixed number that ignores the sale value.

For example, if an NFT has a 5% royalty and sells for 10 ETH, the royalty amount returned should equal 0.5 ETH.

If the same NFT sells for 1,000 units of another payment token, the royalty amount should be calculated in that same payment unit.

The official standard says that the royalty payment should be made in the same unit of exchange as the sale price, which helps avoid confusion between ETH, stablecoins, and other crypto assets.

This design keeps the function flexible because it does not need to know which currency was used for the sale.

The Core Function: royaltyInfo()

The core of EIP-2981 is the

function.

This function is called by a marketplace, smart contract, wallet, or application that wants to know royalty information before or after an NFT sale.

A simplified version of the interface looks like this:

The

parameter identifies the NFT being queried.

The

parameter tells the contract the price used to calculate the royalty amount.

The returned

value tells the paying party where the royalty should be sent.

The returned

value tells the paying party how much should be sent for that sale price.

The standard does not require the receiver to be the original artist, because the receiver could also be a rights holder, studio, DAO treasury, revenue splitter contract, or another address chosen by the NFT project.

EIP-2981 and ERC-165 Interface Detection

EIP-2981 requires support for ERC-165, which is a standard way for smart contracts to report which interfaces they support.

This allows an application to check whether an NFT contract supports the royalty interface before calling

.

The EIP-2981 interface ID is

.

A marketplace or application can use ERC-165 to ask a contract whether it supports that interface ID.

If the contract returns true, the application can call

and use the returned royalty data.

This reduces integration risk because applications do not need to guess whether a contract has royalty support.

How EIP-2981 Connects to ERC-721 and ERC-1155

EIP-2981 is often used with ERC-721, the NFT standard commonly used for one-of-one tokens and unique collectibles.

It is also commonly used with ERC-1155, a multi-token standard often used for gaming items, editions, and collections with many token types.

The official EIP-2981 standard is designed to be compatible with both ERC-721 and ERC-1155 contracts.

However, EIP-2981 is not limited to those two NFT standards.

Any smart contract that can identify assets by token ID can use the EIP-2981 interface to return royalty information.

This gives developers room to use the standard in newer NFT designs, hybrid assets, and other crypto-native ownership models.

What EIP-2981 Does Not Do

EIP-2981 does not automatically force a royalty payment every time an NFT moves from one wallet to another.

This is important because not every NFT transfer is a sale.

A user might transfer an NFT to a hardware wallet, send it as a gift, move it between personal wallets, or bridge it through another system.

If every transfer required a royalty payment, normal wallet management could become expensive and confusing.

For that reason, EIP-2981 focuses on providing royalty information, while actual payment execution is left to marketplaces, settlement contracts, or off-chain agreements.

This is why many developers describe EIP-2981 as a royalty information standard, not a full royalty enforcement system.

Voluntary Royalties and Marketplace Enforcement

The biggest misunderstanding about EIP-2981 is the belief that it guarantees creators will receive royalties from every secondary sale.

In reality, EIP-2981 only makes royalty information available in a standard format.

A marketplace or trading system must still choose to read that data and send the payment to the royalty receiver.

The OpenZeppelin ERC-2981 documentation also notes that on-chain royalty tracking does not automatically mean automatic payouts.

This means creators should understand the difference between royalty signaling and royalty enforcement before launching an NFT collection.

Royalty signaling tells the market what should be paid.

Royalty enforcement controls whether payment must happen before a trade can settle.

EIP-2981 handles the first part, while the second part depends on marketplace rules, smart contract architecture, allowlists, transfer restrictions, escrow systems, or other royalty protection methods.

Why Royalties Are Important for NFT Creators

NFT royalties can create an ongoing revenue stream for artists, game studios, musicians, writers, community builders, and digital creators.

In traditional markets, creators often earn income from an initial sale but may not benefit when their work becomes more valuable later.

With NFT royalties, a creator can set a percentage that is intended to be paid each time the NFT is resold.

This can align incentives between creators and collectors because creators may continue building value around the collection after mint.

For example, a creator might use royalty income to fund new artwork, community events, game development, holder benefits, licensing work, or long-term project operations.

However, royalty income should not be treated as guaranteed revenue because royalty payment still depends on whether the sale venue or transaction flow honors the standard.

Benefits of EIP-2981 for NFT Buyers

EIP-2981 also helps NFT buyers because royalty terms can become easier to discover and compare.

When royalty information is stored in a standard on-chain interface, marketplaces and tools can display it more clearly during the buying process.

This can help buyers understand the total cost of a trade before making a purchase.

It can also help buyers evaluate whether a project has a sustainable creator funding model.

Some collectors prefer projects that support creator royalties because they believe ongoing funding can improve long-term project quality.

Other traders may focus more on transaction cost and liquidity, which is why clear royalty data is important for informed decision-making.

Benefits of EIP-2981 for Developers

For developers, EIP-2981 reduces the need to build custom royalty logic for every NFT integration.

A marketplace, wallet, analytics platform, or portfolio tracker can use the same interface across many NFT collections.

This improves composability, which is one of the main strengths of smart contracts in crypto.

Developers can also use audited contract libraries to add EIP-2981 support more safely.

For example, OpenZeppelin Contracts provides ERC-2981 implementations that can be used with common token contract designs.

Using a well-known library does not remove the need for testing or security review, but it can reduce mistakes compared with writing royalty logic from scratch.

Common Royalty Models Used With EIP-2981

The most common model is a fixed percentage royalty across the whole collection.

For example, a collection may set a 5% royalty that applies to every token ID.

Another model is a token-specific royalty, where different NFTs in the same contract can return different royalty amounts.

This can be useful when different artists, rights holders, or collaborators contributed to different tokens in the same collection.

A third model is a dynamic royalty that changes based on predictable contract state.

For example, a project could reduce royalty percentages over time or after certain transfer counts, as long as the calculation does not depend on assumptions about the payment currency.

The official EIP warns against using unpredictable variables in ways that could create disputes between the sale moment and the royalty calculation moment.

Royalty Percentage and Basis Points

Many NFT contracts store royalties in basis points.

One basis point equals 0.01%.

This means 100 basis points equals 1%, 500 basis points equals 5%, and 1,000 basis points equals 10%.

Basis points are useful in smart contracts because they avoid floating-point numbers, which Solidity does not handle in the same way as normal spreadsheet software.

For example, a contract can calculate a 5% royalty by multiplying the sale price by 500 and dividing by 10,000.

This approach is simple, gas-efficient, and easy for developers to audit.

Example of an EIP-2981 Royalty Calculation

Imagine an NFT has a royalty rate of 7.5% and sells for 2 ETH.

The marketplace calls

.

The NFT contract returns the creator’s royalty receiver address and a royalty amount of 0.15 ETH.

If the marketplace honors the royalty, it sends 0.15 ETH to the receiver and the remaining amount, minus any marketplace fees or other costs, to the seller.

If the same NFT sells for 1,000 units of a stablecoin, the royalty amount should be 75 units of that stablecoin.

The standard expects the royalty amount to follow the sale price unit, which keeps the royalty calculation unit-neutral.

On-Chain and Off-Chain NFT Sales

EIP-2981 is designed to provide royalty information for both on-chain and off-chain sale contexts.

An on-chain sale may happen through a smart contract where the payment and NFT transfer settle in the same transaction.

An off-chain sale may involve an auction house, private agreement, custody provider, or other process where settlement does not fully happen inside a public smart contract.

The official standard says that royalty-supporting entities should pay royalties regardless of where the sale occurred.

In practice, off-chain royalty payment depends heavily on the parties involved and whether they agree to honor the royalty data.

This makes legal terms, marketplace policy, and project communication important parts of NFT royalty design.

Limitations of EIP-2981

The first limitation is that EIP-2981 does not enforce payment by itself.

The second limitation is that it returns one receiver address, so complex revenue splitting usually needs a separate splitter contract or off-chain accounting process.

The third limitation is that the standard does not define how the royalty payment should be transferred, confirmed, reported, or disputed.

The fourth limitation is that royalties can create friction for traders who are focused on short-term liquidity and low transaction costs.

The fifth limitation is that NFT contracts must be carefully designed so royalty settings cannot be abused by an owner, admin, or compromised key.

These limitations do not make EIP-2981 useless, but they show why it should be treated as one building block in a broader NFT royalty strategy.

Security Considerations for NFT Royalty Contracts

Although the EIP-2981 interface is small, NFT royalty implementation still requires careful security planning.

Projects should define who can update royalty settings, whether royalties can be changed after mint, and whether there is a maximum royalty cap.

A royalty receiver address should be protected because sending royalties to the wrong address can cause permanent loss of funds.

If a project uses a splitter contract, that contract should be tested to make sure funds are distributed correctly.

If an upgradeable NFT contract is used, the upgrade admin should be protected with strong operational security.

Developers should also think about how burns, transfers, contract upgrades, and token-specific royalty overrides affect stored royalty data.

Royalty Splitters and Multiple Creators

EIP-2981 returns one receiver address, but many NFT projects involve more than one creator or stakeholder.

A common solution is to set the receiver as a payment splitter contract.

The splitter contract can then distribute incoming royalty payments among artists, developers, studios, musicians, community treasuries, or other participants.

This keeps the EIP-2981 interface simple while allowing more complex payout logic outside the NFT contract.

However, royalty splitters should be transparent and tested because creators and collectors may want to understand how funds are shared.

Projects should also explain whether the split can change and who has permission to update it.

EIP-2981 and NFT Metadata

NFT metadata describes items such as name, image, attributes, animation files, and external content.

EIP-2981 is separate from metadata because it focuses only on royalty information.

This separation is useful because royalty information can be read directly from the smart contract, while metadata may be stored through IPFS, Arweave, centralized servers, or other storage systems.

For example, an NFT image may live in decentralized storage, while the royalty receiver and royalty amount are returned through the contract function.

This design helps marketplaces and tools access royalty data without parsing collection metadata files.

EIP-2981 and Creator Rights

EIP-2981 should not be confused with copyright ownership, commercial licensing, or intellectual property rights.

An NFT can include royalty information without transferring copyright to the buyer.

An NFT can also transfer certain usage rights while still keeping royalty rules separate.

Creators should clearly explain what holders receive when they buy the NFT, including display rights, commercial rights, access rights, or game utility.

Royalty settings are an economic rule, while intellectual property terms are a legal and licensing matter.

Because crypto assets can move globally, projects should avoid vague language and publish clear terms that users can review before buying.

How Marketplaces and Applications Use EIP-2981

A marketplace that supports EIP-2981 usually checks whether the NFT contract supports the interface through ERC-165.

If the interface is supported, the marketplace calls

with the token ID and sale price.

The marketplace then receives the royalty recipient and royalty amount.

If the marketplace honors royalties, it includes that payment in the settlement flow.

A wallet or analytics platform may use the same data to display expected creator fees before a transaction.

An indexing service may use EIP-2981 to collect royalty settings across many NFT contracts and make the data easier to search.

Why EIP-2981 Matters for Crypto Adoption

NFTs are more than profile pictures because they can represent digital art, tickets, game items, memberships, certificates, music, domain names, and tokenized media.

For these use cases to grow, creators need standards that make ownership and payment rules easier to understand.

EIP-2981 helps by making royalty data machine-readable across crypto applications.

This improves the developer experience and can make NFT markets more transparent for users.

It also supports a creator economy where digital assets can keep funding the people and teams that maintain their value.

Even though enforcement remains a challenge, standardized royalty signaling is still an important step toward more mature NFT infrastructure.

Related Royalty Standards and Future Development

EIP-2981 is the main royalty information standard, but the NFT royalty conversation has continued to evolve.

For example, ERC-6786 is a draft proposal for a royalty payment registry that aims to track royalty payments for NFTs.

Research and newer proposals have also explored stronger incentive models for royalty enforcement, including work such as ERC-7526 royalty enforcement research.

These newer ideas show that the NFT ecosystem is still searching for better ways to balance creator income, user freedom, market liquidity, and smart contract enforceability.

For now, EIP-2981 remains important because it gives the market a widely recognized baseline for royalty information.

Best Practices for NFT Projects Using EIP-2981

NFT projects should publish a clear royalty percentage before mint so buyers understand the cost structure.

Projects should avoid hidden or unlimited royalty changes because sudden changes can damage trust.

A reasonable maximum royalty cap can help reassure collectors that fees will not become extreme later.

Projects should use secure access control for royalty updates and avoid leaving sensitive admin functions exposed to a single weak wallet.

Projects should test royalty behavior across ERC-721 or ERC-1155 flows, especially if token-specific royalties are used.

Projects should also make sure royalty receiver addresses are correct before launch because blockchain transactions are difficult or impossible to reverse.

Best Practices for NFT Buyers and Traders

NFT buyers should check royalty information before purchasing because royalties can affect the total cost of trading.

Collectors should understand that paying royalties may support the creator or project team after the initial sale.

Traders should understand that royalty rules may affect resale profit, especially when margins are small.

Users should also remember that royalties can vary by token, collection, marketplace policy, or settlement method.

Reading project documentation, smart contract data, and marketplace fee details can reduce confusion before a transaction.

Because NFT royalty enforcement is not universal, buyers should not assume that every resale will automatically send funds to the creator.

Common Misconceptions About EIP-2981

One misconception is that EIP-2981 forces royalties at the smart contract level.

The correct view is that EIP-2981 provides royalty information, while payment enforcement depends on the trading system.

Another misconception is that EIP-2981 only works for ERC-721 NFTs.

The standard can also work with ERC-1155 and other contract designs that can identify assets through token IDs.

A third misconception is that the royalty receiver must always be the original creator.

The receiver can be any address chosen by the project, including a rights holder, treasury, or splitter contract.

A fourth misconception is that royalties are always good or always bad for NFT markets.

The better view is that royalties are a design choice with trade-offs between creator funding, buyer cost, and market liquidity.

FAQ

What is EIP-2981?

EIP-2981 is an Ethereum NFT royalty standard that lets a smart contract return the royalty receiver and royalty amount for a given NFT sale price.

Is EIP-2981 the same as ERC-2981?

Yes, EIP-2981 is the Ethereum Improvement Proposal, while ERC-2981 is the finalized Ethereum Request for Comments standard name commonly used by developers.

Does EIP-2981 automatically pay NFT royalties?

No, EIP-2981 only provides royalty information, and the marketplace or settlement system must still execute the payment.

Can EIP-2981 enforce royalties on every NFT transfer?

No, the standard does not enforce royalties on every transfer because many NFT transfers are not sales.

Which NFT standards can use EIP-2981?

EIP-2981 is commonly used with ERC-721 and ERC-1155 NFTs, but it can also be used by other contracts that can identify assets by token ID.

What does royaltyInfo() return?

The

function returns a receiver address and a royalty amount based on the token ID and sale price provided by the caller.

Are NFT royalties always paid in ETH?

No, the royalty should be paid in the same unit of exchange as the sale price, so a sale paid in a stablecoin should have a royalty calculated in that same stablecoin.

Can an NFT have different royalties for different token IDs?

Yes, EIP-2981 allows token-specific royalty logic as long as the royalty amount is calculated as a percentage of the sale price.

Can royalties be sent to multiple creators?

EIP-2981 returns one receiver address, but that receiver can be a splitter contract that distributes funds to multiple creators or stakeholders.

Why do some NFT sales not pay royalties even when EIP-2981 exists?

Some sales do not pay royalties because EIP-2981 is voluntary unless the marketplace, contract, or transaction system chooses to honor and enforce the royalty payment.

Conclusion

NFT Royalty Standards, or EIP-2981, give the crypto ecosystem a simple and standardized way to read royalty information from NFT smart contracts.

The standard helps creators communicate expected royalties, helps developers integrate royalty data, and helps buyers understand potential trading costs.

Its main strength is interoperability because one interface can serve many marketplaces, wallets, and NFT tools.

Its main weakness is that it does not enforce payment by itself.

For NFT projects, EIP-2981 should be used with clear documentation, secure contract design, reasonable royalty settings, and transparent communication with collectors.

For users, EIP-2981 is a useful signal that explains what royalty should be paid, but it should not be mistaken for a guarantee that every resale will produce creator income.

As NFT markets continue to mature, EIP-2981 remains one of the most important building blocks for creator royalties and on-chain royalty transparency.