A constellation of tools for content addressing.
Every tool in the IPFS constellation agrees on three principles. Pick one to see it in motion, and grab the building blocks you need.
Self-certifying data publishing decomposes into three problems. IPFS solves each one independently and lets you swap the pieces. The CID is the only shared contract.
A Content Identifier (CID) is a self-describing cryptographic fingerprint. From a plain hash of a single byte to a Merkle DAG that proves an entire dataset, the CID is the contract between publisher and consumer. Anyone can mint one. Anyone can verify one.
A CID alone does not move bytes. Discovery turns a hash into a list of providers willing to serve it. IPFS is plural here: a global open DHT, indexer-style HTTP routing, and newer routing systems compete and interoperate behind the same content-addressed contract.
Once a provider is found, fetch the blocks and verify them on arrival. The transport is interchangeable — HTTP gateways, libp2p with Bitswap, iroh-blobs over QUIC, RASL, even sneakernet. The CID is the integrity check; the wire is whatever fits the deployment.
The constellation is large. Filter by what you actually need to do — run a node, pin content, ship a static site, or embed transfer in your app.
The reference IPFS implementation in Go. A full-featured daemon for desktop, server, and infra deployments — DHT, Bitswap, gateway, and pinning all in one binary.
Modular IPFS in TypeScript. Run a node directly in the browser or in Node — pick the transports and routers you need, leave the rest behind.
A small, embeddable library for verified blob transfer over QUIC. Designed for apps, IoT, and streaming workloads where a full IPFS daemon is too much.
A decentralized pinning network. Submit a CID, get it persisted across many providers — no single host to call, no single host to fail.
A GitHub Action that publishes a build directory to IPFS, returns the CID, and pins it. Drop it into a workflow and ship content-addressed sites on every push.
HTTP endpoints that resolve CIDs into bytes for any browser or curl. The bridge between content addressing and the location-addressed web.
Five jobs to be done, one set of building blocks. A sample of what teams have shipped once they stopped asking where the bytes live and started asking what the bytes are.
AT Protocol uses CIDs so anyone on the network can verify what they receive. No trusted server in the middle.
AT Protocol identifies every post, repo, and event by CID, so any client can verify what it received without trusting the server that delivered it.
Seed builds collaborative documents where every version, comment, and link is addressed by CID, durable across servers, editors, and time.
Anytype uses content addressing to let users build personal knowledge webs that sync peer to peer, with no server lock-in.
IPFS is built in the open by a thriving community. Chat with builders, propose changes, and find the next event near you.