Hex Converter

Hexadecimal strikes a practical balance: each hex digit maps cleanly onto exactly four binary digits, so converting between binary and hex is mechanical and error-free by hand, while hex strings stay far shorter and more readable than the equivalent binary string. That's why memory addresses, color codes, and hashes are conventionally shown in hex rather than binary.

It's a notational convention, used in most programming languages, that marks the number following it as hexadecimal rather than decimal -- without it, a value like FF could be ambiguous or simply wouldn't parse as a number at all in code. The prefix itself isn't part of the numeric value; 0xFF and FF represent the same quantity.

Exactly four bits, since 16 (the base of hex) is 2 to the fourth power. That clean relationship is why a full byte (8 bits) always converts to exactly two hex digits, which is part of why hexadecimal became the standard shorthand for binary data in low-level programming.

Its most common surviving use is Unix and Linux file permission notation, where a mode like 755 encodes read/write/execute permissions for owner, group, and others as three octal digits. Outside of that context, hexadecimal has largely replaced octal as the preferred compact representation for binary data.