How to send large files: every method that works

There are four ways to send a large file and the right one depends almost entirely on size. Under 25 MB, email works. Under a few gigabytes, a transfer service link is simplest. Above that you want a service built for large uploads with resumable transfers. Above a few terabytes, post a physical drive — it is still faster.

That is the whole answer. The rest of this is the detail that saves you a failed upload.

Work out what you are actually sending

Before choosing a method, know the number. People routinely guess wrong by an order of magnitude, especially with video: a minute of 4K ranges from well under a gigabyte to about 5 GB depending on codec.

Right-click the file and check. If it is a folder, check the folder size, not the largest file in it.

Under 25 MB: email

Most mail providers cap attachments around 25 MB, and that figure has barely moved in fifteen years. Gmail, Outlook and most others are in the same range.

Worth knowing: the cap applies after encoding, and attachments are encoded about 33% larger than the file on disk. So a 24 MB file can be refused by a 25 MB limit. Treat 20 MB as the practical ceiling.

If you are near it, the email-specific page covers the workarounds properly.

25 MB to about 2 GB: any transfer service

This is the comfortable middle where everything works and the choice is about convenience. Upload, get a link, send the link. No account needed on most services.

The one decision worth making here is what the recipient sees. Free tiers are often advertising-supported, and if you are sending a deliverable to someone paying you, that is a small but real signal.

2 GB to 50 GB: the interesting range

This is where free tiers start to differ sharply, and where most people first hit a wall. As of the dates checked below, from each company's own documentation:

• SwissTransfer: 50 GB free, no account, files deleted after 15 days (1 August 2026).
• Yungle: 10 GB per transfer, unlimited transfers, 7 days, no account, no ads (mine).
• Filemail: 5 GB free, 7 days (1 August 2026).
• WeTransfer: 3 GB free, counted across a rolling 30 days rather than per transfer (31 July 2026).
• Smash: 2 GB free with priority, above that queued rather than refused (1 August 2026).
• Dropbox Transfer: 2 GB free, 30 days (31 July 2026).

The full picture, including what paid plans change, is in the comparison.

Above 50 GB: what actually matters is resumability

At this size the ceiling stops being the problem and the connection becomes the problem. A 200 GB upload takes hours, and something will interrupt it — a laptop sleeping, a router restarting, a train tunnel.

The question to ask a service is: if my upload is interrupted, does it resume or restart? If it restarts, the file is effectively unsendable, no matter what the advertised limit says. This is rarely on a comparison table and it is the single most important property at this size. Why resumable uploads are hard if you want the technical version.

Practical habits at this size:

• Upload overnight, on a wired connection if you have one.
• Test resumability on a small file first, by deliberately disconnecting.
• Send a low-resolution preview first and get sign-off before shipping the master. This saves more time than any upgrade.

Terabytes: post a drive

There is a threshold where physical media wins, and it is lower than people expect. On a typical connection, uploading 10 TB takes weeks. A courier takes a day.

Encrypt the drive, send the passphrase through a different channel, and post it tracked. This is not a joke answer — it is standard practice in film and scientific work.

The mistake worth avoiding

The most common failure is not choosing the wrong service. It is compressing something that should not have been compressed to fit under a limit.

If you are re-encoding a master, a print-resolution image or a RAW file to squeeze under a free tier, you are damaging a deliverable to save a small amount of money. Send it at full quality by another route. Compression is a decision about the preview, not about the deliverable.

Zipping, by contrast, is lossless and fine — it just adds a step for the recipient, and it flattens nothing. If you are sending a structured folder, check whether your service preserves the structure rather than zipping by reflex.

If the file contains other people's information

Size stops being the interesting question the moment the file has personal data in it — client records, photographs of identifiable people, anything medical or legal. Then the questions are who can reach the link, how long it lives, and whether you can revoke it.

How to send large files securely is the practical version. What the GDPR requires is the version you need before a client asks.

Quick reference

If you send large files regularly rather than occasionally, the thing that will cost you time is not the upload — it is links expiring and having to send everything again. That is worth solving once rather than every few months.