How does Same-Wi-Fi P2P Radar discover nearby devices without a code?

Connected devices sharing the same public IP hash are grouped into a local discovery room so phones and laptops on the same Wi-Fi see each other automatically.

How is the WebRTC transfer encrypted?

Each session generates an ephemeral 256-bit AES-GCM key stored in the URL hash fragment (#k=...) that is never sent to the signaling server.

Same-Wi-Fi Radar + 6-Digit Room + PBKDF2 Static Relay Fallback

Browser-to-Browser P2P File Swing Engine

Stream unlimited files directly from Device A's disk to Device B's disk via WebRTC SCTP DataChannels with 64KB chunking, 4MB backpressure control, and Screen WakeLock.

Batch Format Converter

Backpressure-controlled 64KB chunks keep RAM usage flat on 20GB+ files

AES-256-GCM fragment key (#k=…) is never transmitted to the signaling server

Per-chunk & whole-file SHA-256 verification with FileSystem & StreamSaver disk output

Same-Wi-Fi P2P Radar Discovery

Devices on the same Wi-Fi appear automatically below — zero codes needed

Scanning local Wi-Fi subnet… Open this page on another device to pair automatically

AES-256-GCM file key stays in the peer channel; compare fingerprints before transferringPeer-to-peer · live speed appears during transfer

Phone ↔ PC Room Pairing

VERIFY PEER

6-Digit Swing Room Code

---

Drop Unlimited Files to Swing (20GB+ Direct-to-Disk Stream)

Zero cloud upload caps • 64KB chunked SCTP DataChannel • 4MB backpressure • Mobile Screen WakeLock protection

Ready for zero-cloud WebRTC SCTP streaming (64KB chunks, 4MB backpressure control).

WakeLock: STANDBY