Metadata describes another item rather than necessarily containing the item itself. A digital file may have a name, format, creator, or creation date. In Web3, NFT metadata commonly supplies a token's displayed title, description, traits, and links to images or other media.
How an NFT display is assembled
A token contract can return a metadata reference, often called a token URI. An application retrieves the referenced data, frequently in JSON format, and uses its fields to construct the display. The image may be embedded or fetched from a separate location. Token ownership, metadata, and media are therefore distinct parts of the system.
Metadata can be stored directly onchain, generated by contract logic, hosted on a web server, or referenced through a content-addressed network such as IPFS. Different arrangements create different storage and update dependencies.
Descriptions can change or disappear
A project may allow metadata updates for a reveal, game progression, or other features. Whether changes are possible depends on contract permissions and the referenced storage, not merely on the token being on a blockchain.
A content hash can help verify that retrieved bytes match a reference, but does not ensure their continued availability or the truth of descriptive claims. A creator field alone does not prove authorship, and a listed trait does not guarantee market value.