When you "send" a big file, you're really doing three different jobs in a row: upload, host, download. Most people think of it as one action. And the one that hurts you most isn't the one you're waiting on.

Leg one: the upload (your uplink is the bottleneck)

You push the file from your machine to a server. That speed is your upload speed, not your download speed. Home and office internet is usually much faster downloading than uploading. Your downlink might be 300Mbps. Your uplink might be 20.

So when you upload a 7.5GB 4K wedding video, your uplink is the whole story. That file isn't "sending at your internet speed." It's sending at your upload speed, which is the slow side. 20Mbps is about 2.5MB per second, so 7.5GB takes around 50 minutes if nothing interrupts, and real conditions are worse.

This is the leg where things die. Big uploads fail because of timeouts, a dropped connection, a laptop lid closing, or a service that doesn't let you resume. If the upload breaks at 90% and there's no resume, you start over from zero. That's the silent tax on big sends.

Leg two: the host (where the file sits)

Once it's up, the file sits on a server. This is where the link points. The host is also where the expiry clock lives, if there is one. Free services keep the file for a short window, then delete it. Paid ones keep it longer or forever.

The host matters to you even after you've hit "send," because this is the file your client will pull from. If the host deletes it, your client gets nothing.

Leg three: the download (your client's connection)

Your client pulls the file from the host. This runs on their downlink, which is usually fast, so this leg is rarely the problem. The problem is if they come to it after the host has already deleted the file.

Why the sender's problem is the upload

You're the only one who does the upload. The client just downloads. So the leg you can't outsource, the leg that's slow, the leg that dies at 90%, is the one you own. That's why your uplink speed matters more to you than your client's connection does.

The three ways to send it, and how the legs differ

Email. All three legs are capped. Email attachments top out around 25MB, so a 7.5GB video doesn't even fit. The upload is fine, but the size wall kills the send before it starts.

A drive (a shared folder). Upload and host are fine, you get real storage. But the client has to have access to the folder, often an account, and it's a shared space, not a clean one-off handoff.

A transfer link. Built for the handoff. The upload is still your uplink, but the host gives the client a clean page to download from, no account needed. The only leg that still depends on you is the upload, which is why a service with resume and a fast path for big files matters.

The three legs are the same everywhere. What changes is where the caps land. A transfer link keeps the caps off your client and leaves you with just one leg to manage: getting the file up in the first place.

If you want the deeper look at why the link itself is the deliverable, read what a file link is. And for why the delivery experience matters beyond the file, see why FileSplash exists.

Start free →