Bandwidth Calculator

Estimate how long a file transfer will take given a file size and bandwidth, or work backward to find the bandwidth needed to hit a target time.

Input

Results

Transfer Time
—
Bits Transferred
—
Bytes Transferred
—
Actual transfer speed is typically lower than the theoretical rate due to protocol overhead, network congestion, latency, and other real-world conditions.

Overview

The Bandwidth Calculator estimates how long a transfer of a given size takes over a link of a given speed, or, in reverse mode, what speed you need to move a given amount of data within a target time.

It helps with capacity planning, estimating backup and replication windows, sanity-checking a migration schedule, and understanding why a "100 megabit" connection does not move 100 megabytes per second.

How It Works

Link speeds are quoted in bits per second (bps, Kbps, Mbps, Gbps) while file sizes are quoted in bytes (KB, MB, GB, TB), and one byte is eight bits. The calculator converts the file size to bits, converts the bandwidth to bits per second, and divides: time = bits ÷ bits per second. Reverse mode rearranges the same formula: required bandwidth = bits ÷ seconds.

Units are decimal: 1 KB = 1,000 bytes, 1 MB = 1,000,000 bytes, and so on, matching how link speeds and most vendor storage figures are specified. Operating systems often report sizes in binary units (KiB, MiB, GiB, powers of 1,024), which are about 7% larger at the gigabyte scale.

The result is a theoretical best case. Real transfers are slower because of protocol headers, retransmissions, congestion, latency (especially for protocols that wait for acknowledgements), disk speed, and server-side limits.

How to Use the Bandwidth Calculator

  1. Select the mode: File Size + Bandwidth → Transfer Time or File Size + Transfer Time → Required Bandwidth.
  2. Enter the file size and pick its unit (KB, MB, GB, or TB).
  3. Enter the bandwidth and its unit (bps, Kbps, Mbps, Gbps), or the target time in seconds for reverse mode.
  4. Press Calculate and read the result. Remember that actual throughput will be lower.

Worked Example

How long does 4.7 GB take on a 100 Mbps link?

You need to copy a 4.7 GB image over a 100 Mbps connection, and separately you want to know what speed is required to move 500 MB in one minute.

Input

Mode 1: 4.7 GB at 100 Mbps
Mode 2: 500 MB in 60 seconds

Output

Transfer time:       6m 16s  (376.0 seconds)
Bits transferred:    37,600,000,000
Bytes transferred:   4,700,000,000

Required bandwidth:  66.67 Mbps  (66667 Kbps / 0.0667 Gbps)

4.7 GB is 4,700,000,000 bytes = 37,600,000,000 bits. At 100,000,000 bits per second that is 376 seconds, or 6m 16s. In practice you should expect noticeably longer; treat this as the minimum.

For reverse mode, 500 MB is 4,000,000,000 bits; moving that in 60 seconds needs about 66.67 Mbps. Note that the same 4.7 GB figure is only about 4.38 GiB when your operating system reports binary units, which is why file sizes seen in different tools do not always match.

Interpreting Results

Transfer time
Shown in days, hours, minutes, and seconds. It assumes the link runs at full speed for the whole transfer.
Bits and bytes transferred
The size you entered expressed in both units, handy for checking unit conversions.
Required bandwidth
The minimum steady rate needed to finish in the target time. Add headroom for overhead and other traffic sharing the link.

Troubleshooting

The real transfer is much slower than the estimate.
Check for congestion, a bottleneck elsewhere (disk, VPN, firewall, the remote server's rate limit), high latency with a small TCP window, or a slower negotiated link speed on one hop. Measure the actual path rather than assuming the advertised rate.
"File size must be greater than 0" or "Bandwidth must be greater than 0".
Enter positive numbers. A zero or blank value cannot be used in the calculation.
My numbers do not match my operating system.
The calculator uses decimal units (1 GB = 109 bytes). Your OS may use GiB (230 bytes). Convert before comparing.

Limitations and Accuracy

  • It does not model protocol overhead, packet loss, latency, concurrency, compression, or time-varying throughput.
  • Link speed is assumed constant and fully available to this one transfer.
  • Results describe a single stream; parallel transfers share, not add to, a link's capacity.

Data Handling

Runs in your browser. What you enter is processed on your device and is not sent to NetEngToolkit’s servers or to any third party.

Frequently Asked Questions

Why is 100 Mbps not 100 MB per second?

Mbps is megabits per second. Divide by 8 to get megabytes per second, so 100 Mbps is at most 12.5 MB/s before any overhead.

Is the estimate an upper or lower bound?

It is the best case (a lower bound on time). Real transfers take at least this long.

Does latency matter?

Yes, especially for protocols that wait for acknowledgements. On a long-latency path a small window limits throughput below the link rate, a situation the connectivity guide touches on.