No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Steven Allen 55afc478ec
Merge pull request #6512 from ipfs/fix/default-gossipsub
1 day ago
.circleci ci: show the commit 3 days ago
.github/ISSUE_TEMPLATE Fix automatic labels in issue templates 1 week ago
assets assets: move away from gx 1 month ago
bin debug: copy ipfs binary as well 1 week ago
blocks/blockstoreutil gx: unrewrite 4 months ago
ci ci: test on 32bit os 4 months ago
cmd Merge pull request #6474 from ipfs/feat/builtin-plugin 1 week ago
commands chore: fix a bunch of issues caught by golangci-lint 3 months ago
core feat: add --long as alias for -l in 2 days ago
coverage GOCC implementation & fix in make & build scripts 2 months ago
dagutils switch to new merkledag walk functions 2 days ago
docs doc: align the early testers program description with its goal 2 days ago
fuse migrate to go-libp2p-core. 1 month ago
keystore migrate to go-libp2p-core. 1 month ago
misc remove bitswap unwant 10 months ago
mk build: strip GOPATH from build paths 1 month ago
namesys migrate to go-libp2p-core. 1 month ago
p2p migrate to go-libp2p-core. 1 month ago
pin switch to new merkledag walk functions 2 days ago
plugin feat(plugins): add a bit of documentation 3 weeks ago
repo Update imports to go-filestore 4 days ago
tar gx: unrewrite 4 months ago
test feat: add --long as alias for -l in 2 days ago
thirdparty bootstrap: cleanup randomSubsetOfPeers 3 months ago
.codeclimate.yml disable codeclimate 'maintainability' checks 1 year ago
.dockerignore added binary executable files to .dockerignore 9 months ago
.gitattributes gitattributes: avoid normalizing known binary files 3 months ago
.gitignore build: use protoc-gen-* from gomod 1 month ago
.gitmodules gitmodules: use https so we don't need an ssh key 1 month ago CHANGELOG: add some missed changes 1 month ago docs: Update link format 9 months ago
COPYRIGHT Update COPYRIGHT 2 months ago
Dockerfile fix(Dockerfile): Allow ipfs mount in Docker container 2 months ago
LICENSE-MIT License update to dual MIT and Apache 2 2 months ago
Makefile build: use protoc-gen-* from gomod 1 month ago readme: fix CI badge 3 days ago Fix build with go-filestore 4 days ago
appveyor.yml appveyor: remove 'make toolkit_upgrade' 3 years ago
codecov.yml misc: allow for some coverage fall on commit 1 year ago
doc.go doc: remove out of date documentation 2 months ago
go.mod switch to new merkledag walk functions 2 days ago
go.sum switch to new merkledag walk functions 2 days ago
package-list.json cmdkit -> cmds 2 months ago
version.go version: bump to 0.4.22-dev 1 month ago



standard-readme compliant GoDoc Build Status

What is IPFS?

IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bittorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence built in. You can also mount the world at /ipfs.

For more info see:

Please put all issues regarding:

Table of Contents

Security Issues

The IPFS protocol and its implementations are still in heavy development. This means that there may be problems in our protocols, or there may be mistakes in our implementations. And -- though IPFS is not production-ready yet -- many people are already running nodes in their machines. So we take security vulnerabilities very seriously. If you discover a security issue, please bring it to our attention right away!

If you find a vulnerability that may affect live deployments -- for example, by exposing a remote execution exploit -- please send your report privately to Please DO NOT file a public issue. The GPG key for is 4B9665FB 92636D17 7C7A86D3 50AAE8A9 59B13AF3.

If the issue is a protocol weakness that cannot be immediately exploited or something not yet deployed, just discuss it openly.


The canonical download instructions for IPFS are over at: It is highly suggested you follow those instructions if you are not interested in working on IPFS development.

System Requirements

IPFS can run on most Linux, macOS, and Windows systems. We recommend running it on a machine with at least 2 GB of RAM (it’ll do fine with only one CPU core), but it should run fine with as little as 1 GB of RAM. On systems with less memory, it may not be completely stable.

Install prebuilt packages

We host prebuilt binaries over at our distributions page.

From there:

  • Click the blue “Download go-ipfs” on the right side of the page.
  • Open/extract the archive.
  • Move ipfs to your path ( can do it for you).

You can also download go-ipfs from this project’s GitHub releases page if you are unable to access

From Linux package managers

Arch Linux

In Arch Linux go-ipfs is available as go-ipfs package.

$ sudo pacman -S go-ipfs

Development version of go-ipfs is also on AUR under go-ipfs-git. You can install it using your favourite AUR Helper or manually from AUR.


For Linux and MacOSX you can use the purely functional package manager Nix:

$ nix-env -i ipfs

You can also install the Package by using it’s attribute name, which is also ipfs.


GNU’s functional package manager, Guix, also provides a go-ipfs package:

$ guix package -i go-ipfs


With snap, in any of the supported Linux distributions:

