Download Time Calculator
A 4 GB file takes 320 seconds, or 5 minutes 20 seconds, on a steady 100 Mbps connection. This download time calculator estimates how long a file should take to transfer based on file size and connection speed. Enter the file amount, choose a decimal unit like MB or GB or a binary unit like MiB or GiB, then enter the line speed in Kbps, Mbps, or Gbps. The tool converts the file to bits, converts the speed to bits per second, and returns the result as seconds, minutes, hours, and a rounded clock-style duration. It is useful when you are planning a game download, checking whether a backup can finish before a meeting, comparing internet plans, or estimating transfer windows for cloud storage and deployment work. The answer is an estimate, not a guarantee, because actual throughput can fall below the rated line speed when protocol overhead, Wi-Fi conditions, server throttling, or other traffic gets in the way.
Quick answer
The calculator supports both decimal storage units like KB, MB, GB, and TB and binary storage units like KiB, MiB, GiB, and TiB, which matters because those two systems are close in name but not equal in size.
What this tells you
- •The calculator supports both decimal storage units like KB, MB, GB, and TB and binary storage units like KiB, MiB, GiB, and TiB, which matters because those two systems are close in name but not equal in size.
- •Every file size is converted to bytes first, then multiplied by 8 so the transfer uses bits, which is the same unit family used for internet speeds.
- •Connection speed is normalized into bits per second using common network units, so 100 Mbps and 1 Gbps can be compared on the same base scale without manual conversion.
- •The result appears in seconds, minutes, hours, and a rounded formatted duration so you can use whichever view makes the most sense for a quick file, a movie download, or an overnight backup.
- •Use the number as a planning estimate. Real transfers can finish faster or slower depending on Wi-Fi quality, routing, congestion, server limits, packet loss, and how many other devices are sharing the connection.
How to Use
- 11. Enter the file size you plan to download. Use the amount shown by the source, such as 700 for a 700 MB file or 1.5 for a 1.5 GiB disk image.
- 22. Choose the matching file size unit. Pick GB or TB when the source uses decimal storage labels, and pick GiB or TiB when the source lists binary units.
- 33. Enter your expected connection speed and select Kbps, Mbps, or Gbps. If you have a speed test result, using a realistic measured speed often gives a better estimate than using the highest advertised plan speed.
- 44. Calculate to see the estimated transfer time in seconds, minutes, hours, and a formatted duration such as 0h 13m 20s.
- 55. Compare a few speed scenarios if you are planning a download window. Checking the same file at 50 Mbps, 100 Mbps, and 250 Mbps makes it easier to judge if the transfer fits your schedule or if a different network is worth using.
How It Works
Formula
Download Time (seconds) = (File Size x 8) / Connection Speed (bits per second)The tool first converts your chosen file unit into bytes. For decimal units, 1 GB equals 1,000,000,000 bytes. For binary units, 1 GiB equals 1,073,741,824 bytes. It then multiplies bytes by 8 to get bits because network speeds are expressed in bits per second. Next it converts the connection speed into its full bit rate, such as 100 Mbps becoming 100,000,000 bits per second. Once both values share the same bit-based scale, download time is file bits divided by bits per second. For example, 4 GB at 100 Mbps becomes 4 x 1,000,000,000 x 8 ÷ 100,000,000 = 320 seconds, which is 5.33 minutes and formats to 0h 5m 20s. The method assumes the transfer can hold a steady rate from start to finish.
Calculation note: values are processed in the order shown above, using the current input units.
Worked Examples
Download a 4 GB game patch on a 100 Mbps line
A 4 GB file contains 32,000,000,000 bits after multiplying by 8. Dividing by 100,000,000 bits per second gives 320 seconds. That makes this a short download on a solid home broadband connection, assuming the game server can keep up.
Download a 700 MB video file at 50 Mbps
Here the file converts to 5,600,000,000 bits. Dividing by 50,000,000 bits per second gives 112 seconds. This kind of estimate is useful when you want to know whether a media file will finish before a meeting or a flight boarding call.
Download a 1.5 GiB system image at 300 Mbps
A binary gigabyte is larger than a decimal gigabyte, so 1.5 GiB becomes 1.5 x 1,073,741,824 bytes before converting to bits. That produces 12,884,901,888 bits. At 300,000,000 bits per second, the transfer time is 42.95 seconds, which rounds to 43 seconds in the formatted output.
Download a 120 GB project archive at 1 Gbps
This file size converts to 960,000,000,000 bits. Dividing by 1,000,000,000 bits per second gives 960 seconds exactly. It shows why a gigabit connection can still need a noticeable transfer window when the file is large enough.
Download a 35 MB installer over a 768 Kbps link
The file contains 280,000,000 bits. A 768 Kbps connection transfers 768,000 bits each second, so 280,000,000 ÷ 768,000 = 364.58 seconds. Slow links make even small files feel much larger, which is why unit choice and realistic speed input matter.
Scenario: Jordan uploads a wedding gallery overnight
Jordan has 1,800 RAW photos that average 24 MB each, so the upload dialog shows 43.2 GB. That is 345,600,000,000 bits. Her plan lists 20 Mbps upload, and Run 1 divides by 20,000,000 bits per second to get 17,280 seconds, exactly 4.8 hours. A speed test on her home Wi-Fi at 9 p.m., when she plans to start, shows 17.5 Mbps instead, and Run 2 at that rate needs 19,748.57 seconds, about 41 minutes longer. Started at 9 p.m., the upload should finish around 2:30 a.m., so she leaves the laptop plugged in overnight and expects it to run a little later once protocol overhead is counted.
Download time by file size and connection speed
Each cell is the formatted time this download time calculator returns, rounded to the nearest second. File sizes use decimal units (1 GB = 1,000,000,000 bytes) except the 100 GiB row, and speeds are decimal as well (1 Mbps = 1,000,000 bits per second).
| File size | 10 Mbps | 25 Mbps | 50 Mbps | 100 Mbps | 300 Mbps | 1 Gbps |
|---|---|---|---|---|---|---|
| 100 MB | 0h 1m 20s | 0h 0m 32s | 0h 0m 16s | 0h 0m 8s | 0h 0m 3s | 0h 0m 1s |
| 500 MB | 0h 6m 40s | 0h 2m 40s | 0h 1m 20s | 0h 0m 40s | 0h 0m 13s | 0h 0m 4s |
| 1 GB | 0h 13m 20s | 0h 5m 20s | 0h 2m 40s | 0h 1m 20s | 0h 0m 27s | 0h 0m 8s |
| 4 GB | 0h 53m 20s | 0h 21m 20s | 0h 10m 40s | 0h 5m 20s | 0h 1m 47s | 0h 0m 32s |
| 10 GB | 2h 13m 20s | 0h 53m 20s | 0h 26m 40s | 0h 13m 20s | 0h 4m 27s | 0h 1m 20s |
| 50 GB | 11h 6m 40s | 4h 26m 40s | 2h 13m 20s | 1h 6m 40s | 0h 22m 13s | 0h 6m 40s |
| 100 GB | 22h 13m 20s | 8h 53m 20s | 4h 26m 40s | 2h 13m 20s | 0h 44m 27s | 0h 13m 20s |
| 100 GiB | 23h 51m 39s | 9h 32m 40s | 4h 46m 20s | 2h 23m 10s | 0h 47m 43s | 0h 14m 19s |
| 1 TB | 222h 13m 20s | 88h 53m 20s | 44h 26m 40s | 22h 13m 20s | 7h 24m 27s | 2h 13m 20s |
Computed with this tool's formula, seconds = bytes x 8 / bits per second, then rounded to whole seconds for the h m s display, so 100 MB at 300 Mbps (2.67 seconds) shows as 0h 0m 3s. Decimal prefixes are the SI powers of 10. Binary prefixes are the IEC powers of 2, kibi (2^10) through tebi (2^40), set out in IEC 80000-13 and in NIST's list of prefixes for binary multiples. The 100 GiB row runs 7.37 percent longer than 100 GB because 1 GiB is 1,073,741,824 bytes. Every cell assumes the full rated speed carries file data from start to finish, so even a clean wired TCP transfer over Ethernet takes about 5 to 6 percent longer, as the section below works out.
Why real downloads take longer than the math
Two prefix systems give file sizes almost the same names. SI prefixes are strict powers of 10, and the BIPM's SI Brochure says they should not stand for powers of 2, with the example that a kilobit is 1,000 bits, not 1,024. For powers of 2 the IEC adopted kibi, mebi, gibi, and tebi in 1998, first as an amendment to IEC 60027-2 and now in IEC 80000-13, and NIST publishes the same list. Network speeds always use the decimal set, so 100 Mbps is exactly 100,000,000 bits per second. File sizes can go either way, and the gap grows at every step: 2.4 percent at kilo, 4.9 percent at mega, 7.4 percent at giga, and almost 10 percent at tera.
Pick the unit by where the size came from. Apple's support documentation says its current systems count storage in decimal, and that only older ones such as OS X Leopard and iOS 10 and earlier used binary. Windows counts sizes in powers of 1,024 but still labels them KB, MB, and GB, which is why drive makers such as Seagate explain that a 500 GB drive shows as about 465 GB there. A file Windows calls 4.00 GB is 4 GiB in this calculator. Sizes and speeds also use different base units. A byte is 8 bits, the octet that IP and TCP count in, so 100 Mbps is at most 12.5 MB per second before any overhead, the figure to compare with an app that reports MB/s.
The tool assumes every bit on the line is file data, and no real link works that way. Each packet carries an IPv4 header of at least 20 bytes (RFC 791) and a TCP header of at least 20 bytes (RFC 9293). Ethernet carries at most 1,500 bytes of IP data per frame (RFC 894), and IEEE 802.3 framing adds 38 more bytes on the wire for the preamble, header, checksum, and the gap between frames. That leaves 1,460 bytes of file data out of every 1,538 sent, or 94.9 percent. The TCP timestamps option from RFC 7323 takes 10 bytes plus, usually, 2 of padding, which cuts the share to 1,448 bytes, or 94.1 percent. So a clean wired transfer takes about 5 to 6 percent longer than this tool shows, and the 4 GB at 100 Mbps example lands near 337 seconds instead of 320. Encryption, HTTP framing, and Wi-Fi add their own overhead on top.
Distance matters too. One TCP connection can have only one receive window of data in flight per round trip, so it tops out at window size divided by round-trip time. RFC 6349, the IETF framework for TCP throughput testing, sizes send and receive buffers from this bandwidth-delay product. The window field in the TCP header is 16 bits (RFC 9293), so without the window scale option from RFC 7323 one connection could move only 65,535 bytes per round trip, about 5.2 Mbps over a 100 ms path however fast the line is. Modern systems scale the window, but a small buffer on either end, or a per-user cap on the server, still limits a single download from far away.
Advertised speed is a plan tier, not a promise for every minute of the day. The FCC's Measuring Broadband America program tests this by wiring a measurement box in at the home gateway, ahead of the household's own computers, and comparing what it measures with the advertised tier. Its methodology treats weekday evenings from 7 to 11 p.m. local time as peak hours, and its early technical appendices describe a download test that ran three TCP connections at once so the line was full. A single download over home Wi-Fi shares the line with everything else in the house and may use one connection. For planning, run a speed test on the same device and network at the hour you plan to download, enter that number, and treat the answer as a best case at that speed.
Common mistakes
- Mixing up Mbps and MB/s. A capital B means bytes, and 1 byte equals 8 bits, so 100 Mbps is not the same as 100 MB/s.
- Choosing GB when the source actually lists GiB, or the other way around. The names look similar, but binary units are larger and can change the estimate by a noticeable amount on big files.
- Entering the advertised plan speed instead of a realistic measured speed. If your home internet advertises 300 Mbps but usually tests at 180 Mbps on Wi-Fi, the lower number will produce a better planning estimate.
- Treating the result as guaranteed completion time. Server throttling, congestion, packet loss, and background traffic can all stretch the real transfer.
- Forgetting that the tool estimates transfer time only. Install time, extraction time, checksum verification, and post-download setup are separate steps that can add several more minutes.
Embed this calculator on your site
Paste this code where you want the calculator to appear. It is responsive, mobile-friendly, resizes automatically, and is free to use as long as the credit line stays in place.
<script src="https://calctide.com/embed.js" data-tool="download-time-calculator" async></script>
<p style="font-size:12px;margin:4px 0 0">Download Time Calculator by <a href="https://calctide.com/tech/download-time-calculator/">CalcTide</a></p>Preview the embed at /embed/download-time-calculator/.