The Upload Time Calculator turns a file size and your upload connection speed into a realistic estimate of how long the transfer will take. It is built for the moments uploads actually matter: pushing a video to a host, backing up to the cloud, sending a large design file to a client, or syncing a folder over a slow mobile link. Crucially it focuses on the upload direction, which on most cable, DSL and mobile plans is several times slower than download — the number people forget when they assume a “fast” connection.
How it works
Transfer time is a simple ratio: the amount of data divided by how fast it moves. The data side is your file size converted to bits — bytes times eight. The speed side is your line speed in megabits per second converted to bits per second. Dividing one by the other gives a theoretical minimum. Real uploads never reach that, so the calculator applies two corrections that you control.
Time = (size in bytes × 8) ⁄ (line bits/sec × efficiency ⁄ (1 + overhead))
Protocol overhead accounts for TCP, IP and TLS headers, acknowledgements and retransmissions that share the wire with your payload — typically 5 to 12%. Line efficiency captures the fact that you rarely achieve the advertised speed; 80 to 90% is realistic for a solid wired link and less over Wi-Fi or mobile. Together they shrink the advertised speed down to a believable goodput, the rate at which your actual file data moves. The tool also lets you toggle between decimal sizing (1 MB = 1,000,000 bytes, as ISPs and drives count) and binary sizing (1 MiB = 1,048,576 bytes, as some operating systems report), because that 7% difference quietly distorts large-file estimates.
Worked example
Suppose you are uploading a 2.5 GB video on a 20 Mbps cable upload at 85% efficiency and 8% overhead. Goodput is 20 × 0.85 ⁄ 1.08 ≈ 15.7 Mbps. The payload is 2.5 × 1,000,000,000 × 8 = 20,000,000,000 bits. Dividing gives roughly 1,270 seconds — about 21 minutes, versus a theoretical 16 minutes 40 seconds if the line were perfect. If your cloud provider charges £0.05 per GB of ingress, the same upload also costs about £0.13. The comparison grid then shows the same file finishing in seconds on a 1 Gbps fibre line but taking hours on a 1 Mbps ADSL upstream — making the case for symmetric fibre obvious at a glance.
Reference and formula notes
- Mbps vs MB/s: divide Mbps by 8 for megabytes per second. A 100 Mbps line moves about 12.5 MB/s.
- Asymmetry: check your plan’s upload figure, not the headline download number — they are often very different.
- Binary vs decimal: a “1 GB” file is 1,000,000,000 bytes in decimal but 1,073,741,824 if your OS means GiB. Match the standard to your source.
- Parallel transfers: splitting a fixed link among many files does not increase total throughput; the link stays the bottleneck.
Every figure is computed locally in your browser. No file is ever chosen and nothing is uploaded, logged or stored.