Every day, thousands of internet subscribers upgrade to a "300 Mbps" or "1 Gigabit" fiber optic plan, only to be disappointed when Steam, Battle.net, or their browser downloads files at "37.5 MB/s" or "110 MB/s". Many assume their Internet Service Provider (ISP) is throttling their line or scamming them.
In reality, nothing is broken. You are witnessing the fundamental mathematical distinction between Megabits per second (Mbps) and Megabytes per second (MB/s)—the legendary 8-to-1 conversion ratio that has confused computer users for over three decades.
The Golden Rule: Capital 'B' vs. Lowercase 'b'
The difference between bits and bytes is not just semantics—it represents an 8-fold multiplier in data size:
Lowercase 'b' = Bit (Network Speed)
A bit is the smallest binary atomic unit of computer information (a single 0 or 1). Because telecom equipment transmits data serially along wires bit-by-bit, network speeds are universally rated in bits per second (Kbps, Mbps, Gbps).
Capital 'B' = Byte (File Size & Storage)
A byte is a collection of 8 bits. Computers organize memory and disk drives into bytes because 8 bits can represent a single alphanumeric character. Operating systems show files in Kilobytes (KB), Megabytes (MB), and Gigabytes (GB).
Therefore: 1 Byte = 8 bits. To convert any advertised Mbps plan into your real-world download speed in MB/s, simply divide by 8:
You can verify your connection instantly using our Mbps to MB/s Converter or check the reverse with our MB to Mbps Converter.
Why Do ISPs Advertise in Mbps Instead of MB/s?
Beyond technical conventions dating back to telegraphy and early telephony, marketing psychology plays a major role. To the average consumer, a number that is eight times larger sounds vastly more impressive:
- "100 Mbps Internet" sounds like blazing fast triple-digit performance.
- "12.5 MB/s Internet" sounds modest, even though they represent the exact same physical throughput.
The Protocol Tax: Why You Never Get Exactly 1/8th
If you have a 100 Mbps connection, you might expect exactly 12.5 MB/s. However, when downloading a real file, you will usually max out around 11.5 to 12.0 MB/s. Where does that missing 0.5 - 1.0 MB/s go?
This loss is known as Network Protocol Overhead. When data travels across the internet, raw file chunks must be packaged inside TCP/IP envelopes:
- IP Headers (20 bytes): Destination and source IP routing data.
- TCP Headers (20 bytes): Sequence numbers, flags, and port routing.
- TLS/SSL Encryption (20-30 bytes): Cryptographic security signatures for HTTPS websites.
- Acknowledgement Packets (ACKs): Your computer must continuously send verification packets back to the host server confirming each chunk arrived safely.
Combined, protocol overhead typically consumes 5% to 10% of your total theoretical link speed. To plan realistic download completion times, use our Download Time Calculator.
Quick Reference: Advertised Mbps vs. Real-World MB/s
| Advertised Plan | Theoretical MB/s | Real-World MB/s (with Overhead) | Time to Download 50 GB Game |
|---|---|---|---|
| 25 Mbps | 3.125 MB/s | ~2.8 MB/s | ~5 Hours |
| 100 Mbps | 12.5 MB/s | ~11.5 MB/s | ~1 Hour 15 Mins |
| 300 Mbps | 37.5 MB/s | ~34.5 MB/s | ~25 Minutes |
| 500 Mbps | 62.5 MB/s | ~57.5 MB/s | ~15 Minutes |
| 1,000 Mbps (1 Gbps) | 125.0 MB/s | ~115.0 MB/s | ~7 Minutes |