# Install b2-tools with Homebrew, apk, scoop

B2 Cloud Storage Command-Line Tools. Version 4.7.1 via Homebrew; verified 2026-06-09. Also installable with apk: sudo apk add b2-tools.

## Install

```sh
sudo av install brew:b2-tools
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install b2-tools
```

  Evidence: local Homebrew formula metadata

### Linux

- apk (92%):

```sh
sudo apk add b2-tools
```

  Evidence: Alpine Linux edge package indexes: b2-tools from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz

### Windows

- Scoop (92%):

```sh
scoop install main/b2
```

  Evidence: Scoop official bucket manifest trees: bucket/b2.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:b2-tools
- **Package manager:** Homebrew
- **Version:** 4.7.1
- **Source summary:** B2 Cloud Storage Command-Line Tools
- **Homepage:** <https://github.com/Backblaze/B2_Command_Line_Tool>
- **Last updated:** 2026-06-09T19:24:01Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- b2 (alias)
- b2v3 (alias)
- b2v4 (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 4.7.1
## Project history and usage

B2 Command Line Tool is Backblaze's official `b2` CLI for B2 Cloud Storage. It gives shell access to account, bucket, file, key, replication, listing, removal, and sync operations.

### Project history

Backblaze maintains the tool in the Backblaze/B2_Command_Line_Tool repository and publishes it as a Python package, standalone binaries, Docker image, and Homebrew package. The README describes it as command-line access to all capabilities of the B2 service.

The CLI has evolved across API-versioned command surfaces. The README documents the current guidance: use `b2` for the latest stable interactive interface, and use version-bound commands such as `b2v4` for long-running scripts that need stable behavior.

### Adoption history

B2 users adopted the CLI because object storage needs scriptable upload, download, sync, lifecycle, and key-management workflows. Backblaze's official docs recommend Homebrew as the quickest setup path for Mac users, while the input package facts also list apk and Scoop packages.

The tool is common in backup scripts and CI jobs because B2 is frequently used as low-cost object storage. Its versioned command aliases are especially package-nerdy: they let a package ship a newer implementation while preserving an older command contract for scripts.

### How it is used

Typical usage starts with account authorization, then commands such as `b2 bucket list`, `b2 file upload`, `b2 ls`, `b2 sync`, and `b2 key create`. The official README and Backblaze docs state that `B2_ACCOUNT_INFO` selects the SQLite cache file for authentication information and that the default is `~/.b2_account_info`.

For containers, the README shows either passing `B2_APPLICATION_KEY` and `B2_APPLICATION_KEY_ID` each run or persisting authorization state in a mounted volume.

### Why package nerds care

For package nerds, `b2-tools` is a neat collision between package name, executable name, and API-versioned command names: Homebrew installs `b2-tools`, users run `b2`, and scripts may choose `b2v4` for compatibility.

It is also a Python CLI with official binary and Docker distribution, so packaging choices affect startup time, dependencies, credential cache placement, and whether users get the newest API surface or a stable alias.

### Timeline

- 2020: Backblaze/B2_Command_Line_Tool GitHub Releases include the 2.x release line.
- 2020s: The README documents Homebrew, PyPI, standalone binaries, Docker, and source installs.
- 2020s: Version-bound commands such as `b2v3` and `b2v4` become part of the CLI compatibility model.

### Related projects

- Backblaze B2 Cloud Storage is the object-storage service managed by the CLI.
- The B2 Native API and S3-compatible API are related service interfaces.
- Backblaze's Docker image packages the same CLI for container workflows.

### Sources

- Backblaze official cloud storage command-line tools docs
- Backblaze/B2_Command_Line_Tool README and releases
- source_facts.package-manager


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Credential files

- Unix: ~/.b2_account_info
## Other Package-Manager Records

- apk - b2-tools - 4.6.0-r1: normalized package name match | Alpine Linux edge package indexes: b2-tools from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Command-line tool for Backblaze B2 | https://github.com/Backblaze/B2_Command_Line_Tool
- apk - b2-tools-pyc - 4.6.0-r1: normalized package name match | Alpine Linux edge package indexes: b2-tools-pyc from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Precompiled Python bytecode for b2-tools | https://github.com/Backblaze/B2_Command_Line_Tool
- Scoop - main/b2: installed executable or alias match | Scoop official bucket manifest trees: bucket/b2.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/b2-tools.yml](https://github.com/mxcl/pkgdb/blob/main/combined/b2-tools.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph