Encrypted Direct Link
Browser to Browser Transfer.
10 GB, 100 GB, a terabyte — there is no cap, because nothing is uploaded. Share a six-digit code and the bytes go straight from your device to theirs.
Sender
Drop a file, or click
Any size · Stays on device
File—
Size—
Type—
Share this code
------
Expires in 15:00
Channel idle
0 MB/s
0 B of 0 B
Route unknown
Receiver
IncomingWaiting…
Size—
Saving to—
- Zero Server Upload
- DTLS Encrypted
- No Registration
- No Size Limits
What Peer-to-Peer actually means.
FileXL P2P uses WebRTC data channels to connect two browsers directly. The server only helps them find each other; it never touches the file.
Trade-off: Both people have to be online at the same time, with the page open, for the whole transfer. If you need offline collection, use our standard upload.
-
1. The Handshake
The sender's browser requests a code. The server holds this connection offer for 15 minutes.
-
2. The Connection
The receiver enters the code. Browsers exchange routes and negotiate the fastest encrypted path.
-
3. The Stream
The file streams device to device, writing directly to the receiver's disk to prevent memory crashes.
P2P vs Standard Uploads
When peer to peer beats an upload — and when it doesn't.
| Feature | FileXL P2P | Email Attachment | Cloud Drive Link |
|---|---|---|---|
| Size Limit | Unlimited | ~25 MB | Plan Dependent |
| Server Storage | Zero (Direct) | Permanent | Temporary / Permanent |
| Wait for Upload | No (Streams live) | Yes | Yes |
| Both Must Be Online | Yes | No | No |
Frequently Asked Questions
No limit is imposed by FileXL, because nothing is stored. The practical ceiling is your connection speed and the receiver's free disk space. The receiving browser writes to disk as data arrives rather than holding the file in memory.
WebRTC data channels are encrypted with DTLS and encryption cannot be switched off. The file is encrypted in transit between the two browsers. Note that the six-digit code is the only thing gating the session, so send it over a channel you trust. Each code works exactly once.
On a direct route, throughput is limited by the slower of the two connections. Two machines on the same office or home network often move data dramatically faster than a cloud round trip, because the bytes never leave the building.