Direct
Send files from this browser straight to another one: your laptop to your phone, or to a friend. Start a connection, share the link or the code, and either of you can send the other files. They go directly between the two browsers, encrypted end to end. How it works says what passes through this site.
Both pages stay open while files move. The other browser sees your IP address, as with any direct connection.
Loading…
This browser can't connect directly
Direct needs WebRTC, background workers and the browser's private file storage. Private windows often turn the storage off; a normal window in a current browser has all three.
Start a connection
You get a link, and a code to scan. Whoever opens it connects to this page. A link works once.
Someone shared a connection with you
Connecting opens a direct line between your browser and theirs, and lets you send each other files. Connect if you know who sent you the link.
Send files
Or drop them here. The other page is asked before anything is sent.
The other page wants to send you files
The connection is closed
How it works
Two browsers can't find each other on their own, so this site introduces them. Starting a connection makes a secret, the part of the link after #, which browsers never send to a server. Both pages work out a meeting room from it and send this site's server a few messages to set up the connection, sealed with a key from the same secret. The server passes them on without being able to read them, and can't put itself in the middle. One question goes to Cloudflare's STUN server, which tells each browser its own address on the internet.
After that the files go straight to the other browser, over WebRTC's own encryption, and inside it in the age format, to a post-quantum key the other page made for this connection only. When either page closes, that key is gone, so the link opens nothing afterwards. The server keeps only that the room was used, for a day, so a link that someone else opened first says so.
Files you receive wait in this site's storage in your browser until you save them, and are deleted when you close the page. To check what the page sends: the browser's network panel shows one WebSocket with unreadable frames, and chrome://webrtc-internals (about:webrtc in Firefox) shows the connection and its one STUN server.