When a marketplace removes an NFT listing — for a copyright complaint, inappropriate content, or because a project goes abandoned — the item disappears from the interface. Many owners assume this means the NFT was deleted. It wasn't. But understanding what that means requires separating what an NFT actually is into two distinct parts: the on-chain record and the off-chain content it points to. These can have completely different fates.
What an NFT Actually Stores
An NFT is, at its core, a record in a smart contract. The contract tracks a token ID and assigns it to an owner address. When you own an NFT, what you own is an entry in that contract's ledger: your address controls token #X. That contract, once deployed, lives on the blockchain permanently. Blockchain records can't be deleted — they can only be appended to. Every transfer, every price paid, every prior owner is preserved in the chain's transaction history and visible to anyone with a block explorer.
Here's where the confusion starts. The contract record includes something called a tokenURI — a pointer to a JSON file that describes the NFT. That JSON file contains the name, description, traits, and usually a link to the image. Where that JSON file actually lives is a completely separate question from whether the token exists on-chain.
Three Storage Models, Three Durability Levels
Most NFTs use one of three storage arrangements, and they have very different durability characteristics.
Centralized servers. The tokenURI points to something like https://api.projectname.xyz/tokens/4729. If the project shuts down, that server goes offline. The pointer in the contract still exists — but what it points to returns a 404. The blockchain record persists; the content it references doesn't. Many "deleted NFTs" are just link rot. The project ended, the metadata server went dark, and the NFT is now pointing to nothing. The token still exists on-chain.
IPFS. The tokenURI points to an IPFS content hash — something like ipfs://QmXyz.... IPFS is content-addressed, meaning the hash corresponds exactly to the content. But IPFS only makes data available while at least one node is actively pinning it. If the project stops paying for pinning and nobody else picks it up, the content becomes unretrievable. The hash in the contract is permanent; the data behind it isn't guaranteed to be. Unpinned IPFS content doesn't produce a visible "deleted" event — it just quietly becomes unavailable.
Arweave and on-chain storage. Arweave is a permanent storage protocol where data is intended to persist indefinitely through an endowment model. A tokenURI pointing to Arweave is about as close to permanent as off-chain content gets. Fully on-chain NFTs — certain generative art projects store rendering code and traits directly in smart contract storage — sidestep the off-chain problem entirely. That data is as permanent as the chain itself.
What "Burning" Actually Does
Burning an NFT — sending it to a null address like 0x000000000000000000000000000000000000dead — doesn't delete it either. It transfers the token to an address nobody controls. The token still exists in the contract. The burn transaction is permanently on-chain. The NFT has been made practically inaccessible for human use, but the record of its existence, its full transfer history, and every previous owner remains visible on the chain indefinitely.
"Burning" is useful shorthand — it conveys that the token can't be transferred by a legitimate owner anymore. But the word implies destruction, and that's not what happens at the blockchain level.
Where the Constraints Actually Live
The blockchain record itself isn't a meaningful constraint here — permanence is the design. What varies is the content layer.
For centralized storage: durability depends entirely on whoever runs the server. No technical limitation prevents deletion. For IPFS: content is available while at least one node pins it, which can include original owners with the right tools, but in practice projects don't always maintain this. For on-chain and Arweave storage: content durability is essentially equivalent to the underlying protocol's durability.
Ethereum's state itself can't be pruned in a way that would remove existing NFT records under current consensus rules. Archive nodes may become more specialized infrastructure over time, but the data isn't going anywhere in any near-term scenario.
What's Changing
Fully on-chain NFTs have grown as a meaningful category. Projects storing generative code, traits, and sometimes rendered SVG directly in contract storage have become common in the art space — Art Blocks Curated being the notable reference. These sidestep the off-chain metadata problem at the cost of higher deployment gas.
Arweave adoption has increased since the early years when centralized hosting was the default for most collections. Many newer projects explicitly highlight permanent storage as a differentiator.
EIP-4906, adopted in 2023, standardized on-chain events for metadata updates. It doesn't solve the hosting problem, but at least makes metadata changes observable to anyone watching the chain.
What Would Confirm This Direction
More collections adopting permanent storage as a baseline. Marketplace metadata surfacing storage type at the collection level — so buyers can evaluate durability before purchase. Infrastructure making IPFS pinning economically sustainable over long time horizons.
What Would Break It
The "on-chain records are permanent" framing would require a serious revisit only if Ethereum adopted state expiry or history pruning significant enough to affect existing token records. This has been discussed at the research level but would require major consensus changes and would face strong opposition from the ecosystem. Not a credible near-term risk.
Timing Perspective
Now: If you hold NFTs whose metadata lives on centralized servers, that content could become unavailable at any time. It's worth knowing which storage type your assets use — most explorers and marketplaces display this if you look at the raw token metadata.
Next: Permanence is becoming a real differentiator in how collections are marketed. On-chain and Arweave-hosted projects will likely continue gaining relative share.
Later: Whether Ethereum's long-term roadmap introduces any meaningful state expiry is a multi-year research question, not a near-term concern for NFT holders.
What This Doesn't Mean
This covers the technical mechanism — not the legal status of "deleted" NFTs in copyright or ownership disputes, which courts are still working out.
The on-chain record of an NFT's existence is permanent under current blockchain mechanics. Whether the content it points to still exists is a function of storage architecture — and that varies enormously across collections.
