Peer-to-peer file transfer over QUIC. Devices on the same link discover each other; elsewhere, send by hostname or address.
$ qd receive
qd receiving as "laptop" (4d915ba1) on 192.168.1.42:53320
$ qd send photos --to laptop
ok photos/IMG_4021.jpg (4.20 MiB)
ok photos/2024/beach.jpg (3.98 MiB)
sent 2 / 2 files in 0.4s (20.4 MiB/s)cargo build --release
./target/release/qd --helpRust 1.82+. Linux, macOS, Windows.
Prebuilt assets from the releases page:
| Asset | Contains |
|---|---|
quicdrop-<version>-{linux-x86_64,windows-x86_64,macos-universal}.tar.gz |
qd and quicdropd, no GUI |
quicdrop-desktop-<version>-{amd64.deb,x86_64.rpm,amd64.AppImage} |
desktop app, plus qd and quicdropd in /usr/bin |
quicdrop-desktop-<version>-x64-setup.exe, -universal.dmg |
desktop app only; use the tarball for qd |
quicdrop-<version>.flatpak |
desktop app, plus qd and quicdropd |
Arch and derivatives: AUR recipes for quicdrop-bin (prebuilt) and quicdrop (built
from source) live under packaging/aur.
qd receive [--out DIR] [--policy ask|auto|deny]
qd peers [--timeout 4s]
qd send <PATHS...> --to <PEER> [-j 4]
qd trust [add <ID> | rm <ID> | list]
qd id--to takes a device name, device id prefix, hostname, IP, or ip:port:
qd send report.pdf --to "Brave Otter"
qd send report.pdf --to 4d915ba1
qd send report.pdf --to laptop.tailnet.ts.net
qd send report.pdf --to 192.168.1.42:53320Hostnames resolve through DNS, including Tailscale MagicDNS names and 100.x addresses,
when UDP 53320 is reachable between nodes. Sending by address skips discovery and
certificate pinning.
Folders are walked recursively, symlinks skipped, and relative paths recreated on the
receiver. An existing unrelated file becomes name (1).ext; a leftover QuicDrop partial
resumes.
Names can repeat; the 8-character id shown next to a name is unique. When a name matches
several devices, qd lists the candidates instead of guessing. Send to one of their short
ids to pick exactly.
State is in ~/.config/quicdrop (override QD_CONFIG_DIR):
| Path | Contents |
|---|---|
identity.key, identity.crt |
device certificate and key |
name.txt |
display name |
trusted.json |
approved device ids |
daemon.json |
loopback API address and bearer token |
Incoming offers from unknown devices prompt on the terminal, or are rejected when there is no terminal. Deleting the directory creates a new device.
cargo run --manifest-path apps/desktop/Cargo.tomlThe app embeds quicdropd (loopback API on 53319) and serves the buildless ui/. Linux
needs webkit2gtk-4.1, gtk+-3.0, libsoup-3.0, javascriptcoregtk-4.1.
Peer rows show their id, and sends target the device id so the certificate is pinned. The
Add device dialog accepts a hostname or address with an optional label and port. Tailscale
peers are not discovered automatically, so add them by address. Settings → General renames
this device without changing its id or trust; Network lists the local addresses, including a
Tailscale 100.x interface, click to copy.
QUIC on UDP 53320, discovery on 53321, ALPN quicdrop/1. One connection per transfer,
length-prefixed postcard frames on the control stream:
| Frame | Direction | Purpose |
|---|---|---|
Hello |
sender → receiver → sender | version, device id, name, platform |
Offer |
sender → receiver | session id, FileMeta{id,name,size,hash?} |
Accept / Reject |
receiver → sender | per-file resume offset, or reason |
Complete |
receiver → sender | bytes written |
Error / Bye |
either | terminal |
Each file is cut into 8 MiB chunks that a pool of up to 4 workers sends over its own bidirectional stream:
FileHeader{session,id,offset,size,index,count}
payload
FileTrailer{id,hash}
FileAck{ok,hash,message}
A chunk is acked as soon as it is written; the last ack settles the whole-file digest. Peer discovery uses mDNS and a UDP beacon in parallel.
- ECDSA P-256 identity, stored once;
device_idis the blake3 fingerprint of the cert. - Senders pin the receiver's fingerprint, so a spoofed device id fails the handshake.
- The receiver approves or rejects every offer before touching the disk.
- Sender-supplied names are relative paths:
..is stripped, existing files are not overwritten.
The receiver does not authenticate the sender's certificate, so a trusted device id is scoped to the channel the user approved, not to a signed long-term identity.
MIT. See LICENSE-MIT.