Send files from phone to PC without an app
The QR pairing flow step by step, with no cable and nothing to install.
Files travel live from one browser to the other while you're both on the page. No app, no account, no upload to wait for.
Enter the code from the receiver's screen, or scan their QR code. Then choose your files.
You'll need the receiver's codeSomeone is sending me filesGet a short code and QR code to give the sender. You approve the files before anything arrives.
The receiver goes firstLive, like a call
Both of you keep the page open until the files arrive.
Never stored
Encrypted on the sending device and not kept on our servers.
Nothing to install
Any browser, any device. No account. Up to 1 GB per file.
Open Receive
You get a short code and a QR code, valid for two minutes until someone connects.
Give it to the sender
Send them the link, let them scan the QR code, or read the code out.
Check and accept
You see the file names and sizes, and accept only what you expect.
Files save to your device
Keep the page open until it says the files were received.
Get the receiver's code
Or just open the link they send you — it connects automatically.
Enter it or scan it
Type the code on the Send page, or scan their QR code with your phone.
Choose your files
The receiver sees what you're sending and has to accept it.
Wait for “Files sent”
Keep the page open until the receiver's device confirms everything arrived.
Best when you're both available now — your own devices, or someone you're talking to.
Best when the other person will get to it later, or several people need the file.
Use a cloud link instead →Most ways of sending a file make two journeys: up to someone's server, then back down to the recipient. A direct transfer makes one. The file goes from the browser on one device to the browser on the other, and is never written to storage along the way.
That changes three things at once. There is no upload to wait for before the other person can start receiving. There is no copy left sitting on a server after you are done. And there is no storage quota to run into, because nothing is stored.
When the two devices can reach each other, larger files travel over a direct WebRTC data channel between them — the one route where your file data never touches our infrastructure at all. Setting that channel up takes a moment, so small files skip it and go through our socket relay instead: the setup would take longer than the transfer.
Corporate firewalls and some mobile carriers block a straight route between devices. Some peer connections cannot find a direct route and are relayed by our TURN server instead. It forwards packets that are already encrypted twice over — your AES-GCM ciphertext inside the connection's own DTLS — and holds no key for either layer.
If no peer connection can be made at all, the socket relay is the last resort. Chunks are relayed through our server when a direct connection is impossible, and for small transfers where negotiating one would take longer than sending the file — still as ciphertext we hold no key for. The relay is a bridge, not a reader.
Whichever route is taken, the encryption described below happens on the sending device before the data leaves it. The route decides how the bytes travel, not whether they are protected.
The receiving browser generates a per-session RSA-2048 (RSA-OAEP, SHA-256) key pair. The sender wraps a random 256-bit AES key with that public key, then encrypts every chunk with AES-256-GCM before it leaves the device.
The private key is generated inside the receiving browser, is non-extractable, and is destroyed when the tab closes. It is never transmitted.
Each chunk carries a GCM authentication tag with its sequence number authenticated alongside it, and a SHA-256 hash of the whole file is verified on arrival.
Both devices display a fingerprint of the public key each is actually using, as 8 emoji and 12 hex characters. Comparing them rules out a substituted key — the one attack encryption alone cannot prevent. If the codes on the two screens match, nobody has slipped their own key into the middle of the connection.
That holds as long as the code running in your browser is the code we describe. For the encryption itself you no longer have to take that on trust: it is served as a published build you can reproduce byte for byte and compare against what your browser loaded. What remains is the application around it, which is closed source — it is what hands your file and your password to that code, and nothing here proves it does not read them first.
The security page sets out the full architecture, including what you can check for yourself without trusting us.
The common ways to move a file from one device to another, compared on what they store and what they ask of you.
| Direct transfer | Cloud link | Email attachment | USB cable | |
|---|---|---|---|---|
| Stored on a server | Never | Until the link expires | In both mailboxes, indefinitely | No |
| Largest file | Up to 1 GB | Per-upload limit, shown as you add files | Around 25 MB | Free space on the drive |
| Both people present | Yes, at the same time | No | No | Same room |
| Install or sign-up | Neither | Email verified once | An email account | A cable, sometimes drivers |
| Encryption | AES-256-GCM per chunk, key wrapped with RSA-2048 | Optional, with a password | Usually in transit only | None |
| Works across platforms | Any modern browser | Any modern browser | Yes | Often awkward, e.g. iPhone to Windows |
The receiver. They open the Receive page, which shows a short code and a QR code. The sender then enters that code on the Send page, scans the QR code, or opens the link the receiver sends them. If you're the sender and don't have a code yet, ask the receiver to open Receive first.
Open the Receive page on the device that should get the file and it shows a room code and a QR code. On the sending device, scan the code or type it into the Send page, choose the file, and the receiver approves it. The file then streams from one browser straight to the other, with no upload step and no copy left on a server.
It is as safe as its encryption and its pairing. Here, the receiving browser generates a per-session RSA-2048 (RSA-OAEP, SHA-256) key pair. The sender wraps a random 256-bit AES key with that public key, then encrypts every chunk with AES-256-GCM before it leaves the device. The safety code shown on both screens lets you confirm you are connected to the right device.
Yes. Nothing is stored in between, so the file has nowhere to wait — both browsers need to be open until it finishes. If the other person will open it later, send a cloud link instead.
Sometimes, but only as ciphertext, and it is never written to storage. When the two devices can reach each other, larger files go straight between them and never touch our infrastructure. If a network blocks that route, the connection is relayed through a TURN relay server; small files, and connections that cannot be made at all, go through our socket relay. On every route the data is encrypted before it leaves the sending device, so anything passing through us is ciphertext we hold no key for.
Up to 1 GB per file. For anything larger, split it into parts or send a compressed copy.
No. A direct transfer works across different networks, including mobile data, and is usually just as fast as being on the same Wi-Fi — what actually matters is whether the two devices can connect directly at all. Mobile data and heavily restricted networks are the ones most likely to block that and fall back to our relay, which is slower.
Yes. It runs in any modern browser — Safari, Chrome, Edge or Firefox — so any pair of devices works, including combinations that AirDrop and Quick Share do not support.
Short interruptions are handled: both sides wait for the other to reconnect, and the receiver asks for any chunks it missed. If a tab is closed, the transfer ends and has to be started again.
The file's contents are never stored or logged. Non-content details are — the file name, size and type, timestamps, which route it took, and each side's IP address and browser — for rate limiting and abuse prevention. The privacy policy lists all of it.
The QR pairing flow step by step, with no cable and nothing to install.
Transfer between iPhone, Android, Windows and Mac in any combination.
Laptop to laptop without a USB drive, a network share or a cloud upload.
Why messaging apps shrink your video, and how to send the original.
The key exchange, the cipher and the safety code, in plain English.
What zero-cloud transfer actually means, and where it falls short.
For the full cryptography behind direct transfers, see the security architecture page, or compare every mode on how it works.