Eight tools, side by side, with the measurement and the limits.
Most of these tools send a copy. KEIBIDROP can also mount the other machine's folder, so a read pulls only the bytes it touches and you open one file instead of receiving the whole project. Each page below states where the other tool is the better choice.
| Tool | The short version |
|---|---|
| Blip | US$25 per user per month for commercial work, no Linux build, and it needs a verified email on both sides |
| LocalSend | Local network only, so both machines must be on the same Wi-Fi |
| croc | One transfer per code phrase from the command line, with no saved peers |
| Magic Wormhole | A single-use code typed by hand, once per transfer |
| WeTransfer | Uploads to their servers first, with a size cap and an expiry date |
| Tool | The short version |
|---|---|
| Syncthing | Keeps a full copy on every device, so the disk has to hold the whole share |
| rclone | Needs a storage provider, and in one measured run its mount served stale bytes after an in place edit |
| sshfs | Measured 1.33 MB/s at every file size across a 200 ms link, which is the latency bound |
Three pages cover the flows where the difference is largest: remote DFIR triage, post-production handoff, and datasets on a rented GPU box.
Install · Getting started · Measured performance · The wider comparison table