NFTs (Non-Fungible Tokens) prompted countless buyers to spend tens of thousands — sometimes millions — of dollars on JPEG images during the 2021 bull market, yet few buyers genuinely understood what they had purchased. This isn't a critique but an observation about the cognitive gap the technology itself creates: the distance between an NFT's name, its marketing language, and the actual legal rights it conveys to buyers is far wider than most people recognize. This article tries to close that gap.
When you buy an NFT, what you receive on-chain is a unique Token ID and a link pointing to an external resource (typically a metadata URI). The token records your wallet address as its current owner, and that ownership record exists on an immutable blockchain. This is what you genuinely 'own': an on-chain ownership record.
The problem is that this on-chain token typically does not contain the image or video you think you bought. The reason is simple: storing large files on-chain is prohibitively expensive, so the vast majority of NFT media content (images, audio, video) lives off-chain — usually on centralized cloud storage (AWS S3, etc.) or decentralized storage (IPFS, Arweave). Your NFT token is simply a URL pointing to that external file. If that external server goes down, or that domain expires, your NFT points to a 404 page. This has a name: 'Link Rot' — and documented real cases have already occurred. IPFS-stored NFTs are somewhat more resilient — IPFS addresses by content hash, and files persist as long as someone continues pinning them, even if the original uploader disappears — but this is not a permanent guarantee either.
Using Ethereum's dominant ERC-721 standard as the example, a complete NFT's technical structure is: a Smart Contract address (the Collection contract, such as Bored Ape Yacht Club's contract address) plus a tokenId (that NFT's unique identifier within that contract). Together, these two elements uniquely identify the NFT across the entire chain. The contract also includes a tokenURI function returning a URL pointing to the token's metadata (typically JSON format), which contains the image/animation URL and attribute list (like BAYC's hat, eyes, and other Traits). The actual image file is a third layer of content pointed to by that metadata URL — and can have no direct relationship with the chain itself. More secure approaches include On-chain Metadata (storing metadata and image data directly in the contract as Base64 encoding) or using IPFS Content Hashes rather than mutable HTTP URLs. Nouns DAO is the leading example of a fully on-chain image generation project — relying on no external servers whatsoever.
This is where most confusion occurs. Buying an NFT gives you ownership of the on-chain token — this is not the same as copyright in the image. Copyright is legal protection that creators automatically acquire upon creation, giving the copyright holder exclusive control over reproduction, distribution, and derivative works. Unless the creator explicitly transfers copyright to the buyer via formal legal documentation at the point of sale, copyright remains with the creator. Using Bored Ape Yacht Club as an example: Yuga Labs grants BAYC holders a 'Commercial License' for their specific ape's image in its terms of service — meaning you can open a restaurant, print T-shirts, or build a brand using your ape's image, but you do not own the copyright to that image. Once you sell the NFT, this commercial license transfers to the next buyer — it doesn't stay with you. By contrast, many smaller NFT projects have no clear licensing terms at all — the token you purchased may carry no explicit commercial use license, let alone a copyright transfer.
Beyond speculative digital art trading, NFTs have several genuinely meaningful practical applications. On-chain ownership proof applications: event tickets (NFT tickets can track resale, limit scalping, allow organizers to collect secondary market royalties); gaming item ownership (players genuinely 'hold' items rather than relying on an entry in a game company's database — items persist on-chain even after a game shuts down); proof of ownership for physical assets (real estate, fine art Tokenization, though legal frameworks are still developing). Documented failure modes: during the 2022 bear market, multiple NFT marketplaces (including OpenSea competitors) shut down, and NFT metadata and images that depended on their servers disappeared; multiple well-known NFT game projects' server shutdowns rendered in-game item NFTs functionally meaningless despite remaining technically on-chain; multiple NFT projects' IPFS files degraded over time as no one continued pinning them.
If you plan to buy or already hold NFTs, several practical frameworks are worth establishing. First, investigate 'what you're actually buying' before purchase: where does the metadata and image live (IPFS? Arweave? Centralized server)? What is the project's long-term commitment to storage? Are licensing terms explicit? Second, distinguish 'speculative purchases' from 'functional purchases': if you're buying an NFT because you believe in its market liquidity and future appreciation, you're taking on pure market sentiment risk — largely unrelated to the NFT's technical merits. If you're buying an NFT for a concrete function (ticket, gaming item, community access), verify that function doesn't depend on a centralized server continuing to operate. Third, NFT market liquidity is extremely asymmetric: floor prices rise continuously in bull markets and can find essentially no buyers in bear markets. NFTs are not liquid assets you can sell at will — position sizing must account for this liquidity reality.