> For the complete documentation index, see [llms.txt](https://docs.nftx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nftx.io/how-it-works/creator-royalties.md).

# Creator Royalties

How NFTX honours creator royalties: optional for most collections, enforced for ERC721-C collections whose creators opt in through the Royalty Gate.

NFTX is feeless in and feeless out. That stays true for most collections, but a creator who enforces royalties on their collection can now have NFTX enforce them too.

{% hint style="info" %}
Enforced royalties run through the [Royalty Gate](/contracts/royalty-gate.md), live on every mainnet. A collection is enforced only once its creator opts in.
{% endhint %}

## Two kinds of collection

* **Most collections** keep feeless entry and exit: no royalty on deposits, sales or buys.
* **Royalty-enforced collections** are ERC721-C collections whose creator has approved the Royalty Gate and left the NFTX Locker off their transfer whitelist. Every route into that collection's vault pays the creator's royalty.

## What changes for you on an enforced collection

The royalty is charged once, when an NFT goes **into** the vault, and it's paid by whoever puts it there. Getting an NFT **out** stays free.

| You want to…                         | What happens                                                                      |
| ------------------------------------ | --------------------------------------------------------------------------------- |
| Sell an NFT for ETH                  | The royalty comes out of the floor token your NFT mints; the rest is sold for ETH |
| Deposit an NFT for floor tokens      | You receive one floor token less the royalty                                      |
| Buy an NFT with ETH or floor tokens  | Unchanged: no royalty                                                             |
| Redeem or swap floor tokens          | Unchanged: no royalty                                                             |
| List an NFT above floor              | Not available yet                                                                 |
| Use your NFTs to pay for another NFT | Not available yet: sell them first, then buy                                      |

For example, a collection with a 9% royalty: depositing one NFT mints 1 floor token, 0.09 goes to the creator and you receive 0.91. Selling it for ETH sells those 0.91 floor tokens into the pool.

The app shows this before you confirm: a note that the collection enforces creator royalties, the royalty and its percentage, and your net payout.

## Behind the scenes

ERC721-C collections choose which contracts may move their NFTs. NFTX's Locker normally pulls your NFT into the vault as one of those approved contracts. On an enforced collection it isn't approved, so it can only pull an NFT when the Royalty Gate gives it a one-time permission for that exact token, and the gate only does that after charging the royalty. The permission is cleared before the transaction finishes.

Exits are different: the Locker sends NFTs out as their owner, which every collection allows. That's why buying, redeeming and listing purchases are never affected.

## For creators

Enforcing royalties on NFTX is your call, made on your collection's own transfer validator. You can switch it on or off at any time. [Creator Token Approvals](/contracts/creator-token-approvals.md#enforced-royalties-with-the-royalty-gate) has the steps.

A few honest caveats before you switch it on:

* **The royalty makes selling into the vault more expensive.** Floor tokens can trade up to the royalty below your marketplace floor, because that's what it costs to turn an NFT into one.
* **Some flows close.** Listings and NFT-for-NFT swaps aren't available for enforced collections yet.
* **NFTs already in the vault never paid.** Anything deposited before you switched enforcement on can leave freely.
* **Only NFTX is covered.** Transfers between wallets and other marketplaces follow your validator's own rules.
