If you bought an NFT that linked to an IPFS address, I have bad news: you now own a broken promise. The InterPlanetary File System, the protocol that was supposed to liberate the web from centralized servers, is quietly sunsetting. And the reason isn’t a lack of money—it’s a lethal overdose of it.
IPFS raised $270 million from venture capitalists who believed in a decentralized future. But the money didn’t build a protocol. It built a confusing, bloated ecosystem that looked suspiciously like the thing it was supposed to replace: a centralized, corporate-controlled file distribution network.
“The protocol designed to distribute control ended up depending on a single company and a pile of VC cash to survive.”
Look at the project’s own list of components: Kubo, Helia, Boxo, Rainbow, IPFS Desktop, IPFS Companion, Someguy, Service Worker Gateway, IPFS Check, libp2p, ipfs.io, dweb.link, check.ipfs.network, delegated-ipfs.dev, Wikipedia-on-IPFS. It’s a mess. As one commenter noted, “It feels like the AWS of file distribution, so much stuff so confusing.”
IPFS wasn’t killed by a competitor. It was killed by its own success at raising money. The VC dollars created a bloated organization that chased every possible use case—NFTs, static websites, data storage—without nailing a single one. The result? A fragmented ecosystem that confused developers and priced out grassroots adoption.
“When your decentralized protocol needs a centralized company to keep the lights on, you’ve failed the first test.”
The irony is brutal. IPFS was supposed to be the infrastructure of a new, permissionless internet. Instead, it became a $270 million monument to the idea that money alone doesn’t build ecosystems. It builds feature bloat, internal politics, and a single point of failure.
Ask yourself: when was the last time you actually used IPFS directly? Most people experienced it through Cloudflare’s gateway—and when Cloudflare dropped support, the writing was on the wall. The protocol’s only remaining major use case was NFTs, and that’s a market built on speculation, not utility.
“The lesson is brutal: money doesn’t build ecosystems. Focus does. And IPFS had everything except focus.”
To the builders and investors still celebrating the next big web3 fundraise: look at IPFS. $270 million, a dream of an interplanetary file system, and a future of broken links and abandoned projects. The graveyard is full of projects that thought money could substitute for a clear, sustainable business model. IPFS is just the latest tombstone.
FAQ
Q: Wasn't IPFS just a victim of the crypto winter?
A: No. The crypto winter exposed the fragility, but the root cause was overcapitalization. Too much money led to feature bloat, a confusing ecosystem, and no sustainable business model. IPFS died long before the market turned.
Q: What should other web3 projects learn from this?
A: That raising venture capital is not a strategy. Without a focused, revenue-generating use case, money becomes a liability. Build for one thing, nail it, and let the ecosystem grow organically—not through a corporate bloatfest.
Q: Isn't IPFS still used by some projects?
A: Some projects still use IPFS, but the core maintainers are winding down support. The protocol is effectively abandoned. Any project relying on it now faces a future of broken links and no long-term maintenance. Migration is urgent.