Sending a Large File

No affiliate links on this site, and nothing here is ranked.

What the task actually is

Getting a file from your machine to somebody who does not work with you, where email attachment limits stop you.

Three variables decide the answer: how large, how sensitive, and how often.

Everything else is detail, and the categories built around this task — managed file transfer, secure exchange platforms — are built for organisations answering "very" to all three.

What you already have

A cloud drive. If you pay for an office suite, you have one, and sharing a link to a file is the built-in answer. Where it stops: recipients who cannot or will not accept a link from that provider, and link permissions that are easy to set too broadly.

Free transfer services. Upload, get a link, the file expires. Where it stops: size caps on free tiers, retention periods that may be shorter than you want, and no control over what happens to the file afterwards.

Compression, which occasionally turns an over-limit attachment into an under-limit one and costs nothing to try first.

And a physical drive, which for very large one-off transfers to somebody local remains faster than any connection.

When you need something else

Confidentiality with a legal dimension. Client records, health information, anything where an unauthorised disclosure has consequences beyond embarrassment. A general transfer service is not the answer, and the requirement is usually specified by whoever regulates you rather than chosen.

Recipients who cannot create accounts. Some organisations block link-sharing from consumer services entirely, and the transfer fails silently.

Repeated, scheduled transfers. Sending the same kind of file weekly to the same recipient is a different task from sending one, and it is where automation earns its price.

And audit requirements — proof of what was sent, to whom, and when it was collected.

What the paid tools add

Expiry and revocation. A link that stops working, or can be stopped.

Password protection with real encryption, rather than a zip password.

Delivery confirmation, which is the feature most often actually wanted and least often available free.

Recipient identity, where it matters that the person who downloaded it was the person you sent it to.

And branded sending, which is a presentation feature sold as a security one.

What to check before buying

Where the file rests. Which country, on whose infrastructure, and for how long — a question that applies to any tool holding your data.

What the recipient experiences. The best transfer tool is the one your recipients can actually use, and testing that requires sending something to an actual recipient rather than to yourself.

Retention and deletion. How long the file stays and whether you can remove it.

And what happens at the limit. Every plan has a step, and for transfer tools it is usually storage volume or transfer count, both of which are easy to hit in a busy month.

The mistake that causes the purchase

Sending it the wrong way once, having it fail, and concluding the category is needed.

A file that bounced because of an attachment limit does not mean you need a transfer platform. It means the attachment route was wrong for that file.

A link a recipient could not open frequently means the permission was set to your organisation rather than to anyone, which is a two-click fix and is mistaken for a product limitation surprisingly often.

Try the free route properly before concluding it failed — including asking the recipient what they actually saw, which is the step nobody takes and which explains most apparent failures.

Size, honestly

Attachment limits sit around twenty to twenty-five megabytes on most mail systems, and the effective limit is lower because encoding inflates the file.

Consumer cloud drives handle files into the tens of gigabytes. Free transfer services commonly cap at a few gigabytes per transfer, with larger sizes on paid tiers.

Which means the range where you need anything beyond free is narrow: files too large for a free transfer service, sent by somebody who has no cloud drive.

That combination is rare, and it is worth checking you are actually in it before buying for it.

The version most people should use

The cloud drive already paid for, with link expiry set.

It costs nothing additional, the recipient experience is familiar, and permissions are revocable.

The main risk is a link set to "anyone with the link" and forgotten, which is a habit problem rather than a tooling one — set expiry when creating the link, every time, and the problem does not arise.

What not to do

Do not email it in parts. It fails, it annoys the recipient, and reassembly goes wrong.

Do not put confidential material on a free service to save a step. The confidentiality question is the one that changes the answer, and it is worth two minutes of thought before rather than a disclosure conversation after.

And do not buy a platform because one transfer was awkward. One awkward transfer is a data point; a pattern is a reason. A separate outside reference is Evernote.

The short version

• Three variables decide it: how large, how sensitive, how often — everything else is detail
• A cloud drive you already pay for, or a free transfer service, covers almost every ordinary case
• Buy something else for legal confidentiality, recipients who cannot use links, scheduled repeats, or audit requirements
• What paid tools add: expiry and revocation, real encryption, delivery confirmation, and recipient identity
• Check where the file rests, what the recipient experiences, retention rules, and where the plan steps
• For most people the answer is the drive they already have, with link expiry set every time