Install IPFS Kubo

This guide describes the available installation processes for IPFS Kubo, a Go-based implementation of the InterPlanetary File System (IPFS) protocol. Kubo was the first implementation of IPFS, and is the most widely used implementation today. Kubo allows you to do everything that IPFS Desktop can do, but at a more granular level, since you can specify which commands to run. Kubo has the following features:

• An IPFS daemon server
• Extensive command line tooling
• An HTTP RPC API for controlling the node
• An HTTP Gateway for serving content to HTTP browsers
• Binaries for Windows, MacOS, Linux, FreeBSD and OpenBSD

Installing Kubo in the command line is handy for many use cases, such as building applications and services on top of an IPFS node, or setting up a node without a user interface (which is usually the case with remote servers or virtual machines).

To get started, familiarize yourself with the system requirements. Then, determine if you'd like to install Kubo using one of the 5 official binary distributions, or build Kubo from source. Once you've installed Kubo, determine which node to use in the command line. Finally, check out the next steps.

WARNING

Building from source is only recommended if you are running Kubo on a system with severe resource constraints, or are contributing to the Kubo project.

System requirements

Kubo runs on most Windows, MacOS, Linux, FreeBSD and OpenBSD systems that meet the following requirements:

• 6 GiB of memory.
• 2 CPU cores (kubo is highly parallel).

Note the following:

• The amount of disk space your IPFS installation uses depends on how much data you're sharing. A base installation uses around 12MB of disk space.
• You can enable automatic garbage collection via --enable-gc and adjust using default maximum disk storage (opens new window) for data retrieved from other peers.

Kubo on resource-constrained systems

If you are running Kubo on a resource-constrained system (such as a Raspberry Pi), you should initialize your daemon with the lowpower profile.

ipfs init --profile=lowpower

This reduces daemon overhead on the system but may degrade content discovery and data fetching performance.

Install official binary distributions

This section describes how to download and install the Kubo binary from dist.ipfs.tech on Windows, MacOS, Linux, FreeBSD and OpenBSD operating systems. The IPFS team publishes the latest, official prebuilt Kubo binaries on the dist.ipfs.tech website (opens new window). New IPFS Kubo binary releases are automatically shown on the Kubo page on dist.ipfs.tech.

If you are unable to access dist.ipfs.tech (opens new window), you can also download Kubo (go-ipfs) from the project's GitHub releases (opens new window) page or /ipns/dist.ipfs.tech at the dweb.link (opens new window) gateway.

Binaries are available for the following operating systems:

OS	32-bit	64-bit	ARM	ARM-64
macOS	No	Yes	No	Yes
FreeBSD	Yes	Yes	Yes	No
Linux	Yes	Yes	Yes	Yes
OpenBSD	Yes	Yes	Yes	No
Windows	Yes	Yes	No	No

For installation instructions for your operating system, select the appropriate tab.

Windows

1. Download the Windows binary from dist.ipfs.tech (opens new window).

   wget https://dist.ipfs.tech/kubo/v0.23.0/kubo_v0.23.0_windows-amd64.zip -Outfile kubo_v0.23.0.zip
   

2. Unzip the file to a sensible location, such as ~\Apps\kubo_v0.23.0.

   Expand-Archive -Path kubo_v0.23.0.zip -DestinationPath ~\Apps\kubo_v0.23.0
   

3. Move into the kubo_v0.23.0 folder

   cd ~\Apps\kubo_v0.23.0\kubo
   

4. Check that the ipfs.exe works:

   .\ipfs.exe --version
   
   > ipfs version 0.23.0
   

   At this point, Kubo is usable. However, it's strongly recommended that you first add ipfs.exe to your PATH using the following steps:

5. Save the current working directory into a temporary variable:

   $GO_IPFS_LOCATION = pwd
   

