On-Chain Tokens, Metadata, Storage Layers

The Question: What NFT Art Actually Is

When someone asks what NFT art is, they usually mean the visual asset displayed in marketplaces and wallets. The technical answer is different: an NFT is a token on a blockchain that points to metadata, which points to an image file stored somewhere else.

That distinction matters because most NFT images are not stored on the blockchain. The blockchain stores a unique identifier and a URL. The art itself lives off-chain.

Where that art lives, who maintains it, and what happens when storage providers fail determines whether your NFT displays properly or breaks into a 404 error.

How NFT Art Architecture Actually Works

An NFT consists of three layers: the on-chain token, the metadata JSON file, and the artwork file. Each layer has a different job and a different failure mode.

The On-Chain Token Layer

The token on Ethereum or another blockchain is just a unique identifier and a pointer. On Ethereum, an ERC-721 token contains a tokenURI, which is a URL that leads to a JSON file containing the metadata.

Smart contracts use mappings where _owners maps each tokenId to its current holder, _balances tracks ownership counts, and _tokenURIs acts as a pointer. That pointer is usually an IPFS hash or an HTTPS URL to a structured JSON object that describes the asset’s attributes.

The token itself does not contain the image. It contains a reference.

The Metadata JSON Structure

Metadata is typically in JSON format. It includes fields such as name, description, image URL, and other attributes like traits or rarity information.

A typical metadata file looks like this:

Example metadata JSON:

• name: “Cool Cat #1234”
• description: “A cool cat NFT”
• image: “ipfs://QmX…abc123” or “https://example.com/images/1234.png”
• attributes: [{“trait_type”: “Background”, “value”: “Blue”}]

The image field is another pointer. It tells wallets and marketplaces where to fetch the actual artwork file.

Most explainers skip this step. They treat the metadata as trivial. It’s not. The metadata is the second link in a chain, and if that link breaks, the NFT becomes undisplayable even though the blockchain token remains valid.

The Artwork Storage Layer

The artwork file itself lives somewhere off-chain in most projects. Storage options include IPFS with pinning services, Arweave, centralized servers like AWS or Google Cloud, or full on-chain storage for small files.

Each option has trade-offs in cost, permanence, and speed.

Where NFT Images Actually Live

On-Chain Storage: Permanent But Expensive

On-chain metadata is stored directly in the smart contract on the blockchain. It’s permanent and censorship-resistant but expensive due to high gas costs.

Storing data on Ethereum is expensive, which limits on-chain NFTs to small file sizes. Typical on-chain projects use generative SVG art, ASCII art, or text-based content. High-resolution images, videos, and 3D models are impractical to store fully on-chain at current costs.

Projects like Nouns store all artwork as on-chain SVG. The entire image is encoded in the contract. When you query the tokenURI, you get a data URI with the SVG embedded. No external dependencies.

This is the only truly permanent option, but it’s cost-prohibitive for most projects.

IPFS With Pinning Services: Semi-Permanent

IPFS (InterPlanetary File System) with pinning services like Pinata or nft.storage offers semi-permanent storage. Costs range from $0 to $20 per month depending on data volume. Speed is fast via gateways, and this is the most common option for NFT projects.

IPFS stores content by hash (CID), not by location. If you have the CID, you can retrieve the file from any node that has pinned it. The problem: to keep files alive on IPFS, you need pinning. Pinning tells a node to keep a specific piece of content and not discard it.

You can run your own node and pin files yourself, or use a pinning service. These services charge recurring fees. Third-party pinning services like Pinata charge $0.48 per GB per year based on their current plans.

The permanence of your IPFS content depends on whether someone keeps paying. If the pinning service shuts down or stops being paid, the content can disappear from IPFS.

Arweave: Permanent Storage With A One-Time Fee

Arweave offers permanent storage with a one-time fee. As of 2026, storing 1 MB costs approximately $0.002 to $0.005 in AR tokens. For a typical NFT with a 5 MB image and 2 KB of JSON metadata, you’re looking at roughly $0.01 to $0.03 for permanent storage.

Arweave guarantees data storage for at least 200 years, or as long as the endowment exists. Data stored on Arweave can be kept for at least 200 years based on the current economic model.

On Solana, the Metaplex standard prefers Arweave storage. Most Solana tooling defaults to Arweave uploads. This is the best option for high-value collections and projects that want genuine permanence without recurring costs.

For a 50 MB collection over 10 years, IPFS Pinata at $20 per month costs $2,400 total. Arweave one-time costs approximately $150. Arweave wins at seven years or longer.

Centralized Servers: Fast And Fragile

Centralized servers like AWS, Google Cloud, or project-owned hosting are the fastest option with standard hosting costs. They also carry the highest risk: NFT metadata can be deleted, modified, or become unavailable if the company shuts down or changes policy.

