How to send large files without uploading them
By the WispFile team · Updated 24 September 2026
To send a large file without uploading it, use a direct (peer-to-peer) transfer: your device connects to the receiver’s and the file streams straight across while you are both online. There is no upload wait, no storage quota and no copy left on anyone’s server. With WispFile you add the files, share a link, and the other person downloads from you in their browser.
Key facts
- No upload step: the receiver starts downloading as soon as they open the link.
- No storage limit to hit, because nothing is stored.
- End-to-end encrypted with a 256-bit key that only the link carries.
- The one condition: keep your device online until they finish.
Why most services make you upload first
WeTransfer, Dropbox, Google Drive and OneDrive all work the same way underneath. Your file goes up to their servers, sits there, and comes down again when the other person clicks the link. That model has one great strength: the receiver can download whenever they like, even after you have switched off.
It also has costs that grow with the file. The upload takes as long as the download, and happens first. The file counts against a storage allowance (2 GB on Dropbox Basic, 5 GB on OneDrive, 15 GB shared with Gmail on Google Drive). Free transfer services cap what you can send: WeTransfer’s free plan allows 10 transfers or 3 GB in total in any 30 days. And the file sits on a company’s servers for days or indefinitely, which matters when it is confidential.
How a direct transfer skips the upload
Browsers can open a direct, encrypted connection to each other using a standard called WebRTC, the same technology behind browser video calls. A small server helps the two browsers find each other (it passes a few connection details back and forth), then steps aside. The file itself flows from your device to theirs.
- You add files on WispFile. They stay on your device; only their names and sizes are shared.
- You share the link. It carries a key after the
#, which browsers never send to a server. - The receiver opens it. Their browser connects to yours and asks for the files.
- Your browser reads each file in 256 KB pieces, encrypts each piece, and sends it. Theirs checks and decrypts each piece and writes it to disk as it arrives.
Because the file streams, neither side needs the whole thing in memory. In our tests a 5 GB transfer arrived byte-for-byte identical while the receiver’s browser used under 10 MB of memory.
How long it takes
Speed is set by the slower of the two connections: usually the sender’s upload. Home broadband uploads are often 10–50 Mbit/s; fibre and office lines can reach hundreds. Rough times for a direct transfer:
| File size | At 20 Mbit/s | At 100 Mbit/s | At 500 Mbit/s |
|---|---|---|---|
| 1 GB | 7 minutes | 80 seconds | 16 seconds |
| 10 GB | 67 minutes | 13 minutes | 3 minutes |
| 50 GB | 5.6 hours | 67 minutes | 13 minutes |
With an upload service, the receiver waits for your upload to finish and then for their own download, so their wait is roughly doubled.
When uploading is still the better choice
Direct transfer is the wrong tool when you cannot stay online: if a client will download next Tuesday, put the file in cloud storage. It is also the wrong tool for files you want to keep and edit together over months; that is what a shared Drive or Dropbox folder is for. Direct transfer is for handing files over, now, without keeping a copy anywhere else.
One more limit to know: some office and mobile networks block direct connections between devices. WispFile’s free plan is direct only, so on such a network pair the transfer cannot start; switching one side to another network usually solves it. Paid plans fall back to an encrypted relay.
Step by step: sending a large file with WispFile
- Open wispfile.com in Chrome or Edge (Firefox and Safari are still in testing).
- Drop in the files or a folder. There is no size limit to check.
- Optionally add a password, or make the link work for one download only.
- Press Get transfer link and send it by chat, email or QR code.
- Keep the tab open. You will see the receiver connect and their progress. If the connection drops, the download continues where it stopped.
For very large jobs, see how to send a 50 GB file.
Frequently asked questions
Can I send a large file without uploading it anywhere?
Yes. A direct, peer-to-peer transfer connects your device to the receiver’s and streams the file between them, so nothing is uploaded to a server first. The trade-off is that you need to be online while they download.
Is sending without uploading faster?
Usually, for the person waiting. With an upload service the file crosses the internet twice, one leg after the other: your upload, then their download. A direct transfer does both at once, so the total wait is roughly the slower of the two connections rather than both added together.
What if the receiver is offline?
A direct transfer needs both of you online at the same time. If the receiver will only download later, an upload service or cloud storage is the better tool. If they open a WispFile link while you are offline, they see that you are away and can ask to be notified when you are back.
Does the file go through WispFile’s servers?
On the free plan, never. WispFile’s servers only introduce the two browsers to each other. On paid plans, if two networks block a direct connection, the encrypted bytes pass through a relay that cannot read them and stores nothing.
Related guides
- How to send a 50 GB file online — Every realistic way to move 50 GB, with the times and limits.
- WebRTC file transfer, explained — Signaling, NAT traversal, data channels and what can go wrong.
- How to transfer files between two computers — Cable, drive, network share, cloud or a direct link: which to pick.
Send it directly now
Open WispFile, add your files and share the link. No account, nothing uploaded, nothing stored. Free.
Send files with WispFile