Nibble to Megabit

A nibble is 4 bits, or half a byte. It encodes one hexadecimal digit (values 0–15, represented as 0–9 and A–F). Nibbles are important in BCD (binary-coded decimal) encoding, where decimal digits are packed two per byte (each digit occupying one nibble). Packed BCD is used in financial systems and legacy databases to represent decimal numbers without floating-point rounding errors.

Hexadecimal (base 16) maps perfectly to nibbles because 4 bits can represent exactly 16 values (2⁴ = 16). One byte = two nibbles = two hex digits. A byte value of 0xFF (255 in decimal) is two nibbles: F (1111) and F (1111). This mapping makes hexadecimal the natural notation for expressing binary data — programrs use hex because one hex digit always represents a fixed number of bits.

Binary-Coded Decimal (BCD) encodes each decimal digit (0–9) as a 4-bit binary value (nibble). Two decimal digits fit in one byte using "packed BCD". For example, the decimal number 47 is stored as 0100 0111 in packed BCD — each nibble holds one digit. BCD avoids the rounding errors of binary floating-point, which is why it is used in financial software, calculators, and legacy banking systems.

A nibble = 4 bits (1 hex digit). A byte = 8 bits (2 hex digits, 2 nibbles). A word = typically 16, 32, or 64 bits depending on the processor architecture (see the "word" unit for details). These are the fundamental granularities of digital data: nibble for hex/BCD, byte for text and addressing, word for native processor arithmetic.

Nibbles are rarely referenced directly in modern high-level programming but remain fundamental at the hardware level. Embedded systems, FPGA design, network packet parsing, and hardware description languages (VHDL, Verilog) regularly manipulate nibbles. The nibble is also the key concept behind hexdump utilities — the canonical way to inspect raw binary files and network packets.

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.