A Pinata analysis found that 27% of top collections relied on centralized hosting. Some metadata links already disappeared.

Amazon Web Services removed hosting for multiple NFT projects in 2024 due to policy violations. Those NFTs broke permanently.

What Breaks When Storage Fails

NFT storage has failed repeatedly over the last four years. The pattern is consistent: a gateway shuts down, a hosting provider changes policy, or a pinning service stops being paid. The NFT token remains on the blockchain, but the image becomes unreachable.

Documented Storage Failures

Infura deprecated its public IPFS gateway in August 2022. Thousands of projects had hardcoded Infura’s hostname into their token metadata. Those tokens broke permanently because the address written into the chain pointed at a company, not at content.

Cloudflare shut down its public IPFS gateways in May 2024 and redirected all traffic to ipfs.io and dweb.link. NFT.Storage decommissioned uploads in June 2024, telling users that retrieval would keep working but that latency and availability “may degrade over time.”

In March 2023, the Magic Eden marketplace discovered that several popular Solana NFT collections had lost their images due to expired hosting on centralized servers. This affected thousands of NFTs with a combined value of millions of dollars.

The Evolved Apes project in October 2021 saw the anonymous developer disappear with $2.7 million and shut down the project’s website and storage servers. This rendered 10,000 NFTs effectively worthless overnight. The blockchain still recorded ownership of these tokens, but the absence of accessible metadata and images meant that marketplaces could not display the NFTs properly.

Nike’s RTFKT stored CloneX NFT art on Cloudflare-proxied servers. When access restrictions were applied in April 2025, the entire collection’s images became unreachable. Holders owned tokens pointing to broken URLs. This affected a collection worth hundreds of millions.

CryptoPunks temporarily displayed blank images due to server migration issues in 2022, affecting 12,000 assets.

How Common Broken NFTs Are

A 2022 study that sampled roughly 498,000 NFTs found about 20% already broken: unresolvable metadata, dead image paths, IPFS links that no longer resolved.

Interplanetary Shipyard wound down IPFS maintenance on September 30, 2026. Projects relying on that infrastructure faced retrieval degradation.

The Cascading Failure Path

Here’s how an NFT breaks:

1. The tokenURI points to a metadata JSON file at a specific hostname or gateway.
2. That hostname goes offline (company shutdown, policy change, unpaid bill).
3. The metadata JSON becomes unreachable.
4. Wallets and marketplaces can’t load the image URL.
5. The NFT displays as a broken link or placeholder.

Even if the image file still exists somewhere on IPFS, the metadata pointer is broken, so wallets don’t know where to look.

One saving grace: if the URL contains /ipfs/ followed by a CID, the CID can be extracted and re-pinned. The art is rescuable even after the hostname dies. But this requires manual intervention and technical knowledge most holders don’t have.

How To Verify NFT Storage Before Buying

If you’re deploying capital into NFT flipping or royalty-generating projects, you need to verify storage before purchase. Here’s the sequence.

Step 1: Find The TokenURI

Go to Etherscan or the relevant block explorer. Look up the contract address. Call the tokenURI function for the specific token ID. This returns the metadata URL.

Step 2: Check The Metadata Format

If metadata starts with ipfs://, the project is using IPFS. Extract the CID and check if it’s pinned on a service like Pinata or NFT.Storage.

If it starts with arweave.net/ or ar://, it’s permanently stored on Arweave. This is the most reliable option.

If it starts with https:// from a company domain like opensea-creatures.com or mysteryproject.io, it’s centralized hosting. This is the highest risk.

Step 3: Test The Image URL

Load the metadata JSON. Check the image field. Try loading the image URL directly in your browser.

If it fails to load, the NFT is already broken. If it loads but points to a centralized server, it could break at any time.

Step 4: Check For Hostname Dependency

If the metadata or image URL includes a specific hostname (like gateway.pinata.cloud or cloudflare-ipfs.com), the NFT depends on that company staying online. If the hostname dies, the link breaks even if the content survives somewhere on IPFS.

This is exactly what broke tokens in the Infura shutdown.

When Storage Risk Matters And When It Doesn’t

Storage risk matters when you’re holding NFTs for the long term, when you’re building creator royalty income streams, or when you’re deploying significant capital into a collection.

If the project uses centralized hosting, the images could disappear at any time. If the project uses IPFS without a clear pinning commitment, the images could degrade over time as nodes drop the content.

Storage risk doesn’t matter much if you’re flipping NFTs on a short time horizon (days to weeks). The images will likely stay live long enough for you to exit the position.

It also doesn’t matter if the project is fully on-chain. Projects like Nouns, Autoglyphs, and some generative art collections store everything in the contract. Those NFTs are as permanent as Ethereum itself.

The Cost Break-Even For Permanence

