P2P File Share Between Two Devices

How To Use

1. On the sending device, open this page, choose Send files and press Start sharing. A short code appears.
2. On the receiving device, open this same page, choose Receive files, type the code and press Receive.
3. On the sender, press Add files to share any number of files — they appear as a list on the receiving device.
4. On the receiving device, tap Download on the files you want (or Download all). Only the files you pick are transferred, device to device.
5. Faster option: press Copy link on the sender, and open that link on the other device — it joins the room automatically.

Use Cases

This is ideal for moving small, self-contained files between two of your own WebRTC-capable devices over the same network: pushing an ebook between phone and tablet, transferring a config file from your computer to your phone, or sharing a document with someone in the same room. Because the data flows device to device, nothing is left behind on a server — a privacy-friendly way to pass files around.

If the receiving device can’t run WebRTC (for example, a Kindle e-reader), use TXT to Kindle (short link): it only needs the other device to open a plain download link. It is also the better fit when you want a link you can paste into a message that auto-expires, rather than pairing two live browsers at the same moment — and for single text files it works on any browser that can open a URL, no pairing step required.

Limitations

• Both devices must be online and able to reach the internet for the initial connection handshake.
• Both the sending and receiving browser need WebRTC. E-readers such as the Kindle don’t ship WebRTC, and old or restricted browsers often lack it — on those devices the direct transfer can’t work. Use the “TXT to Kindle (short link)” tool instead (it only needs a plain download link).
• Large files transfer more slowly and use memory on the receiving device; text and ebook files are effectively instant. If a transfer would push the receiving browser past 500 MB held in total, it is refused with an explicit message instead of failing silently.

Frequently Asked Questions

Is my file uploaded to a server?

No. The file bytes travel directly between the two connected browsers over a WebRTC peer-to-peer data channel. Nothing is uploaded to, or stored on, any server.

Do both devices need to be on the same network?

They can be — same Wi-Fi is the most reliable — but they do not have to be. Because the connection is negotiated over the internet, senders and receivers anywhere can pair with the sharing code, as long as both are online.

How do I move a file between two of my devices (e.g. phone to Kindle)?

If both devices have modern, WebRTC-capable browsers (two phones, a computer and a phone, etc.): open this page on one, press "Start sharing" to get a code, add the file(s), and on the other device open this same page, choose "Receive files", and enter the code — files appear as a list you can download. For an e-reader like a Kindle, its browser rarely supports WebRTC, so this page cannot work on it — use the "TXT to Kindle (short link)" tool instead, which only needs the Kindle to open a plain download link.

How do I transfer files from an Android phone to a PC without a cable?

Open this page in Chrome on the Android phone, press "Start sharing", and add the files. On the PC, open the same page in any modern browser, choose "Receive files", and type the short code shown on the phone — the files stream directly over Wi-Fi and you download them from the list. The same flow works in reverse (PC to Android) and between two Android phones. No app install, no cable, no cloud upload.

Why does the page connect to a signaling server?

To start a direct connection the two browsers must first find each other. Only a tiny connection handshake (not your file) goes through a free public signaling service. Once paired, the file flows straight between your devices.

Does the receiving browser need to be modern?

Yes — both the sending and the receiving browser must support WebRTC, because the device that downloads the file also has to run WebRTC to receive the stream. E-readers like the Kindle do not ship WebRTC, and old or restricted browsers often lack it, so the direct transfer cannot work on those devices. If you need to reach a Kindle, use the "TXT to Kindle (short link)" tool, which works with any browser that can open a plain download link.

Is there a file size limit?

No file format is blocked, but the receiving browser keeps received files in memory, so a transfer is refused with a clear message if the total the receiver is holding would exceed 500 MB. Files you have already downloaded count toward that total until the page is reloaded. Large files also transfer more slowly, so a fast, stable network still gives the best result.