Building Blocks For a Better Web.

A constellation of tools for content addressing.

Read the specs → open-source
three commitments

Not a platform to migrate to. A property you add.

Every tool in the IPFS constellation agrees on three principles. Pick one to see it in motion, and grab the building blocks you need.

Hash around, and find out.

Change one character. Watch the whole CID change.
file → CID
sha-256 · 0 bytes
↓ drop a file or edit
anatomy of a CID
change one character……the digest changes completely →
three problems, one protocol family

Addressing. Discovery. Transfer.

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.

01 Addressing
→ What is the data?

Name data by what it is.

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.

02 Discovery
→ Who has it?

Find who has it.

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.

03 Transfer
→ How do the bytes arrive?

Move the bytes.

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.

tools, by job-to-be-done

Pick the tool that fits the job.

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.

how are people using IPFS

Running in science labs, game studios, art vaults, and low earth orbit.

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.

join the constellation

By the community, for the community.

IPFS is built in the open by a thriving community. Chat with builders, propose changes, and find the next event near you.

Chat
→ Matrix · Discord
Real-time help, working groups, and the Friday show-and-tell.
↗ #ipfs-space:ipfs.io↗ discord.gg/ipfs
Forums
→ discuss.ipfs.tech
Long-form questions, RFCs, and proposals. Searchable and public.
↗ Browse the categories↗ github.com/ipfs
Calendar
→ lu.ma/ipfs
Working group calls, in-person meetups, conferences, and IPFS Camp.
↗ See upcoming events
Newsletter
→ ipfs.fyi/newsletter
A monthly digest of releases, RFCs, and what shipped across the network.
↗ Subscribe
YouTube
→ youtube.com/@ipfs
Recordings of working group calls, conference talks, and IPFS Camp sessions.
↗ Watch the channel