Open an NFT in a block explorer and three different things can appear to be one asset. The blockchain records a token and its controller. The token may point to a metadata file, which may point again to an image or other media. A separate licence or contract determines what, if anything, the controller may do with that work.
Calling all three “ownership” hides the questions that matter. An NFT can provide a transferable onchain record without making its media permanent, its intellectual-property rights automatic or its use compatible with every application.
The token is the onchain record
On Ethereum, ERC-721 identifies a token with the combination of a contract address and a token ID. The contract exposes functions for checking control, approving an operator and transferring the token. That standardised interface is what allows wallets and marketplaces to recognise many collections.
The ERC-721 specification calls the metadata extension optional. It also states that a token URI may be mutable. Consequently, the existence of a token does not prove that its name, description or image is stored permanently on the blockchain.
ERC-1155 uses another model. One contract can manage several token types, and each ID can have its own supply. The multi-token standard accommodates fungible, non-fungible and mixed configurations, including batch transfers. The blanket claim that every NFT is indivisible is therefore wrong: implementation and supply rules determine whether a holder controls a unique unit, one item from an edition or a quantity of a token type.
Metadata and media can live in different places
A token URI can return metadata directly, point to content-addressed storage such as IPFS, or depend on an ordinary web server. The metadata then commonly includes another URI for the image, animation or file. Each link has its own availability and mutability properties.
Content-addressed storage lets a reader verify that retrieved bytes match an address derived from the content. It does not guarantee that somebody will continue hosting those bytes. A conventional HTTPS URL can remain available for years, but the server operator may replace the file or stop serving it. Fully onchain media avoids that external host, at the cost of storage and implementation constraints.
Before describing an NFT as immutable, inspect the contract and the complete URI chain. Ask whether the contract owner can change a base URI, whether metadata has been frozen, how content is retained and what the interface displays if an external service fails.
Token control is not automatically copyright
Transferring a token normally transfers the blockchain position defined by its contract. Copyright, trademark rights, commercial-use permission and ownership of a physical object are separate legal questions. They move only when applicable law and the project’s terms or licence make them move.
The US Copyright Office and US Patent and Trademark Office reached the same practical conclusion in their joint NFT and intellectual-property study: buyers and sellers often do not understand which rights are involved, while existing IP rules continue to apply. Minting a token that points to somebody else’s artwork does not cure infringement or establish authorship.
A buyer should locate the licence in force at the time of acquisition, determine whether it follows later transfers and save a copy. A marketplace description is not a substitute for enforceable terms. If the token represents a ticket, membership or physical redemption, the issuer’s continuing ability and obligation to honour that benefit are also material.
Royalties require a payment mechanism
Smart contracts can expose royalty information, but they cannot infer that every transfer is a sale. ERC-2981 lets a contract report a recipient and royalty amount to a marketplace. The standard itself describes payment as voluntary: a venue that does not implement it may complete a transfer without paying the indicated royalty.
Creators should therefore distinguish a royalty preference from enforceable collection logic or a separate contractual claim. Buyers need to account for marketplace fees and any honoured royalty without assuming that the same rules apply on every venue.
Interoperability stops at application boundaries
A compatible wallet may display an ERC-721 token, but that does not make an in-game sword useful in another game. The second application would need to recognise the contract, interpret its metadata and deliberately implement behaviour for it. Art, animation and access-controlled files also depend on the receiving interface knowing how to retrieve and render them.
Moving an NFT to another blockchain usually requires a bridge, custody arrangement or a new representation. That operation adds contracts, signers and message verification; it is not native portability created by the NFT standard. The dependency model in our smart-contract explainer applies to the token and to every bridge or marketplace layered above it.
What the token can credibly support
NFTs are useful when an application needs distinguishable, transferable records: collectibles, tickets, credentials, memberships, game objects or claims against an issuer. Whether the design is worthwhile depends on the full system, not the token label.
- Verify the blockchain, contract address, token standard and token ID.
- Read whether minting, pausing, upgrading or metadata changes remain under administrator control.
- Follow the token URI to the metadata and the metadata to the media.
- Identify the licence, issuer obligations and redemption conditions separately.
- Check approvals before signing; a marketplace operator may receive authority over tokens in the wallet.
- Do not infer authenticity, scarcity or future value from a marketplace badge or an onchain record alone.
An NFT is strongest as evidence of a specific state transition under a specific contract. Claims about art, rights, permanence and utility become reliable only when their offchain dependencies are named and can be checked.
Editorial note: The original 2021 article was replaced on September 3, 2026. This version corrects its claims about indivisibility, immutable metadata, interoperability, royalties and intellectual-property ownership. It is educational content, not legal or financial advice.
