A common complaint sounds like this: the internet plan promises 100 Mbps, yet downloads never climb past about 12 megabytes per second, so something must be broken. Nothing is broken. The gap comes from two units that look almost identical on the page, megabits and megabytes, which differ by a factor of eight. Providers measure connection speed in one, your download manager reports progress in the other, and confusing the two makes a perfectly healthy line look like it is falling short. Sorting out which is which clears up most of the worry people have about their speeds.
What a bit and a byte each measure
A bit is the smallest unit of digital information, a single one or zero. A byte is a group of eight bits, and it is the unit files are measured in, because one byte is roughly the space of a single character of text. The lowercase b stands for bits, the uppercase B for bytes, so Mb means megabits and MB means megabytes. That one letter is the whole source of the trouble. A megabyte contains eight megabits, so any figure given in megabits is eight times larger than the same quantity written in megabytes, even though the two abbreviations look nearly the same at a glance.
Why internet plans are quoted in bits
Network speed has been measured in bits per second since the earliest data links, because data travels along a wire or fibre as a stream of individual bits, one after another. Quoting the rate in bits per second describes what the line literally does. It also yields a larger, more appealing number: 100 megabits per second reads as faster than 12.5 megabytes per second, though the two are the same speed. Fixed and mobile providers alike follow the convention, so plan comparisons stay in bits whether you are reading about home broadband or a phone contract, a parallel our coverage of mobile data against fixed broadband follows. Files and storage, by contrast, are counted in bytes, which is why the units switch the moment a download begins.
Turning a plan’s Mbps into real download speed
To convert an advertised speed into the download rate you will see, divide the megabits by eight. A 100 Mbps plan can move at most about 12.5 megabytes per second; a 25 Mbps plan tops out near 3.1 megabytes per second. The table lists a few common tiers and how long each would take, in ideal conditions, to fetch a 5 GB file.
| Plan speed | Peak download rate | Time for a 5 GB file |
|---|---|---|
| 25 Mbps | About 3.1 MB/s | Roughly 27 minutes |
| 100 Mbps | About 12.5 MB/s | Roughly 7 minutes |
| 500 Mbps | About 62.5 MB/s | Roughly 80 seconds |
| 1000 Mbps | About 125 MB/s | Roughly 40 seconds |
These figures are ceilings, the fastest the arithmetic allows, and real transfers usually settle a little below them.
Where dividing by eight trips people up
The mistake is subtle because both numbers are correct; they simply measure different things. Someone sees 100 in the plan and 12 in the download and concludes they are getting a tenth of what they pay for, when 12 megabytes per second is precisely what 100 megabits per second delivers. The reverse error happens too, when a download tool reports in megabits and appears eight times faster than expected. The habit that avoids both is to check the units, capital B or lowercase b, before comparing any two speed figures. Even after the conversion, the felt speed of a connection rests on more than raw throughput, since how quickly a page or request answers is a matter of latency, the point the breakdown of how latency shapes a connection develops.
Why a fast connection can still feel slow
A large download number does not guarantee a smooth experience, because throughput is only one property of a link. A connection can carry plenty of bandwidth yet still stutter during a video call or a game if its packets arrive late or unevenly, or if some go missing and have to be sent again. Those qualities, reported as ping, jitter, and packet loss, describe the consistency of a connection rather than its raw capacity, and they often matter more for responsiveness than the headline speed, as our piece on ping, jitter, and packet loss sets out. A fast plan with poor consistency can feel worse than a slower plan that delivers its packets steadily.
When browsing drags but downloads are fine
There is a particular case where downloads run at full speed yet web pages are slow to appear. The delay there is usually not bandwidth at all, but the time spent looking up each site’s address before the browser can fetch anything. That lookup, handled by the domain name system, happens before the first byte of a page arrives, and a slow or distant resolver adds a visible pause to every new site, which our guide to the way name lookups shape page loads examines. Recognising that loading a page and downloading a file stress different parts of the connection keeps you from blaming your megabits for a problem that lives elsewhere.
Making sense of the numbers
The bits-and-bytes confusion is a units problem, not a performance problem. A plan sold in megabits per second will always deliver about an eighth as many megabytes per second, and once you expect that, a download running at 12 megabytes per second on a 100 megabit plan reads as correct rather than disappointing. The single letter, lowercase b or capital B, carries the entire factor of eight.
It helps to separate the two questions a connection raises. One is how much data it can move, answered by the megabit figure and its megabyte equivalent. The other is how quickly and steadily it responds, answered by latency and the evenness of its packets. A plan can be strong on one and weak on the other, so the headline speed is a starting point, not the full account. Reading the units correctly, and knowing what they do and do not describe, is enough to judge whether a connection is genuinely underperforming or simply being measured in a different currency.
Answers to common questions
Why is my download speed one-eighth of my plan’s number?
Because your plan is measured in megabits and your download is measured in megabytes, and one byte is eight bits. A 100 megabit per second plan moves about 12.5 megabytes per second at best, so a download showing roughly 12 MB/s is performing exactly as it should. Divide the plan’s megabit figure by eight to find the megabyte per second rate you can expect to see.
What is the difference between Mbps and MBps?
Mbps means megabits per second, with a lowercase b, and MBps means megabytes per second, with a capital B. They differ by a factor of eight, since a byte contains eight bits. Providers quote connection speed in Mbps, while file sizes and download tools use megabytes, so MBps is always about one-eighth of the Mbps figure for the same line. The capital letter is the clue.
Is a 100 Mbps connection fast?
For most households it is comfortable. A 100 Mbps line delivers about 12.5 megabytes per second, enough for several simultaneous high-definition streams, video calls, and large downloads that finish in minutes. Whether it feels fast also depends on latency and consistency, not throughput alone, so a 100 Mbps connection with low latency often feels quicker than a higher-bandwidth one that responds slowly. For typical use, it is a solid speed.
