P2P File Share
Send files directly between browsers. Encrypted, compressed, verified.
AES-256-GCM Encryption
Set a shared passphrase and every byte is encrypted with a PBKDF2-derived 256-bit key before it leaves the browser.
SHA-256 Integrity
The receiver recomputes SHA-256 and verifies the hash — you'll know instantly if a byte was corrupted.
True Peer-to-Peer
WebRTC data channels carry the payload directly between browsers. No server sees your files.
Frequently Asked Questions
Is any file uploaded to a server?
No. Files travel directly between browsers over a WebRTC data channel. A public STUN server helps discover network paths, but it never sees your data.
What if my peer and I are on different networks?
STUN handles most home networks. Symmetric NATs may block direct connection — try again on a shared Wi-Fi or use a TURN relay if you have one.
How do I encrypt?
Enter the same passphrase on both sides after connecting. Everything after that is AES-256-GCM encrypted before it leaves the sender.
Is there a file size limit?
Only what your device can hold in memory. Each chunk is streamed with backpressure so browsers stay responsive.
What about integrity?
The sender computes SHA-256 up front and includes it in the offer. After decompression the receiver recomputes and compares — mismatches are surfaced immediately.