Megabyte to Nibble

A JPEG photo from a modern smartphone is typically 3–8 MB depending on resolution and compression settings. A RAW format photo from a DSLR or mirrorless camera is 20–50 MB per shot. A PNG screenshot at full HD (1920×1080) is about 1–3 MB; a compressed JPEG screenshot may be under 200 kB.

Video data usage depends heavily on quality: SD video uses roughly 700 MB per hour; HD (1080p) uses 1.5–3 GB per hour; 4K uses 7–20 GB per hour. These are byte-based measurements. In terms of bitrate: SD ≈ 1.5 Mbps, HD ≈ 5–8 Mbps, 4K ≈ 15–25 Mbps — where the "b" is bits, requiring division by 8 to convert to MB/s.

Compression algorithms like ZIP, GZIP, and ZSTD find and eliminate redundancy in data. Typical ratios vary dramatically by file type: plain text compresses to 20–30% of original size (a 10 MB log file becomes 2–3 MB); source code compresses to 25–35%; office documents (DOCX, XLSX) are already ZIP-compressed internally, so re-compressing gains little. JPEG, MP3, and H.264 video are already lossy-compressed and typically shrink by less than 5% with ZIP. A 100 MB folder of mixed files typically compresses to 40–60 MB. The key principle: compression removes statistical redundancy, so already-compressed or random data cannot be reduced further.

MB (megabyte) = 1,000,000 bytes (SI decimal). MiB (mebibyte) = 1,048,576 bytes (IEC binary). The difference is about 4.9%. Windows historically displayed storage in binary units but labelled them as "MB" — confusingly. Since Windows Vista, Microsoft has used the binary calculation consistently. macOS switched to SI decimal units in OS X 10.6 Snow Leopard (2009), matching the way hard drive manufacturers measure capacity.

Approximate data consumption per hour: web browsing = 60–100 MB, social media scrolling = 100–300 MB, music streaming (Spotify standard) = 40–50 MB, video calls (Zoom standard quality) = 300–500 MB, YouTube HD = 1,500–3,000 MB. These are rough averages and vary by content, settings, and network conditions.

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.