Calculate exactly how long any file will take to download — with proper decimal vs binary prefix handling and bits-vs-bytes accuracy.
Hours
0
Minutes
1
Seconds
20
Calculator
Estimated download time
1m 20s
80 seconds total
Hours
0
Minutes
1
Seconds
20
Speed comparison
How download time is calculated
The fundamental formula is: time = (file size in bits) ÷ (bandwidth in bits per second). Since bandwidth is measured in bits but file sizes are reported in bytes, we multiply the byte count by 8. The critical distinction is between decimal prefixes (1 MB = 1 000 000 bytes) and binary prefixes (1 MiB = 1 048 576 bytes) — ISPs advertise in decimal, but operating systems often report in binary, causing the classic confusion.
The optional overhead percentage models real-world inefficiency: TCP/IP headers, TLS encryption handshakes, and packet retransmission all consume bandwidth. A typical value of 5–10% is common on reliable connections; VPNs can add 15–20%. The formula becomes: time = file_bits ÷ (bps × (1 − overhead/100)).
Why is my actual download slower than the calculator says?
ISPs advertise speeds in Mbps (megabits), but file sizes are often shown in MB (megabytes). Multiply by 8 to convert. Additionally, real-world factors like Wi-Fi interference, server throttling, shared bandwidth and TCP overhead all reduce effective speed. Use the overhead field to model this.
What is the difference between MB and MiB?
MB (megabyte) = 1 000 000 bytes by the SI decimal standard. MiB (mebibyte) = 1 048 576 bytes by the IEC/NIST binary standard (2²⁰). Windows Explorer historically reports in binary MiB but labels them MB — the source of much confusion. This calculator distinguishes them correctly.
What overhead percentage should I use?
For a wired Ethernet download from a nearby server, 2–5% is realistic. Wi-Fi adds 5–10%. A VPN adds 10–20%. For rough estimates, leave it at 0%; for more conservative planning, enter 10%.
Results are estimates. Verify with a professional for important decisions.
About this calculator
This calculator tells you exactly how long a file will take to download given its size and your connection speed. It handles the two most common sources of confusion: the bits-vs-bytes factor (your ISP quotes speed in megabits, files are measured in megabytes) and the decimal-vs-binary prefix distinction (MB = 1,000,000 bytes; MiB = 1,048,576 bytes). Enter your file size and bandwidth, pick the right units, and get the result in hours, minutes and seconds.
How to read your results
The result shows the theoretical download time broken into hours, minutes and seconds. Real-world transfers are slower — TCP/IP protocol overhead, connection congestion, Wi-Fi packet loss and server throttling all eat into the rated speed. A 5–15% reduction from the theoretical figure is normal on a good connection; expect more on mobile or public Wi-Fi. The optional overhead field lets you model this directly.
Worked example
File size: 700 MB (a DVD-quality video, decimal megabytes). Connection: 50 Mbps (megabits per second).
The calculator converts 700 MB to 5,600,000,000 bits (700 × 1,000,000 × 8), divides by 50,000,000 bps, and returns 112 seconds — 1 minute 52 seconds. Note: at the same 50 Mbps, a 700 MiB file (binary) would take about 117 seconds because MiB is roughly 4.86% larger than MB.
Frequently asked questions
Why is my actual download slower than the calculator predicts?
The calculator gives the theoretical ceiling — bits of payload divided by bits of capacity. Real transfers include TCP acknowledgement packets, TLS handshakes, HTTP headers, and retransmissions, so effective throughput is usually 80–95% of the rated speed. Distance to the server, Wi-Fi interference and ISP throttling add further delays. Use the overhead field (try 10%) to get a more realistic estimate.
What is the difference between Mbps and MBps?
Mbps is megabits per second; MBps is megabytes per second. One byte equals 8 bits, so 50 Mbps is only 6.25 MBps. Internet service providers advertise in megabits; operating systems and download managers usually show transfer rates in megabytes. Mixing these units up is the single most common reason people think their connection is slower than advertised.
When should I use MB vs MiB for my file size?
Use MB (megabytes, 10⁶ = 1,000,000 bytes) for files reported by modern operating systems on macOS and Windows, streaming services, storage manufacturers and most web content. Use MiB (mebibytes, 2²⁰ = 1,048,576 bytes) if your operating system or tool explicitly shows "MiB" — Linux, some disk utilities, and older Windows Explorer versions use binary units. If in doubt, check whether the tool appending the label spells it with a lower-case "i".
Does the overhead percentage account for my Wi-Fi or VPN?
It is a simple scaling factor rather than a protocol-specific model. A 10% overhead means the calculator assumes only 90% of your rated bandwidth carries useful payload, which roughly captures typical Wi-Fi or VPN cost. If you are on a heavily loaded network or a high-latency satellite connection, 15–30% may be more realistic.
Can I use this for upload time as well?
Yes — enter your upload bandwidth in the connection speed field. The physics is identical: upload time equals file size in bits divided by upload speed in bits per second. Most home connections have asymmetric speeds (upload is 5–20× slower than download), so uploading a large file takes considerably longer than downloading it.
How it's calculated
Download time in seconds equals (file size in bytes × 8) ÷ bandwidth in bits per second. The factor of 8 converts bytes to bits, matching the unit your ISP uses for connection speed. For decimal size units (KB, MB, GB, TB) the calculator applies SI prefixes: 1 MB = 10⁶ bytes, 1 GB = 10⁹ bytes. For binary size units (KiB, MiB, GiB, TiB) the calculator applies IEC 80000-13 prefixes: 1 MiB = 2²⁰ = 1,048,576 bytes, 1 GiB = 2³⁰ bytes. Bandwidth units are normalised similarly: 1 Mbps = 10⁶ bits per second; 1 MBps = 8 × 10⁶ bits per second. If an overhead percentage p is supplied, the raw time is divided by (1 − p/100) to model the share of capacity consumed by protocol headers and retransmissions. The final result is expressed in hours, minutes and whole seconds.
Spot a translation issue, a calculation issue, or have a suggestion? Let us know.