How to send large files securely (without a cloud drive)
Email caps attachments at 25 MB and cloud drives keep a copy indefinitely. Here is how to send multi-gigabyte files privately, and what to check before you trust a transfer service.
You have a 4 GB file and one person who needs it. This should be simple, and it is one of the most annoying problems in computing.
Why the obvious options do not work
Email. Gmail caps attachments at 25 MB, Outlook at 20 MB, and most corporate mail servers lower still. Above that, mail providers quietly convert the attachment into a cloud drive link, which changes the problem rather than solving it. Email is also stored indefinitely on at least four machines — your sent folder, your provider, their provider, their inbox — none of which you control.
Consumer cloud drives. Dropbox, Google Drive and OneDrive all work, and all keep the file until you remember to delete it. The provider can read it. Share links are frequently over-permissive: "anyone with the link" is a real access-control decision that people make in two seconds while distracted. And a shared file often lives on inside someone else's account after they save a copy.
Transfer sites. WeTransfer and its competitors are built for exactly this, and they are genuinely convenient. But most are not end-to-end encrypted: the file is readable by the service, it usually sits on their servers for a week regardless of whether it has been collected, and the free tiers are ad-supported, which tells you what the business model is.
USB drives and physical media. Fine when the person is in the room. Not a solution otherwise, and a lost drive is a worse outcome than most of the alternatives.
What to actually check before using a transfer service
Cutting through the marketing, there are five questions:
- Is it end-to-end encrypted, or just HTTPS? Almost every site has HTTPS. That protects the file from strangers on the network, not from the company. If the service can generate a preview of your file, it can read your file. (There is a longer explanation of the difference in what end-to-end encryption actually means.)
- When is the file deleted? "After 7 days" and "as soon as it is collected" are very different retention profiles. The second means the window in which anything can go wrong is minutes, not a week.
- Does the recipient need an account? If they do, half of them will not bother, and you will end up emailing it anyway.
- What is the actual size limit? Free tiers often advertise a headline number and enforce a lower one. Worth testing before you need it.
- Does an interrupted upload resume? For anything over a gigabyte this is not a nicety. A 4 GB upload on a domestic connection takes long enough that something will interrupt it.
The mechanics of doing it properly
If you want the strong version, the shape of the solution is always the same:
Encrypt before upload, on your own device. The file is scrambled with a key generated locally. What leaves your machine is already unreadable. This is what makes the service's honesty irrelevant — they cannot read it whether they want to or not.
Encrypt in chunks, not all at once. A naive implementation loads the whole file into memory to encrypt it, which fails immediately on multi-gigabyte files in a browser tab. Streaming encryption processes the file in small frames, so memory use stays flat regardless of size. This is also what makes the next point possible.
Upload in pieces, with resume. A single HTTP request carrying 4 GB is fragile: any interruption means starting over. Worse, most CDNs and reverse proxies reject request bodies over a fixed size — Cloudflare's limit is 100 MB on its free and pro plans — so a single-request upload of a large file fails at the edge before it ever reaches the application. Splitting the file into chunks of a few megabytes each sidesteps both problems and makes resuming trivial: the server reports how many bytes it has, and the client continues from there.
Deliver the key separately from the data. The key that unlocks the file must reach the recipient without passing through the same channel in readable form. Public-key cryptography solves this cleanly: the sender encrypts the file key to the recipient's public key, so only their private key opens it.
Delete on collection. The shortest retention window is one that ends when the file has been received.
Doing it with AliasCloak
This is the flow the product implements, so it is a concrete example rather than a hypothetical:
- The recipient creates a mailbox — one click, no email address, no password. They give you their alias, which looks like
quiet_forest_owl. - You open AliasCloak, enter their alias, and attach the file.
- Your browser generates a one-off symmetric key, encrypts the file with it in 64 KB frames, and encrypts that key to their public key.
- The encrypted file uploads in chunks. If your connection drops, it resumes from the last confirmed byte rather than restarting.
- They collect it. Their browser downloads the ciphertext and decrypts it locally.
- Once their device confirms the decrypt succeeded, our copy is deleted.
Files up to 4 GB each, up to 100 per message, free. Neither of you needs an account in the traditional sense, and we never hold a key that opens any of it.
A note on very large transfers
Some honest caveats for anything above about 2 GB:
- Browser memory is real. Streaming encryption keeps usage flat, but the browser still has to buffer the decrypted result somewhere before handing it to you. On a phone with limited RAM, very large downloads can still fail. A desktop browser handles them far better.
- Time matters. A 4 GB upload on a 20 Mbit connection takes about 27 minutes. Start it when you can leave the tab open.
- Both ends need the tab. Encryption happens in the browser, so closing it mid-transfer stops the transfer. Resume works, but it needs you to come back.
If you are moving files between your own machines regularly rather than sending them to someone else, that has a slightly different setup that is worth reading.
The short version
Do not email large files, and do not put anything you care about on a cloud drive purely to move it. Use something that encrypts on your device, chunks the upload so it survives a dropped connection, and deletes the copy once it has been collected.
Try it — creating a mailbox takes about a second and needs nothing from you.
Keep reading
Private by design
