p2p file sharing. No uploads, no limits, no traces.

0 bytes stored 🔒 E2E encrypted ⚡ P2P live 📦 Unlimited size

☁️

No cloud, no retention, no leaks. The server only introduces your two browsers — bytes flow device-to-device.

🔒

WebRTC + DTLS. Only you and your receiver can read the files — not us, not anyone in the middle.

📏

No storage means no quotas. A 100 MB deck or a 20 GB video project — same flow.

dotted = introductions via server · solid beam = your files, device to device

signaling · SDP + ICE — zero file bytes DataChannel · DTLS-encrypted · 256 KB chunks

signal serverintroductions only · 0 bytes stored idle

You · senderyour browser 🔒 files stay on device

🔒 files stay put

Receivertheir browser 💾 streams to disk

📡 via server 0 B ⚡ device → device 0 MB the whole point: the left meter never moves

You pick filesThey never leave your device — a private link + 4-digit nearby code is minted instantly.

1 · You pick filesnever leave your device — link + code mintedPOST /api/rooms → private link + 4-digit code
2 · You send the linkQR, copy, or share — they hit DownloadWebSocket signaling · SDP offer/answer + ICE trickle
3 · Direct streamshortest path, encrypted, to their diskRTCDataChannel · 256 KB chunks · DTLS · 0 B via server

How long are files available?

As long as your tab stays open. Close it and the link dies instantly — nothing was ever uploaded, so there's nothing to delete.

Is there really no size limit?

Correct. The limit is your devices + network, not us. Chrome / Edge / Firefox stream straight to disk; Safari holds files in memory (~4 GB).

What if we're on a strict corporate network?

Some symmetric NATs block direct P2P. A TURN relay fallback (paid tier) is next on the roadmap — free P2P covers most home / café / campus networks.

Can the receiver get files while I'm offline?

Not in P2P mode — both sides must be online together.

Payload — pick files