Megabit to Mebibit

Divide Mbps by 8 to get megabytes per second (MB/s). A 100 Mbps connection = 12.5 MB/s. A 1 Gbps connection = 125 MB/s. This conversion is essential when comparing advertised internet speeds (always in Mbps) to actual file download speeds (shown in MB/s by browsers and download managers).

Netflix recommends 25 Mbps for 4K Ultra HD. Disney+ and Apple TV+ recommend 25 Mbps; YouTube recommends 20 Mbps for 4K. These are per-stream figures — a household streaming two 4K sources simultaneously needs roughly 50 Mbps of reliable throughput, plus headroom for other devices.

ISP speed ratings are theoretical maximums under ideal conditions. Real-world factors include network congestion, router quality, Wi-Fi interference, the server's upload speed, and protocol overhead. Additionally, browsers and download managers report speeds in MB/s (bytes), which is 8× smaller than the Mbps figure — a 100 Mbps plan showing 11 MB/s in a browser is performing normally.

One gigabit equals 1,000 megabits (SI decimal system). Gigabit broadband (1 Gbps) = 1,000 Mbps = 125 MB/s theoretical download speed. In the binary IEC system, one gibibit = 1,024 mebibits — but for internet speeds the SI decimal values are always used.

Fiber-to-the-home (FTTH) delivers symmetric speeds of 100–10,000 Mbps with consistent performance regardless of distance from the exchange. Cable (DOCSIS 3.1) offers 100–1,200 Mbps download but typically 10–50 Mbps upload, and throughput degrades during neighborhood peak hours due to shared bandwidth. DSL (VDSL2) maxes out at 50–100 Mbps download and drops sharply beyond 500 meters from the DSLAM cabinet. In practice, most cable users see 60–80% of advertised speeds; DSL users at distance may see under 50%. Fiber is the only technology that reliably delivers its rated megabit throughput.

A megabit (Mb) = 1,000,000 bits (SI decimal). A mebibit (Mibit) = 1,048,576 bits (IEC binary = 2²⁰ bits). The mebibit is 4.857% larger. Network speeds use megabits (Mb); embedded memory and flash storage specifications use mebibits when binary precision is required.

Mebibit appears primarily in microcontroller and microprocessor datasheets (e.g. "2 Mibit flash memory"), FPGA configuration file sizes, and some wireless protocol standards (802.11 frame size limits, Bluetooth payload specifications). It is rarely seen in consumer-facing applications but is common in embedded systems engineering documentation.

Yes. In 2007, a class-action settlement required Western Digital to pay $2.1 million because their hard drives advertised capacity in decimal megabits/gigabits while operating systems reported binary values — making drives appear ~7% smaller than labeled. Similar suits hit Seagate and Samsung. These lawsuits accelerated industry adoption of IEC prefixes and pushed Apple (2009) and later Windows (2021) to clarify their capacity labeling.

SPI flash chips are addressed at the bit level during serial communication — the programr shifts data in one bit at a time over the SPI bus. Datasheets specify capacity in mebibits (e.g. W25Q16 = 16 Mibit = 2 MiB) because the serial interface operates on bits, not bytes. Calculating transfer time requires bit-level math: reading a full 16 Mibit chip at 80 MHz SPI clock takes about 0.2 seconds.

Flash memory chips organise storage in binary-aligned blocks (sectors, pages) whose sizes are powers of 2. Specifying capacity in mebibits (1,048,576 bits per Mibit) maps precisely to the physical organisation of the memory array. Using decimal megabits would result in non-integer block counts, making datasheet specifications harder to verify against hardware design.