6. Create a PowerShell profile:

   if (!(Test-Path -Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force }
   

   This command first checks to see if you have a profile set. If you do, it leaves it there and doesn't create a new one. You can view the contents of your profile by opening it in an editor, such as Notepad:

   notepad $PROFILE
   

7. Add the location of your Kubo daemon and add it to PowerShell's PATH by truncating it to the end of your PowerShell profile:

   Add-Content $PROFILE "`n[System.Environment]::SetEnvironmentVariable('PATH',`$Env:PATH+';;$GO_IPFS_LOCATION')"
   

8. Load your $PROFILE:

   & $profile   
   

9. Navigate to your home folder

   cd ~
   

10. Test that Kubo installed correctly:

    ipfs --version
    
    > ipfs version 0.23.0
    

macOS

The brew installation method supports both Intel and Apple Silicon hardware. If you prefer a manual installation, darwin-amd64 (Intel) and darwin-arm64 (Apple Silicon) artifacts available here (opens new window).

1. Navigate to a terminal.

2. Use brew to install Kubo:

   brew install ipfs
   

3. Confirm your Kubo installation:

   ipfs --version
   

   If Kubo is installed, the version number displays. For example:

   > ipfs version 0.23.0
   

Linux

1. Download the Linux binary from dist.ipfs.tech (opens new window).

   wget https://dist.ipfs.tech/kubo/v0.23.0/kubo_v0.23.0_linux-amd64.tar.gz
   

2. Unzip the file:

   tar -xvzf kubo_v0.23.0_linux-amd64.tar.gz
   
   > x kubo/install.sh
   > x kubo/ipfs
   > x kubo/LICENSE
   > x kubo/LICENSE-APACHE
   > x kubo/LICENSE-MIT
   > x kubo/README.md
   

3. Move into the kubo folder:

   cd kubo
   

4. Run the install script

   sudo bash install.sh
   
   > Moved ./ipfs to /usr/local/bin
   

5. Test that Kubo has installed correctly:

   ipfs --version
   
   > ipfs version 0.23.0
   

FreeBSD

1. Download the FreeBSD binary from dist.ipfs.tech (opens new window).

   wget https://dist.ipfs.tech/kubo/v0.23.0/kubo_v0.23.0_freebsd-amd64.tar.gz
   

2. Unzip the file:

   tar -xvzf kubo_v0.23.0_freebsd-amd64.tar.gz
   
   > x kubo/install.sh
   > x kubo/ipfs
   > x kubo/LICENSE
   > x kubo/LICENSE-APACHE
   > x kubo/LICENSE-MIT
   > x kubo/README.md
   

3. Move into the kubo folder:

   cd kubo
   

4. Run the install script:

   doas bash install.sh
   
   > Moved ./ipfs to /usr/local/bin
   

5. Test that Kubo has installed correctly:

   ipfs --version
   
   > ipfs version 0.23.0
   

OpenBSD

1. Download the OpenBSD binary from dist.ipfs.tech (opens new window).

   wget https://dist.ipfs.tech/kubo/v0.23.0/kubo_v0.23.0_openbsd-amd64.tar.gz
   

2. Unzip the file:

   tar -xvzf kubo_v0.23.0_openbsd-amd64.tar.gz
   
   > x kubo/install.sh
   > x kubo/ipfs
   > x kubo/LICENSE
   > x kubo/LICENSE-APACHE
   > x kubo/LICENSE-MIT
   > x kubo/README.md
   

3. Move into the kubo folder:

   cd kubo
   

4. Run the install script:

   doas bash install.sh
   
   > Moved ./ipfs to /usr/local/bin
   

5. Test that Kubo has installed correctly:

   ipfs --version
   
   > ipfs version 0.23.0
   

Build Kubo from source

For the current instructions on how to manually download, compile and build Kubo from source, see the Build from Source (opens new window) section in the Kubo repository.

Determining which node to use with the command line

The command line can detect and use any node that's running, unless it's configured to use an external binary file. Here's which node to use for the local daemon or a remote client:

Local daemon

The local daemon process is automatically started in the CLI with the command ipfs daemon. It creates an $IPFS_PATH/api file with an RPC API address.

Remote client

You can install the standalone IPFS CLI client independently and use it to talk to an IPFS Desktop node or a Brave node. Use the RPC API to talk to the ipfs daemon.

When an IPFS command executes without parameters, the CLI client checks whether the $IPFS_PATH/api file exists and connects to the address listed there.

• If an $IPFS_PATH is in the default location (for example, ~/.ipfs on Linux), then it works automatically and the IPFS CLI client talks to the locally running ipfs daemon without any extra configuration.

• If an $IPFS_PATH isn't in the default location, use the --api <rpc-api-addr> command-line argument. Alternatively, you can set the environment variable to IPFS_PATH. IPFS_PATH will point to a directory with the $IPFS_PATH/api file pointing at the Kubo RPC of the existing ipfs daemon instance.

Most common examples

If you are an IPFS Desktop user, you can install CLI tools and an .ipfs/api file is automatically picked up.

If you're not running IPFS Desktop, specify a custom port with ipfs --api /ip4/127.0.0.1/tcp/<port> id in the CLI.

For example, Brave RPC API runs on port 45001, so the CLI can talk to the Brave daemon using ipfs --api /ip4/127.0.0.1/tcp/45001 id. You can use mkdir -p ~/.ipfs && echo "/ip4/<ip>/tcp/<rpc-port>" > ~/.ipfs/api to avoid passing --api every time.

Next steps

Now that you've installed IPFS Kubo:

• Check out the IPFS Kubo Tutorial in Guides, which will guide you through taking a Kubo node online and interacting with the network.
• Learn how to quickly install, uninstall, upgrade and downgrade Kubo using ipfs-update.