How to use
- Open this page on both devices.
- On the first device press Start pairing; a QR code (and a text code) appears.
- On the second device scan that QR code with the camera (it opens this page and joins), or press Join with a code and paste the text code. It shows a reply code.
- Scan the reply with the first device's camera (Scan reply with camera) or paste it, and press Connect. The devices are now connected directly.
- Choose files on either device and press Send. The other device sees names and sizes and must press Accept first, then downloads the received files.
Worked example
A 6 MB file sent between two paired tabs arrives in 64 KB pieces; the receiver's SHA-256 matches the sender's, the sender sees “Delivered · SHA-256 verified”, and the status bar shows that the connection is direct on the local network.
Supported formats and limits
| Input | Any file type |
|---|---|
| Output | The original files, unchanged |
| Limits | No size cap from toolsdocks; both tabs must stay open. Received files are held in the receiving tab's memory until you download them, so very large files depend on that device's memory. |
| Engine | WebRTC data channel (64 KB chunks, buffered-amount backpressure, SHA-256 check on arrival); serverless pairing by exchanging deflate-compressed connection codes (QR or copy-paste) |
Limitations
- Browsers cannot scan your network for devices, so pairing always uses QR codes or copy-paste codes, once in each direction.
- Without the optional public STUN server, devices must be on the same local network.
- Some networks (guest Wi-Fi with client isolation, strict corporate firewalls) block direct connections; there is no relay server, so the transfer cannot start there.
Questions
Do both devices need to be on the same network?
By default, yes. You can allow connections across networks, which uses Google's public STUN server to learn your public IP address; the files still go directly between the devices. Guest Wi-Fi with client isolation or strict firewalls can block the connection, and there is no relay to fall back on.
Is there a size limit?
No limit from toolsdocks, but both tabs must stay open, and received files are held in the receiving tab's memory until you download them, so very large files depend on that device's memory.
Privacy
Device to device. Content travels directly between your two paired devices over an encrypted WebRTC connection. Pairing uses QR codes or copy-paste codes, so no server sees or relays your files.
- Google public STUN server (optional): Only when you allow connections across networks: your device's public IP address, so the two devices can find a direct route. File contents are never sent to it.
See the privacy policy for how toolsdocks handles data.