Why Your 100 Mbps Connection Downloads at 12 MB/s: Bandwidth Explained
The bits-versus-bytes mix-up that makes downloads feel eight times slower than your plan, how to turn any connection speed and file size into a real download time, why ~10% overhead is normal, and decimal versus binary units.
You pay for a “100 megabit” internet plan, you start a 5 GB download, and the progress bar settles at about 12 MB/s. It feels like you’re being short-changed by a factor of eight — but you’re not. The number on your bill and the number in your download manager are measured in two different units that happen to share almost the same name, and the eight-times gap between them is exactly the ratio you’d expect once you know what each one means. Understanding the difference turns “is my internet broken?” into a quick mental calculation you can do before any download even starts.
Bits versus bytes: the factor of eight
The whole confusion comes down to one fact: one byte is eight bits. Internet service providers advertise speed in bits per second — megabits per second, written Mbps with a lowercase b. Files on your disk are measured in bytes — megabytes, written MB with an uppercase B. So to get the download speed you actually see, you divide the advertised number by eight:
MB/s = Mbps ÷ 8
A 100 Mbps connection therefore tops out at 100 ÷ 8 = 12.5 MB/s, which is exactly what your download manager shows. The marketing department quotes the bigger-sounding bits number; your operating system reports the bytes number because that’s the unit files come in. Neither is lying — they’re just different units. The same rule runs in reverse: a 1 Gbps fibre line is 1000 ÷ 8 = 125 MB/s, and a 25 Mbps connection is about 3.1 MB/s. Whenever a speed feels “8× too slow,” this is almost always why.
Turning speed and size into time
Once both numbers are in the same unit, download time is simple division:
time (seconds) = file size (bytes) ÷ throughput (bytes per second)
Take that 5 GB file on the 100 Mbps line. Convert the file to bytes — 5 GB = 5,000 MB = 5,000,000,000 bytes — and divide by 12.5 MB/s (12,500,000 bytes/s): you get 400 seconds, or about six minutes and forty seconds. The same arithmetic scales to anything: a 50 GB game patch on the same connection is ten times longer, around 67 minutes; on a 1 Gbps line it drops to under seven minutes because the throughput is ten times higher. Two variables — how big and how fast — fully determine the third, so you can always solve for whichever one you don’t know.
Decimal versus binary: GB or GiB?
There’s a second, smaller source of confusion: what “giga” means. This calculator and most ISPs and drive manufacturers use decimal SI prefixes, where 1 GB = 1,000 MB = 1,000,000,000 bytes. Some operating systems (notably Windows) report storage in binary units but still label them “GB,” when they really mean gibibytes: 1 GiB = 1,024 MiB = 1,073,741,824 bytes. The two differ by about 7% at the gigabyte level and grow further apart for larger sizes, which is why a “1 TB” drive shows up as roughly 931 “GB” in your file manager. For download-time estimates the decimal convention is the right one to use because it matches how both ISP speeds and file sizes are advertised — mixing a binary file size with a decimal speed is a common way to get an answer that’s quietly off by several percent.
Why real downloads are slower than the math
Even with the units sorted out, a real download rarely hits the theoretical number exactly, and that’s expected. Data on the internet doesn’t travel as a pure stream of your file’s bytes — it’s wrapped in TCP and IP headers, packets occasionally get lost and retransmitted, and servers deliver in bursts rather than a perfectly smooth flow. The usual rule of thumb is to add about 10% overhead, i.e. multiply the theoretical time by roughly 1.11. So that 400-second ideal download is more realistically around 444 seconds in practice. Other real-world factors pile on top: a slow or distant server, Wi-Fi interference, congestion at peak hours, or another device on your network hogging bandwidth. The theoretical figure is the floor — the fastest the transfer could go — and the overhead factor nudges it toward what you’ll actually experience.
Bandwidth is not the same as latency
One last distinction saves a lot of confusion: bandwidth and latency measure different things, and a fast connection can still feel slow. Bandwidth is how much data can move per second — the width of the pipe — and it’s what determines download time for a large file. Latency is how long a single packet takes to make the round trip, measured in milliseconds (your “ping”). For pulling down a 50 GB game, bandwidth is what matters and latency is almost irrelevant. For a video call or an online game, the opposite is true: you’re sending tiny packets constantly, so a 20 ms ping feels instant while a 200 ms ping feels laggy no matter how many megabits you’re paying for. This is why “upgrade your internet speed” doesn’t always fix a stuttery video chat — the bottleneck there is latency, which a bigger bandwidth number does nothing to improve. When you estimate download time you’re working purely in the bandwidth world, so latency doesn’t enter the formula, but it’s worth knowing which problem you actually have before you blame your plan.
It’s also why upload and download speeds often differ. Many home connections are asymmetric — a plan might give you 100 Mbps down but only 10 Mbps up — so the same file that downloads in minutes can take ten times longer to send. When you’re backing up to the cloud or sharing a large video, plug your upload speed into the calculation, not the headline download figure.
Estimate before you download
The whole calculation needs just three things: your speed, the file size, and the bits-to-bytes divide-by-eight. To skip the unit juggling, the Bandwidth & Download Time Calculator lets you enter a speed in Kbps, Mbps, Gbps or MB/s and a file size in KB through TB, optionally applies the ~10% real-world overhead, and shows the download time plus every unit conversion side by side. If you’re working out how big a video file will be before you download or upload it, pair it with the Video Bitrate & File Size Calculator; and for logging or scheduling transfers, the Unix Timestamp Converter handles the time side. Learn the divide-by-eight rule once and you’ll never be surprised by a download speed again.
Try the tools from this guide
-
Bandwidth & Download Time Calculator (Mbps ↔ MB/s)
Convert Mbps to MB/s and calculate download time for any file size at any internet speed.
-
Video Bitrate & File Size Calculator (H.264, H.265, AV1)
Calculate video file size from bitrate, resolution, FPS and duration for H.264, H.265, AV1 and ProRes.
-
Unix Timestamp Converter (with Timezone)
Bidirectional Unix timestamp ↔ human date converter with timezones, milliseconds and ISO 8601.