P2P File Transfer — Direct Device-to-Device
Your files go from your device to theirs. No server in the middle, no copy stored on our infrastructure, no 'we updated our Terms of Service to use your files for AI training.' Just WebRTC, a direct connection, and your full upload speed.
By starting, you agree to our Terms
How It Works
Your Device
Sender
Their Device
Recipient
No server in the middle. Files stream directly between browsers using WebRTC.
WebRTC Connects
A secure peer-to-peer connection is established between the two browsers using WebRTC.
Files Stream Directly
Your files travel directly from your browser to theirs. No server upload, no middleman.
Nothing Stored
After transfer completes, nothing remains on any server. Files exist only on sender's and recipient's devices.
Privacy by Architecture, Not by Promise
Privacy by Architecture, Not by Promise
Most services promise not to look at your files. We architecturally cannot. P2P means the file data travels directly between browsers — our servers handle connection setup, not file contents.
Zero Server Storage
No files on our infrastructure. Ever. There's nothing to subpoena, nothing to breach, nothing to accidentally expose. The data exists on two devices: yours and the recipient's.
WebRTC Under the Hood
DTLS encryption, ICE/STUN/TURN for NAT traversal, SCTP data channels for reliable delivery. It's the same protocol stack that powers video calls — battle-tested by billions of connections.
Automatic Relay Fallback
If direct P2P fails (strict corporate firewalls, symmetric NAT), Perkoon routes through an encrypted TURN relay. Still encrypted end-to-end. Slower, but it works where direct connections can't.
P2P Transfer vs Cloud-Based Transfer
| Aspect | P2P (Perkoon) | Cloud Upload |
|---|---|---|
| Where files go | Directly to recipient | Uploaded to server, then downloaded |
| Privacy | Files never leave your devices | Provider can access your files |
| Size limits | None | 2GB – 50GB typically |
| Speed | As fast as your connection | Limited by upload + download |
| Cost | Free | Free tier + paid plans |
| One sender, one receiver | Sender queues, fires on join | No |
Frequently Asked Questions
Do both people need to be online at the same time?
Nope. The sender can hit send before the receiver joins. We queue the transfer and fire it the second they show up. Just keep the sender tab open.
What if the recipient is offline?
Send anyway — the transfer queues. When they join, it starts automatically. If you can't keep your tab open that long, cloud storage lets you upload and walk away.
Why is P2P better than cloud upload?
P2P is faster (one hop, not two), more private (files never stored), has no size limits, and is free. The real difference: P2P is a one-to-one handoff. Cloud is for distribution — upload once, let multiple people download.
What are the actual limitations?
One sender. One receiver. The sender tab stays open until the transfer completes. That's it. No size limit, no account, no monthly cap.