Command line

Install

Downloads for Linux, macOS and Windows on x86_64 and ARM64, and the install commands, are on the command line page. On a Mac with HyperDrop Desktop the command is also inside the app: /Applications/HyperDrop.app/Contents/Resources/hyperdrop.

On Debian, Ubuntu, Fedora and RHEL, add the package repository rather than installing a downloaded file: the command line then updates with the rest of the system (updates).

Connect

With the address, login and password an administrator gave you:

hyperdrop connect https://share.example.com --user you

It asks for the password, and for a code when the account has a second factor (a recovery code works too). With a join code or invite link, paste it on stdin:

hyperdrop connect --join-code-stdin

hyperdrop status shows the active server; hyperdrop servers list and servers use <host> switch between several.

Share

hyperdrop share ~/Photos --expires 7d

A folder or several files become one share with a listing page and a zip download; one file opens directly. A selection holding an index.html is refused until you pass --files for the listing or --entry <path> for that page. Every share prints a View link and a Download link. Flags: --name, --password-stdin, --expires 2d|6mo|never, --copy view (on Linux it needs xclip, xsel or wl-copy). Manage with hyperdrop list, edit and delete; hyperdrop --help lists everything.

Video and pictures upload untouched; the Mac app does the converting.

The version rule

hyperdrop version prints the version. It works with servers whose first number is the same and whose second is at most one apart from its own (the rule). While the server is one minor version ahead, hyperdrop status notes that updating the command line unlocks what that server added; every other command keeps working. Further apart, every command that talks to the server is refused except hyperdrop status, hyperdrop server update and the hyperdrop 2fa commands that set up a second factor, which Update Server requires: a newer server says to update HyperDrop, an older one says an administrator should update it.

Where the sign-in is kept

Connecting stores a device token, never your password. With a keyring (Secret Service, such as gnome-keyring) the token lives there. Without one, on a server or in a container, it goes to ~/.config/hyperdrop/secrets.json, readable by your user alone. On a Mac it is in the Keychain, on Windows in Credential Manager. Addresses and labels are in ~/.config/hyperdrop/config.json (on Windows, under your user folder).

Sign a machine out and remove its token:

hyperdrop servers forget share.example.com --sign-out