Real downloads also depend on the server, Wi-Fi signal and other traffic, so actual times are often longer.
At 100 Mbit/s with 5% overhead, the useful rate is 11.88 MB/s, so 50 GB takes 1 h 10 min 10 s.
Same file at common connection speeds
How it's calculated S
Size in bits
50,000,000,000bytes×8=400,000,000,000bits
1 byte = 8 bits. GB means 10⁹ bytes; GiB means 2³⁰ bytes.
Speed after overhead
100,000,000bit/s×(1−5%)=95,000,000bit/s
Time
t=95,000,000400,000,000,000=4,210.526316s
That is 1 h 10 min 10 s.
About the download time calculator
Download time is file size divided by the useful data rate. The calculator turns the size into bits (1 byte = 8 bits; GB means 10⁹ bytes and GiB means 2³⁰ bytes), takes the connection speed in bits per second, and removes the share of each packet taken by protocol headers: time = bits ÷ (speed × (1 − overhead)).
People use it before downloading a game or a cloud backup, and to judge whether a faster plan is worth paying for. The default, a 50 GB file on a 100 Mbit/s line with 5% overhead, takes 1 h 10 min 10 s; at 1,000 Mbit/s the same file takes about 7 minutes.
The result is a best case. The 5% default is the framing cost of TCP/IPv4 over Ethernet; the server's own limit, Wi-Fi signal and other traffic are not modelled. For an upload, enter your upload speed, which on asymmetric lines such as ADSL is lower than the download speed.
How long does it take to download 1 GB at 100 Mbps?
About 84 seconds with 5% protocol overhead, or 80 seconds at the raw line rate. 1 GB is 8,000 megabits, and 8,000 ÷ 100 = 80 s. Halving the speed doubles the time: 160 s raw at 50 Mbps. At 1 Gbps the same gigabyte takes 8 s raw, about 8.4 s with overhead.
What is the difference between Mbps and MB/s?
Mbps (megabits per second) is how connection speeds are sold; MB/s (megabytes per second) is how browsers and download managers show progress. A byte is 8 bits, so divide Mbps by 8: a 100 Mbps line moves at most 12.5 MB/s, and about 11.9 MB/s after 5% overhead. Both use decimal prefixes, so 1 Mbit = 10⁶ bits (NIST).
Why is my download slower than my internet speed?
Part of every packet is headers, not your file. With a 1,500-byte Ethernet MTU, TCP/IPv4 carries 1,460 bytes of data in every 1,538 bytes on the wire (IEEE 802.3 framing plus 20-byte IP and TCP headers), a 5.1% loss; the 12-byte TCP timestamp option cuts the data to 1,448 bytes, 5.9%. Beyond that, the server's upload limit, Wi-Fi signal and other devices sharing the line slow it further.
Why does a 50 GB download show as 46.6 GB on my computer?
Because Windows File Explorer counts in binary units but labels them GB: it divides by 2³⁰ (1,073,741,824) bytes, so 50 × 10⁹ bytes appears as 46.6 GB. Stores and ISPs use decimal gigabytes (10⁹ bytes, IEC 80000-13), and macOS has shown decimal sizes since Mac OS X 10.6 in 2009. Choose GiB in the size field for a size copied from Windows.
How accurate is the download time calculator?
Accuracy depends on your inputs and the method's assumptions. Decimal arithmetic uses 50 significant digits, but estimates, numerical methods and source data can be less precise; the displayed rounding does not remove those limits. It is checked against 5 worked examples whose answers come from independent sources; for example, “50 GB at 100 Mbit/s with 5 % overhead” is checked against 50 × 8 × 10⁹ bits ÷ (100 × 10⁶ × 0.95) bit/s = 4210.526… s (Python fractions).
Where does the method come from?
NIST — Prefixes for binary multiples (IEC 80000-13): 1 byte = 8 bits, GB vs GiB; IEEE 802.3 Ethernet framing (1,500-byte MTU + 38 bytes of preamble, header, FCS and gap) with RFC 791 / RFC 793 20-byte IPv4 and TCP headers.