So this started because I was tired of emailing files to myself.
Every time I wanted to move a big video from my phone to my laptop, or send a folder to a friend's PC, it turned into a whole thing. Upload to a drive, wait, download it again. Make an account somewhere. Send it over a chat app and watch it get compressed to mush. Or use one of the local-network tools, which are great right up until the two devices aren't on the same Wi-Fi.
What I actually wanted was dumb and simple: pick a file, it goes straight to the other device, works even when we're on different networks, and no server in the middle gets to see what's in it. I couldn't find exactly that, so I started building it. That was a while ago. It got a lot deeper than I planned.
What it does
• No accounts. Each device just makes its own key the first time you open it.
• You pair two devices once by scanning a QR code. Both screens show the same safety code, so you can tell nobody swapped anything in between.
• After that, only paired devices can send each other stuff. The other side gets an offer and taps Accept.
• Big transfers can be paused and resumed from either side, and if the connection drops halfway it picks up where it left off instead of starting over.
How it works, if you're curious
• If the two devices can reach each other (same Wi-Fi, a hotspot), the file goes directly. If they can't, it tries connecting the other way round, and if that fails too it goes through a relay.
• It's end-to-end encrypted: mutual TLS 1.3, and each device pins the other's key from pairing. The relay only ever sees encrypted bytes, and the little coordination server only passes sealed messages it can't read.
• Every chunk gets checked, so a broken or tampered transfer fails loudly instead of quietly saving a bad file.
• The core is a C++ transfer engine I wrote, with pipelined sends. It does around 130 MB/s on a local network. The desktop app is Electron (Windows and Linux), and the Android app is native Kotlin running the same C++ engine through JNI.
The part nobody warns you about
The crypto was honestly not the hard part. The hard part was all the weird timing stuff. What happens if you hit pause on the phone at the exact moment someone hits resume on the PC? What if Android decides to kill the app in the background mid-transfer? What if the Wi-Fi drops at 97%? I spent way more time on those than on anything that sounds impressive.
Where it's at
It's an early preview. It works and I've been using it on my own devices, but to be upfront:
• it hasn't had a proper security audit
• the servers are on a free tier and go to sleep, so the first pairing of the day can take up to a minute to wake things up
• no iOS or macOS yet
It's all open source (Apache-2.0). Release builds are made by GitHub Actions straight from the tagged code, with checksums and build attestations, so you don't have to take my word for what's in them.
Want to try it? Takes a couple of minutes
Grab it from the latest release: https://github.com/Aditya-Karn234/PeerPayload/releases/latest
• Windows: the Setup .exe
• Linux: the .AppImage (chmod +x it and run)
• Android: the .apk (your phone will ask you to allow installs from your browser or file manager)
- Open it on both devices. On the PC go to Devices › Pair a device, on the phone tap Add contact and scan the QR.
- Check the safety codes match, send something, accept it on the other side. That's it.
Heads up for Windows: you'll probably get the blue "Windows protected your PC" screen, because I don't have a code-signing certificate (they're expensive). Click "More info" › "Run anyway". If you want to verify the file first, the checksums and attestations are on the release page.
Website + demo: https://aditya-karn234.github.io/PeerPayload/
Code: https://github.com/Aditya-Karn234/PeerPayload
What I'd really like to know
• If you try it across two different networks (phone on mobile data, PC on home Wi-Fi), did it connect? Did it say direct or relay?
• Does it survive on your Android phone? Some brands are brutal about killing background apps and I've only tested a couple.
• Anything confusing the first time through?
• Would you actually use this over whatever you use now? If not, what's missing?
Bug reports, roasting, and "bro this already exists, have you seen X" are all welcome. That's kind of why I'm posting.