On-Chain vs Off-Chain NFT Metadata: The Tradeoffs

The metadata that makes an NFT visually meaningful — the image, the attributes, the name — can be stored in many places. The choice has serious implications for permanence, gas costs, and what you can do with the token after launch.

Centralized Server

The simplest option: tokenURI returns a URL like https://api.yourproject.com/tokens/{id}. Fast, flexible, supports reveal mechanics and dynamic updates. The critical flaw: if your server goes down or your company shuts down, every NFT in the collection becomes a broken image link. Not acceptable for anything claiming to be a permanent digital asset.

IPFS

IPFS (InterPlanetary File System) is the most common metadata storage choice. Files are addressed by content hash (CID) — the URL is derived from the file itself, so the content can't change without changing the URL. Metadata stored on IPFS is immutable and decentralized. The catch: IPFS files disappear if no node pins them. IPFS pinning services (Pinata, NFT.Storage) provide persistence, but they're still centralized services that could shut down.

Arweave

Arweave offers permanent storage via a one-time storage fee (paid in AR tokens). Data stored on Arweave is provably permanent — the network's endowment model funds storage in perpetuity. Significantly more durable than IPFS pinning. Used by projects that want to credibly claim their metadata is permanent. Higher cost per file than IPFS.

Fully On-Chain

The ultimate in permanence: metadata stored directly in the smart contract as a base64-encoded data URI. No external dependencies at all. If the blockchain survives, the NFT's metadata survives. Extremely gas-intensive to deploy and store. Practical only for simple metadata (no large images) or where the image itself is SVG generated on-chain.

On-Chain Generation

Projects like CryptoPunks (stored on Ethereum mainnet) and Nouns (fully on-chain SVG generation) prove the on-chain model works. Nouns generates unique, complex SVG artwork from on-chain seed data — zero external dependencies. This is technically ambitious and expensive but creates genuinely permanent digital artifacts.

Hybrid Approach

Store metadata JSON on IPFS or Arweave, but store the IPFS/Arweave hash in the contract as an immutable base URI set at launch. The contract can't change after deployment (unless you build an upgrade path), making the metadata immutable by construction. If you need a reveal, store a placeholder URI first, then set the final URI after reveal. This is the most common approach for serious collections.

Recommendation

IPFS + Pinata/NFT.Storage for most projects. Arweave for projects where long-term credibility matters and you want to avoid IPFS pinning risk. On-chain SVG for projects where the artwork is generated from on-chain data. Never centralized servers for anything beyond the reveal window.