SendXa / Articles
Guide
Send large files between computers and phones — no account, nothing to install
Updated 2026-08-08 · 7 min read
Short answer
Open sendxa.app in a browser on both devices. Drop the file on the sending device, then type the 9-digit ID and 6-digit code on the receiving device — or open the link it gives you. The file streams straight from one device to the other, up to 32.0 GB per file, with no account to create and nothing to install. When both devices are on the same Wi-Fi the transfer runs at local network speed, because the two browsers connect to each other directly.
Every few weeks the same thing happens. A video that is too big for email. A folder of RAW photos that the chat app insists on squashing. A database dump you need on the laptop across the desk, and a USB stick that is somewhere in a drawer. The file is right there on one screen and you need it on another screen two feet away, and somehow that is a twenty-minute problem.
This is a guide to solving it with nothing but a browser tab on each device — no sign-up, no app store, no cable, and no cloud account holding your file hostage behind a storage quota.
Why this is still annoying in 2026
It is worth naming the reasons, because each one rules out a different tool and that is how you end up with no tool at all.
- Email caps attachments at 25 MB on Gmail and Outlook. A single phone video clears that in about 40 seconds of recording.
- Chat apps compress. Send a photo through most messengers and what comes out the other end is not the photo you sent — it is a smaller, softer copy. Fine for a meme, useless for a print job.
- AirDrop is Apple-only, and it has to be Apple on both ends. The moment one side is a Windows laptop or an Android phone, it is not an option.
- Cloud drives make you wait twice: once for the whole file to go up, then again for it to come down. And they want an account, on both ends, before anything happens.
- Cables have become a lottery. Which end, which adaptor, and does this phone even mount as a disk on this operating system.
| Method | Size limit | Account needed | Works across platforms |
|---|
| Email attachment | 25 MB | Yes, both sides | Yes |
| Chat apps | Varies, files recompressed | Yes, both sides | Mostly |
| AirDrop | No practical limit | No | Apple to Apple only |
| Cloud drive | Storage quota | Yes, usually both sides | Yes |
| USB cable / stick | Drive size | No | Depends on the ports and the phone |
| Browser transfer | 32.0 GB per file | No | Yes, any combination |
What each option actually costs you
The browser way, start to finish
The whole flow is five steps and takes about twenty seconds once you have done it once.
On the sending device, open sendxa.app and drop the file onto the page. Several files at once is fine.
The page shows a 9-digit ID and a 6-digit code. There is also a Copy link button if the other person is not in the room with you.
On the receiving device, open the same address, pick the Receive tab, and type the two numbers. Or just open the link — no typing.
The file list appears. Hit Download on the file you want, or Download all.
Keep the sending page open until the transfer finishes. That is the one rule; everything else takes care of itself.
That last step is not a bug, it is the point. The file does not get uploaded anywhere when you drop it. All that goes to the server is a list of names and sizes. The bytes stay on your disk until the other side actually presses Download, and then they flow straight through to that device without ever being written down in the middle. That is why there is no storage quota, why a file of tens of gigabytes is fine, and why nobody has to remember to delete anything afterwards — there is nothing to delete.
Four directions, four guides
The steps are the same whichever way the file is going, but the details differ — where the file lands on a phone, what a browser will and will not let you write to disk, what happens when the screen locks. Each direction has its own guide, linked at the end of this page.
- Computer to computer — the everyday case: laptop to desktop, Mac to Windows, work machine to home machine.
- Computer to phone — getting a video or a set of documents off the laptop and onto the phone you are about to walk out the door with.
- Phone to computer — the one people search for most: photos and videos off the phone, at full quality, without a cable.
- Phone to phone — including the awkward one, iPhone to Android, where AirDrop and Quick Share both give up.
How big can the file be
32.0 GB per file, and as many files as you like in one session, up to 500 of them. There is no daily cap and no counter that runs out.
At that size, interruptions are not a possibility, they are a certainty — Wi-Fi drops, a phone locks, a laptop decides to sleep. So a transfer that breaks does not start over. The receiving side remembers how many bytes it already has and asks for the rest from exactly that point, and the page reconnects on its own up to 30 times, waiting a little longer each attempt. The Stop button is a pause, not a cancel: what has arrived stays, and the button turns into Resume. Pressing the wrong button 40 minutes into a 20 GB file should not cost you the 20 GB.
What makes it fast, and what makes it slow
Before anything moves, the two browsers try to open a direct connection to each other. If that works, the data does not touch our server at all — not one byte. On the same Wi-Fi network that means local network speed, and even across the internet it is dramatically faster than bouncing through a server in Singapore.
| Route | Time |
|---|
| Direct, device to device | 3.6 seconds |
| Relayed through the server | 42.2 seconds |
The same 6 MB file, measured on this service
When a direct connection cannot be made — some corporate networks and a few mobile carriers block it — the transfer quietly falls back to going through the server. Nothing breaks; it is just slower. And when it is slower, the thing holding it back is almost always the sending device's upload speed. Home internet connections routinely give you ten times more download than upload, so a file crawling out of a laptop on home broadband will crawl no matter what the receiving end does.
Two practical consequences. First: if both devices can be put on the same Wi-Fi, do that — it is the single biggest speed difference available to you. Second: if the transfer is slow, check the upload speed of the device that is sending, not the one that is waiting.
Who can see the file
The file is never written to our disk, so there is nothing on our side to read, leak, or subpoena. A few more details that matter:
- The 6-digit code locks out after 10 wrong guesses on a given ID. Without that, working through a million combinations is a few minutes of scripting.
- The share link puts its code after the hash in the address. Browsers never send that part to any server, so it does not appear in access logs, in the Referer header, or in any proxy record along the way. The page also wipes it out of the address bar as soon as it has read it.
- Everything runs over port 443, the same port as any HTTPS website, so it works from behind a corporate firewall without anyone opening anything.
- No account means no profile, no email address on file, and nothing to delete later.
Honesty is more useful than a sales pitch. If both devices are Apple and both are in the same room, AirDrop is fewer taps and you should use it. If you need the file to sit somewhere for a week while three colleagues get around to downloading it, that is what a cloud drive is for. If you are moving 500 GB, use a disk and your feet.
The browser transfer wins in the gap those leave behind: two devices that do not share an ecosystem, a file too big for email, nobody wanting to install anything, and both people available right now.
Questions people actually ask
Do I need to install anything?
No. It is a web page. It works in Safari, Chrome, Edge, Firefox and the browsers on iPhone and Android. Nothing is installed and nothing asks for permission to run in the background.
Do I need an account?
No. There is no sign-up, no email verification and no login. Open the page and you are ready.
How large a file can I send?
Up to 32.0 GB per file, with up to 500 files in one session.
Is the file stored on your server?
No. Only a list of file names and sizes reaches the server. The bytes stay on the sending device until the other side presses Download, and then they pass straight through without ever being saved.
Does it work between an iPhone and a Windows PC?
Yes, in both directions, and the same goes for Android to Mac, Linux to iPhone, or any other combination. Both sides only need a browser.
What happens if the Wi-Fi drops in the middle?
The transfer resumes from where it stopped rather than starting over. The page reconnects by itself up to 30 times, and the receiving side asks only for the bytes it does not have yet.
Can I send several files at once?
Yes. Drop as many as you like, and add more later without the ID or code changing. The receiving side can take them one at a time or press Download all.
Try it with the file you are stuck on right now
Open the page on both devices, pick the file, read out two numbers. Nothing to install, no account, and the file never rests on our server.
Send a file now →