bored ape nft

Most of us think about files in terms of where they are stored.

When you visit a website, your browser requests a file from a specific server. The URL tells your browser where to find it.

https://example.com/images/logo.png

If that server goes offline, the file disappears. If someone moves the file, every link pointing to it breaks. The Internet has worked this way for decades.

IPFS takes a completely different approach. Instead of asking, “Where is the file?”, IPFS asks, “What is the file?” That simple change makes IPFS one of the most interesting technologies behind Web3.

The Problem with Today’s Web

Traditional websites use location-based addressing.

A URL contains two pieces of information:

  • The server that stores the file.
  • The location of the file on that server.

This works well until something changes.

Servers fail. Companies shut down. Websites reorganize their directories. Broken links become a permanent part of the Internet.

The file itself might still exist, but nobody knows where to find it.

Enter IPFS

IPFS stands for the InterPlanetary File System.

Rather than identifying a file by its location, IPFS identifies it by its contents. When you upload a file, IPFS calculates a cryptographic hash of the file.

The result is called a Content Identifier, or CID. A CID looks something like this:

bafybeigdyr...

The CID is a hash of the file’s contents. Think of a CID as a digital fingerprint. No two different files share the same fingerprint. Even changing a single character produces an entirely different CID.

Finding Files

Suppose you want to download a PDF stored on IPFS. Instead of requesting a file from a particular server, you ask the IPFS network for the file with a specific CID. Every node on the network checks whether it has a copy.

If multiple computers have the file, your computer downloads it from whichever source is available. You don’t care where the file came from. You only care that its fingerprint matches the CID you requested.

That built-in verification gives IPFS an important security advantage.

Why Hashes Matter

Imagine downloading a software installer. If an attacker secretly modifies the file, its contents change.

Because the contents changed, the hash changes.

Because the hash changes, the CID changes.

The modified file no longer matches the original identifier. Your computer immediately knows something is wrong. This is one of IPFS’s greatest strengths. Content cannot be silently replaced without changing its identity.

Efficient Storage

IPFS also reduces duplicate storage. Imagine two people upload the exact same 1 GB Linux installation image. Traditional cloud storage often stores two separate copies.

IPFS recognizes the files are identical because they generate the same CID. Only one copy needs to exist. Everyone simply references the same content.

Breaking Large Files into Pieces

Large files are divided into smaller blocks. Each block receives its own cryptographic hash. Those blocks are then linked together into a larger structure that produces a single CID for the entire file.

This approach offers several advantages. Downloads can come from multiple computers simultaneously. Interrupted downloads resume more easily.

If only part of a file changes, only the affected blocks need to be replaced.

Location vs. Content

Think about borrowing a book. The traditional web says: “Go to Bob’s house and ask for the book.” IPFS says: “Find anyone who owns the edition with this ISBN.”

The location no longer matters. The content does. That shift is the core idea behind IPFS.

Keeping Files Available

One common misconception is that IPFS automatically stores files forever.

It does not.

Files remain available only while someone stores them. If everyone deletes a file, it disappears from the network. To prevent this, users pin important files.

Pinning tells an IPFS node to keep a permanent copy of specific content. Many organizations pay commercial pinning services to ensure their files remain available.

Browsing IPFS

Most web browsers don’t communicate directly with IPFS.

Instead, users often access content through an IPFS gateway.

The gateway retrieves the requested content from the IPFS network and serves it over HTTPS like any other website. From the user’s perspective, it behaves much like visiting a normal webpage.

Why Blockchain Projects Love IPFS

One of the most common uses of IPFS is storing NFT images and metadata. Blockchains are excellent at storing small amounts of permanent information. They are terrible at storing large files.

Imagine placing a 5 MB image directly on Ethereum. Every full node would need to store that image forever. That quickly becomes expensive.

Instead, blockchain applications store only the CID. The actual image lives on IPFS.

A typical NFT works like this:

  1. The image is uploaded to IPFS.
  2. The metadata describing the NFT is uploaded to IPFS.
  3. The blockchain stores the CID of the metadata.

Anyone can verify that the image has not changed because changing the image would generate a completely different CID.

Advantages of IPFS

IPFS offers several important benefits.

  • Files are verified automatically using cryptographic hashes.
  • Multiple computers can serve the same content.
  • Duplicate files consume less storage.
  • There is no single server whose failure makes content unavailable.
  • It works naturally with blockchain applications that need immutable content.

Limitations

IPFS is not perfect. Someone must continue hosting important files. Public content is visible to everyone unless it is encrypted before uploading.

Rarely accessed files may download more slowly than files served by commercial content delivery networks.

Finally, IPFS is not a database. You cannot modify a file in place. Any change creates an entirely new CID.

Final Thoughts

The biggest idea behind IPFS is surprisingly simple. The traditional web asks, “Which server has my file?” IPFS asks, “Who has the file with this exact fingerprint?”

That shift from location-based addressing to content-based addressing makes files easier to verify, more resilient to failure, and better suited for decentralized applications.

Once you understand that single concept, the rest of IPFS begins to make sense.