What your download bar is telling you about Mbps and MB/s
Your internet plan says 500 Mbps. Your browser shows the download crawling along at 61 MB/s. At some point most of us have paused and wondered whether the ISP kept a factor of eight for themselves. They didn't. The math is boringly simple, and knowing it saves you from misreading every speed number you see.
Bits versus bytes
Network speeds are marketed in bits per second. File sizes are counted in bytes. Eight bits make a byte, so 500 megabits per second is 62.5 megabytes per second, in the perfect case. Nobody sells you a plan in MB/s because the bigger number looks better in an ad. Storage vendors do the reverse: they measure capacity in bytes and disk speed in MB/s, because those are the units that describe what is actually being written.
Why the real number sits below 62.5
Several small losses stack up between the advertised figure and what your download manager shows:
- Protocol overhead. Every TCP packet carries headers, and some of every connection is spent on acknowledgments rather than your file. For ordinary HTTPS downloads, plan on about 9 to 10 bits of line time per byte of payload, not exactly 8.
- Decimal versus binary units. Many download managers report MiB (multiples of 1,048,576) while marketing quotes decimal megabits (multiples of 1,000,000). That discrepancy alone makes 62.5 look like 59.6.
- The path in the middle. Wi-Fi is slower than the wire it hangs off, and other devices on the line are using it with you. The advertised number describes the wall jack, not your laptop.
Stack all of it and a 500 Mbps line honestly delivers 55 to 60 MB/s. If you see 6 MB/s, that is a real problem: something else is throttling, or you are reading a different unit.
The divide-by-10 rule
For quick mental math, divide the advertised Mbps by 10. The extra two bits of headroom stand in for protocol overhead and rounding, and the estimate lands close enough for most decisions. 100 Mbps is roughly 10 MB/s. 2,000 Mbps is roughly 200 MB/s. A 2 GB game patch on a 100 Mbps line is therefore about 200 seconds, call it three and a half minutes, and that is the kind of arithmetic worth having before the patch starts.
Reading numbers on the other side
The same trap waits in cloud workflows. A backup of 50 GB over an upload rated at 20 Mbps is not "about an hour"; it is more than five, because 20 Mbps delivers around 2 MB/s once overhead is paid. Teams that back up nightly discover this when the window they thought would take 40 minutes eats the whole working day.
If you would rather skip the mental division, the data transfer time estimator takes file size and line speed and returns the honest window, and the speed converter handles the bit-to-byte arithmetic across every unit pair. For the file-size side of the same confusion, data size converter sorts out MB, MiB, GB, and GiB.
None of this means the marketing lied. It means the marketing measures in bits while your patience is measured in bytes. Divide by ten, add a margin, and every speed number you meet becomes sanity-checkable.