v2.1These docs are for deaddrop 2.1: serve local files, stdin and URLs, allow-listed clients, expiring tickets, resumable fetches and seven new notifiers.What's new in 2.1 →

v2.1.0 · open source · public domain · written in rust

Leech it. Pass it.
Drop it. Leave a trace.Leave nothing.

Leech a torrent, or take any file, on a server. Hand it to one client over an encrypted peer-to-peer link. Leave nothing behind.

$ brew install asheliahut/tap/deaddrop
deaddrop — two machines, zero open ports
🖥 server
  1. $ deaddrop serve 'magnet:?xt=urn:btih:9f3c…'
  2. leeching ubuntu-24.04.iso · upload disabled
  3. ████████████████████ 100% ↑ 0 B
  4. swarm session stopped (dht, trackers, peers)
  5. serving over iroh · single use
  6. stdout ▸ blobafk3…q7z
  7. ✔ sent 6.1 GiB in 58s to b2319767b8
  8. single use: shutting down. nothing left.
💻 client
  1. $ deaddrop fetch blobafk3…q7z -o ./dl
  2. connection to e86045b272 using the relay
  3. … switched to a direct path
  4. ████████████████████ 6.1 GB BLAKE3 ✓
  5. ✓ ubuntu-24.04.iso

Output abridged for illustration.

// how it works

A dead drop in two commands.

A server downloads a torrent without seeding it (or takes local files, stdin, or an http(s) download), then hands the files to one client overiroh: end-to-end encrypted peer-to-peer QUIC with NAT traversal and relay fallback. Add --encrypt to age-encrypt them at rest too.

  1. 01

    Leech

    The server downloads the torrent with uploading disabled. Nothing is seeded, ever.

  2. 02

    Stop

    The swarm session is torn down. With --encrypt, each file is also age-encrypted to a new key and the plaintext is deleted.

  3. 03

    Drop

    A ticket is printed. The client connects peer to peer over end-to-end encrypted iroh, direct or relayed, and pulls the files.

  4. 04

    Vanish

    The client verifies every chunk. The single-use server shuts down, or wipes the data and waits.

// features

Small tool. Sharp edges, on purpose.

Zero seeding

Built on librqbit's disable-upload. No incoming BitTorrent listener, and the swarm session is torn down before serving starts.

End-to-end encrypted

iroh connections are QUIC with TLS 1.3, relays included. Add --encrypt to also age-encrypt every file and hide file names, with a key that never touches the server's disk.

NAT-proof, path-aware

iroh punches through NATs and falls back to relays, so neither side needs an open port. Every connection says if it's direct or relayed. Use n0's relays, your own, or none.

Verified delivery

Every chunk is checked against its BLAKE3 hash. Tampering (or a wrong key) fails loudly. No partial file is left under its real name.

Single use by default

One client, one download, then the server shuts down, or wipes the data and waits for the next drop.

Hot swaps

Point a running server at a new torrent with deaddrop reset. The old ticket dies.

Only the right client

--allow <ID> turns away everyone but the clients you name, so a leaked ticket is useless. --expire-after 24h wipes a drop nobody picked up.

Not just torrents

Serve local files and directories in place, whatever is piped into stdin, or a file the server downloads over http(s).

Notifications

Push tickets to Discord, Slack, Mattermost, Rocket.Chat, Telegram, ntfy, email, SMS or any webhook. With --encrypt, choose per notifier who also gets the key, or with --hide-key, who gets the only copy.

Progress bars

For the torrent, each transfer on the server, and the client download, with an ETA. Plain lines for logs, pipes and --no-progress.

Script friendly

The ticket on stdout, everything else on stderr. TOML config, env vars, shell completions.

Agent ready

deaddrop skill install teaches Claude Code, Codex, GitHub Copilot and other AI coding agents how to use and configure deaddrop.

// with --encrypt

Even the names are redacted.

iroh always encrypts the connection. Add --encrypt and only ciphertext goes into the blob store and over the wire. Collection entries are named 0, 1, 2… and the real file names live in an encrypted manifest. The key exists only in the server's memory, and with--hide-key it never even reaches the server's terminal.

What it doesn't hide: file sizes, file count, and the fact that a transfer happened. Plaintext exists on the server's disk while the torrent downloads. Without --encrypt, the ticket alone is enough to read the data. Read the threat model →

collectiondeaddrop-manifest.age 🔒
  • 0Season 1/E01.mkv
  • 1Season 1/E02.mkv
  • 2extras/notes.txt
  • 3cover.jpg

hover or tap to decrypt: needs AGE-SECRET-KEY-1…

// install

Brew it, grab a binary, or build it.

On macOS and Linux, Homebrew is the easiest way: it installs the prebuilt binary with shell completions set up. Prebuilt binaries for Linux (gnu + musl, x86_64 + aarch64), macOS (Intel + Apple Silicon) and Windows (x86_64 + ARM) are attached to every GitHub release, with SHA256SUMS.

# macOS and Linux, Intel + ARM
brew install asheliahut/tap/deaddrop

Then: quick start · config file ·shell completions

// faq

Questions, answered.

Does deaddrop seed the torrent?

No. The server downloads with librqbit's disable-upload, accepts no incoming BitTorrent connections, and tears the swarm session down before serving starts. No piece data is ever uploaded.

Is the transfer encrypted?

Yes. iroh connections are QUIC with TLS 1.3, end to end, relays included. Add --encrypt to also age-encrypt every file and its name on the server's disk, so the ticket alone isn't enough to read the data.

Do I need to open ports or set up a VPN?

No. iroh punches through NATs and falls back to a relay when a direct connection isn't possible. Relays only forward encrypted packets. Use n0's public relays, your own, or none.

What happens to the files after the download?

A single-use server deletes the downloaded data and shuts down once its one client has everything, or with --wait-for-reset, deletes it and waits for the next drop. Local files you serve are never moved, changed or deleted.

What if someone else gets the ticket?

Use --allow so only the clients you name can download, --expire-after so an unclaimed drop is wiped, and --encrypt so the ticket is useless without the key. By default, a single-use server serves only the first client.

Can it send things other than torrents?

Yes. Serve local files and directories in place, whatever is piped into stdin, or a file the server downloads over http(s).

Which platforms does it run on?

Linux, macOS and Windows, on x86_64 and ARM. Install with Homebrew, a prebuilt binary, or build from source with Cargo.

Is deaddrop free?

Yes. It's free and open source, released into the public domain under the Unlicense.

Read the docs. Then leave nothing behind.