Bandwidth Speed Estimator

How to use 3 steps
  1. Enter your Internet Speed in Mbps.
  2. Enter the File Size to Download in GB.
  3. Press Calculate Download Duration.
Download Estimate

How this tool works

Enter a connection speed in megabits per second and a file size in gigabytes, and the result is an estimated download time in minutes and seconds.

The conversion turns on a distinction that causes most of the confusion in this area: connection speeds are quoted in bits and file sizes in bytes, and there are eight bits to a byte. Megabits per second are converted to bytes per second by multiplying by a million and dividing by eight; the file size is converted to bytes by multiplying by 1024 three times. That mixture of decimal and binary units is deliberate, because it matches how the two figures are conventionally quoted — but it is also why a 1 GB file is not exactly a thousand megabytes.

Why real downloads take longer

  • Advertised speed is a maximum, not a guarantee: contention, Wi-Fi conditions and distance from the exchange all reduce it, and the shortfall is usually largest at peak times.
  • Protocol overhead is real: headers, acknowledgements and retransmissions consume part of the link, typically a few per cent even on a clean connection.
  • The server has a say: a slow or throttled source, or a busy one, caps your download regardless of how fast your own connection is.
  • Bits and bytes differ by a factor of eight: a 100 Mbps connection delivers about 12.5 MB per second at best. Confusing the two is the single most common source of disappointment.

The distinction behind most of the confusion here

Connection speeds are quoted in bits and file sizes in bytes, and there are eight bits to a byte — the entire source of the gap between an advertised connection speed and the download figure a file manager actually shows. The [msm_tool slug="speed-data-converter"] converts megabits per second into bytes per second by multiplying by a million and then dividing by eight, which is the whole calculation behind why a 100 Mbps connection delivers roughly 12.5 MB per second at its theoretical best rather than the 100 the headline number seems to promise.

Why a gigabyte is not exactly a thousand megabytes here

File size is converted to bytes by multiplying by 1024 three times rather than 1000, matching how operating systems conventionally display file sizes even though storage manufacturers typically use the decimal 1000 convention instead. The difference between the two conventions comes to roughly seven per cent at gigabyte scale, which is enough to notice on a genuinely large file.

Advertised speed is a ceiling, not a guarantee

Network contention, Wi-Fi conditions and distance from the exchange all reduce real throughput below the advertised figure, typically by the largest margin during peak usage hours when the most people are competing for the same shared capacity.

Protocol overhead takes its own share

Headers, acknowledgements and retransmissions all consume part of any connection's real capacity, typically a few per cent even under otherwise clean conditions — a cost that exists regardless of how fast the underlying connection actually is.

The source matters as much as the connection

A slow, throttled or simply busy server caps a download at its own limit no matter how much faster the receiving connection could otherwise go, which is why two downloads over an identical connection can finish at noticeably different speeds depending entirely on where each file is coming from.

This converts figures, it does not measure anything

The result is calculated entirely from numbers supplied by hand rather than from an actual transfer — measuring real throughput requires genuinely moving data across the connection, which is a different kind of tool from a converter working purely from figures typed in.

Frequently Asked Questions

Specific to the Bandwidth Speed Estimator. Broader questions about this category are answered on the category page.

That is exactly what 100 Mbps means. Speeds are quoted in megabits and file transfers are usually reported in megabytes, and there are eight bits to a byte, so dividing by eight gives the expected figure. Nothing is wrong.
Mbps is megabits per second, the unit connection speeds are sold in. MB/s is megabytes per second, the unit download managers display. One MB/s is eight Mbps.
The estimate assumes you get the full advertised speed with no overhead. In practice protocol overhead, network contention, Wi-Fi conditions and the source server's own limits all reduce throughput. Treat the figure as a best case.
Both conventions exist. Storage manufacturers use 1000, operating systems typically use 1024, and this calculation uses 1024 to match how file sizes are usually displayed. The difference is about seven per cent at gigabyte scale.
No. It converts figures you supply. Measuring throughput requires transferring data, which this tool does not do.

Subscribe to receive notifications about new tools, features, and productivity tips.