How It Works
HyperLink is a peer-to-peer file transfer application that uses WebRTC to create direct, encrypted connections between browsers—no servers in between.
The Transfer Process
Connection Setup
Both sender and receiver connect to a signaling server using PeerJS. This server only facilitates the initial handshake—it never touches your files.
Peer Discovery
Sender enters receiver's Peer ID (or scans QR code). The signaling server exchanges ICE candidates to establish a direct P2P connection.
Direct Transfer
Once connected, files are split into chunks and sent directly browser-to-browser via WebRTC data channels. Maximum speed, zero server storage.
Completion
Receiver downloads the reassembled file. The connection closes and no trace of your data remains on any server.
Technology Stack
WebRTC
Real-Time Communication protocol enabling direct browser-to-browser data transfer with built-in NAT traversal using STUN/TURN servers.
DTLS/SRTP
Military-grade encryption protocols (DTLS 1.2, SRTP) are enforced by WebRTC, ensuring all data is encrypted end-to-end during transit.
Next.js + Supabase
React framework for the frontend, Supabase for auth and transfer metadata (not file content). Fully serverless architecture.
Security & Privacy
End-to-End Encryption
All transfers are encrypted using DTLS 1.2. Keys are negotiated directly between your browser and the recipient's—not even our signaling server can access them.
Zero Server Storage
Your files never touch our servers. The signaling server only coordinates the initial handshake. After that, data flows directly between peers.
Open Source
Our codebase is transparent. You can inspect, audit, and verify our security claims yourself. Trust through transparency.
Frequently Asked Questions
Is there a file size limit?
Technically, no. However, very large files (10GB+) may encounter browser memory limitations. For best results, we recommend files under 5GB.
What if the connection drops?
Currently, you'll need to restart the transfer. We're working on resume functionality that will allow transfers to pick up where they left off.
Which browsers are supported?
Chrome, Edge, Firefox, Safari, and Opera all support WebRTC. For best performance, use the latest version of Chrome or Edge.
Why can't I connect to my peer?
Connection issues are usually caused by restrictive firewalls or NAT configurations. Try using a different network, or check if your firewall is blocking WebRTC connections.