QR file transfer
Share tool
Only this public address is included. Your files, inputs and results stay out of the link.
Connect two browsers, confirm the other device and choose what to send.
Preparing your tool…
A visual example
Connect first, then choose what to receive
A connection link joins two browsers. It does not by itself approve a file transfer.
- Session link or QR codeSending browserReceiving browser
Join the same session
Open the session link or QR code on the other device. Keep the session link private.
- Checked: Fingerprints match on both devices
- Checked: Both sides explicitly confirm
Compare and confirm
Compare the complete displayed fingerprints on both devices, then confirm on both sides. Stop if they do not match.
Accept only the wanted file Offered file Choice notes.txt · 12 KiB Accept photo.jpg · 240 KiB Decline Accept only the wanted file
The offer displays names and sizes. The receiver chooses which file contents may follow.
Joining, confirming the connection and accepting files are separate decisions.
Illustrative example. The current release has no relay fallback; some networks will not connect. File contents travel over the direct connection after acceptance. Save the received download before closing the page. The tool displays the active limits.
How to use it
- Create an invitation on the sending device and open its private QR code or fragment link on the receiver.
- Join explicitly. Compare both complete sender and receiver fingerprints on both devices, then confirm on each.
- Select files on the sender. Check the offered names and sizes on the receiver and explicitly accept or decline.
- Wait for received and chunk-verified bytes. Request each download and check the actual saved files on your device. Close the session to clear temporary files.
Send a small test text file between two devices on your home network. Both devices confirm the same fingerprints; the receiver accepts the file and checks its downloaded contents. Separate or isolated networks can fail without a relay.
Details & limits
One receiver; eight files per offer; 50 MiB total per connection. Short text up to 8 KiB. A configured relay can connect different networks; without it, use the same trusted network. Signaling stores temporary connection data; files and text use the encrypted WebRTC channel. Downloads need an explicit save. No resume, cloud mailbox or malware scan.
Are the files uploaded to a server, and does 'received' mean they are saved?
File names and bytes travel over the confirmed, transport-encrypted WebRTC channel. Short-lived connection descriptions, fingerprints and network addresses pass through signaling infrastructure. Received files remain in the receiver's tab; a download request does not prove a filesystem save. The private invitation is a temporary access capability and should reach only the intended receiver.