You use Sui’s Object Display Standard to tell wallets and marketplaces exactly how to show your objects (like NFTs) by registering a “Display” for your Move type and mapping friendly keys—typically name, description, and image_url—to fields or computed values from your object; in practice, you define your object type in Move, publish your package, create a Display for that type (via the 0x2::display module), set the template values (e.g., map name → MyNft.title, image_url → MyNft.image), and wallets will read those keys to render consistent cards, lists, and details without hard-coding your schema; you can also include optional keys (like link, project_url, or traits) and update the display later to fix images or metadata without changing the on-chain object itself