P2P File Transfer

Send files directly between browsers using WebRTC — no server, no cloud, no size limit.

How it works

1. Exchange codes

Sender generates a connection offer. Receiver pastes it to accept.

2. Direct channel opens

WebRTC creates a direct encrypted tunnel between both browsers.

3. Transfer files

Files stream peer-to-peer. Nothing touches a server.

Choose your role to get started:

Send Files

I want to send files to someone

Receive Files

I have a code from a sender

Sender

Waiting to connect…

1 Your connection offer

Share this code (or QR) with the receiver. They paste it on their side.

Generating offer…

2 Paste receiver's answer

Once the receiver accepts, they'll give you an answer code. Paste it here.

3 Queue files to send

Drop files here

or click to browse — any size, any type

Receiver

Waiting to connect…

1 Paste sender's offer

The sender will give you a connection offer code. Paste it here.

3 Received files

Files sent by the sender will appear here for download.

100% private. Files travel directly between browsers via an encrypted WebRTC DataChannel. No file data is sent to any server. The signalling codes (SDP) contain only connection metadata, never file content.

About P2P File Transfer & WebRTC

What is Peer-to-Peer (P2P) Sharing?

Traditional file sharing works by uploading your file to a cloud server (like Google Drive or Dropbox) and then having the recipient download it from that same server. P2P sharing removes the middleman. By using WebRTC (Web Real-Time Communication), this tool creates a direct, encrypted tunnel between two browsers. Your files stream directly from your hard drive to theirs, meaning higher speeds, no storage limits, and absolute privacy.

[Image of P2P vs Client-Server network architecture]

Why Use WebRTC for Transfers?

WebRTC is a powerful browser technology that enables professional-grade communication without plugins. For file transfers, it offers unique advantages:

No File Size Limits: Since the file never sits on a server, you aren't limited by cloud storage quotas. You can send a 10GB video file just as easily as a small PDF, provided both parties stay online.
End-to-End Encryption: The data channel is encrypted using DTLS (Datagram Transport Layer Security), ensuring that even if someone intercepted the traffic, they couldn't read the content.
Direct Local Speed: If both devices are on the same local Wi-Fi network, the transfer happens at the speed of your router, bypassing the bottleneck of your internet upload speed entirely.
Browser-to-Browser: No software installation is required. It works on Chrome, Firefox, Safari, and Edge across Windows, macOS, Android, and iOS.

The Connection Process Explained

To establish a direct connection without a central server knowing who you are, browsers perform a "handshake" using Session Description Protocol (SDP) codes:

The Offer: The Sender generates a code containing their network capabilities and cryptographic keys.
The Answer: The Receiver processes that offer and generates a matching "Answer" code to agree on the connection parameters.
The Tunnel: Once both codes are exchanged, the browsers find the shortest path to each other and open the data pipe.

Privacy & Zero-Logging

The Client-Side Toolbox does not run a "signalling server" to automatically connect users because that would involve tracking your IP address. By requiring you to manually exchange the codes (via chat, email, or QR code), we ensure that zero information about your transfer is ever logged. We don't know who is sending what, how large the files are, or when the transfer happens. It is the ultimate tool for confidential document sharing.