There are four ways to send a large file, and the right one depends almost entirely on size. Under 25 MB, email works. Up to a few gigabytes, any transfer link is simplest. Above that you want a service built for big uploads that resumes when the connection drops. Above a few terabytes, post a drive — it is still faster.
That is the whole answer. The rest is the detail that saves you a failed upload at eleven at night.
Work out what you are actually sending
Before choosing a method, know the number. People 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 the codec.
Right-click the file and check. If it is a folder, check the folder, not the largest file in it. Once you have the number, the limits by file size and app show what each route will take.
Under 25 MB: email
Most mail providers cap attachments around 25 MB, and that figure has barely moved in fifteen years.
The catch: the cap applies after encoding, and attachments grow by about a third on the way. A 24 MB file can be refused by a 25 MB limit. Treat 20 MB as the real ceiling — and the email page has the workarounds if you are close.
25 MB to about 2 GB: any transfer service
The comfortable middle, where everything works and the choice is about convenience. Upload, get a link, send the link. Most services need no account.
The one decision worth making here is what your recipient sees. Free tiers are often paid for by advertising, and if you are sending a deliverable to someone who is paying you, an advert on the download page is a small but real signal.
2 GB to 50 GB: where free tiers split apart
This is where most people first hit a wall, because free plans differ sharply. From each company's own documentation, on the dates shown:
- SwissTransfer: 50 GB free, no account, deleted after 15 days unless you extend to 30 (1 August 2026).
- Yungle: 10 GB per transfer, as many transfers as you like, 7 days, no account, no ads (mine).
- Filemail: 5 GB free (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 (31 July 2026).
The per-service detail, with sources, is on the comparison pages. The short version for the most common switch is below.
Above 50 GB: resumability is the only feature that matters
At this size the limit stops being the problem and the connection becomes the problem. A 200 GB upload takes hours (the upload time calculator gives the figure for your own connection), and something will interrupt it — a laptop going to sleep, a router restarting, a train tunnel.
So ask one question of any service: if my upload is interrupted, does it resume or start again? If it starts again, the file is effectively unsendable, whatever the advertised limit says. It is rarely on a comparison table, and it is the single most important property at this size. (Why resuming is hard to get right, if you want the technical version.)
Habits that help at this size:
- Upload overnight, on a cable if you have one.
- Test resuming on a small file first: start it, pull the network, reconnect.
- Send a low-resolution preview first and get sign-off before shipping the master. It saves more time than any upgrade.
Terabytes: post a drive
There is a size where a courier beats the internet, and it is lower than people expect. On a typical home 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 picking the wrong service. It is compressing something that should not be compressed to squeeze under a limit.
If you are re-encoding a master, a print-resolution image or a RAW file to fit a free tier, you are damaging a deliverable to save a little money. Send it at full quality another way. Compression is a decision about the preview, not about the deliverable.
Zipping is different: it is lossless and changes nothing. It just adds a step for the recipient — and if you are sending a structured folder, check whether the service keeps the folders as they are before you zip by reflex.
If the file has other people's information in it
The moment a file holds personal data — client records, photos of identifiable people, anything medical or legal — size stops being the interesting question. The questions become: who can reach the link, how long it lives, and whether you can take it back.
How to send large files securely is the practical version, and what the GDPR actually requires is the one to read before a client asks. For the product side, secure sharing covers passwords, expiry dates and end-to-end encrypted transfers.
Quick reference
| Size | Method |
|---|---|
| Under 20 MB | Email attachment |
| 20 MB – 2 GB | Any transfer service |
| 2 – 50 GB | A service with a big free tier, or a paid plan |
| 50 GB – 1 TB | A service that resumes interrupted uploads. Upload overnight |
| Over 1 TB | Post an encrypted drive |
If you send big files every week rather than once a year, the thing that costs you time is not the upload. It is links expiring and sending everything again. That is worth solving once — it is what a collection is for, and what the paid plans buy.