ipfs /kubo

IPFS implementation in Go: a daemon that stores and serves content-addressed data, with a CLI, HTTP Gateway, and RPC API

★ 17,187⑂ 3,171👁 504⑃ 6,512● 4,858▤ 135
Download: v0.43.1kubo-0.43.1 ↓0.43.12026-09-15
+2
Daily
17,187
stars
3,171
forks
504
watchers
6,512
prs
4,858
issues
135
releases

README

Kubo: IPFS Implementation in Go
  


The first implementation of IPFS.


  
  
  
  
  





What is Kubo? | Quick Taste | Install | Documentation | Development | Getting Help


 What is Kubo?

Kubo was the first IPFS implementation and is the most widely used one today. It takes an opinionated approach to content-addressing (CIDs, DAGs) that maximizes interoperability: UnixFS for files and directories, HTTP Gateways for web browsers, Bitswap and HTTP for verifiable data transfer.

Features:

- Runs an IPFS node as a network service (LAN mDNS and WAN Amino DHT)
- Command-line interface (ipfs --help)
- WebUI for node management
- HTTP Gateway for trusted and trustless content retrieval
- HTTP RPC API to control the daemon
- HTTP Routing V1 client and server for delegated routing
- FUSE mounts for mounting /ipfs, /ipns, and /mfs as local filesystems (experimental)
- Content blocking for public node operators

Other IPFS implementations: Helia (JavaScript), more...

 Quick Taste

After installing Kubo, verify it works:

console
$ ipfs init --profile=unixfs-v1-2025
generating ED25519 keypair...done
peer identity: 12D3KooWGcSLQdLDBi2BvoP8WnpdHvhWPbxpGcqkf93rL2XMZK7R

$ ipfs daemon &
Daemon is ready

$ echo "hello IPFS" | ipfs add -q
bafkreicouv3sksjuzxb3rbb6rziy6duakk2aikegsmtqtz5rsuppjorxsa

$ ipfs cat bafkreicouv3sksjuzxb3rbb6rziy6duakk2aikegsmtqtz5rsuppjorxsa
hello IPFS


Verify this CID is provided by your node to the IPFS network: 

See ipfs add --help for all import options. Ready for more? Follow the command-line quick start.

 Install

Follow the official installation guide, or choose: prebuilt binary | Docker | package manager | from source.

Prefer a GUI? Try IPFS Desktop and/or IPFS Companion.

 Minimal System Requirements

Kubo runs on most Linux, macOS, and Windows systems. For optimal performance, we recommend at least 6 GB of RAM and 2 CPU cores (more is ideal, as Kubo is highly parallel).

 [!IMPORTANT]
 Larger pinsets require additional memory, with an estimated ~1 GiB of RAM per 20 million items for reproviding to the Amino DHT.

 [!CAUTION]
 Systems with less than the recommended memory may experience instability, frequent OOM errors or restarts, and missing data announcement (reprovider window), which can make data fully or partially inaccessible to other peers. Running Kubo on underprovisioned hardware is at your own risk.

For running Kubo on constrained hardware such as a Raspberry Pi, see Kubo on low-memory devices.

 Official Prebuilt Binaries

Download from https://dist.ipfs.techkubo or GitHub Releases.

 Docker

Official images are published at https://hub.docker.com/r/ipfs/kubo/: 

 🟢 Release Images

Use these for production deployments.

- latest and release always point at the latest stable release
- vN.N.N points at a specific release tag

console
$ docker pull ipfs/kubo:latest
$ docker run --rm -it --net=host ipfs/kubo:latest


To customize your node, pass config via -e or mount scripts in /container-init.d.

 🟠 Develop

Top issues

Latest release

v0.43.1 v0.43.1 2026-09-15
[!NOTE]
 This release was brought to you by the Shipyard team.

 [!IMPORTANT]
 v0.43 is the last Kubo by the Shipyard. Our IPFS work ends on September 30, 2026. Bring your support and transition questions to the community forum.



- 🔦 Highlights
  - 🔇 Empty Bootstrap list disables all bootstrap dialing
  - 🗄️ Improved datastore profiles and docs
  - 🗂️ Setting the flatfs shard depth is less error-prone
  - 📁 ipfs ls can print readable sizes and sort by size
  - 📌 Files on FUSE mounts keep their inode number
  - 🧹 FUSE mounts keep what you write after a rename
  - 🔐 ipfs key exp

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON