Bandwidth Calculator - Network
Calculate how long a file transfer takes from file size in MB and available bandwidth in Mbps, using transfer time = file size / bandwidth.
Bandwidth Calculator - Network
Calculator
Adjust values & calculateEnter your values below. Every result is computed in your browser โ no data is sent to any server.
Formula: Time = File Size / Bandwidth
Worked example โ 80 seconds
Formula
Time = File Size / Bandwidth
Calculate file transfer time based on available bandwidth.
Worked Examples
Example 1: 1 GB file
Problem:1000 MB at 100 Mbps
Solution:8000 Mb / 100 Mbps = 80 sec
Result:80 seconds
Frequently Asked Questions
Why is actual speed lower than advertised?
Protocol overhead (TCP headers, packet framing), network congestion, and shared bandwidth reduce real throughput to 60-90% of the theoretical maximum.
How is transfer time calculated?
Transfer time (seconds) = File Size in bits / Bandwidth in bits per second. Convert MB to Mb by multiplying by 8, then divide by the link speed in Mbps.
What does the 80% efficiency estimate mean?
Network protocols, error correction, and TCP acknowledgments consume roughly 20% of raw bandwidth. The 80% figure gives a realistic estimate for real-world conditions rather than laboratory maximums.
When would I use Bandwidth Calculator - Network?
Use it to estimate backup window durations, video upload times, large file transfer schedules, or to check whether your internet connection is fast enough for a specific workload before provisioning infrastructure.
What is the difference between Mbps and MB/s?
Link rates are quoted in bits per second while file sizes are counted in bytes, and one byte is eight bits, so the two figures differ by a factor of eight. A 100 Mbps connection delivers at most 12.5 MB/s and a 1 Gbps link tops out near 125 MB/s. The capital B means bytes and the lowercase b means bits, which is the whole reason a download manager appears to run at a fraction of the advertised speed.
How does round-trip latency cap a single TCP transfer?
A sender may have only one receive window of unacknowledged data in flight, so a single stream cannot exceed the window divided by the round-trip time, a limit known as the bandwidth-delay product. A 64 KB window over a 100 ms path allows 65,536 bytes, or 524,288 bits, every 0.1 seconds, which works out near 5.2 Mbps however fat the link is. Window scaling from RFC 7323 lifts the 64 KB ceiling, and parallel streams work around whatever remains.
What does goodput mean and how does it differ from link rate?
Link rate is what the interface signals; goodput is the payload the application actually receives each second once headers, acknowledgements and retransmissions are subtracted. On Ethernet with a 1500-byte MTU, 20 bytes of IP header and 20 of TCP header leave 1460 bytes of payload, and each frame also costs 18 bytes of Ethernet header and checksum, an 8-byte preamble and a 12-byte interframe gap. That is 1460 useful bytes for every 1538 bytes of wire time, about 94.9 percent, before any loss.
Why do decimal and binary units make the same transfer look slower?
Networking follows SI, so 1 Mbps is exactly 1,000,000 bits per second, while operating systems often report file sizes in binary units where a megabyte means 1,048,576 bytes. Mixing the two inflates the payload relative to the rate by 4.9 percent at the mega scale and 7.4 percent at giga. Take a size from Windows Explorer and a rate from an ISP advertisement and the estimate already runs a few percent optimistic before protocol overhead is counted at all.
Why do many small files transfer far slower than one large file of the same size?
This model assumes one continuous stream. Moving thousands of small files instead adds a per-file cost: directory lookups, open and close calls, metadata writes and, on chatty protocols such as SMB or SFTP, a round trip or two per file that latency then multiplies. Each fresh TCP connection also restarts in slow start and never reaches full rate. Packing the set into a single tar or zip stream, or running several transfers in parallel, usually recovers most of the gap.
How do I size a nightly backup window from a change rate?
Convert the data that changes each night into bits, then divide by the rate you can realistically sustain, which on a domestic or branch link is the upload figure rather than the download one. With 200 GB of change and a 200 Mbps upload running at the 80 percent planning figure, the usable rate is 160 Mbps: 200 GB is 1.6 x 10^12 bits, so the transfer needs roughly 10,000 seconds, just under three hours. Compare that with the hours the window actually allows.
Background & Theory
History
Reviewed for accuracy by Daniel Agrici, Founder & Lead Developer ยท Editorial policy
Related Calculators
๐ถBandwidth Calculator
Calculate download times and data transfer rates
๐พData Size Converter
Convert between data sizes
๐งฎBandwidth Time Transfer Calculator
Calculate bandwidth time transfer with inputs, formulas, and instant results.
๐งฎAPI Latency Calculator
Calculate expected API latency from network RTT, processing time, and payload size.
๐งฎDownload Time Calculator
Calculate download time with inputs, formulas, and instant results.
๐งฎThroughput Efficiency Calculator
Calculate throughput efficiency with inputs, formulas, and instant results.
๐งฎBase64 Encode & Decode Calculator
Calculate base64encode decode with inputs, formulas, and instant results.
๐งฎHash Checksum Calculator
Calculate hash checksum with inputs, formulas, and instant results.