Browser P2P File Transfer

Browser P2P File Transfer sends one or more files directly between modern browsers with an encrypted WebRTC DataChannel. No account is required, and codingtool.dev does not receive or store the file contents.

1. On the sender, create an offer and copy it to the receiver. 2. On the receiver, paste the offer, create an answer, and copy it back. 3. On the sender, paste and apply the answer. 4. Select files and request a transfer. 5. The receiver reviews the file list and accepts or rejects it. 6. After completion, the receiver chooses which files to download.

File bytes travel through the WebRTC connection and are never uploaded to codingtool.dev. Transfer history stores only file name, size, type, direction, status, and timestamp in this browser. Received file bytes remain in memory only until the page is reset or closed.

Room codes use short-lived server-side signaling metadata to help two browsers exchange WebRTC connection details; file contents are never sent through room signaling. Manual pairing remains available as a fallback. Some corporate networks, VPNs, firewalls, or NAT configurations block direct WebRTC connections. No TURN relay is configured, so connections that require a relay may fail. Large received files can use significant memory because the browser assembles each file before download.