75 repositories preserving the complete InterPlanetary File System development ecosystem: core implementations, desktop applications, browser extensions, NFT storage, content addressing, Filecoin integration, decentralized websites, and the infrastructure that makes data permanent, censorship-resistant, and universally addressable.
The conventional internet is built on location addressing: data lives at a URL, on a server, owned by a company. When the server goes down, the data disappears. When the company shuts down, decades of human knowledge vanish. When a government blocks a URL, the information ceases to exist for an entire population.
IPFS replaces location addressing with content addressing. Data is identified by what it is (its cryptographic hash), not where it is. The same file served from any node in the network resolves to the same address. This single architectural change makes data:
- Permanent — content-addressed data cannot be silently altered or deleted from the network as long as any node hosts it
- Censorship-resistant — there is no single URL to block; the content exists wherever peers choose to host it
- Verifiable — the hash of the data proves its integrity; you can verify that what you received is exactly what was requested
- Deduplicated — identical content across the entire network resolves to a single address, reducing storage waste at planetary scale
- Offline-capable — content can be shared peer-to-peer without any internet connection, through local networks or even sound waves
These properties make IPFS the natural storage layer for NFTs, decentralized applications, scientific data, legal records, creative works, and any information that must survive institutional failure.
Every other technology in the decentralized ecosystem — blockchains, smart contracts, DAOs, tokens — deals with computation and coordination. IPFS deals with data itself. Without permanent, verifiable storage, the decentralized movement builds castles on sand:
- NFTs without IPFS point to URLs that 404 when the hosting company folds
- Smart contracts without IPFS reference metadata that can be silently changed
- DAOs without IPFS store governance documents on servers they don't control
- Identity systems without IPFS depend on centralized credential databases
IPFS is the layer that makes all other decentralized systems trustworthy, because it ensures the data they reference will still exist tomorrow.
The foundational tools for running, managing, and interacting with IPFS nodes.
| Repository | Description |
|---|---|
| ipfs-desktop | Desktop application for IPFS on Windows, Mac, Linux |
| ipfs-webui | Web frontend for IPFS node management |
| ipfs-companion | Browser extension for IPFS resource access |
| js-ipfs-examples | JavaScript IPFS implementation examples |
| helia | Modern IPFS implementation in JavaScript |
| ipfs-car | Convert files to content-addressable archives |
| ipfs-cluster | Zero-dependency client for IPFS Cluster HTTP API |
| ipfs-check | Check accessibility of data by IPFS peers |
| ipfs-deploy | Zero-config CLI to deploy static websites to IPFS |
| ipfs-linux-service | Run IPFS daemon as a Linux system service |
| ipfs-blog | IPFS Blog and News |
| ipfs-docs | IPFS documentation platform |
| ipfs-pubsub-compute | Run code on other machines using IPFS Pubsub as message queue |
| npm-on-ipfs | Install npm modules through IPFS |
| ipfsPython | Upload files to IPFS in Python |
The bridge between NFTs and permanent storage. These tools ensure that NFT metadata and assets survive beyond any single marketplace or hosting service.
| Repository | Description |
|---|---|
| nft.storage | Free decentralized storage for NFTs on IPFS and Filecoin |
| nftstorage.link | Caching IPFS gateway optimized for NFT retrieval |
| nftup | No-code app to upload NFTs to IPFS via NFT.Storage |
| nft.storage-tools | Utilities for working with nft.storage |
| nft.storage-example-next.js | Next.js interface for NFT on IPFS |
| ipnft | InterPlanetary NFT specification |
| ipnftx | InterPlanetary NFT Extensions |
| checkup | Verify data availability in dotStorage |
| react-nftstorage.link-fallback-example | React fallback gateway example |
The data model that makes IPFS traversable. IPLD defines how data structures link to each other across protocols.
| Repository | Description |
|---|---|
| ipld | InterPlanetary Linked Data — traversing data across protocols |
| js-ipld | JavaScript implementation of IPLD |
| go-ipld-prime | Golang IPLD Data Model interfaces with codecs and schema support |
| ipld-explorer-components | React components for exploring IPLD data |
IPFS provides the addressing; Filecoin provides the incentivized, verifiable, persistent storage layer.
| Repository | Description |
|---|---|
| lotus | Reference implementation of the Filecoin protocol (Go) |
| ref-fvm | Reference Filecoin Virtual Machine implementation |
| FVM-Resouces | Resources for Filecoin Virtual Machine |
| web3.storage | Simple file storage service for IPFS and Filecoin |
Tools for building websites, applications, and services that run on IPFS rather than traditional hosting.
| Repository | Description |
|---|---|
| decentralized-websites | Resources for building decentralized websites |
| agregore-browser | Minimal browser for the distributed web |
| ipfs-website | Official IPFS project website |
| sns-deploy | Upload to IPFS and update Solana Name Service records |
| public-gateway-checker | Check which public IPFS gateways are online |
| interform | Forms on the decentralized web (Filecoin + IPFS) |
| polydocs | Protected documents on Polygon and IPFS |
| ghostshare-frontend | Private file sharing — Web3 without wallets or gas costs |
| example-image-gallery | Web3.Storage image sharing example |
| Web3.StorageLitIntegrationExample | Lit Protocol + Web3.Storage integration |
The peer-to-peer networking layer that IPFS runs on.
| Repository | Description |
|---|---|
| go-libp2p-relay-daemon | Standalone circuit relay daemon (v1 and v2) |
| specs | Technical specifications for the libp2p networking stack |
| Repository | Description |
|---|---|
| ens.domains | Ethereum Name Service domains |
| react-ens-address | React component for ENS name resolution |
| sign-in-with-web3 | Authentication with Web3 accounts instead of OAuth |
| ethmail.cc | Ethereum-based email |
| DoACS | Access control service for IPNS file management |
| Repository | Description |
|---|---|
| web3.js | Ethereum JavaScript API |
| graphprotocolcontracts | The Graph Protocol Solidity contracts |
| merkletreejs | Construct Merkle Trees and verify proofs |
| eth-ipfs-browser-client | Ethereum browser client based on IPFS/libp2p |
| ICPwasm | Internet Computer example applications |
| metadata-playground | Solidity metadata hash and CBOR playground |
| sha.js | Streamable SHA hashes in pure JavaScript |
| blueprint | Solid framework for building APIs |
| Repository | Description |
|---|---|
| deltasearch | Search engine for the InterPlanetary Filesystem |
| awesome-ipfs | Curated list of IPFS resources |
| torrent-paradise | Decentralized DHT search site for IPFS |
| indexvm | The context layer of the decentralized web |
| Repository | Description |
|---|---|
| community | Community practices documentation |
| team-mgmt | IPFS team planning and coordination |
| camp | IPFS Camp — 3-day hacker retreat for distributed web builders |
| IPFS-Ethereum-Hackathon | Hackathon submissions |
| IPFS-Theory | IPFS theoretical considerations |
| IPFS-Practical | Practical IPFS NFT reference |
| Repository | Description |
|---|---|
| lightspeed | DeltaVerse at the speed of light (original) |
| wave-share | Peer-to-peer file sharing through sound waves |
| web-llm | Large language models in the browser — no server needed |
| deltaverse | DeltaVerse platform delivery architecture |
| persssist | Decentralized file storage and sharing on IPFS |
| resolution-browser-extension | Surf the dweb with browser extension |
| Metric | Value |
|---|---|
| Total repositories | 75 |
| Original | 2 (lightspeed, .github) |
| Forked | 73 |
| IPFS core repos | 15 |
| NFT storage repos | 9 |
| Filecoin repos | 4 |
| Decentralized web repos | 10+ |
┌─────────────────────────────────────────────────┐
│ Content Addressing │
│ Every file identified by its cryptographic hash │
│ Same content → same address → anywhere │
└──────────────────────┬──────────────────────────┘
│
┌──────────────────────┴──────────────────────────┐
│ IPFS Network │
│ Peer-to-peer distribution across all nodes │
│ No single point of failure or censorship │
└──────────────────────┬──────────────────────────┘
│
┌──────────────┼──────────────┐
│ │ │
┌───────┴──────┐ ┌─────┴─────┐ ┌─────┴──────┐
│ Filecoin │ │ NFT.Stg │ │ Web3.Stg │
│ Incentivized│ │ Free NFT │ │ Simple │
│ persistent │ │ storage │ │ file API │
│ storage │ │ on IPFS │ │ for IPFS │
└──────────────┘ └───────────┘ └────────────┘
│ │ │
┌───────┴──────────────┴──────────────┴──────────┐
│ Applications │
│ Decentralized websites · NFT metadata │
│ DAO governance docs · Scientific data │
│ Legal records · Creative works · Identity │
└─────────────────────────────────────────────────┘
| Organization | Role |
|---|---|
| bankonme | Sovereign banking infrastructure — uses IPFS for content addressing |
| Professor-Codephreak | Parent architect — bankonOS |
| DeltaVThrust-NFT | NFT source code — relies on IPFS for metadata persistence |
| DELTAVERSE | Metaverse construction — IPFS for asset distribution |
| dairef | DAI stablecoin reference — preserved on content-addressed storage |
The conventional web forgets. IPFS remembers.
Content addressing means data survives institutions, servers, and censorship.
The InterPlanetary File System is not a feature of the decentralized web. It is the foundation.