Fan-out & fan-in
send --to a,b, pull --to a,b, daemon --to a,b. Several servers behaving like one mailbox, driven from cron.
One Rust binary that speaks the real LocalSend protocol. Send a file to a whole fleet at once, from a cron job, over SSH, from a box with no display. The receiving device needs nothing installed — anything that runs LocalSend can take it. Nothing leaves your network.
curl -fsSL https://raw.githubusercontent.com/Urdemonlord/zapsend/master/install.sh | sh
Linux & Windows (Git Bash). No Rust toolchain needed — downloads the matching release binary, verifies its SHA-256, installs to ~/.local/bin. Or cargo install zapsend.
Measured on loopback on the author's VPS. Your LAN will differ — the point is the shape of the improvement: parallel SHA-256 hashing plus an on-disk hash cache, so repeat transfers skip work they already did.
$ zapsend send film.mkv --to pixel
sending film.mkv to "pixel" (192.168.1.42:53317)
film.mkv [============> ] 1.2 GiB/4.1 GiB (12s)
✓ done
send --to a,b, pull --to a,b, daemon --to a,b. Several servers behaving like one mailbox, driven from cron.
Drop a file in a watched folder and it goes out to the fleet on its own. No one has to sit at the machine.
Sync asks the other side what it already holds before sending. sync --replace backs up what it overwrites and verifies with SHA-256.
Peers are identified by fingerprint: --fingerprint pinning, --tofu on first use. --ip without a fingerprint is refused outright.
Every one-shot command takes --json (or ZAPSEND_JSON=1 for a whole session). Machine-readable output, verdict in the exit code.
No runtime dependencies. Linux x86_64 and aarch64 (including a Raspberry Pi), Windows x86_64, and cargo install anywhere else. Plus a browser-readable share page.
ZapSend is not the best tool for every transfer. Here is when to reach for what.
| ZapSend | rsync over SSH | LocalSend app | |
|---|---|---|---|
| Headless / cron / fleet | Yes — this is the point | Yes, if every box has SSH | No — it is a GUI |
| Phone or Windows box without SSH | Yes — the other side just runs LocalSend | No SSH, no rsync | Yes |
| Both ends have SSH | Works | Better — thirty years better at it | Works |
| One file, one device | Works | Works | Simplest — or lsq / lsend-cli |
| Cloud / internet transfer | No — LAN only, nothing leaves your network | Needs a reachable host | LAN only |
| GUI | No — CLI only | No | Yes |
Rule of thumb from the README: pick ZapSend when the other end cannot run rsync, or when several servers should behave like one mailbox. Skip it when both ends have SSH, and skip it for one file on one device — lsq, lsend-cli and localsend-rs all do that already. It is not a GUI, not a Syncthing replacement, not a cloud service.
Interop, stated plainly: checked in all four directions against lsq, an independent implementation (11/11), plus loopback and Android. Interop with the LocalSend app on iOS, macOS and desktop has not been tested yet.
curl -fsSL https://raw.githubusercontent.com/Urdemonlord/zapsend/master/install.sh | sh
Linux and Windows (Git Bash). Verifies the SHA-256 of the release binary. Pin a version: sh -s -- --version v0.1.0 --dir ~/.local/bin.
cargo install zapsend
Also the way to go on macOS — there is no prebuilt macOS binary yet — and on musl systems like Alpine Linux, which the installer refuses.
Release v0.1.0 — Linux x86_64 and aarch64 .tar.gz, Windows x86_64 .zip, each with a .sha256 file, plus SHA256SUMS.
Try it in 30 seconds, no network peers needed: clone the repo and run ./demo.sh — it starts a receiver on one port, discovers it, sends three files, verifies the hashes, and proves a wrong fingerprint is refused.
Running a fleet? Read docs/agent-fleet.md: one receive per machine as a mailbox, systemd units, pulling results back to your laptop.
Intro video — coming soon.
Until then, the 30-second demo.sh run in the README shows the whole flow: discover, send, verify, refuse the wrong fingerprint.
Send, receive, resume, folders, fan-out, fan-in, a watched folder, sync and a browser-readable share page all work. Interop is checked against an independent implementation, and the share page is checked in a real browser at phone and desktop width. No GUI, and no users yet beyond the author. Open source under the MIT license.