Seconds
--
Free · Instant · No signup
Time to move a file from size and a link speed in Mbps, with overhead you can set.
Page updated 2026-09-04.
Seconds
--
Effective Mbps
--
A 4.5 GB file over a 100 Mbps link, with 8% protocol overhead accounted for, takes 6 minutes 31.3 seconds (391.3 seconds) -- not the roughly 6 minutes a naive gigabytes-over-megabits calculation without unit conversion or overhead would suggest.
The most common error in this exact calculation is mixing up megabits and megabytes: a '100 Mbps' link speed is 100 megabits per second, but a '4.5 GB' file size is measured in gigabytes -- converting the file size to megabits first (4.5 GB x 8 bits/byte x 1,000 = 36,000 megabits, using the decimal GB convention) is required before dividing by the megabit-per-second link speed, or the result would be off by a factor of 8.
The 8% protocol overhead reduces effective throughput from the advertised 100 Mbps down to 92 Mbps -- real-world data transfer always carries some overhead from the networking protocols themselves (TCP/IP headers, retransmissions, handshaking), so actual achievable throughput is reliably somewhat below the advertised raw link speed.
Megabits vs megabytes are explicit. Real throughput is lower than advertised rate. ISPs and hardware specs advertise link speed in megabits per second (Mbps), while file sizes and download progress bars are almost always shown in megabytes (MB) or gigabytes (GB) -- since 1 byte = 8 bits, this unit mismatch alone can make a transfer seem 8x slower than expected if not accounted for, which is exactly why this calculator keeps the two units explicit and separate.
Beyond protocol overhead, real-world throughput is also affected by network congestion, the performance of the server on the other end, and Wi-Fi versus wired connection quality -- the 8% overhead figure here models one specific, fixed source of slowdown, not every possible real-world factor that could reduce actual transfer speed.
This calculation assumes a sustained, consistent connection at the stated Mbps for the entire transfer -- a real download's speed can fluctuate throughout, especially over a longer transfer, making the actual elapsed time vary from this steady-state estimate.
For working out file size from a bitrate and duration instead (the reverse direction, common for video/audio planning), the Bandwidth/Bitrate File Size Estimator handles that calculation.
For converting between storage units more generally (bits, bytes, GB, TB) outside the context of a specific transfer time, the General Data Storage Unit Converter is the broader reference tool.
Because Mbps (megabits per second) and GB (gigabytes) use different units -- converting 4.5 GB to megabits (x8 for bits per byte) is required before dividing by the 100 Mbps rate, and the 8% protocol overhead further reduces effective throughput, both of which push the actual time to 6m 31.3s.
Effective Mbps = advertised Mbps x (1 - overhead %) = 100 x (1 - 8%) = 92 Mbps. This models the real-world reduction in usable throughput caused by protocol overhead (headers, handshaking, retransmissions) inherent to any real network transfer.
Megabits vs megabytes are explicit. Real throughput is lower than advertised rate. It's a long-standing convention split between the telecom/networking industry (which measures link speed in bits per second) and file systems/software (which measure size in bytes) -- since 1 byte = 8 bits, mixing them up without converting produces an 8x error.
Approximately, under steady-state conditions matching the stated inputs. Real transfers can vary due to network congestion, server-side performance, and connection quality fluctuations that this calculation, which assumes a constant sustained speed, doesn't model.
It varies by network conditions and protocol -- 8% is a reasonable planning estimate, but actual overhead depends on factors like packet loss, retransmission rates, and the specific protocols in use, which can push real overhead higher or lower than this single fixed assumption.
This-Origin Web Storage Inspector List keys from window.localStorage or sessionStorage for this site origin only.
Base64 Encoder & Decoder UTF-8 and emoji-safe encode/decode, Standard or URL-safe, with byte telemetry.
Meta Tags Generator Open Graph and Twitter Card tags.
Regex Tester JavaScript regex flags, match table with groups, presets, and a 20k ReDoS cap.