The Bandwidth Calculator computes file transfer time for any file size and network speed, handling all unit conversions with protocol overhead correction. Essential for IT administrators planning data migrations, backups, and media workflows where transfer time is a critical planning variable.
8
s
0.13
min
0.0022
h
0.098
GB
800
Mb
12.5
MB/s
0.1
Gbps
450
files/h
8
s
0.13
min
0.0022
h
0.098
GB
800
Mb
12.5
MB/s
0.1
Gbps
450
files/h
A 2 TB backup over a 100 Mbps corporate WAN takes longer than most IT administrators expect — and the reason is usually the gap between advertised bandwidth and effective throughput, compounded by the bits-vs-bytes confusion that traps even experienced engineers. The calculator for bandwidth and data transfer time handles all unit conversions correctly, applies realistic protocol efficiency factors, and gives the honest transfer time estimate that enables accurate project planning.
Transfer time calculation appears trivial:
Time (seconds) = File Size (bits) / Bandwidth (bits per second)
The complexity lies in getting units right. The critical convention: data sizes use binary prefixes (1 GiB = 2³⁰ = 1,073,741,824 bytes; 1 GB in common usage often = 10⁹ bytes by storage manufacturers); network speeds use decimal SI prefixes (1 Gbps = 10⁹ bits per second). Multiplying a 2 TB file (2 × 10¹² bytes = 1.6 × 10¹³ bits) by a 1 Gbps connection (10⁹ bps) gives 16,000 seconds = 4.44 hours at theoretical maximum. Converting: 2 TB = 2 × 10¹² × 8 = 1.6 × 10¹³ bits; Time = 1.6 × 10¹³ / 10⁹ = 16,000 s = 4.44 hours. Use this online calculator to avoid unit errors. The data transfer calculator provides extended multi-file transfer analysis.
Advertised bandwidth is not effective throughput. Protocol overhead at multiple levels reduces actual data transfer rate below raw bandwidth:
For planning purposes, use 70–80% of advertised bandwidth as achievable effective throughput for large file transfers over LAN; 50–65% for WAN transfers without optimization.
Reference transfer times for common data management scenarios at different network speeds:
The download/upload time calculator and network calculators provide complementary network planning tools.
For large bulk transfers, bandwidth is the limiting factor. For interactive applications and short transfers, latency dominates. The TCP throughput ceiling formula explains why high-latency WAN links underutilize available bandwidth:
Maximum TCP throughput ≈ Window Size / Round-Trip Time
A standard TCP receive window of 65,535 bytes on a 100 ms RTT link: throughput ceiling = 65,535 / 0.1 = 655,350 bytes/s ≈ 5.2 Mbps — regardless of the actual 100 Mbps link bandwidth. This is why trans-oceanic data transfers achieve only a fraction of available bandwidth without TCP window scaling or application-layer optimization. WAN acceleration appliances address this by increasing effective window sizes through proxy-based acknowledgment, enabling 80–90% link utilization even at 100+ ms latency.
The calculator converts file size from bytes to bits, then divides by bandwidth to get transfer time:
File Size in Megabits:
$$S_{bits} = S_{MB} \times 8$$
Since 1 byte = 8 bits, a file measured in megabytes must be multiplied by 8 to obtain megabits. This is the critical conversion that aligns the file size unit with the bandwidth unit (Mbps).
Transfer Time (seconds):
$$T_{sec} = \frac{S_{bits}}{B_{Mbps}}$$
Dividing megabits by megabits-per-second yields time in seconds. This assumes continuous transfer at full rated bandwidth with zero overhead.
Transfer Time (minutes and hours):
$$T_{min} = \frac{T_{sec}}{60} \qquad T_{hr} = \frac{T_{sec}}{3600}$$
Bandwidth Conversion:
$$B_{MB/s} = \frac{B_{Mbps}}{8} \qquad B_{Gbps} = \frac{B_{Mbps}}{1000}$$
These conversions let you compare ISP-advertised speeds (Mbps) with actual file transfer rates shown by your operating system (MB/s).
The transfer time in seconds gives you the theoretical minimum time assuming 100% bandwidth utilization. In practice, expect 10-30% longer due to protocol overhead (TCP, TLS, application-layer framing), network congestion, and server-side rate limiting. For planning purposes, multiply the calculated time by 1.2 to get a realistic estimate. The MB/s conversion of your bandwidth is what your download manager or file transfer tool will display — if your ISP advertises 100 Mbps, expect to see approximately 12.5 MB/s in your transfer tool (not 100). For large transfers (multi-GB or TB), the hours display is most practical. If the estimated time exceeds your available window, consider compressing the data first (which can reduce size by 30-80% depending on content type), using parallel transfer streams, or upgrading your connection.
Inputs
Results
A 15 GB (approximately 15,000 MB) 4K movie file on a 100 Mbps connection takes 1,200 seconds (20 minutes) to download at full speed. The connection delivers 12.5 MB/s actual throughput. In practice, expect 22-25 minutes due to overhead and congestion.
Inputs
Results
Transferring a 500 GB database backup over a 1 Gbps dedicated link takes approximately 4,000 seconds (66.7 minutes, or about 1.1 hours). At 125 MB/s throughput, this fits within most nightly backup windows. With compression, the actual data transferred could be 40-60% less.
ISPs advertise speeds in megabits per second (Mbps), but download managers show megabytes per second (MB/s). Divide the ISP speed by 8 to get MB/s. Additionally, protocol overhead (TCP/IP headers, TLS encryption), network congestion, server-side rate limiting, and Wi-Fi signal degradation all reduce actual throughput below the theoretical maximum.
Mbps = megabits per second (lowercase 'b' for bits). MB/s = megabytes per second (uppercase 'B' for bytes). Since 1 byte = 8 bits, 1 MB/s = 8 Mbps. ISPs and networking use Mbps; operating systems and applications display MB/s. This 8x difference is the most common source of bandwidth confusion.
No, this calculator computes the theoretical minimum transfer time assuming 100% bandwidth utilization. Real-world TCP/IP adds approximately 3-5% overhead per packet (TCP headers, IP headers, Ethernet framing). TLS encryption adds another 1-2%. For realistic estimates, multiply the calculated time by 1.1 to 1.3 depending on conditions.
1 TB = 1,048,576 MB = 8,388,608 Megabits. At 100 Mbps: ~23.3 hours. At 1 Gbps: ~2.3 hours. At 10 Gbps: ~14 minutes. At 100 Mbps, TB-scale transfers are typically impractical over WAN — physical media shipping (AWS Snowball) is often faster.
Bandwidth is the maximum theoretical capacity of a link (e.g., 1 Gbps Ethernet). Throughput is the actual data successfully transferred per second, which is always less than bandwidth due to overhead, congestion, and protocol inefficiencies. This calculator uses bandwidth (ideal), not throughput (real-world).
Streaming requires sustained bandwidth: 720p needs ~3-5 Mbps, 1080p needs ~5-10 Mbps, 4K needs ~25-40 Mbps per stream (varies by codec — H.265/HEVC is more efficient than H.264). Multiply by concurrent streams, then add 30% headroom. For 4 simultaneous 4K streams: 4 x 35 x 1.3 ≈ 182 Mbps minimum.
In networking, 1 Gbps = 1,000 Mbps (decimal/SI prefix). This differs from storage where 1 GiB = 1,024 MiB (binary prefix, IEC standard). Network speeds always use decimal: 10 Gbps = 10,000 Mbps. This calculator uses the decimal convention consistent with networking standards.
Most consumer ISP connections are asymmetric (ADSL, cable, typical fiber plans) because residential users download far more than they upload. Business-grade connections often offer symmetric speeds. When calculating upload times (cloud backup, video uploading), use your upload speed — typically 10-50% of download speed on consumer plans.
Latency (ping time) has minimal impact on large file transfers because TCP uses windowing to send multiple packets before waiting for acknowledgment. However, high latency (>100ms) reduces TCP throughput on high-bandwidth links due to the bandwidth-delay product. For transfers across continents, tools with parallel streams (like rsync or Aspera) mitigate latency effects.
Networking uses decimal (SI) prefixes: 1 MB = 1,000,000 bytes, 1 Mbps = 1,000,000 bits/s. Storage historically used binary (IEC) prefixes: 1 MiB = 1,048,576 bytes. This calculator uses the decimal convention (MB = 1,000,000 bytes), consistent with how ISPs measure bandwidth. The difference is ~4.86% at the mega level and grows at higher prefixes.
How helpful was this calculator?
5.0/5 (1 rating)
