🔢 Bits vs Bytes Converter

Why Mbps and MBps Are Not the Same Thing — And Why It Costs You Real Money

The day your ISP advertised "100 Mbps broadband" and your download manager showed a maximum of 12.5 MB/s, you probably thought something was wrong. Nothing was. You simply ran into one of the most persistently confusing unit mismatches in all of computing — the difference between a bit and a byte, multiplied across the dizzying zoo of SI and IEC prefixes. Once you understand the underlying logic, conversions that used to feel like guesswork become instantly obvious.

The Foundation: Bits and Bytes

A bit is the smallest unit of digital information — a single binary digit, either 0 or 1. A byte is a group of exactly 8 bits. That relationship — 1 byte = 8 bits — is the only constant you need to carry in your head. Everything else is multiplication.

The confusion enters when prefixes get added. In the physical sciences, "mega" means exactly one million (10⁶). In early computing, though, engineers grabbed the same word to mean 1,048,576 (2²⁰), because binary hardware made powers of two natural. For decades both meanings coexisted under the same symbol. The result: when someone says "megabyte," they might mean 1,000,000 bytes or 1,048,576 bytes depending on the context, and the difference between those two numbers is about 4.9 percent — not trivial when you're buying a 2 TB drive.

The SI System: Clean Powers of Ten

The International System of Units (SI) resolved this by reserving prefixes strictly for powers of ten:

• kilo (k) = 10³ = 1,000
• mega (M) = 10⁶ = 1,000,000
• giga (G) = 10⁹ = 1,000,000,000
• tera (T) = 10¹² = 1,000,000,000,000
• peta (P) = 10¹⁵

Network speeds are almost universally quoted in SI units. Your "100 Mbps" connection carries 100,000,000 bits every second — not 104,857,600. Hard drive manufacturers also use SI when labeling capacity, which is why a "500 GB" drive shows up as roughly 465 GiB in your operating system's file manager. They're both right; they're using different definitions.

The IEC System: Honest Binary Prefixes

In 1998, the International Electrotechnical Commission introduced a separate prefix family specifically for binary multiples, with the suffix "-bi" and the symbol modified to include an "i":

• kibi (Ki) = 2¹⁰ = 1,024
• mebi (Mi) = 2²⁰ = 1,048,576
• gibi (Gi) = 2³⁰ = 1,073,741,824
• tebi (Ti) = 2⁴⁰ = 1,099,511,627,776
• pebi (Pi) = 2⁵⁰

So 1 GiB is always 1,073,741,824 bytes, no ambiguity. Linux distributions and modern Windows have largely adopted these IEC labels in their system tools, which is why you see "GiB" in disk management utilities but "GB" on the box the drive came in.

The Mbps vs MBps Problem, Solved Once and For All

This is the single most common conversion people actually need. The lowercase "b" in Mbps stands for bits; the uppercase "B" in MBps stands for bytes. To convert a speed from megabits per second to megabytes per second, divide by 8. Always.

100 Mbps ÷ 8 = 12.5 MBps

That 12.5 MB/s is the absolute ceiling on how fast files can download over your 100 Mbps connection — and in practice you'll see less due to protocol overhead, TCP/IP headers, and congestion. If your download manager shows 10 MB/s on a 100 Mbps line, you're actually getting a great real-world result. Understanding this stops you from filing unnecessary support tickets.

The same logic applies at every prefix level. A 1 Gbps gigabit Ethernet port maxes out at 125 MB/s of actual file transfer speed. A 10 Gbps server NIC can push 1.25 GB/s. These aren't approximations — they're exact conversions using the SI decimal definition that networking universally uses.

Step-by-Step: How to Use the Converter

Step 1: Type your value in the "Value" field. Decimals are fine — 1.5, 0.25, 1000, all work.

Step 2: Select the unit you're starting from in the dropdown. The list is organized into three groups: base units (bit, byte), SI decimal units (kilobit through petabyte), and IEC binary units (kibibit through pebibyte). Pay attention to capitalization in the label — "Mb" is megabits, "MB" is megabytes.

Step 3: Click Convert (or press Enter). The tool calculates your input's total bit count as an intermediate value, then divides by each output unit's bit-factor to produce all the equivalents simultaneously. You get a complete table across all 22 units at once.

Try converting 1 GiB and notice that it equals approximately 1.074 GB (gigabytes, SI). That 7.4% difference is exactly why a manufacturer can call a drive "1 TB" while your OS reports "931 GiB" — and both answers are technically correct.

Real-World Scenarios Where This Matters

Streaming video: Netflix's 4K stream uses about 25 Mbps. That's 3.125 MB/s — so even a 25 Mbps connection can sustain it, barely. Add two people watching HD at 8 Mbps each and you've consumed 21 Mbps of your link.

Cloud backup: If you have 500 GB of photos to upload and your upload speed is 20 Mbps (= 2.5 MB/s), the minimum transfer time is 500,000 MB ÷ 2.5 MB/s = 200,000 seconds, roughly 55 hours. This calculation explains why cloud backup software stretches over days.

Storage purchases: When a NAS advertises "4 TB raw capacity," expect roughly 3.64 TiB visible in your file system. Multiply 4 × 10¹² bytes ÷ 2⁴⁰ ≈ 3.637 TiB. RAID overhead on top of that cuts usable space further.

RAM specs: Memory modules are always sized in binary — 8 GiB, 16 GiB, 32 GiB — because RAM addressing is inherently binary. Network adapters are rated in SI decimal Mbps/Gbps because communication standards define bit rates in powers of ten. Mixing these contexts without converting is how bugs and miscommunications happen in data center planning.

A Note on Bits Per Second vs Bits

This converter works on quantities (bits, bytes, kilobytes, etc.), not rates (bits per second). To convert a rate, just convert the numeric part — the "per second" carries through unchanged. 100 Mbps converts to 12.5 MBps because 100 megabits converts to 12.5 megabytes, and the "/s" is the same on both sides.

Network throughput, storage interface speeds (SATA at 600 MB/s, NVMe at 7 GB/s), and wireless standards (Wi-Fi 6 at 9.6 Gbps theoretical) all use this same structure. Once you've internalized the bit-to-byte ratio and the SI-vs-IEC distinction, you can cross-compare any spec sheet in seconds.

The persistent confusion around these units has real financial consequences — ISPs rely on consumers not knowing that 100 Mbps doesn't mean 100 megabytes per second, and storage vendors lean on the SI/IEC gap to make drives look larger than they appear in the OS. Knowing your conversions puts you on equal footing with the spec sheets.