What Is Peer-to-Peer File Sharing? And Why It Beats Email and Cloud for Big Files

Sending a 4 GB video to a friend usually looks like this: upload it to a cloud bucket, wait, share a link, ask them to download it. The file crosses the internet twice, sits on a stranger’s server in between, and counts against somebody’s storage quota. None of that is necessary. The two devices are sitting on the same planet — often the same Wi-Fi — and they can just talk to each other.

That’s peer-to-peer file sharing: the file moves directly from sender to recipient, with no middle server holding a copy. The role of the cloud shrinks to a one-second handshake at the start — “Hey, are you there? Here’s how to reach me.” After that, it’s just two devices and a wire.

How it actually works

The protocol underneath InterDrop is WebRTC — the same real-time engine that powers Google Meet, Discord voice, and Zoom. It was designed for audio and video, but a single primitive in it, the RTCDataChannel, can carry any bytes you want. We use it to carry your file.

1. You and the recipient each load the same web page. The page asks a small “signalling” server for help finding each other — like asking the operator to connect a call. The signalling server never sees the file. It only relays connection instructions.
2. Both browsers exchange network addresses and pick the fastest path between them — usually directly over your local Wi-Fi, sometimes through your home router, only rarely through a public relay.
3. They run a cryptographic handshake (DTLS) and agree on a one-time symmetric key. From that moment, every byte is encrypted on the sender and decrypted on the receiver. Nothing in between can read it.
4. The file streams across as a sequence of encrypted chunks, in order, until done. Then the connection closes and the keys are discarded.

Cloud upload vs. peer-to-peer

The difference is easier to feel than to describe. Toggle below to see both paths animated, and the four numbers that change the most:

With a cloud upload, the file is copied three times: sender → server → server’s disk → recipient. Each hop is a place where the file can be slow, throttled, logged, scanned, or breached. With P2P, there is exactly one hop: sender → recipient.

“If the recipient is in the same room as you, sending them a file through California is not engineering — it’s habit."

"But is it actually private?”

Yes. The bytes on the wire are encrypted with DTLS-SRTP, the same scheme browsers use for video calls. The encryption keys live in your two browsers and are thrown away when the transfer ends. No server holds the file, and no server holds the keys to read it.

What that means in practice: even an attacker who taps your Wi-Fi sees an opaque stream of bytes — not the file. Even a misconfigured signalling server can’t read what gets sent later. The cryptography is the same stuff banks use; the only unusual thing is that, for once, it’s running end-to-end with no third party in the middle.

When to use P2P (and when not to)

Use peer-to-peer when:

• The file is large. Anything over a few hundred MB is faster device-to-device than via the cloud.
• The file is sensitive. Contracts, passport scans, medical PDFs, anything you’d rather not see breached later.
• The recipient is nearby — same Wi-Fi, same office, same household. You’ll typically hit your network’s full speed.
• You don’t want to make accounts. No sign-up, no app install — both sides just open a tab.

Use cloud storage when:

• The recipient is offline and will pick the file up later.
• You want a long-lived link to send to many people.
• You need versioning, comments, or other collaboration features.

The two are complements, not competitors. Most people just default to cloud for everything because they don’t know P2P is an option — and now you do.

Frequently asked