How to send large files for free without uploading them
Last updated: July 29, 2026
Every free way of sending a big file runs into the same wall: somebody has to store it. Storage costs money, so the free tier gets a limit — 25 MB on email, a couple of gigabytes on most transfer sites, and a queue behind an upload bar either way. This guide covers a different approach that removes the storage step entirely, and when it is the right choice.
Why upload limits exist
With a conventional service, your file makes two journeys. First it is uploaded to a server and written to disk. Then the recipient downloads it again. The service pays for the storage in between, the bandwidth in both directions, and the retention window — which is why free tiers cap file size, expire links after a few days, and ask you to upgrade.
It also means waiting twice. On a typical home connection with 20 Mbps upload, pushing a 3 GB file to a server takes about twenty minutes before the recipient can even start their download.
The alternative: skip the middle
A direct browser transfer sends the file from your device to theirs over an encrypted peer-to-peer connection. There is no upload step, because there is nowhere to upload to. The file is read from your disk in pieces and streamed straight across as it goes.
Two consequences follow from that:
- No practical size limit. Nothing has to fit in memory or in a storage quota, so the ceiling is time and free space on the receiving device.
- No double wait. The recipient's progress bar and yours are the same progress bar.
How to send a large file
- Open sharebetweendevices.com on the device holding the file and choose Send.
- Select the file. Several at once is fine — the recipient sees the list with sizes and can accept or skip each one.
- Share the link, or have them scan the QR code or type the PIN.
- Keep the tab open until it completes. The file is coming from your device, so closing the page stops the transfer.
How long it takes
On the same Wi-Fi network the transfer runs at local speed and your internet connection is irrelevant. Across the internet it is bounded by the sender's upload. Rough figures for a 3 GB file:
- Same network, direct: roughly 1 to 3 minutes
- Across the internet, 20 Mbps upload: around 20 minutes
- Upload to a cloud service, then download: the 20 minutes above, plus the recipient's download time afterwards
The gap between the first and last line is the entire argument for this approach when both people are available at once.
The real trade-off
Being honest about this matters more than a feature list: a peer-to-peer transfer needs both devices online at the same time. There is no copy sitting on a server, so you cannot send a file at midnight for someone to collect at nine. If the recipient is not there, you need a service that stores it — that is exactly what you are paying for with a storage-based service, and it is a reasonable thing to want.
Use a direct transfer when you are both present, when the file is large, or when you would rather no copy existed anywhere. Use a storage service when delivery has to be asynchronous. The comparison page lays this out against WeTransfer, AirDrop and Send Anywhere.
Getting the best speed
- Same Wi-Fi beats everything. If you are in the same building, get both devices on the same network and the internet stops mattering.
- No shared network? Use a hotspot. Connecting one device to the other's personal hotspot creates a private local network, and the data never leaves it — so it costs no mobile data.
- Turn off VPNs for the transfer. A VPN almost guarantees the slow relayed path.
- Wired is fastest when both ends are computers on the same network.
If it is running slowly, this guide explains why and what to change.
Large files, practically
- Check free space on the receiving device first.
- Keep both screens awake — a suspended tab pauses the transfer.
- Plug in, or start with plenty of battery, for anything over a few gigabytes.
- Zip a large folder before sending if you want a single item rather than a queue of files.
- Confirm the integrity check at the end; a mismatch means the file is truncated and should be sent again.
Sending video specifically? That has its own guide, because the compression question matters more there than anywhere else.
Send a large file now — no account, no upload, no size cap.