How to send large files securely

Big files are where most “quick” sharing methods break down. Email bounces the attachment, chat apps compress or reject it, and cloud links leave a full copy sitting on someone else's server. Sending a large file securely means solving two problems at once: getting past the size limits and making sure no one but your recipient can read it.

The short answer

Don't upload the file and share a “anyone with the link” URL. Instead, use an end-to-end encrypted transfer that streams the file directly to the recipient. The file is encrypted in your browser, never stored on a server, and only your recipient — holding the link and a separate PIN — can open it. That handles both the size and the privacy in one step.

Concretely, with SaferDrop: up to 100 MB per transfer on the free plan, and up to 2 GB on Pro, which also unlocks whole folders and multiple files in one go. Nothing is uploaded to storage first, so there is no waiting for an upload to finish before the recipient can start — and no copy left behind when it does.

The size limits you are actually hitting

Before choosing a method it helps to see the real numbers side by side. Most people discover the limit only when a message bounces, and the figure is rarely the one they expected.

Two things stand out. First, email is never the answer for a large file — the caps are an order of magnitude too small, and no amount of zipping closes that gap. Second, every option that does handle the size does it the same way: by keeping a copy of your file on a server. That copy is the privacy problem, and it is the one thing a peer-to-peer transfer removes.

These are the providers' published caps and they do change; treat them as the order of magnitude rather than a guarantee.

Why the usual ways to send large files fall short

• Email attachments hit a hard wall around 20–25 MB, and even when they fit they aren't end-to-end encrypted — the file lingers on mail servers and in inboxes.
• Cloud share links remove the size limit but keep a readable copy on the provider's server, often for far longer than you need, and the link can be forwarded or logged.
• USB drives and physical handoff work offline but get lost, and the files on them are rarely encrypted.

The pattern is the same as with small files, just more exposed: a readable copy sits on a server you don't control — only now it's a big, valuable one.

The best way to send large files securely, compared

For big files the trade-off is between size, privacy and speed. Here is how the usual options compare on the four things that matter for a large, sensitive transfer.

Only the peer-to-peer, end-to-end encrypted option clears all three: it removes the size limit, keeps the file unreadable to anyone but the recipient, and leaves no copy behind. That's why it's the best way to send large files when they're also sensitive.

The secure way: stream it, don't store it

A peer-to-peer transfer avoids the upload entirely. Rather than copying your file to a server so the recipient can download it later, the file streams browser to browser in real time, encrypted with AES-256-GCM the whole way. There's no intermediate copy because the data never lands on a server — which is both faster for large files and far more private. A related guarantee is zero-knowledge: the service is built so it never holds the decryption key and literally cannot read what you send.

How to send a large file securely, step by step

1. Pick an end-to-end encrypted, peer-to-peer tool. That's exactly what SaferDrop does — files are encrypted in your browser and stream straight to the recipient.
2. Add the file (or a whole folder). On Pro you can send up to 2 GB and include multiple files and folders in a single transfer.
3. Generate the link. The decryption key lives only in the link's URL fragment (after #), which browsers never send to a server.
4. Share the link and the PIN on separate channels — link by email or chat, PIN by phone or text — so one intercepted message is useless on its own.
5. Keep the tab open until it finishes. Because the transfer is direct, both browsers stay connected while the file streams; on Chrome and Edge it writes straight to the recipient's disk.

A quick checklist for big transfers

• Is the file encrypted before it leaves your device (end-to-end)?
• Does the tool avoid storing a full copy on a server?
• Is the decryption key kept off the server (e.g. in the URL fragment)?
• Can you add a second factor (a PIN) on a different channel?
• Does the link expire instead of leaving a large file downloadable forever?

If your case is more specific, these go deeper: a 1 GB file, a large video file, a whole folder, an attachment your inbox rejected, or the mechanics of sending without uploading at all.

If you're sending sensitive material specifically — contracts, records, financial files — see how to send confidential documents. For the general method on any file size, start with how to send files securely, or compare the Free and Pro plans.

Frequently asked questions