You're uploading a 10GB master and the progress bar crawls. You run a speed test, see 500Mbps, and think the service is broken. It isn't. You're reading the wrong number — and that number is why you've been blaming the tool.

Upload is not download

The number you see on a speed test — 500Mbps, 300Mbps — is almost always your downlink, the speed you receive data at. Your uplink, the speed you send data at, is a separate, much smaller number, and it's the only one that matters when you're sending.

On most home plans, upload runs 5–10x slower than download. That 500Mbps you saw might hide a 50Mbps uplink. That's why "my internet is fast" and "my upload is slow" are both true at the same time. Your fast number was never the one doing the uploading.

The first fix is just to look. Run a speed test and read the UP line, not the down line. Write that number down. It's the one that decides how long your next delivery takes, and it's almost always a lot smaller than the headline.

How long 10GB really takes

A 10GB file is 80,000 Mbit (10 GB × 8 bits/byte = 80,000 Mbit). Divide that by your upload speed in Mbps and you get the transfer time in seconds. No mystery, no broken service — just the arithmetic of a slow uplink:

  • At 20Mbps upload: 80,000 ÷ 20 = 4,000 seconds = 66 min 40 s ≈ 1 hour 7 minutes.
  • At 10Mbps upload: 80,000 ÷ 10 = 8,000 seconds = 133 min ≈ 2 hours 13 minutes.

Same file, half the speed, roughly double the time. If your UP line reads 20Mbps, a 10GB client delivery should take about an hour. Anything close to that is working exactly as designed — the slowness is your line, not the destination.

Do the same for your real file size before you send. A 50GB folder at 20Mbps is over five hours. Knowing that up front is the difference between planning the send and discovering it overnight.

The four fixes

1. Wired beats wifi. A cable to your router removes the biggest source of uplink loss. Wifi is shared, interfered with, and often half your wired speed. For a one-hour upload, plug in. It's the single highest-value change.

2. Upload off-peak. Your uplink is most congested in the evening when the whole street is streaming. Late at night the same line often gives you noticeably more. Schedule the big send for when the neighbourhood is quiet.

3. One big upload, not many small ones. Each new transfer pays a handshake and ramp-up cost. A single large upload keeps the connection at full tilt instead of starting over ten times. Batch your files into one send.

4. A tool that keeps the connection alive. Slow uploads are long, and long uploads are the first to hit a timeout or a blink. A resumable, chunked tool means a slow or interrupted upload doesn't become a restart — it just continues. You protect the progress you've already paid for.

Plan the send around your uplink

You can't make your uplink faster. But you can stop wasting what you have: wired, off-peak, one big send, and a tool that won't throw the whole thing away at 92%. That's the difference between a one-hour upload and a two-hour re-upload.

Read your UP number, do the math, and plan the send around it. When you know a 10GB file will take an hour, an hour of progress no longer feels like a failure.

For a delivery service sized for big client files, see Beautifully Delivered. And if your upload isn't slow but failing, Why Do Uploads Fail? covers the seven causes.

Start free →