What this tool helps you work out
Broadband packages often advertise download speed first, but cloud backups, video publishing and sending large files depend on upload speed. This calculator converts the file size into bits, divides by the available upstream rate and adds the overhead you select.
Enter your details
Before you begin
Run a speed test over the same connection and device that will perform the upload. Wi-Fi, VPNs, other users, cloud-service throttling and background traffic can all reduce the sustained rate.
Use measured values where possible and leave headroom for busy periods, overhead and future growth.
How the result is worked out
Upload time in seconds = total file bits ÷ usable upload bits per second. A 10 GB file contains roughly 80 gigabits using decimal units. At a sustained 20 Mbit/s, the mathematical minimum is about 4,000 seconds, or 1 hour 7 minutes.
Worked example
Uploading a 100 GB backup over a 35 Mbit/s upstream connection takes about 6 hours 21 minutes at 100% efficiency. Allowing 15% overhead increases the planning figure to roughly 7 hours 28 minutes.
Practical tips
- Use the upload result from a speed test, not the download figure.
- Leave extra time for encryption, hashing and cloud-side processing.
- Schedule large backups outside busy household or office hours.
- Use Ethernet where possible if Wi-Fi speed varies.
Why uploads feel so much slower than downloads
Most UK broadband is asymmetric by design: the download capacity is much larger than the upload. On a typical fibre-to-the-cabinet connection the upload might be a tenth of the download, and on older cable services it can be less. The reason is historical — consumer internet use was assumed to be mostly consumption — and while full-fibre services increasingly offer symmetric speeds, most connections still are not.
This is why sending a video to a family member takes an afternoon while streaming a film takes seconds. It is also why a large upload running in the background can make the whole connection feel broken: browsing, video calls and even downloads depend on small outbound packets — acknowledgements, requests, keystrokes — and if the upload path is saturated, those packets queue behind it. The download capacity is untouched, but everything still crawls.
Connection speeds are quoted in megabits per second, file sizes in megabytes. There are eight bits in a byte, so a 40 Mb/s upload moves at most 5 MB per second. This factor of eight accounts for most of the confusion about why a connection seems slower than advertised, and it is built into this calculator.
Where the missing throughput goes
Nobody achieves the full line rate. The efficiency figure in this calculator accounts for several unavoidable losses at once.
- Protocol overhead. Every packet carries headers — TCP, IP, and whatever the link layer adds. On a typical connection this alone is around 3 to 5% before anything else happens.
- Encryption. HTTPS and VPNs add their own overhead, and a VPN encapsulates entire packets inside other packets, which can cost 10% or more.
- The server at the other end. Your upload speed is a ceiling, not a promise. If the destination throttles per-connection uploads, or is busy, that becomes the limit.
- Many small files. Each file carries a setup and teardown cost. Ten thousand small files upload far more slowly than one archive of the same total size, sometimes by an order of magnitude.
- Wi-Fi. If the upload starts on wireless, the wireless link is often the narrower point, particularly at 2.4 GHz or at distance.
- Other traffic. Anything else on the connection — a phone backing up, a console updating — shares the same upstream.
An efficiency of 85 to 90% is realistic for a single large file over a wired connection to a well-provisioned service. For many small files over Wi-Fi through a VPN, 50% would not be surprising.
Making a large upload finish sooner
- Use a cable. For a genuinely large upload this is the single most effective change, and it removes the most variable part of the path.
- Archive many small files into one. A single zip avoids thousands of per-file round trips. It also makes the transfer resumable as one operation rather than needing to work out which files completed.
- Check whether compression helps. Documents, logs and raw data compress substantially. Video, photographs and audio are already compressed and will not shrink meaningfully — compressing them wastes time at both ends.
- Start it when nothing else needs the connection. Overnight is the obvious answer, and most backup and sync tools can be scheduled.
- Use a tool that resumes. A browser upload that fails at 90% usually starts again from nothing. Dedicated sync clients and file transfer tools resume from where they stopped, which matters when the transfer is measured in hours.
- Consider whether it needs uploading at all. For very large one-off transfers, posting a drive is still sometimes faster than the connection, and it costs nothing in bandwidth.
Frequently asked questions
Why is my upload speed much lower than my download speed?
Many consumer broadband services are asymmetric, providing more downstream than upstream capacity.
Does compressing files help?
It can when the files compress well. Photos, videos and existing archives often shrink very little.
Will a VPN make the upload slower?
It may, because encryption, routing and the VPN service's capacity add overhead.
Can I use the advertised package speed?
A measured sustained upload speed is better. The package rate is a maximum or typical service figure, not a promise for every transfer.
Why does a cloud upload pause near the end?
Some services perform verification, indexing or server-side processing after the data transfer, so the progress indicator may not represent network activity alone.
Why does my upload speed test result not match what I actually get?
A speed test measures the best case: a short burst to a nearby, well-provisioned server with nothing else competing. A real upload runs for longer, to a server that may be distant or busy, through whatever encryption the application uses, alongside your other traffic. Achieving 80 to 90% of the tested figure on a sustained transfer is normal and not a fault.
Does uploading slow down my downloads?
It can, considerably, even though they use separate capacity. Downloads rely on small acknowledgement packets travelling upstream, and if the upload path is completely saturated those acknowledgements are delayed. The result is a download that stalls while the upload runs. Many routers have a quality of service or smart queue setting that reserves a little upstream capacity to prevent exactly this.
Is it faster to upload one large file or many small ones?
One large file, usually by a wide margin. Each file involves its own setup, authentication and confirmation, and that fixed cost dominates when files are small. Combining thousands of small files into a single archive first is often faster overall even including the time spent creating it.
What upload speed do I need for video calls or streaming?
A single high-definition video call needs somewhere in the region of 2 to 4 Mb/s upstream, and several at once scale roughly linearly. Live streaming to a platform needs more, typically 5 to 10 Mb/s for 1080p, and the requirement is for sustained capacity rather than a peak — a connection that briefly dips below will drop frames or reduce quality.
Related networking tools
References
Official guidance and standards can change. Check the linked source when applying the result to an important network.