For projects choosing between IPFS and Arweave, the break-even point is around seven years. IPFS pinning costs $20 per month for moderate storage. That’s $240 per year or $1,680 over seven years.

Arweave charges a one-time fee. For a 50 MB collection, that’s roughly $150 total. After seven years, Arweave is cheaper. After ten years, it’s dramatically cheaper.

If you’re launching a project, use Arweave for anything meant to last. If you’re buying into a project, check whether it’s using Arweave or committed IPFS pinning with a funded plan.

The Illusion Of Permanence

Most NFTs do not store images on-chain. A common misconception about web3 storage is that an NFT’s image or underlying metadata is stored on the blockchain. In most NFT projects, the token’s metadata is usually not stored on the blockchain.

Instead, the token’s unique identifier (or ID) is stored on-chain. The metadata and image live off-chain, pointed to by that identifier.

This creates a multi-layered architecture with several potential failure points. The loss of any single component can break the entire NFT’s functionality.

Arweave and IPFS attempt to bridge the gap, though IPFS still suffers from the “pinning problem” where data can be lost if not actively maintained by third parties.

Metadata-Only Versus Full On-Chain

Some projects store metadata on-chain but host images off-chain. This is a middle ground: the traits and description are permanent, but the visual still depends on external hosting.

Other projects store everything on-chain. This is rare and expensive but the only option with true permanence.

The difference matters for royalty enforcement and long-term value. If the image breaks, the NFT loses its visual identity even though ownership remains intact.

ERC Standards And Metadata Flexibility

The ERC-721 standard does not dictate how or where an NFT’s metadata should be stored. It might be stored on a centralized server, via decentralized file storage like IPFS, or on the blockchain itself using smart contract data storage.

ERC-721 typically gives each token its own metadata URI, set individually or derived from the token ID.

ERC-1155 defines a single URI template with an {id} placeholder that clients substitute at query time. One string like https://example.com/metadata/{id}.json serves every token type in the contract.

Both standards are storage-agnostic. They define the pointer mechanism but not the storage layer.

The Takeaway

NFT art is a three-layer system: a blockchain token that points to a metadata file that points to an image file. Most images live off-chain on IPFS, Arweave, or centralized servers.

IPFS with pinning offers semi-permanent storage for $0 to $20 per month. Arweave offers permanent storage for a one-time fee of $0.01 to $0.03 per typical NFT. Centralized servers are fast but fragile.

A 2022 study found 20% of sampled NFTs already broken due to storage failures. Infura, Cloudflare, and NFT.Storage gateway shutdowns broke thousands of collections. Amazon Web Services policy changes removed hosting for multiple projects in 2024.

Before deploying capital into NFT flipping or royalty income projects, verify the storage layer. Check the tokenURI, identify the storage type, and test the image URL. If metadata starts with ipfs://, check pinning. If it starts with arweave.net/, it’s permanent. If it starts with https:// from a company domain, it’s centralized and could break.

For a 50 MB collection, IPFS costs $2,400 over 10 years. Arweave costs $150 one-time. Arweave wins at seven years or longer.

The only truly permanent option is full on-chain storage, used by projects like Nouns. Everything else depends on someone paying to keep the servers running.

Frequently Asked Questions

Is NFT art stored on the blockchain?

No, in most cases. The blockchain stores a token with a unique identifier and a pointer (URL) to metadata. That metadata contains another pointer to the image file, which typically lives on IPFS, Arweave, or centralized servers. Only a small percentage of NFT projects store the actual artwork on-chain due to high storage costs on blockchains like Ethereum.

What happens if IPFS storage fails for my NFT?

If the IPFS pinning service stops being paid or shuts down, your NFT image can become unreachable. The token still exists on the blockchain, but wallets and marketplaces can’t display the image. If the metadata contains a content identifier (CID) rather than a hostname, the content can be re-pinned by someone else, but this requires manual intervention.

Which NFT storage method is most permanent?

Full on-chain storage is the only truly permanent option, where the entire image is encoded in the smart contract. Arweave is the next best option, guaranteeing storage for at least 200 years with a one-time fee. IPFS with committed pinning offers semi-permanence as long as someone continues paying for the pinning service.

How do I check where an NFT’s image is stored?

Look up the contract on a block explorer like Etherscan and call the tokenURI function for the specific token ID. This returns the metadata URL. If it starts with ipfs://, it’s on IPFS. If it starts with arweave.net/, it’s on Arweave. If it starts with https:// from a company domain, it’s centralized hosting.

Why do some NFTs show broken images?

NFTs show broken images when the storage layer fails. This happens when IPFS pinning services shut down, centralized hosting providers remove content, or payment for storage services lapses. A 2022 study found roughly 20% of sampled NFTs already had broken metadata or image links due to storage provider failures.