DropLink WeTransfer
WeTransfer is convenient — but your files sit on their servers, limited to 2 GB on the free tier, expiring after 7 days. DropLink transfers files peer-to-peer with end-to-end encryption: no cloud, no size limits, no expirations.
Quick answer
WeTransfer uploads your files to its servers, limits them to 2 GB on the free plan, and expires them after 7 days. DropLink transfers files peer-to-peer with end-to-end encryption — files never touch our servers, there are no size limits, and they do not expire because they are not stored anywhere server-side. When NAT hole-punching fails we fall back to a DERP relay, but the relay only sees encrypted bytes (Noise + TLS 1.3) and cannot read content. Integrity is verified with BLAKE3 hash tree via Bao verified streaming.
Feature matrix
| Feature | DropLink | WeTransfer |
|---|---|---|
| Peer-to-peer (no cloud) | ||
| End-to-end encryption | Partial | |
| File size limit | None | 2 GB (free) |
| Account required | ||
| Expiration of shared files | Never (direct) | 7 days |
| Native apps | Partial | |
| Works on LAN (no internet) | ||
| Files stored on servers | ||
| Open source protocols (QUIC, Noise) | ||
| Price | Free | Free / $12/mo Pro |
Should you switch to DropLink?
For privacy-conscious users and anyone sending files larger than 2 GB, DropLink is a clear upgrade. You skip the upload/download cycle entirely, files stay private, and there is nothing to expire.
Common questions
Why choose DropLink over WeTransfer?
WeTransfer uploads your files to their servers — they can (and do) see file metadata, sizes, and recipients. DropLink transfers files directly between devices with end-to-end encryption. Your files never touch our servers, and there are no limits or expirations.
Can DropLink replace WeTransfer for sending large files?
Yes. DropLink has no file size limit and transfers happen peer-to-peer, so you are only limited by your network speed. For 10 GB files, DropLink will be dramatically faster than WeTransfer since there is no upload/download round trip through a server.
Does the receiver need DropLink installed?
No. DropLink includes a built-in Web UI — the receiver opens a link in any browser and downloads the files. You only need DropLink on the sending device.
How DropLink avoids the cloud
Peer-to-peer, not server-stored
WeTransfer is a cloud product: the sender uploads to WeTransfer's storage, the receiver downloads from the same storage. Files sit on WeTransfer's servers for 7 days (or longer on paid plans). DropLink has no storage: files stream directly from the sender's device to the receiver's device over QUIC. The DropLink relay server only coordinates the initial handshake and, in the worst case, forwards encrypted packets — it has no storage, no uploads, no file content.
No size limits because no server
WeTransfer's 2 GB (free) and 20 GB (Pro) limits exist because they have to store each file. DropLink streams directly peer-to-peer, so the only limits are your network speed and available disk on the receiver. We have tested transfers up to 100 GB. Folders are automatically zipped with adaptive compression: Deflate level 6 for text/code, Deflate fast for files > 10 MB, Stored (no compression) for already-compressed formats (mp4, jpg, zip, etc.).
End-to-end encryption by design
WeTransfer encrypts in transit (HTTPS) and at rest on their servers, but since the files are on their servers, WeTransfer itself can technically access them — and is legally obliged to comply with subpoenas. DropLink uses end-to-end encryption: TLS 1.3 on LAN with TOFU fingerprint, Noise protocol (IK, ed25519 + curve25519) for iroh remote transfers. Even the DropLink relay, which may forward bytes when direct P2P is impossible, only sees encrypted traffic and cannot decrypt file contents.
No accounts, no emails, no tracking
WeTransfer sends emails to track downloads, requires an account for larger plans, and monetizes attention via advertising. DropLink has no account system, no email collection, no analytics on file content. Each install generates a local ed25519 keypair stored in the Keychain (or on disk) — that is the only identity.
Why is DropLink more private than WeTransfer?
With WeTransfer, files live on their servers for at least 7 days. Anyone with legal access (law enforcement, employees with privileges, attackers who breach the storage) can potentially read them. DropLink files exist only on the sender and the receiver. The signaling server sees share IDs and connection metadata (NodeID, timestamps, IP addresses during active sharing) but never file content. The DERP relay, used only when direct P2P fails, forwards Noise-encrypted QUIC packets — decrypting them is computationally infeasible without the session keys, which are only on the two endpoints. BLAKE3 verified streaming via Bao tree ensures no tampering is possible mid-transfer.
Speed and limits
- File size limit
- None (tested up to 100 GB)
- Upload/download cycle
- None — direct streaming
- Transfer speed
- Limited only by the slower endpoint's bandwidth
- Compression
- Adaptive (Deflate, Fast, Stored)
- IO buffer
- 1 MB (reduces syscalls on large files)
- Expiration
- None — files are not stored anywhere
Technical FAQ
Do files ever touch the DropLink server?
No file content does. The signaling server coordinates the initial handshake (share ID generation, NodeID resolution). If direct peer-to-peer fails, the DERP relay forwards Noise-encrypted QUIC packets between the two endpoints — the relay sees only ciphertext, not plaintext. There is no storage layer.
What is the largest file I can send?
There is no imposed limit. We have tested single transfers up to 100 GB. The practical limit is your network speed and the receiver's available disk space. For very large folders, DropLink's adaptive compression automatically chooses the best strategy: Deflate for compressible data, Stored for already-compressed files (mp4, jpg, zip, etc.).
Can the receiver download in a browser, without an app?
Yes. For LAN receivers, the sender's device starts a local HTTP server with a shareable link. For remote receivers, the DropLink gateway on our relay server acts as a bridge: it downloads the file from the sender via iroh and proxies it as an HTTP response to the browser. The gateway decrypts on the fly but never stores the file.
How is this different from magic wormhole or similar P2P tools?
Conceptually similar (both are P2P with code-based pairing) but DropLink uses QUIC + iroh instead of the wormhole protocol, which gives us 1-RTT handshakes, better NAT traversal via DERP, BLAKE3 verified streaming, and a built-in Web UI so the receiver never needs an app. It is also available as native apps on macOS, Windows and (soon) iOS — not just a CLI.
Is there an expiration date on DropLink links?
Links are active as long as the sender keeps the share open (sender's app running, share not explicitly closed). There is no server-side TTL on files because there are no files server-side. You can optionally enable password protection: the relay will then hold a session token with a configurable TTL (default 3600 s) — but still no file content is stored.