Megabit to Kibibyte

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.

KB (kilobyte, SI) = 1,000 bytes. KiB (kibibyte, IEC binary) = 1,024 bytes. The difference is 24 bytes (2.4%) — small individually but the source of the well-known discrepancy between storage manufacturer labels and OS-reported sizes. Storage manufacturers use KB = 1,000 bytes; operating systems traditionally used KB = 1,024 bytes (now correctly called KiB).

Linux memory management, filesystem block sizes, and page sizes are all powers of 2 (typically 4,096 bytes = 4 KiB). Using kibibytes aligns with the physical hardware structure. The GNU coreutils (df, du, ls -h) display sizes in KiB, MiB, GiB by default for consistency with how the kernel allocates memory and disk blocks — decimal kilobytes would produce fractional values for normal aligned allocations.

Most languages expose both conventions depending on the API. Java's Runtime.totalMemory() returns bytes aligned to KiB (binary), but Files.size() returns raw byte counts that file managers may display as decimal KB. Python's os.path.getsize() returns bytes — the developer chooses how to format. Go's humanize library defaults to IEC (KiB) while many JavaScript libraries default to SI (KB). This inconsistency means the same file can appear as different sizes across tools written in different languages.

A memory page is the smallest unit of memory the OS allocates from physical RAM. Most modern CPUs use 4 KiB (4,096 byte) pages; some support 2 MiB or 1 GiB "huge pages" for performance. Every memory allocation is rounded up to the nearest page boundary. This binary alignment is why computer memory sizes are always powers of 2 (4 GB, 8 GB, 16 GB RAM) rather than round decimal numbers (5 GB, 10 GB).

The 3.5-inch floppy's capacity was 1,474,560 bytes — which is neither 1.44 MB (1,440,000 bytes) nor 1.44 MiB (1,509,949 bytes). The label came from a hybrid calculation: 80 tracks × 2 sides × 18 sectors × 512 bytes = 1,474,560 bytes, then divided by 1,000 to get 1,474.56 KB, then divided by 1,024 to get "1.44 MB." This mix of decimal and binary division in the same label is one of the most famous unit blunders in computing history.