Ask ten people what an NFT is and you'll get ten answers about monkey pictures, overpriced JPEGs, or a cultural moment that came and went. Almost none of those answers describe what an NFT actually is at the protocol level. The picture is not the point. The point is the ledger entry underneath it — a single row, in a specific smart contract, that records one token ID against one wallet address.
Once that mapping clicks, the rest of the subject stops being mysterious. Token standards, metadata, marketplaces, and chain-specific quirks are all layers built on top of one simple idea: a unique ID the blockchain tracks, with one address designated as its current owner. This article walks through that foundation in plain language, without cheerleading and without dismissing the category.
An NFT Is a Token, Not a Picture
NFT stands for Non-Fungible Token: a unique entry in an on-chain ledger that cannot be swapped one-for-one for another identical unit. A dollar bill is fungible — any one dollar is as good as any other. A numbered concert ticket or a serial-numbered property deed is non-fungible, because the specific one matters.
The image, music file, or video you associate with an NFT is almost always stored somewhere else — on a regular web server, on IPFS, or on a storage network like Arweave. The NFT itself is just a ledger record that points to that content. This is why the common beginner line — "I own the JPEG" — is technically wrong. You own the token. The JPEG is a separate question, handled by metadata and storage, and anyone can right-click and save the file whether or not they own the token.
This is closer to owning a numbered deed than owning a painting. The deed proves a specific record exists against your name in a registry. What that record entitles you to — and whether anyone else respects it — depends on the system around it. To understand the difference between interchangeable units and unique ones more broadly, it helps to understand coins and tokens as two different tools on the same chain.
How Ownership Is Actually Recorded
A smart contract is a small program that lives on a blockchain. For NFTs, its main job is almost boring: keep a table of who owns what. In the most common Ethereum standard, that table is literally a data structure called a mapping(uint256 tokenId => address owner) inside the contract's storage. One column is the token ID. The other column is the wallet address that currently owns it.
Transferring an NFT is a transaction that calls a function like transferFrom or safeTransferFrom. The contract checks that you have permission, then overwrites the owner address for that token ID. That's it. No file moves, no picture gets copied — only the row in the table changes.
The globally unique identifier for any specific NFT is the pair (contract address, tokenId). There might be thousands of contracts on Ethereum that each use the number 42 as a token ID, but the combination of the contract's address and that ID points to exactly one asset. This is important to understand because it means your wallet doesn't "hold" the NFT the way it holds a file on your phone. The contract holds the record. Your wallet holds the private key that proves you control the address the contract lists as the owner.
If you want to see the mechanics underneath the transfer itself, it's worth understanding how a blockchain transaction is built, signed, and confirmed — because every NFT move is just one of those, with a specific function call attached.
Token Standards Across Chains
Different blockchains implement the same core idea with different vocabulary. A few are worth knowing by name.
ERC-721 is the original non-fungible token standard on Ethereum, finalized on January 24, 2018 by William Entriken, Dieter Shirley, Jacob Evans, and Nastassia Sachs. One contract typically represents one collection, and each NFT inside it has a unique ID. Almost every early profile-picture project used this standard.
ERC-1155, published on June 17, 2018, is a multi-token standard. A single contract can hold fungible tokens, non-fungible tokens, or both at once, and it supports batch transfers to save on gas. This is common in blockchain games, where one contract might track swords, potions, and unique legendary items side by side.
Solana takes a different approach. An NFT there is an SPL token with a supply of 1, zero decimals, and no mint authority — paired with a Metaplex Token Metadata account that describes it. Structurally it's a tiny fungible token that can never be divided or re-minted, with extra metadata bolted on.
Bitcoin Ordinals, introduced by Casey Rodarmor in early 2023, work without smart contracts at all. Arbitrary content is inscribed onto individual satoshis — the smallest unit of a bitcoin — and ownership follows that satoshi through normal Bitcoin transactions. No contract, no ERC standard, just content riding along on a specific unit of BTC.
The vocabulary differs. The core idea is the same everywhere: a unique ID the chain tracks, with one address designated as its current owner.
Fungible vs Non-Fungible
It's worth slowing down on this distinction because it's the word hiding inside "NFT."
Fungible means interchangeable. Your 1 ETH and my 1 ETH are identical; swapping them changes nothing. A fungible-token contract tracks balances — a mapping from address to a number — and doesn't care about individual units.
Non-fungible means each unit is individually identified and not interchangeable. Token #42 is not Token #43, even if they look alike on the surface. A non-fungible contract tracks owners per ID, not balances per address.
ERC-1155 blurs the line intentionally. In that standard, a given ID can have a supply of 1 — effectively non-fungible — or a supply of a million, effectively fungible. A game might use ID 1 for "gold coin" with a huge supply and ID 2 for "sword of destiny" with a supply of one. Same contract, both behaviours.
What You Own vs What You See
The token lives on-chain. The image, audio, or video it represents usually does not. Most NFTs carry a tokenURI — a URL stored in the contract that points to a JSON metadata file describing the token.
That metadata file is where the name, the description, the image link, and any traits live. It might be hosted on IPFS, on Arweave, on a normal web server the project runs, or — occasionally, for smaller or more ambitious projects — fully on-chain. Where it lives matters a lot for long-term durability, but that's a topic for another article.
What a transfer actually gives the buyer is the on-chain token and whatever rights the project creator chose to attach to it. Sometimes that's a commercial license. Often it's nothing beyond the on-chain record itself. The token is real and verifiable. What that token entitles you to in the outside world is a separate question handled by the project's terms, not by the blockchain.
Why This Matters in Practice
NFTs are not just profile pictures. The same primitive — a unique ledger entry tied to an address — is used for domain names like ENS, event tickets, in-game items, music-rights tokens, and deed-like records for real-world assets. The artwork boom of 2021 was one use case. It wasn't the category.
Because ownership is a line in a public ledger, NFTs work across wallets, marketplaces, and apps without a central operator. No platform has to grant you permission to move your token; the contract does, based on whether you can sign with the right key. Understanding what a crypto wallet actually stores makes this concrete: the wallet stores keys, and the keys are what the contract checks.
The self-custody rule from coin-land still applies, and it bites harder with NFTs because a single asset can't be split or partially recovered. If someone else controls the private key for the address that holds your NFT, they control the NFT. Seed-phrase hygiene, hardware-wallet use, and scam-awareness all matter at least as much here as they do for fungible crypto — arguably more, since a drained NFT wallet can't be refilled from a paycheck the way a checking account can.
Reframing NFTs as "unique ledger entries" makes the whole category easier to reason about. JPEGs are one use case. Tickets, names, deeds, and game items are others. Some will matter in ten years; some won't. But the underlying primitive — a wallet address mapped to a token ID inside a contract — is a genuinely new kind of record, and it isn't going anywhere.
Key takeaways
- An NFT is a unique ledger entry, not a file. Ownership is a row in a smart contract's storage that maps a token ID to your wallet address.
- The image or media is usually off-chain. The token points to metadata, which points to the file — three separate layers that can fail independently.
- Token standards vary by chain — ERC-721, ERC-1155, Solana SPL + Metaplex, Bitcoin Ordinals — but the core idea is identical across all of them.
- A transfer just rewrites the owner field for that token ID. Whoever controls the private key for the listed address controls the NFT, full stop.
- NFTs are a general-purpose primitive. Art is one use case; domain names, tickets, and in-game items are others — judge each on its own merits.