$ sudo snap install ipfs

From Windows package managers


The package ipfs currently points to go-ipfs and is being maintained.

PS> choco install ipfs


Scoop provides go-ipfs in its ‘extras’ bucket.

PS> scoop bucket add extras
PS> scoop install go-ipfs

Build from Source

Install Go

The build process for ipfs requires Go 1.12 or higher. If you don’t have it: Download Go 1.12+.

You’ll need to add Go’s bin directories to your $PATH environment variable e.g., by adding these lines to your /etc/profile (for a system-wide installation) or $HOME/.profile:

export PATH=$PATH:/usr/local/go/bin
export PATH=$PATH:$GOPATH/bin

(If you run into trouble, see the Go install instructions).

Download and Compile IPFS

$ git clone

$ cd go-ipfs
$ make install

If you are building on a non-GNU system, use gmake in place of make.
Unsupported platforms (run (g)make supported for a list) will also need to set the nofuse gotag during build.

$ GOTAGS=nofuse (g)make install


  • Separate instructions are available for building on Windows.
  • git is required in order for go get to fetch all dependencies.
  • Package managers often contain out-of-date golang packages. Ensure that go version reports at least 1.10. See above for how to install go.
  • If you are interested in development, please install the development dependencies as well.
  • WARNING: Older versions of OSX FUSE (for Mac OS X) can cause kernel panics when mounting!- We strongly recommend you use the latest version of OSX FUSE. (See
  • For more details on setting up FUSE (so that you can mount the filesystem), see the docs folder.
  • Shell command completion is available in misc/completion/ipfs-completion.bash. Read docs/ to learn how to install it.
  • See the init examples for how to connect IPFS to systemd or whatever init system your distro uses.

Updating go-ipfs

Using ipfs-update

IPFS has an updating tool that can be accessed through ipfs update. The tool is not installed alongside IPFS in order to keep that logic independent of the main codebase. To install ipfs update, download it here.

Downloading IPFS builds using IPFS

List the available versions of go-ipfs:

$ ipfs cat /ipns/

Then, to view available builds for a version from the previous command ($VERSION):

$ ipfs ls /ipns/$VERSION

To download a given build of a version:

$ ipfs get /ipns/$VERSION/go-ipfs_$VERSION_darwin-386.tar.gz # darwin 32-bit build
$ ipfs get /ipns/$VERSION/go-ipfs_$VERSION_darwin-amd64.tar.gz # darwin 64-bit build
$ ipfs get /ipns/$VERSION/go-ipfs_$VERSION_freebsd-amd64.tar.gz # freebsd 64-bit build
$ ipfs get /ipns/$VERSION/go-ipfs_$VERSION_linux-386.tar.gz # linux 32-bit build
$ ipfs get /ipns/$VERSION/go-ipfs_$VERSION_linux-amd64.tar.gz # linux 64-bit build
$ ipfs get /ipns/$VERSION/go-ipfs_$VERSION_linux-arm.tar.gz # linux arm build
$ ipfs get /ipns/$VERSION/go-ipfs_$ # windows 64-bit build


  ipfs - Global p2p merkle-dag filesystem.

  ipfs [<flags>] <command> [<arg>] ...

    init          Initialize ipfs local configuration
    add <path>    Add a file to ipfs
    cat <ref>     Show ipfs object data
    get <ref>     Download ipfs objects
    ls <ref>      List links from an object
    refs <ref>    List hashes of links from an object

    block         Interact with raw blocks in the datastore
    object        Interact with raw dag nodes
    files         Interact with objects as if they were a unix filesystem

    daemon        Start a long-running daemon process
    mount         Mount an ipfs read-only mountpoint
    resolve       Resolve any type of name
    name          Publish or resolve IPNS names
    dns           Resolve DNS links
    pin           Pin objects to local storage
    repo          Manipulate an IPFS repository

    id            Show info about ipfs peers
    bootstrap     Add or remove bootstrap peers
    swarm         Manage connections to the p2p network
    dht           Query the DHT for values or peers
    ping          Measure the latency of a connection
    diag          Print diagnostics

    config        Manage configuration
    version       Show ipfs version information
    update        Download and apply go-ipfs updates
    commands      List all available commands

  Use 'ipfs <command> --help' to learn more about each command.

  ipfs uses a repository in the local file system. By default, the repo is located
  at ~/.ipfs. To change the repo location, set the $IPFS_PATH environment variable:

    export IPFS_PATH=/path/to/ipfsrepo

Getting Started

See also:

To start using IPFS, you must first initialize IPFS’s config files on your system, this is done with ipfs init. See ipfs init --help for information on the optional arguments it takes. After initialization is complete, you can use ipfs mount, ipfs add and any of the other commands to explore!

Some things to try

Basic proof of ‘ipfs working’ locally:

echo "hello world" > hello
ipfs add hello
# This should output a hash string that looks something like:
# QmT78zSuBmuS4z925WZfrqQ1qHaJ56DQaTfyMUF7F8ff5o
ipfs cat <that hash>

Docker usage

An IPFS docker image is hosted at To make files visible inside the container you need to mount a host directory with the -v option to docker. Choose a directory that you want to use to import/export files from IPFS. You should also choose a directory to store IPFS files that will persist when you restart the container.

export ipfs_staging=</absolute/path/to/somewhere/>
export ipfs_data=</absolute/path/to/somewhere_else/>

Start a container running ipfs and expose ports 4001, 5001 and 8080:

docker run -d --name ipfs_host -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p -p ipfs/go-ipfs:latest

Watch the ipfs log:

docker logs -f ipfs_host

Wait for ipfs to start. ipfs is running when you see:

Gateway (readonly) server
listening on /ip4/

You can now stop watching the log.

Run ipfs commands:

docker exec ipfs_host ipfs <args...>

For example: connect to peers

docker exec ipfs_host ipfs swarm peers

Add files:

cp -r <something> $ipfs_staging
docker exec ipfs_host ipfs add -r /export/<something>

Stop the running container:

docker stop ipfs_host

When starting a container running ipfs for the first time with an empty data directory, it will call ipfs init to initialize configuration files and generate a new keypair. At this time, you can choose which profile to apply using the IPFS_PROFILE environment variable:

docker run -d --name ipfs_host -e IPFS_PROFILE=server -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 4001:4001 -p -p ipfs/go-ipfs:latest


If you have previously installed IPFS before and you are running into problems getting a newer version to work, try deleting (or backing up somewhere else) your IPFS config directory (~/.ipfs by default) and rerunning ipfs init. This will reinitialize the config file to its defaults and clear out the local datastore of any bad entries.

Please direct general questions and help requests to our forum or our IRC channel (freenode #ipfs).

If you believe you’ve found a bug, check the issues list and, if you don’t see your problem there, either come talk to us on IRC (freenode #ipfs) or file an issue of your own!


This table is generated using the module package-table with package-table --data=package-list.json.

Listing of the main packages used in the IPFS ecosystem. There are also three specifications worth linking here:

Name CI/Travis Coverage Description
go-unixfs Travis CI codecov the core ‘filesystem’ logic
go-mfs Travis CI codecov a mutable filesystem editor for unixfs
go-ipfs-posinfo Travis CI codecov helper datatypes for the filestore
go-ipfs-chunker Travis CI codecov file chunkers
go-ipfs-exchange-interface Travis CI codecov exchange service interface
go-ipfs-exchange-offline Travis CI codecov (dummy) offline implementation of the exchange service
go-bitswap Travis CI codecov bitswap protocol implementation
go-blockservice Travis CI codecov service that plugs a blockstore and an exchange together
go-datastore Travis CI codecov datastore interfaces, adapters, and basic implementations
go-ipfs-ds-help Travis CI codecov datastore utility functions
go-ds-flatfs Travis CI codecov a filesystem-based datastore
go-ds-measure Travis CI codecov a metric-collecting database adapter
go-ds-leveldb Travis CI codecov a leveldb based datastore
go-ds-badger Travis CI codecov a badgerdb based datastore
go-ipns Travis CI codecov IPNS datastructures and validation logic
go-ipfs-config Travis CI codecov go-ipfs config file definitions
go-fs-lock Travis CI codecov lockfile management functions
fs-repo-migrations Travis CI codecov repo migrations
go-block-format Travis CI codecov block interfaces and implementations
go-ipfs-blockstore Travis CI codecov blockstore interfaces and implementations
go-ipfs-cmds Travis CI codecov CLI & HTTP commands library
go-ipfs-api Travis CI codecov a shell for the IPFS HTTP API
Metrics & Logging
go-metrics-interface Travis CI codecov metrics collection interfaces
go-metrics-prometheus Travis CI codecov prometheus-backed metrics collector
go-log Travis CI codecov logging framework
go-ipfs-routing Travis CI codecov routing (content, peer, value) helpers
go-ipfs-util Travis CI codecov the kitchen sink
go-ipfs-addr Travis CI codecov utility functions for parsing IPFS multiaddrs

For brevity, we’ve omitted go-libp2p and go-ipld packages. These package tables can be found in their respective project’s READMEs:


Some places to get you started on the codebase:

CLI, HTTP-API, Architecture Diagram


Description: Dotted means “likely going away”. The “Legacy” parts are thin wrappers around some commands to translate between the new system and the old system. The grayed-out parts on the “daemon” diagram are there to show that the code is all the same, it’s just that we turn some pieces on and some pieces off depending on whether we’re running on the client or the server.


make test

Development Dependencies

If you make changes to the protocol buffers, you will need to install the protoc compiler.

Developer Notes

Find more documentation for developers on docs


We ❤️ all our contributors; this project wouldn’t be what it is without you! If you want to help out, please see

This repository falls under the IPFS Code of Conduct.

You can contact us on the freenode #ipfs-dev channel or attend one of our weekly calls.