/hek-sə-ˈdes-məl/

noun — “base sixteen, where digits stop behaving and letters get promoted.”

Hexadecimal is a positional number system with base 16, widely used in computing as a compact representation of binary data. Each digit represents four bits, allowing long binary sequences to be expressed in a shorter, more readable form using symbols 0–9 and A–F.

// binary → hexadecimal

1111 0001 1010 1100
= F1AC

The term itself was not always stable. It was coined in the early 1960s as a replacement for the earlier sexadecimal, a form that was considered too informal, slightly suggestive, and generally unsuitable for corporate documentation—especially in environments as conservative as early IBM engineering culture. The more neutral hexa- prefix (from Greek) eventually won out and propagated through the rest of the industry.

Like many computing terms, however, hexadecimal is not etymologically “pure” in a strict linguistic sense. It sits inside a larger ecosystem of number-base naming conventions that are historically inconsistent, partially Latin, partially Greek, and occasionally just improvised until something stuck.

If one uses binary as a conceptual baseline, then:

  • Decimal (base 10) comes from Latin decem, but more precisely aligns with ordinal-derived structure rather than strict distributive numbering.
  • The more linguistically consistent form would arguably be denary, derived from Latin deni (“ten at a time”), a distributive number system.
  • Following that logic, base 16 might have been more properly described as something like sendenary, though this never caught on outside theoretical discussions.

The situation becomes more tangled when comparing other bases:

  • Decimal is often treated as standard, though a parallel form like sextidecimal would be more structurally consistent if one were following strict morphological symmetry.
  • Octal (base 8) is similarly irregular; a more systematic form would be octaval (parallel to decimal) or octonary (parallel to binary).

Even the naming conventions begin to wobble further when extended beyond familiar bases. If a base-3 system were ever standardized in mainstream computing, it would immediately confront an unusual linguistic problem: two competing “correct” forms already exist.

Both:

ternary
trinary

have legitimate etymological arguments, depending on whether one prioritizes Greek derivation patterns or Latin-style consistency. Unlike hexadecimal, where history eventually converged on a single dominant form, ternary systems would inherit ambiguity from the start.

In practice, none of this linguistic inconsistency affects computation. Machines do not care whether base-16 is called hexadecimal, sexadecimal, or that weird thing with A–F digits. Humans, however, prefer names that feel stable enough to write in manuals without causing raised eyebrows.

Thus hexadecimal survives as a compromise: linguistically imperfect, historically patched together, but structurally elegant and deeply useful. It compresses binary into readable form, bridges human and machine representation, and quietly ignores its own messy etymology.

See hex, binary, decimal, octal, Bit