Word to Nibble

A word's size depends on the CPU architecture. In x86/x64 (Intel/AMD) documentation: word = 16 bits, DWORD = 32 bits, QWORD = 64 bits. In ARM 32-bit: word = 32 bits. In most modern 64-bit systems (excluding x86 documentation): word = 64 bits. When reading technical documentation, always check the architecture's definition, as "word" is not a universal fixed size.

In Windows API documentation and x86 architecture, a DWORD (Double Word) = 32 bits = 4 bytes, capable of holding values 0–4,294,967,295 (unsigned) or -2,147,483,648 to 2,147,483,647 (signed). DWORD is the most common fixed-width integer type in the Windows API, used for flags, handles, and return codes. The equivalent in modern C/C++ is uint32_t (unsigned) or int32_t (signed).

A CPU's word size determines: (1) the maximum addressable memory — a 32-bit CPU addresses up to 4 GiB (2³² bytes); a 64-bit CPU addresses up to 16 EiB (2⁶⁴ bytes); (2) the precision of integer arithmetic — a 64-bit word handles numbers up to ~18.4 × 10¹⁸ in a single instruction; (3) performance — operations on data smaller than the word size may require extra sign-extension instructions on some architectures.

Modern x86-64 CPUs (Intel Core, AMD Ryzen) have 64-bit general-purpose registers, so their native word size is 64 bits for most operations. However, x86 documentation maintains the legacy definition: "word" = 16 bits, DWORD = 32 bits, QWORD = 64 bits. This creates a confusing terminology mismatch between the architectural naming convention and the physical register size.

Memory alignment means storing data at addresses that are multiples of the data's size. A 32-bit word should be stored at an address divisible by 4 (bytes); a 64-bit word at an address divisible by 8. Misaligned access is either forbidden (causes a CPU fault) or penalised (requires two memory reads instead of one). Compilers automatically align variables; manual struct packing can create misalignment that causes subtle performance issues or crashes on strict architectures.

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.