Real-World IPFS Case Studies: Audius and LikeCoin
Most explanations of IPFS stay abstract: content addressing, decentralization, censorship resistance. Two of IPFS's own documented case studies, Audius and LikeCoin, show what that actually looks like built into a real, functioning platform. Both are worth a direct look, not because their numbers are current (they're not, both case studies date to 2020 and this article is upfront about that), but because the architectural problem each one solved is still exactly the same problem any project storing user-generated content or verifiable metadata runs into today.
TL;DR:
- Audius, a decentralized music streaming platform, used IPFS's content addressing specifically to solve deduplication: identical audio content uploaded by different users gets the same CID and gets stored once, not once per uploader
- LikeCoin, a blockchain-based content-attribution system, built two custom plugins tying IPFS directly into its own chain, so any IPFS node could resolve blockchain-associated metadata without a separate lookup system
- Both case studies are dated (Audius's own figures are from July 2020, LikeCoin's from October 2020), their numbers shouldn't be read as current, but the architecture each one settled on is still a reasonable reference pattern today
- The common thread in both: neither company built its own deduplication or content-verification system from scratch, they built on a property IPFS already provides
- Both patterns map directly onto simpler AIOZ Pin use cases: deduplication matters for any app storing user-uploaded media, and metadata-to-content association matters for any NFT or on-chain project relying on off-chain files
Audius: Solving Deduplication at Platform Scale
Audius stores tracks and metadata through IPFS, registers content on smart contracts, and indexes it through a discovery layer, a fairly typical decentralized-app architecture. The specific IPFS benefit the platform's own case study calls out isn't decentralization in the abstract, it's a concrete deduplication guarantee: "every segment of content is guaranteed to be unique," and identical audio content, however many different users upload it, resolves to the same CID rather than getting stored as separate copies per uploader. The team's own framing of this is direct: they didn't have to build a content-deduplication system, or a separate metadata-sync layer to keep everything consistent, "something we didn't have to even think about with IPFS," because it's a property that falls directly out of content addressing rather than something the platform had to engineer on top.
Worth being clear about the numbers here: Audius's own case study cites roughly 5 million CIDs, 3.5 terabytes stored, and 40,000 registered users, and explicitly dates that snapshot to July 2020. Six years is a long time for any active platform's numbers to hold steady, treat those figures as illustrative of scale at one point in time, not as Audius's current footprint.
LikeCoin: Wiring IPFS Directly Into a Blockchain
LikeCoin took a structurally different approach: rather than using IPFS alongside a blockchain, it built two custom plugins that couple the two together directly. iscn-ipld associates LikeCoin's own metadata standard (ISCN) with IPFS-stored content at the data-model level, and ipfs-cosmosds lets an IPFS node delegate metadata queries straight to the LikeCoin chain when a CID references chain-associated data. The practical result: every LikeCoin blockchain node, not just validators, runs an embedded IPFS node, so metadata resolution and content storage aren't two separate systems a client has to reconcile, they're one integrated lookup path. The case study frames this explicitly as an IPLD-enabled pattern, using IPLD as what it calls a "blockchain intermediary," so any IPFS node, not just LikeCoin-specific infrastructure, can resolve the association.
LikeCoin's own case study is dated October 2020, with the same caveat as Audius: read the architectural pattern as the durable part, not any specific metric attached to it.
What Both Have in Common
Neither team built a bespoke solution to the problem they actually had. Audius needed to avoid storing the same audio content redundantly across thousands of uploads, content addressing gave it that for free. LikeCoin needed a way to tie arbitrary metadata to content in a way any node could resolve without a custom API, IPLD gave it that directly. In both cases, the interesting engineering work was in how deeply each team integrated with IPFS's existing properties, not in building something IPFS doesn't already provide.
The Same Patterns at Smaller Scale
Neither pattern requires Audius-scale infrastructure or LikeCoin-level custom tooling to be useful. Deduplication matters the moment any app lets multiple users upload potentially identical media, a marketplace where the same stock asset gets used across many listings, for instance, benefits from the exact same property Audius relied on, without needing to build anything to get it. And the metadata-to-content association LikeCoin engineered custom tooling for is, at a smaller scale, exactly what an NFT project already gets by referencing a CID directly from on-chain metadata, no custom plugin required, because the association is inherent to how content addressing works in the first place.
Frequently Asked Questions
Are Audius's and LikeCoin's IPFS usage numbers still current? No. Audius's figures are dated to July 2020 and LikeCoin's to October 2020, both explicitly noted in their own case studies. Treat them as illustrative of scale at a point in time, not current metrics.
What specific IPFS property did Audius rely on? Content-addressed deduplication: identical audio content uploaded by different users resolves to the same CID and gets stored once, rather than once per uploader.
How did LikeCoin integrate IPFS with its blockchain? Through two custom plugins, one associating its metadata standard with IPFS content at the data-model level, one letting an IPFS node delegate metadata queries directly to the LikeCoin chain.
Do I need custom tooling like LikeCoin's to get metadata-to-content association? Not at a smaller scale. Referencing a CID directly from on-chain NFT metadata already gets you that association inherently, since it's a property of content addressing itself, not something that needs separate engineering.
Why does deduplication matter for an app with user-uploaded content? Without it, identical files uploaded by different users get stored as separate copies, wasting storage. Content addressing means identical content always resolves to the same CID and gets stored once, automatically.
Related Reading
- How IPFS Really Works: Merkle DAGs, Chunking, and Routing - the content-addressing mechanics behind the deduplication property both case studies rely on
- IPLD: The Data Model Underneath IPFS's Merkle DAG - the data model LikeCoin's integration builds directly on
- Content Addressing for NFTs: How to Verify a CID Yourself - the same metadata-to-content association pattern, at NFT scale
- How to Host a Static Website on IPFS, and Why It Needs Pinning - a smaller-scale, practical companion to the platform-level architectures covered here
References
Related Content
IPFS Is Rate-Limiting Public Gateways: What Changes for You
Free public IPFS gateways are being rate-limited on purpose, not as a bug. Here is exactly what IPFS's own blog says is changing, and what to actually do.
Real-World IPFS Case Studies: Audius and LikeCoin
Two real, documented IPFS deployments, a media platform and a blockchain publisher, and the specific architectural problem each one solved with it.
How to Host a Static Website on IPFS (and Why Pin It)
Uploading a site to IPFS is the easy part. Here is the full picture: CID, gateway access, a real domain, and the pinning step most tutorials skip.
What Happens to Your Files If You Stop Using AIOZ Pin
Cancelling a pinning service is not documented the way it should be, anywhere in the industry. Here is exactly what you can control before you stop paying.
Types of IPFS Nodes: The Different Roles, Explained
IPFS node types aren't a full-vs-light weight class the way some blockchains work. They are specific jobs a node opts into. Here is what each one does.
IPFS Immutability: Why You Can't Edit a File in Place
IPFS content is immutable by design: change one byte and the CID changes with it. Here is exactly what happens when you edit a file, and why IPNS fixes it.