How to send large files without email getting in the way
Email gives up at around 25 MB, and every workaround costs you something different. Here are the five real ways to get a big file to another person, what each one asks of you and of them, and how to choose.
At some point everyone hits the same wall. You attach the video, the folder of photos, the design files, the recording of the meeting — and the message bounces, or the send button greys out, or, worst of all, it appears to send and quietly never arrives. The file is fine. Email is the problem.
This is a practical guide to the alternatives: why the limit exists, the five routes people actually use, and the questions worth asking about any of them before trusting one with something that matters.
Why email refuses your file
Email was designed to carry text. Attachments were bolted on afterwards, and the way they work is unflattering: the file is encoded into the body of the message as text, which inflates it by roughly a third. A 20 MB file becomes about 27 MB of message.
That has two consequences people rarely expect. The first is that a file comfortably under the stated limit can still be refused, because the limit applies to the encoded message rather than to the file you picked. The second is that both ends have a say: your provider caps what you can send, the recipient's provider caps what it will accept, and the smaller of the two wins. That is why the same file reaches one colleague and bounces off another at a different company.
| Provider | Roughly where it stops |
|---|---|
| Gmail | 25 MB per message |
| Outlook.com | 20 MB per message |
| Microsoft 365 (work accounts) | 25 MB by default, changeable by an administrator |
| Yahoo Mail | 25 MB per message |
| iCloud Mail | 20 MB, or up to 5 GB via Mail Drop |
Treat these as the ceiling on a good day. A corporate mail gateway, an antivirus scanner or a mailing list can all impose something lower, and none of them will tell you in advance.
The five ways to send a large file
1. A transfer link
You upload the file once to a service, it hands you a URL, and you send the URL instead of the file. The recipient clicks and downloads. Nothing is attached to anything, so the mail limits stop being relevant — a link is a few dozen characters.
This is the fastest route for a one-off, and usually the only one that needs nothing at all from the person receiving it: no account, no app, no shared folder. The trade-offs are worth knowing. You are putting the file on somebody else's computer for a while, so it matters a great deal whether it is encrypted, how long it stays there, and who else could reach the link.
2. Cloud storage
Google Drive, Dropbox, OneDrive and iCloud all do the same thing: the file lives in your storage and you share a link or invite someone to it. If you are already paying for one, it costs nothing extra.
The catch is that it is built around keeping files, not sending them. A shared link stays alive until you remember to revoke it, permissions default to something you may not have read, and "anyone with the link" quietly means anyone with the link, forever. It is also awkward across organisations, where sharing often demands the recipient sign in to an account they do not have and cannot create.
Use it when the file is part of an ongoing working relationship. It is a poor fit for handing something over once.
3. Physical media
A USB drive or an external disk still beats every network for very large amounts of data. The old line about never underestimating the bandwidth of a van full of tapes remains arithmetically true: 2 TB posted overnight outruns almost any upload you could start today.
It is the right answer for genuinely enormous transfers — video rushes, scientific datasets, a full archive migration. For anything a person could download in an afternoon it is slower door to door, and a lost drive is a data breach with no way to revoke it.
4. FTP, SFTP or a server you run
Plenty of industries still move files this way, and there is nothing wrong with it when both sides are set up for it. You get complete control, no third party, and no size ceiling but your own disk.
The cost is everyone's time. Someone has to run the server, issue credentials, keep it patched and explain to the recipient what an SFTP client is. Plain FTP additionally sends its credentials in the clear and should not be used across the internet at all. This is infrastructure, not a way to send your sister a video.
5. Peer to peer
Browser-to-browser tools open a direct connection between the two computers and stream the file across it. Nothing is stored in the middle, which is genuinely appealing.
The condition is that both people are present at the same moment with the tab open. Close the laptop and the transfer dies. That makes it excellent for two people on a call together and unusable for "here is the file, get to it when you can" — which is most of the time.
So which one?
| Route | Best for | Main cost |
|---|---|---|
| Transfer link | Handing something over once | The file sits on a third party's storage |
| Cloud storage | Files you keep working on together | Links outlive their purpose; accounts required |
| Physical media | Terabytes | Slow door to door, and losable |
| SFTP | Routine machine-to-machine transfers | Somebody has to run it |
| Peer to peer | Two people, both online now | Both must stay connected |
What to ask of a transfer service
If you land on a transfer link — the usual answer — these are the questions that separate them, and most of them are not on the pricing page.
- When does the link die? A link with no expiry is a file you have forgotten you published. Being able to say "this stops working on Friday" is the single most useful control in the category.
- Who can read the file? "Encrypted" on a marketing page usually means encrypted on their disk, with their key. That protects against a stolen hard drive and nothing else. End-to-end encryption means the file is sealed in your browser before it is uploaded, and the service holds bytes it cannot open.
- Does the recipient need an account? If they do, you are not sending a file, you are asking a favour.
- Can you take it back? Sent to the wrong address, or the file turned out to be wrong: revoking should be one click, and it should be immediate.
- Do you find out what happened? Whether the link was opened, and how many times, is the difference between following up and wondering.
- What happens to the file afterwards? Read the retention line in the privacy policy. Deleted should mean deleted, on a stated schedule.
The two that matter most are expiry and encryption. Everything else is convenience; those two decide who can read what, and for how long.
Sending one, step by step
Here is the whole flow on BetterFileTransfer, which takes about as long to do as to read.
- Drop the files onto the page. Up to 100 MB without an account, 1 GB with a free one, 10 GB on Pro. They are encrypted in your browser as they upload, so what leaves your machine is already sealed.
- Choose when it expires. A day, a week, a month, or never on Pro. This is the decision worth thinking about for a second — pick the shortest window that is actually workable.
- Hand the link over. Copy it, show a QR code for someone standing next to you, or have the link emailed for you. A free account mails to one person, Pro to a hundred, always as separate messages so nobody sees who else received it.
The recipient clicks, and the file downloads. There is nothing to install and no account on their side, which is the part that makes it usable with people outside your own organisation.
What end-to-end encryption actually means
The phrase is used loosely, so it is worth being precise about what it buys.
When a transfer is encrypted end to end, the key is generated in your browser and the file is sealed there, before the upload starts. The service receives ciphertext. The key travels to the recipient in the part of the link after the #, which browsers never send to the server — or, if you prefer, you pass it to them yourself and the download page asks for it.
The practical result is that a subpoena, a rogue employee or a breach of the storage yields sealed bytes. On our own service the filenames are sealed too, because quarterly-layoffs-final.xlsx tells a story on its own.
The honest cost: a lost key is a lost file. There is no reset link, because a reset link would prove the service could open your files all along. If that trade is wrong for a particular transfer, turn encryption off for that one.
How long should the link live?
Most people leave this at the default and then never think about it again. A better habit is to match the window to the job.
- A day for anything sensitive, and for anyone you are actively talking to. If they miss it, send another.
- A week for normal work, across a weekend and a time zone.
- A month for something a group needs to get to in their own time.
- Never only for a file you genuinely intend to publish, such as a download link on a page.
Short expiry is not paranoia. Links get forwarded, pasted into group chats and left in inboxes that later get compromised, and none of that can hurt you once the link has stopped resolving.
When something goes wrong
The upload stalls near the end. Usually the network, not the file. Uploads here are cut into chunks, so a dropped connection costs the chunk in flight rather than the whole transfer, and it retries by itself. Leave the tab open.
The recipient says the link is dead. Either it expired or it was revoked. Check the date you set; the link stops working the moment the clock runs out, by design.
The link works but the file will not open. On an encrypted transfer this is nearly always a truncated download rather than a broken file — the browser stopped early. Download it again on a stable connection.
It went to the wrong person. Revoke it from the dashboard. The files are deleted and the link stops resolving immediately; there is no window in which it half works.
Questions people ask
What is the largest file I can send for free?
100 MB with no account at all, and 1 GB with a free account, which also gives you 10 GB of storage and a record of what you have sent. Pro raises it to 10 GB per transfer. The pricing page has the full comparison.
Can I send a folder?
Yes — drop the whole thing in, or select the files together. They arrive as one transfer with one link.
Is a transfer link private if anyone with it can open it?
The link is the credential, so treat it like one: it is unguessable, it is never indexed by search engines, and it expires. If you need a second factor, turn on encryption and pass the key separately — then the link alone is not enough.
How long do you keep the files?
Until the expiry you chose, then they are deleted. The privacy policy states the retention windows exactly, including what is kept afterwards as a record and for how long.
Do you look at what I send?
On an encrypted transfer we cannot: we hold sealed bytes and no key, and the filenames are sealed as well.
The short version
Email stops at around 25 MB and that is not going to change. For a file you are handing over once, a transfer link is almost always the right tool — and the two things worth choosing carefully are how long it lives and whether it is sealed before it leaves your machine.
Send one now: drop a file in, pick a day for it to disappear, and copy the link.
