Your internet plan says "100 Mbps" — and your download manager says you're getting 12 MB/s, which sounds like a problem, but is actually almost exactly what 100 Mbps means, because internet speeds are measured in bits and file sizes are measured in bytes, and the difference is a factor of 8
The previous articles on this site covered bit/byte unit conversion and why a "1TB" drive shows as "931GB." This article addresses a related, but distinct, source of confusion: internet connection speeds (Mbps) vs file/download sizes (MB) — where the bits-vs-bytes distinction (covered, in general, in the original article) has a specific, frequently-confusing application.
The convention: network speeds in bits, file sizes in bytes
Internet service providers (and networking equipment generally) advertise/measure connection speeds in bits per second — "Mbps" = megabits per second.
File sizes, download managers, and most operating systems' file-size displays use bytes — "MB" = megabytes (1 megabyte = 8 megabits, since 1 byte = 8 bits — covered in the original article).
The conversion: divide Mbps by 8 to get (theoretical maximum) MB/s:
100 Mbps ÷ 8 = 12.5 MB/s (theoretical maximum download speed, in megabytes per second, for a "100 Mbps" connection)
This is not a "loss" or "inefficiency" — it's purely a unit difference — a "100 Mbps" connection literally is a "12.5 MB/s" connection — these are two descriptions of the same thing, in different units, just as "1 kilometer" and "1000 meters" describe the same distance in different units.
Why this causes confusion: lowercase "b" vs uppercase "B"
The notational convention (covered in the original article): lowercase "b" = bits; uppercase "B" = bytes.
- Mbps = Megabits per second
- MB/s (or MBps) = MegaBytes per second
The visual difference between "Mbps" and "MB/s" is subtle — a single-case difference in one letter — and many consumer-facing displays/contexts don't consistently distinguish these (informal writing, marketing materials, and even some software interfaces sometimes use "Mb" and "MB" inconsistently/interchangeably, despite the 8x difference in meaning) — **this notational ambiguity, combined with the genuine 8x factor, is the root of most "why is my download speed only 1/8th of what I was promised" confusion.
"Theoretical maximum" vs "actual" speed: a separate gap, with additional causes
Even after correctly converting Mbps to MB/s (dividing by 8) — actual, observed download speeds are often somewhat lower than this theoretical maximum, for reasons unrelated to the bits/bytes distinction:
Protocol overhead: data transmitted over a network includes header/protocol information, in addition to the actual file content — some portion of the "raw" connection bandwidth is consumed by this overhead, not available for file content itself — typically a relatively small percentage, but non-zero.
Server-side limitations: the server you're downloading from might not be capable of, or configured to, send data as fast as your connection could theoretically receive it — the download speed is limited by whichever is slower: your connection's capacity, or the server's capacity/configuration (and, for popular/shared servers, the server's available bandwidth, divided among many concurrent downloaders, might be far below its total capacity, for any individual download).
Wi-Fi vs wired connections: Wi-Fi connections have their own, separate theoretical-maximum-vs-actual gap — Wi-Fi speeds are affected by signal strength, interference, the number of devices sharing the Wi-Fi network, and the specific Wi-Fi standard/hardware involved — a device connected via Wi-Fi might experience meaningfully lower speeds than the same connection accessed via a wired (ethernet) connection, for reasons entirely separate from the ISP's advertised speed or the bits/bytes conversion.
"Up to" advertising: ISP-advertised speeds are frequently phrased as "up to X Mbps" — explicitly framing the advertised figure as a maximum, not a guarantee — actual speeds can (and often do) fall below this maximum, for various network-conditions reasons, within what's considered "normal" for such "up to" plans.
"Mbps" for upload vs download: often different numbers
Many consumer internet plans have different upload and download speeds — often significantly different (download speeds typically higher than upload, for most consumer-oriented plans, reflecting typical usage patterns — most consumer internet usage involves more downloading — streaming, browsing, downloading files — than uploading).
A plan advertised as "100/10 Mbps" (a common format for expressing asymmetric speeds) means 100 Mbps download, 10 Mbps upload — converting to bytes: roughly 12.5 MB/s download, 1.25 MB/s upload — if you're uploading a large file (to cloud storage, for instance) and experiencing speeds around 1.25 MB/s (or somewhat less, per the theoretical-vs-actual factors above) — this is consistent with a "100/10 Mbps" plan's upload speed, not a sign of a problem — checking which number (the 100 or the 10) is relevant to the direction of data transfer you're experiencing is essential before concluding "my speed seems low."
Speed test results: typically already in the "correct" unit for comparison
Internet speed test tools typically report results in Mbps (matching the ISP-advertised unit) — making direct comparison to your plan's advertised speed straightforward (no unit conversion needed for this specific comparison).
The "Mbps vs MB/s" conversion becomes relevant specifically when: (a) you're looking at a download manager's displayed speed (typically in MB/s or KB/s — bytes-based, matching file-size conventions) and want to relate it to your Mbps plan — or (b) you're estimating "how long will this download take" based on a file size (in MB/GB — bytes) and your connection speed (in Mbps — bits) — this estimation requires the conversion (either converting the connection speed to MB/s, or converting the file size to megabits, to get consistent units before dividing).
How to use the Data Storage Converter on sadiqbd.com
- For "is my actual download speed consistent with my plan": convert your plan's Mbps figure to MB/s (divide by 8) — compare this against your download manager's displayed MB/s (or KB/s) speed — expect the actual speed to be somewhat below the converted theoretical maximum, due to the additional factors discussed (overhead, server-side limits, Wi-Fi, "up to" framing)
- For "how long will this download take": convert either the file size (bytes) to bits, or your connection speed (bits) to bytes — so that file-size-divided-by-speed uses consistent units — then divide to estimate download time (recognizing this as a theoretical-maximum-based estimate, likely somewhat optimistic vs actual experienced time)
- For upload-speed-related questions: double-check whether your plan's upload speed (often significantly lower than download) is the relevant figure for your specific scenario (uploading files, video calls requiring upload bandwidth, etc.)
Frequently Asked Questions
Why do some download managers show speed in "KB/s" or "MB/s" while others show "Kbps" or "Mbps"? This inconsistency across different software is, unfortunately, real — some applications follow the "bytes-based, matching-file-size-conventions" approach (KB/s, MB/s); others (particularly some network-monitoring/diagnostic tools, which may be more oriented toward "network"-style bits-based units, matching ISP-advertised speeds) use bits-based units (Kbps, Mbps). Checking which convention a specific application uses (often, unfortunately, requires checking documentation, or inferring from context — e.g., if a displayed "speed" seems implausibly high/low compared to expectations, checking whether it'd make "more sense" under the "other" unit-interpretation can be a practical diagnostic) is, unfortunately, necessary given the lack of a single, universal convention across all software.
Is the Data Storage Converter free? Yes — completely free, no sign-up required.
Try the Data Storage Converter free at sadiqbd.com — convert between bits, bytes, Mbps, MB/s, and all storage/bandwidth units instantly.
