DeviceHopCreate a session
A random, temporary session token is created in server memory. It expires after inactivity.
BEHIND THE TRANSFER
How browser-to-browser file transfer works
DeviceHop combines a temporary QR pairing link, WebRTC and an encrypted relay fallback so two browsers can exchange files without first placing them in permanent cloud storage.
Pair by QR or link
The QR code contains only the private pairing URL — it does not contain the selected files.
Connect the browsers
The server introduces the two browsers so they can negotiate a WebRTC connection.
Send and download
File data travels over the encrypted connection and is assembled in the receiving browser.
What the QR code actually does
When a session starts, DeviceHop generates a high-entropy URL and displays it as a QR code. Scanning the code opens that same temporary session on the second device. The QR code is a convenient way to share the pairing address; the file itself is never encoded inside the QR image.
How the two browsers find each other
A small signaling server exchanges connection descriptions and network candidates between the browsers. This is coordination data, not file content. Once WebRTC is ready, the file transfer uses a browser DataChannel.
Direct connection and TURN fallback
DeviceHop first attempts a direct connection. Some mobile, office or carrier networks block the required path. In that case, encrypted WebRTC packets can pass through the DeviceHop TURN relay. The relay moves network packets but does not write the transferred file to storage.
Encryption during transfer
WebRTC DataChannels are encrypted in transit. The receiving browser reconstructs each file in memory and offers it for download. The browser and operating system then control where the receiver saves it.
Do the devices need the same Wi-Fi?
No. The devices can be on the same network, different Wi-Fi networks, or one can use mobile data. Both need internet access and should keep the transfer tab open until every file completes.
Current practical limits
Each file can be up to 512 MB. Multiple files can be queued in one session, but an interrupted file restarts from the beginning. Received files are temporarily assembled in browser memory, so available device memory still matters for large transfers.
NO INSTALLATION