Download Time Calculator Widget
ISPs, hosting providers and backup services can let visitors see how long a game, video library or backup takes on their line, with decimal and binary file sizes handled correctly and an allowance for protocol overhead. A second mode answers the planning question: what speed moves this much data in this much time?
Live preview
Under the widget on your page: Powered by A2Z Tools
Embed code
<iframe src="https://a2z.tools/embed/w/download-time-calculator" title="Download Time Calculator by A2Z Tools" width="100%" height="640" style="border:0;width:100%" loading="lazy" allow="clipboard-write"></iframe>
A plain iframe. Works everywhere, including site builders that strip scripts. Adjust height if your content needs more room.
<div data-a2z-widget="download-time-calculator" data-height="640"></div> <script async src="https://a2z.tools/embed.js"></script>
Adds a small script (what it does) that sizes the widget to fit its content, loads it lazily and keeps it isolated from your page's CSS.
Works with
How it works
Connection speeds are quoted in bits per second with decimal prefixes - 100 Mbps is 100,000,000 bits a second - while file sizes are in bytes, sometimes with decimal prefixes (GB = 10^9 bytes) and sometimes binary ones (GiB = 2^30 bytes), as defined by IEC 80000-13 and summarised by NIST. The widget converts the size to bits (bytes x 8), reduces the line rate by the overhead percentage to get the usable payload rate, and divides: 50 GB is 400 gigabits, which takes 4,000 seconds - 1 h 6 min 40 s - at a full 100 Mbps. A 1 GiB file is 7.4% larger than 1 GB and takes 85.9 s instead of 80. In the inverse mode the bits are divided by the target time and grossed up for overhead: 10 GB in ten minutes needs 133.33 Mbps. Overhead covers packet headers and retransmissions; TCP over Ethernet alone costs about 5%.
Calculation method
- Bits = size x bytes per unit x 8 (MB 10^6, GB 10^9, TB 10^12, MiB 2^20, GiB 2^30, TiB 2^40)
- Usable rate = link rate x (1 - overhead % / 100); kbps 10^3, Mbps 10^6, Gbps 10^9 bit/s
- Time = bits / usable rate
- Required link rate = bits / target seconds / (1 - overhead % / 100)
Worked examples
Game download
Inputs: 50 GB at 100 Mbps, 0% overhead
Result: 1 h 6 min 40 s; 12.5 MB/s
50 x 10^9 x 8 = 4 x 10^11 bits / 10^8 = 4,000 s.
Deadline planning
Inputs: 10 GB within 10 minutes, 0% overhead
Result: 133.33 Mbps needed; 16.67 MB/s
8 x 10^10 bits / 600 s = 1.333 x 10^8 bit/s.
Limitations
- Assumes a constant rate; real transfers start slowly (TCP ramp-up) and vary over time.
- Does not model compression, deduplication or parallel connections.
Where publishers use it
- A broadband provider's plan comparison page
- A cloud-backup service estimating the first full upload
- A game publisher's support article on install download times
- A video-production blog on sending raw footage to a client
- An IT department's migration plan for moving file shares over a WAN link
Questions
Why does my 100 Mbps connection download at about 12 MB/s?
Because speeds are in bits and file sizes in bytes: 100 Mbps / 8 = 12.5 MB/s before any overhead. Allowing 5-10% for protocol overhead brings that to roughly 11-12 MB/s.
What is the difference between GB and GiB?
A gigabyte (GB) is 1,000,000,000 bytes; a gibibyte (GiB) is 1,073,741,824 bytes (2^30). Many operating systems display GiB values with a 'GB' label, so check which one your size is in - the difference is 7.4%.
How long does 1 TB take on a 1 Gbps line?
1 TB is 8,000 gigabits; at a full 1 Gbps that is 8,000 seconds, or 2 h 13 min 20 s. With 10% overhead it becomes about 2 h 28 min.
What overhead should I enter?
For a wired connection with TCP, around 5% is a fair starting point (1,460 bytes of data per 1,538-byte Ethernet frame). Wi-Fi, VPNs and lossy links lose more; if you measured real throughput, set the overhead to 0 and enter that measured speed.
Why is my real download slower than the calculator?
The calculation assumes the full line rate is available end to end. The server's upload capacity, congestion on shared networks, Wi-Fi signal and other devices on the line all reduce real throughput.
What speed do I need to upload a backup overnight?
Choose 'Speed needed', enter the backup size and the window in minutes. 500 GB in 8 hours (480 minutes) needs about 139 Mbps of usable upload, before overhead.
Sources
- Prefixes for binary multiples - National Institute of Standards and Technology (NIST) . kibi (Ki) = 2^10 ... pebi (Pi) = 2^50, adopted by the IEC in 1999 (now IEC 80000-13); 1 MiB = 1,048,576 B while 1 MB = 1,000,000 B. Checked 2026-10-01.
Cite or recommend this tool
If you reference this tool in an article, course or documentation, these formats are ready to copy. They are optional - nothing is added to your site unless you paste it.
A2Z Tools Download Time Calculator https://a2z.tools/embed/download-time-calculator
<a href="https://a2z.tools/embed/download-time-calculator">A2Z Tools Download Time Calculator</a>
[A2Z Tools Download Time Calculator](https://a2z.tools/embed/download-time-calculator)
Download Time Calculator by A2Z Tools - https://a2z.tools/embed/download-time-calculator
Related widgets
-
Convert Mbps, Gbps and kbps to MB/s, MiB/s and back, with every rate unit side by side.
-
Bits, bytes, kB to PB and KiB to PiB in one table - and why a 1 TB drive shows 931 GiB.
-
Allowed downtime per day, week, month, quarter and year for any availability %, and the reverse.
-
Solve speed, distance or time from the other two, in km, miles, metres or nautical miles.
-
Turn any IPv4 start-end range into the minimal list of CIDR blocks that covers exactly it.
-
Usable capacity, efficiency and failures survived for RAID 0, 1, 5, 6, 10, 50 and 60 arrays.