The Files.com Command Line Interface (CLI) App transfers files between a local machine and Files.com and manages your site from the command line. It runs on Windows, macOS, and Linux, and performs fast, concurrent transfers.

The CLI App is designed for scripted and automated transfers, because it works from any shell without writing code against an SDK. If you already work in a language that Files.com offers an SDK for, our SDK will integrate more deeply with your application.

Beyond file operations like list, upload, download, move, and delete, the CLI App performs administrator actions on every resource in Files.com, including users, groups, permissions, and remote servers.

The CLI App communicates with Files.com over HTTPS on port 443, so it requires no firewall changes to connect.

For Remote Server types that support it, the CLI App sends file data straight to the storage instead of routing it through Files.com's network, typically running several times faster. Supported cloud storage providers use Direct Routing, and an On-Premise Agent acts similarly when its Direct Transfers feature is enabled. The CLI App uses the direct connection automatically and falls back to the standard connection when the direct connection cannot be established.

Direct transfers with an Agent are the one case where a firewall change can apply on the CLI App's side, and only on networks that restrict outbound traffic. Allow outbound TCP and UDP connections from the CLI App to the Agent's direct transfer ports, which default to 4001 through 4010. When that traffic stays blocked, transfers simply continue over the standard connection route.

Installation

Download the latest release for your operating system from the CLI App Releases page. The app is a single self-contained binary, so there is no installer to run. Place the binary in a directory listed in your %PATH% (Windows) or $PATH (macOS and Linux) so you can run files-cli from any location.

Windows

Download the Zip archive for your processor architecture, amd64 for most systems or arm64 for ARM processors. Extract it, then place the files-cli.exe binary in a directory listed in your %PATH%.

macOS

On systems with Homebrew, add the Files.com tap, trust it, then install the CLI App:

brew tap Files-com/homebrew-tap
brew trust --formula files-com/tap/files-cli
brew install files-cli

Trusting a tap authorizes Homebrew to run that tap's code on your machine and Homebrew requires it before installing. The --formula form trusts only the files-cli formula, the granularity Homebrew recommends. To trust the entire tap instead, run brew trust files-com/tap.

Tap trust is available in Homebrew 6.0 and newer. On earlier versions, the brew trust command does not exist and is not required for installation.

Without Homebrew, download the compressed Tar archive, extract the files-cli binary, and move it into your $PATH:

curl -L https://github.com/Files-com/files-cli/releases/latest/download/files-cli_macOS_64bit.tar.gz | tar zxv
sudo mv ./files-cli /usr/local/bin

Linux

On RPM-based distributions, such as Red Hat, Fedora, CentOS, openSUSE, and Oracle Linux, install with the RPM package. Replace {ARCH} with your system architecture, such as amd64 or arm64.

curl -L https://github.com/Files-com/files-cli/releases/latest/download/files-cli_linux_{ARCH}.rpm -o files-cli.rpm
sudo rpm -i ./files-cli.rpm

On Debian-based distributions, such as Ubuntu and Debian, install with the APT package. Replace {ARCH} with your system architecture, such as amd64 or arm64.

curl -L https://github.com/Files-com/files-cli/releases/latest/download/files-cli_linux_{ARCH}.deb -o files-cli.deb
sudo apt install ./files-cli.deb

Help for CLI Commands

Every command supports the --help option, which lists the available subcommands, options, and usage. Run it on its own for an overview, or on any command or subcommand for details specific to it.

files-cli --help
files-cli folders --help