Connect two devices

Start here, then open the link on the other device. Once connected, either side can send files — they go straight between the two, encrypted, never through a server.

Got a link? Paste it here
  • 100% Free
  • No Sign-Up
  • No Credit Card
  • No Free Trial
  • No Pro Tier
  • No Watermarks

Nothing is uploaded. Just open it and start.

Send files straight to another device

Free, no sign-up, no app. Connect two devices with a link and a QR code, then send photos, videos and documents of any size directly between them. Your files never touch a server — not ours, not anyone's — so there's nothing to expire, delete or leak.

Nothing uploaded

Files go straight between the two browsers — no server in the middle, no copy left behind.

Encrypted

Every WebRTC connection is encrypted end to end in transit.

No size limit

Streamed in checked 1 MB parts, and written straight to disk in Chrome and Edge.

Checked, not hoped

Every part has a SHA-256 fingerprint. Damaged parts are re-sent, and 'Sent ✓' means the other side confirmed it.

Resumes after a drop

Lose Wi-Fi halfway and reconnect: files carry on from the last checked part.

Folders and .zip

Send whole folders with their structure and save everything as one .zip.

Scan to connect

QR codes both ways: phone to laptop in a few seconds, no typing.

Both directions

Either side can send at any time; the other accepts each batch first.

Notes and links

Pass a quick message, a password or a URL along with the files.

Frequently asked questions

How do I send a file?
On one device, press Create a connection link. Open that link on the other device — scan its QR code with a phone camera, or copy it and send it however you like. The second device then shows a reply code: on the first device, press Scan its QR code and point the camera at it, or copy and paste the code. Once they're connected, drop files on either device, and the other is asked to accept them.
Are my files uploaded anywhere?
No. The two browsers connect directly to each other with WebRTC, and the files go straight from one to the other, encrypted in transit. They never pass through our servers or anyone else's. To help the two browsers find each other, they ask Google's public STUN servers for their own public address, which means those servers see your IP address — but nothing you send.
Why do I need to send a reply code back?
Two browsers need to swap a little connection information before they can talk directly. Most services do that through their own server; this page doesn't have one, so the link carries the first half and the reply code carries the second. That's also why each link works for one connection — make a new one next time.
Is there a size limit?
There's no set limit. Files are streamed in 1 MB parts, and speed depends on your connection — on the same Wi-Fi it's usually much faster than uploading to the cloud and downloading again. In Chrome and Edge you can choose Save to disk when you accept, and the file is written as it arrives, so even a file bigger than your memory works. In other browsers the received file is held in the page until you save it, so very large files (several gigabytes) are best sent to Chrome or Edge on a computer with free disk space.
How do I know the file arrived intact?
Every file is cut into 1 MB parts and each part has a SHA-256 fingerprint. The receiving page checks each part before it keeps it; a damaged part is asked for again, and a file that keeps failing is stopped rather than saved. When the whole file is done, both devices work out the file's overall fingerprint and compare. 'Sent ✓' appears only after the other device confirms it has the file and the fingerprints agree. The fingerprint is shown on the row so you can compare it yourself.
What if the connection drops halfway?
Unfinished files are paused, not lost. Press Reconnect, make a new link on one device and open it on the other (the same steps as the first time), and each file carries on from its last checked part instead of starting over. This works as long as the page stays open on both devices — nothing is saved if either is closed or reloaded. If a different device answers the new link, nothing carries on.
Can I send a whole folder?
Yes. Choose a folder (or drop one on the page) and its structure is kept: the other device sees names like 'Holiday/2025/IMG_01.jpg'. On receipt you can save them all as one .zip (stored without compression, up to about 3.5 GB at a time), or in Chrome and Edge save straight into a folder you pick. Folder names are cleaned so nothing can be written outside the place you chose.
How can I be sure it's the right device?
Once connected, both screens show the same short safety code worked out from the two devices' encryption certificates. Compare it out loud or in another app. If it differs, the link or reply code was altered on the way, and you should disconnect. It's a check you do, not something the page can do for you.
It says the devices couldn't reach each other. What now?
Some networks — many offices, schools, hotels and some mobile carriers — block direct connections between devices. Connecting both devices to the same Wi-Fi almost always works. Otherwise, try a different network, such as a phone's hotspot. This page connects devices directly and has no relay server, by design: a relay would see your traffic and addresses, so strict networks that block direct connections simply can't connect.
Can both devices send?
Yes. Once connected, it works both ways at the same time: either side can drop files, and each batch has to be accepted by the other side before it starts. You can also send short notes and links.
Do I need to keep the page open?
Yes — keep this page open on both devices until the files have arrived, and keep phones unlocked (the page asks the screen to stay on while files are moving). Closing the page or locking the phone ends the connection. Received files are only kept in the page until you save them.

Spotted a bug or have a suggestion?

Found something broken, have an idea, or just want to say thanks about any of our tools? Every message reaches a real person.