How peer-to-peer file transfer works

TL;DR
Peer-to-peer (P2P) file transfer moves a file directly from one device to another instead of uploading it to a server and back down again. In the browser this uses WebRTC: a small signaling step helps the two devices find each other, then the file streams straight between them over an encrypted connection. Because no server holds the file, it’s faster for a live handoff and more private. Shafle works exactly this way.

Most file-sharing services are client-server: you upload your file to a company’s servers, they store it, and the recipient downloads it later. Peer-to-peer flips that — the file goes device to device, with no copy parked in the middle.

The three steps of a P2P transfer

  1. Signaling— the two devices need to discover each other. A lightweight signaling step swaps a short connection code (in Shafle, that’s the share code / QR). This exchanges only connection details, not your file.
  2. Connection— using those details, the browsers open a direct WebRTC data channel between themselves, punching through home routers with help from STUN servers (and a TURN relay only as a fallback when a direct path isn’t possible).
  3. Transfer — the file is split into chunks and streamed straight across that channel. It arrives on the other device and is reassembled there.
Encrypted
WebRTC data channels are encrypted in transit by default (DTLS). [MDN]

Why it’s private

Since the file never touches a server, there’s no stored copy to be scanned, retained, leaked, or handed over. The signaling server only ever sees a short code used to introduce the two devices — never the file contents. That’s the core reason people choose P2P; see is P2P file sharing safe? for the honest risk picture.

Why it’s free

Storing and serving everyone’s uploads is what costs money at scale. When the file moves directly between users, the service isn’t paying for storage or download bandwidth — which is why a P2P tool like Shafle can be free with no size quota. The trade-off:

P2P is synchronous. Both people have to be online at the same moment for the transfer to run, because there’s no server holding the file for later pickup. For a live handoff that’s ideal; for “leave it for them to grab tomorrow,” a store-and-forward service fits better.

Want to just use it? Here’s how to send a large file free, or read about sending files without a cloud upload.

Frequently asked questions

What is peer-to-peer file transfer?

It's a way to send a file directly from one device to another without uploading it to a server in between. The file streams straight between the two devices.

How does peer-to-peer transfer work in a browser?

Browsers use WebRTC. A short signaling step helps the two devices find each other, then they open a direct encrypted data channel and stream the file across it. No copy is stored on a server.

Is peer-to-peer file transfer encrypted?

Yes. WebRTC data channels are encrypted in transit by default using DTLS, so the file is protected as it travels between the two devices.

Why does peer-to-peer require both devices to be online?

Because there is no server storing the file for later. The transfer is live, so the sender and receiver both need to be online at the same time.

Try it now — no signup, no upload wait.Open Shafle →

Related guides

Last updated: July 5, 2026