IPFS vs. Filecoin: How the Two Protocols Actually Relate

"Isn't IPFS just Filecoin?" is one of the most common mix-ups in this space, and it's an understandable one: both came out of Protocol Labs, both use content addressing, and both show up in the same sentence constantly. But they solve genuinely different problems, and understanding where one stops and the other starts clarifies a lot about how AIOZ Pin, and pinning services generally, actually fit into this picture.

TL;DR:

• IPFS and Filecoin are separate, complementary protocols, both created by Protocol Labs, but you can use either one without the other
• IPFS handles content addressing and transfer: turning data into CIDs and moving it between peers. It has no built-in payment or incentive layer
• Filecoin adds exactly that missing piece: a blockchain-based market where storage providers get paid, with cryptographic proofs, to persist data long-term
• A pinning service like AIOZ Pin solves the same "who guarantees this stays available" problem Filecoin solves, but through a direct pay-as-you-go relationship rather than an on-chain storage-deal market
• Content stored via a Filecoin deal is still addressed the same way IPFS addresses everything, by CID, which is part of why the two get conflated so often

Two Protocols, One Shared Origin

IPFS and Filecoin were both created by Protocol Labs, and that shared origin is a real part of why they get confused. But per Protocol Labs' own framing, they are "two separate, complementary protocols," and critically, "these components are separable, you can use one without the other." Using IPFS to address and move data doesn't require touching Filecoin at all, and a Filecoin storage deal doesn't require anything IPFS-specific beyond the content-addressing model both systems share.

What Each One Actually Does

IPFS is a protocol for content addressing and transfer. It lets peers "store, request, and transfer verifiable data with each other." Every piece of content gets a CID derived from its own hash, and IPFS's job is finding and moving that content between whoever has it and whoever's asking. What it deliberately does not include is any mechanism for guaranteeing a specific piece of content stays available long-term, or paying anyone to keep it around.

Filecoin is "designed to provide a system of persistent data storage." It's a blockchain network where storage providers commit to storing specific data for a specific duration, in exchange for payment, and prove they're actually still holding it through cryptographic mechanisms the network can verify without trusting the provider's word. Put simply: "IPFS addresses and moves content, while Filecoin is an incentive layer to persist data."

Where the Confusion Actually Comes From

Content stored through a Filecoin deal is still addressed by CID, the exact same content-addressing model IPFS uses everywhere. That shared addressing layer is real and not a coincidence, Filecoin builds on IPFS's data model rather than inventing its own. But sharing an addressing scheme isn't the same as being the same system: you can compute a CID, publish content, and retrieve it entirely within IPFS's own peer-to-peer network, with no Filecoin storage deal, no FIL token, and no blockchain involved anywhere in that flow.

Where a Pinning Service Fits Into This Picture

IPFS alone doesn't guarantee your content stays available, someone has to actively keep hosting it, and nothing in the base protocol pays anyone to do that. That's the exact gap both Filecoin and a pinning service exist to close, just through different mechanisms:

• Filecoin solves it through an on-chain storage-deal market: providers bid, commit for a fixed duration, and prove continued storage cryptographically on a blockchain.
• A pinning service like AIOZ Pin solves the same underlying problem through a direct relationship instead: you pay for pinning, the service guarantees persistence through its own infrastructure, no blockchain storage deal or on-chain proof mechanism involved in the actual pinning transaction.

Neither approach is "the real IPFS way," they're two different answers to the same missing-incentive-layer problem, and a project can reasonably choose either depending on whether it wants a decentralized storage-deal market or a direct, managed relationship with a provider.

Side by Side

Frequently Asked Questions

Is Filecoin required to use IPFS? No. IPFS and Filecoin are separable, per Protocol Labs' own description. You can address, store, and retrieve content on IPFS's peer-to-peer network without any Filecoin storage deal.

Is IPFS required to use Filecoin? Filecoin builds on IPFS's content-addressing model, but using Filecoin's storage-deal market doesn't require running your own separate IPFS retrieval infrastructure, the two are complementary, not strictly dependent on each other in either direction.

Does IPFS pay anyone to store my content? No. IPFS has no built-in payment or incentive layer. Persistence depends entirely on some node actively choosing to keep hosting your content, which is exactly the gap Filecoin and pinning services each address differently.

Is AIOZ Pin built on Filecoin? No. AIOZ Pin is a pinning service, it guarantees persistence through a direct, pay-as-you-go relationship on its own DePIN infrastructure, not through Filecoin's on-chain storage-deal market.

Why do people confuse IPFS and Filecoin so often? Both were created by Protocol Labs, both use the same CID-based content-addressing model, and Filecoin-stored content is still addressed the IPFS way, that shared foundation makes the two easy to conflate even though they solve different problems.

Related Reading

• How IPFS Really Works: Merkle DAGs, Chunking, and Routing - the addressing and transfer mechanics this article assumes
• Understanding IPFS Pinning Services - the pinning-service side of the persistence problem this article compares against Filecoin
• IPFS Garbage Collection: What Unpinning Actually Does - why persistence isn't automatic without something like pinning or a Filecoin deal
• How AIOZ Pin Works: Pinning, Gateways, and NFT Tools - AIOZ Pin's actual mechanism for guaranteeing persistence

References

• IPFS Docs: Frequently Asked Questions
• Filecoin Docs: What Is Filecoin?