All Tools

P2P File Transfer

Transfer files directly between browsers — no server, no uploads

How to send a file browser to browser

  1. The sender chooses a file. The page creates an 8-character code and a share link.
  2. Send the code or the link to the receiver by chat, email or phone.
  3. The receiver opens the link, or enters the code on this page, and requests the file.
  4. The sender approves the request, and the file streams directly to the receiver.
  5. Keep both tabs open until the transfer reaches 100%.

Why peer-to-peer?

Most file sharing services upload your file to their servers, store it, and let the other person download it later. That means waiting twice, trusting a third party with your data, and living with size limits and expiry dates.

This tool connects the two browsers directly with WebRTC. The file is read from the sender's disk and streamed in small chunks straight to the receiver's browser. There is no upload step and no copy left on a server.

Security and privacy

  • WebRTC encrypts every data channel with DTLS, so the file content is encrypted in transit.
  • A public signaling server (PeerJS) only introduces the two browsers; it exchanges connection details, not file data.
  • When a direct connection is blocked by a firewall, traffic can pass through a relay (TURN) server. It stays encrypted, and the relay cannot read it.
  • Nothing is transferred until the sender approves the receiver.

Tips for large files

  • Transfers are usually fastest when both devices are on the same network.
  • Keep both tabs in the foreground and stop the computer from sleeping during the transfer.
  • Files over 500 MB work but take longer; files over 2 GB may hit browser memory limits on the receiving side.
  • To send several files or a folder, compress them into a single .zip first.

Frequently asked questions

Is there a file size limit?
There is no server-side limit because nothing is uploaded. The practical limit is the receiving browser's memory: the page warns above 500 MB, and transfers above 2 GB may fail on some devices.
Are my files stored on a server?
No. The file goes straight from the sender's browser to the receiver's browser. Snow Quest never receives or stores it.
Is the transfer encrypted?
Yes. WebRTC requires DTLS encryption on every data channel, so the file is encrypted end to end between the two browsers, including when a relay server is needed.
Do both people need to be online at the same time?
Yes. It is a live transfer between two open tabs. If the sender closes the tab, the code stops working and the transfer ends.
Why does the connection fail on some networks?
Strict corporate firewalls, some VPNs and certain mobile networks block peer-to-peer connections. Try another network, turn off the VPN, or put both devices on the same Wi-Fi.
Can I send multiple files at once?
One file is sent per transfer. Compress several files or a folder into a .zip archive and send that instead.