P2P File Transfer with WebRTC
Military-grade encrypted file transfer. Browser to browser. No servers. No cloud. No compromise.
Create Secure Session
You will send files. Generate an offer and share it with the receiver.
Share this key securely with the receiver BEFORE connecting.
Join Secure Session
You will receive files. Paste or scan the sender's offer to connect.
What is P2P Share Vault ULTRA?
P2P Share Vault ULTRA is a cutting-edge, 100% browser-based file transfer tool that uses WebRTC (Web Real-Time Communication) to create a direct, encrypted tunnel between two browsers — with absolutely no server in the middle. Your files never touch any third-party server. They travel from your browser directly to the receiver's browser.
Every byte of your data is encrypted using AES-256 (the same standard used by governments and military organizations) before transmission. Even if a sophisticated attacker intercepts your WebRTC packets, the data is unreadable without your secret passphrase. This is the pinnacle of privacy-first file sharing.
How to Transfer Files: Step-by-Step Guide
For the Sender (Person A)
- Go to the Sender tab. Enter a strong Encryption Key (passphrase). Share this with the receiver via phone or messaging app.
- Click "Generate Offer SDP". A block of cryptographic session text (SDP) will appear.
- Copy the Offer SDP and send it to the receiver (via email, chat, etc.) — or click the QR button for the receiver to scan.
- Wait for the receiver to send back an Answer SDP. Paste it into the "Paste Answer" field and click "Establish Secure Channel".
- Once connected, drop your files into the transfer zone and click "Send All". Done!
For the Receiver (Person B)
- Go to the Receiver tab. Enter the same Encryption Key as the sender.
- Paste the sender's Offer SDP into the text box (or click the camera icon to scan the QR code).
- Click "Generate Answer SDP". An Answer SDP will be generated.
- Copy the Answer SDP and send it back to the sender.
- The connection is established automatically. Files will download automatically when received.
Under the Hood: The Technology Stack
1. WebRTC SDP Handshake (Zero-Server)
WebRTC requires an initial "handshake" to establish the peer connection. Normally, a "signaling server" handles this. Our "Paranoid Mode" eliminates this by having you manually copy/paste SDP (Session Description Protocol) text. This means zero metadata, zero logs, and zero server infrastructure involved. We use Google's free STUN servers (stun:stun.l.google.com:19302) only for NAT traversal, which is required for devices behind routers.
2. AES-256 Encryption Pipeline
Before any chunk is sent over the data channel, it is encrypted using CryptoJS AES-256 with your passphrase. The receiver uses the same key to decrypt each incoming chunk. The plaintext file never leaves your RAM. The AES key is derived from your passphrase using a secure hashing function and is never transmitted.
3. Large File Chunking (64KB Slices)
WebRTC data channels have a practical message size limit. We solve this by splitting your file into 64KB chunks using the FileReader.readAsArrayBuffer() API. Each chunk is encrypted, tagged with a sequence number and file metadata, then sent individually. The receiver reassembles them in order using a Blob and triggers an auto-download via FileSaver.
4. Folder ZIP on the Fly
When you drag and drop a folder, JSZip compresses the entire folder structure into a single .zip file in your browser's memory. This zip is then chunked and encrypted for transfer. The receiver gets a single zip file containing the full folder structure.
P2P Share Vault vs. Traditional Services
| Feature | P2P Share Vault ULTRA | WeTransfer / Dropbox | |
|---|---|---|---|
| Server Storage | Zero (P2P) | Stored on servers | Stored on servers |
| Encryption | AES-256 E2E | In-Transit only | Minimal |
| File Size Limit | Unlimited | 2GB - 5GB limit | ~25MB |
| Privacy | Maximum | Data analyzed | Scanned for ads |
| Sign-up Required | Never | For large files | Yes |
Initializing secure discussion portal...