Where Are NFTs Stored? IPFS and Arweave for Beginners

One of the most common misunderstandings about NFTs is the idea that your image lives inside the blockchain. In reality, the blockchain usually stores only a small record that points to your file somewhere else. Knowing where that file actually sits, and how permanent that storage is, matters a great deal if you want your NFT to still display correctly years from now.

This guide explains the two storage systems you will encounter most often, IPFS and Arweave, in plain language for beginners.

What the blockchain actually stores

When you mint an NFT, the blockchain records ownership and a reference called a token URI. That reference is essentially an address that tells wallets and marketplaces where to find the token metadata. The metadata is a small file, usually in JSON format, that holds the name, description, attributes, and a link to the media file such as an image, video, or audio clip.

Storing a full high resolution image directly on a chain like Ethereum would be extremely expensive, so almost no one does it. Instead, the media and metadata are kept on a separate storage layer, and the chain simply points to them. This is why understanding that storage layer is so important.

IPFS: addressing files by their content

IPFS stands for InterPlanetary File System. It is a peer to peer network that uses content addressing. When you add a file to IPFS, the file is hashed and given a unique identifier called a CID, short for Content Identifier. The CID is derived from the content itself, so the same file always produces the same CID, and any change to the file produces a completely different one.

This has a useful side effect for NFTs. Because the link is based on the content, nobody can quietly swap your artwork for something else without breaking the reference. If the file changes, the CID changes, and the mismatch is easy to detect. That property helps prove that an NFT has not been tampered with.

The catch with IPFS: pinning

IPFS does not guarantee that your file stays online forever on its own. A file remains available only while at least one node on the network keeps a copy and continues to share it. Keeping a copy intentionally is called pinning. If every node that pinned your file goes offline, the file can become unreachable, even though the CID still exists.

To avoid this, many creators use pinning services such as Pinata, Filebase, or Storacha, which keep redundant copies available. Because the file is addressed by its CID rather than by a single server location, you can move between pinning services without breaking the NFT. The responsibility for keeping the data alive, however, is ongoing.

Arweave: paying once for long term storage

Arweave takes a different approach. It is designed for permanent storage through a model often described as pay once, store forever. Instead of paying a recurring fee, you make a single upfront payment when you upload your file.

A small portion of that payment compensates the network immediately, and the larger portion goes into a storage endowment. The endowment is intended to pay for ongoing storage over a very long horizon, based on the historical trend of storage costs falling over time. The network advertises that data should remain accessible for at least 200 years under conservative assumptions. The collection of content stored this way is sometimes called the permaweb.

It is worth being precise here. Permanence on Arweave depends on economic assumptions about future storage costs and network incentives holding true. It is a strong long term design, but no system can offer an absolute guarantee across centuries. Treat permanence as a well engineered probability rather than a certainty.

IPFS or Arweave: how to think about the choice

Both systems are widely used and both are far better than storing your media on a single private server that could disappear. The practical difference comes down to how the cost and the responsibility are handled.

• IPFS is flexible and inexpensive to start with, but you, or a pinning service you trust, must keep the file pinned over time. If pinning lapses, availability can suffer.
• Arweave asks for a larger one time payment and aims to remove the ongoing maintenance burden entirely, which suits creators who want a set and forget approach to permanence.

Many creators are comfortable with either option once they understand the tradeoff. The key is to make an informed choice rather than assuming the file is safe automatically.

A quick way to check where your NFT lives

If you already own an NFT, you can often inspect its metadata through a marketplace or a block explorer and look at the token URI. A link that begins with ipfs:// points to IPFS, while a link to an Arweave gateway points to Arweave. If the link points to an ordinary website address on a single domain, your media depends on that one server staying online, which is the least durable option of the three.

Final thoughts

An NFT is more than the entry on the blockchain. The artwork and metadata that give it meaning usually live on a separate storage layer, and the durability of that layer is what determines whether your NFT will still display properly in the future. IPFS and Arweave both solve this problem in thoughtful ways, with IPFS favoring flexibility and Arweave favoring long term permanence.

If you are ready to create and mint your own NFTs without managing this plumbing by hand, the Simple NFT Creator app handles storage and minting for you in a few simple steps. It is available on the App Store and on Google Play.