Hexadecimal

In almost all modern use, the letters A–F or a–f represent the values 10–15, while the numerals 0–9 are used to represent their usual values.

There is no universal convention to use lowercase or uppercase, so each is prevalent or preferred in particular environments by community standards or convention; even mixed case is often used. Seven-segment displays use mixed-case AbCdEF to make digits that can be distinguished from each other.

There is some standardization of using spaces (rather than commas or another punctuation mark) to separate hex values in a long list. For instance in the following hexdump each 8-bit byte is a 2-digit hex number, with spaces between them, while the 32-bit offset at the start is an 8-digit hex number.

00000000  57 69 6b 69 70 65 64 69  61 2c 20 74 68 65 20 66  |Wikipedia, the f|
00000010  72 65 65 20 65 6e 63 79  63 6c 6f 70 65 64 69 61  |ree encyclopedia|
00000020  20 74 68 61 74 20 61 6e  79 6f 6e 65 20 63 61 6e  | that anyone can|
00000030  20 65 64 69 74 0a                                 | edit.|

In contexts where the base is not clear, hexadecimal numbers can be ambiguous and confused with numbers expressed in other bases. There are several conventions for expressing values unambiguously. A numerical subscript (itself written in decimal) can give the base explicitly: 159₁₀ is decimal 159; 159₁₆ is hexadecimal 159, which is equal to 345₁₀. Some authors prefer a text subscript, such as 159_decimal and 159_hex, or 159_d and 159_h.

Donald Knuth introduced the use of a particular typeface to represent a particular radix in his book The TeXbook.[1] Hexadecimal representations are written there in a typewriter typeface: 5A3

In linear text systems, such as those used in most computer programming environments, a variety of methods have arisen:

• Unix (and related) shells, AT&T assembly language and likewise the C programming language (and its syntactic descendants such as C++, C#, Go, D, Java, JavaScript, Python and Windows PowerShell) use the prefix 0x for numeric constants represented in hex: 0x5A3. Character and string constants may express character codes in hexadecimal with the prefix \x followed by two hex digits: '\x1B' represents the Esc control character; "\x1B[0m\x1B[25;1H" is a string containing 11 characters with two embedded Esc characters.[2] To output an integer as hexadecimal with the printf function family, the format conversion code %X or %x is used.
• In URIs (including URLs), character codes are written as hexadecimal pairs prefixed with %: http://www.example.com/name%20with%20spaces where %20 is the code for the space (blank) character, ASCII code point 20 in hex, 32 in decimal.
• In XML and XHTML, characters can be expressed as hexadecimal numeric character references using the notation &#xcode;, for instance ’ represents the character U+2019 (the right single quotation mark). If there is no x the number is decimal (thus ’ is the same character).[3]
• In the Unicode standard, a character value is represented with U+ followed by the hex value, e.g. U+20AC is the Euro sign (€).
• Color references in HTML, CSS and X Window can be expressed with six hexadecimal digits (two each for the red, green and blue components, in that order) prefixed with #: white, for example, is represented as #FFFFFF.[4] CSS also allows 3-hexdigit abbreviations with one hexdigit per component: #FA3 abbreviates #FFAA33 (a golden orange:  ).
• In MIME (e-mail extensions) quoted-printable encoding, character codes are written as hexadecimal pairs prefixed with =: Espa=F1a is "España" (F1 is the code for ñ in the ISO/IEC 8859-1 character set).[5])
• In Intel-derived assembly languages and Modula-2,[6] hexadecimal is denoted with a suffixed H or h: FFh or 05A3H. Some implementations require a leading zero when the first hexadecimal digit character is not a decimal digit, so one would write 0FFh instead of FFh
• Other assembly languages (6502, Motorola), Pascal, Delphi, some versions of BASIC (Commodore), GameMaker Language, Godot and Forth use $ as a prefix: $5A3.
• Some assembly languages (Microchip) use the notation H'ABCD' (for ABCD₁₆). Similarly, Fortran 95 uses Z'ABCD'.
• Ada and VHDL enclose hexadecimal numerals in based "numeric quotes": 16#5A3#. For bit vector constants VHDL uses the notation x"5A3".[7]
• Verilog represents hexadecimal constants in the form 8'hFF, where 8 is the number of bits in the value and FF is the hexadecimal constant.
• The Smalltalk language uses the prefix 16r: 16r5A3
• PostScript and the Bourne shell and its derivatives denote hex with prefix 16#: 16#5A3. For PostScript, binary data (such as image pixels) can be expressed as unprefixed consecutive hexadecimal pairs: AA213FD51B3801043FBC...
• Common Lisp uses the prefixes #x and #16r. Setting the variables *read-base*[8] and *print-base*[9] to 16 can also be used to switch the reader and printer of a Common Lisp system to Hexadecimal number representation for reading and printing numbers. Thus Hexadecimal numbers can be represented without the #x or #16r prefix code, when the input or output base has been changed to 16.
• MSX BASIC,[10] QuickBASIC, FreeBASIC and Visual Basic prefix hexadecimal numbers with &H: &H5A3
• BBC BASIC and Locomotive BASIC use & for hex.[11]
• TI-89 and 92 series uses a 0h prefix: 0h5A3
• ALGOL 68 uses the prefix 16r to denote hexadecimal numbers: 16r5a3. Binary, quaternary (base-4) and octal numbers can be specified similarly.
• The most common format for hexadecimal on IBM mainframes (zSeries) and midrange computers (IBM System i) running the traditional OS's (zOS, zVSE, zVM, TPF, IBM i) is X'5A3', and is used in Assembler, PL/I, COBOL, JCL, scripts, commands and other places. This format was common on other (and now obsolete) IBM systems as well. Occasionally quotation marks were used instead of apostrophes.
• Any IPv6 address can be written as eight groups of four hexadecimal digits (sometimes called hextets), where each group is separated by a colon (:). This, for example, is a valid IPv6 address: 2001:0db8:85a3:0000:0000:8a2e:0370:7334 or abbreviated by removing zeros as 2001:db8:85a3::8a2e:370:7334 (IPv4 addresses are usually written in decimal).
• Globally unique identifiers are written as thirty-two hexadecimal digits, often in unequal hyphen-separated groupings, for example 3F2504E0-4F89-41D3-9A0C-0305E82C3301.

The use of the letters A through F to represent the digits above 9 was not universal in the early history of computers.

• During the 1950s, some installations, such as Bendix-14 favored using the digits 0 through 5 with an overline to denote the values 10–15 as 0, 1, 2, 3, 4 and 5.
• The SWAC (1950)[12] and Bendix G-15 (1956)[13][12] computers used the lowercase letters u, v, w, x, y and z for the values 10 to 15.
• The ILLIAC I (1952) computer used the uppercase letters K, S, N, J, F and L for the values 10 to 15.[14][12]
• The Librascope LGP-30 (1956) used the letters F, G, J, K, Q and W for the values 10 to 15.[15][12]
• The Honeywell Datamatic D-1000 (1957) used the lowercase letters b, c, d, e, f, and g whereas the Elbit 100 (1967) used the uppercase letters B, C, D, E, F and G for the values 10 to 15.[12]
• The Monrobot XI (1960) used the letters S, T, U, V, W and X for the values 10 to 15.[12]
• The NEC parametron computer NEAC 1103 (1960) used the letters D, G, H, J, K (and possibly V) for values 10–15.[16]
• The Pacific Data Systems 1020 (1964) used the letters L, C, A, S, M and D for the values 10 to 15.[12]
• New numeric symbols and names were introduced in the Bibi-binary notation by Boby Lapointe in 1968. This notation did not become very popular.

Bruce Alan Martin's hexadecimal notation proposal[17]

• Bruce Alan Martin of Brookhaven National Laboratory considered the choice of A–F "ridiculous". In a 1968 letter to the editor of the CACM, he proposed an entirely new set of symbols based on the bit locations, which did not gain much acceptance.[17]
• Some seven-segment display decoder chips show the random result of logic designed only to produce 0-9 correctly.

There are no traditional numerals to represent the quantities from ten to fifteen – letters are used as a substitute – and most European languages lack non-decimal names for the numerals above ten. Even though English has names for several non-decimal powers (pair for the first binary power, score for the first vigesimal power, dozen, gross and great gross for the first three duodecimal powers), no English name describes the hexadecimal powers (decimal 16, 256, 4096, 65536, ... ). Some people read hexadecimal numbers digit by digit, like a phone number, or using the NATO phonetic alphabet, the Joint Army/Navy Phonetic Alphabet, or a similar ad-hoc system. In the wake of the adoption of hexadecimal among IBM System/360 programmers, Magnuson (1968)[18] suggested a pronunciation guide that gave short names to the letters of hexadecimal – for instance, "A" was pronounced "ann", B "bet", C "chris", etc.[18] Another naming system was elaborated by Babb (2015), off a TV series as a joke.[19] Yet another naming-system has was published online by Rogers (2007)[20] that tries to make the verbal representation distinguishable in any case, even when the actual number does not contain numbers A–F. Examples are listed in the tables below.

Hexadecimal finger-counting scheme

Systems of counting on digits have been devised for both binary and hexadecimal. Arthur C. Clarke suggested using each finger as an on/off bit, allowing finger counting from zero to 1023₁₀ on ten fingers.[21] Another system for counting up to FF₁₆ (255₁₀) is illustrated on the right.

The hexadecimal system can express negative numbers the same way as in decimal: −2A to represent −42₁₀ and so on.

Hexadecimal can also be used to express the exact bit patterns used in the processor, so a sequence of hexadecimal digits may represent a signed or even a floating point value. This way, the negative number −42₁₀ can be written as FFFF FFD6 in a 32-bit CPU register (in two's-complement), as C228 0000 in a 32-bit FPU register or C045 0000 0000 0000 in a 64-bit FPU register (in the IEEE floating-point standard).

Just as decimal numbers can be represented in exponential notation, so too can hexadecimal numbers. By convention, the letter P (or p, for "power") represents times two raised to the power of, whereas E (or e) serves a similar purpose in decimal as part of the E notation. The number after the P is decimal and represents the binary exponent. Increasing the exponent by 1 multiplies by 2, not 16. 10.0p1 = 8.0p2 = 4.0p3 = 2.0p4 = 1.0p5. Usually, the number is normalized so that the leading hexadecimal digit is 1 (unless the value is exactly 0).

Example: 1.3DEp42 represents 1.3DE₁₆ × 2^42₁₀.

Hexadecimal exponential notation is required by the IEEE 754-2008 binary floating-point standard. This notation can be used for floating-point literals in the C99 edition of the C programming language.[22] Using the %a or %A conversion specifiers, this notation can be produced by implementations of the printf family of functions following the C99 specification[23] and Single Unix Specification (IEEE Std 1003.1) POSIX standard.[24]

Most computers manipulate binary data, but it is difficult for humans to work with a large number of digits for even a relatively small binary number. Although most humans are familiar with the base 10 system, it is much easier to map binary to hexadecimal than to decimal because each hexadecimal digit maps to a whole number of bits (4₁₀). This example converts 1111₂ to base ten. Since each position in a binary numeral can contain either a 1 or a 0, its value may be easily determined by its position from the right:

• 0001₂ = 1₁₀
• 0010₂ = 2₁₀
• 0100₂ = 4₁₀
• 1000₂ = 8₁₀

Therefore:

With little practice, mapping 1111₂ to F₁₆ in one step becomes easy: see table in written representation. The advantage of using hexadecimal rather than decimal increases rapidly with the size of the number. When the number becomes large, conversion to decimal is very tedious. However, when mapping to hexadecimal, it is trivial to regard the binary string as 4-digit groups and map each to a single hexadecimal digit.

This example shows the conversion of a binary number to decimal, mapping each digit to the decimal value, and adding the results.

Compare this to the conversion to hexadecimal, where each group of four digits can be considered independently, and converted directly:

The conversion from hexadecimal to binary is equally direct.

Although quaternary (base 4) is little used, it can easily be converted to and from hexadecimal or binary. Each hexadecimal digit corresponds to a pair of quaternary digits and each quaternary digit corresponds to a pair of binary digits. In the above example 5 E B 5 2₁₆ = 11 32 23 11 02₄.

The octal (base 8) system can also be converted with relative ease, although not quite as trivially as with bases 2 and 4. Each octal digit corresponds to three binary digits, rather than four. Therefore we can convert between octal and hexadecimal via an intermediate conversion to binary followed by regrouping the binary digits in groups of either three or four.

As with all bases there is a simple algorithm for converting a representation of a number to hexadecimal by doing integer division and remainder operations in the source base. In theory, this is possible from any base, but for most humans only decimal and for most computers only binary (which can be converted by far more efficient methods) can be easily handled with this method.

Let d be the number to represent in hexadecimal, and the series h_ih_i−1...h₂h₁ be the hexadecimal digits representing the number.

1. i ← 1
2. h_i ← d mod 16
3. d ← (d − h_i) / 16
4. If d = 0 (return series h_i) else increment i and go to step 2

"16" may be replaced with any other base that may be desired.

The following is a JavaScript implementation of the above algorithm for converting any number to a hexadecimal in String representation. Its purpose is to illustrate the above algorithm. To work with data seriously, however, it is much more advisable to work with bitwise operators.

function toHex(d) {
  var r = d % 16;
  if (d - r == 0) {
    return toChar(r);
  }
  return toHex((d - r) / 16) + toChar(r);
}

function toChar(n) {
  const alpha = "0123456789ABCDEF";
  return alpha.charAt(n);
}

A hexadecimal multiplication table

It is also possible to make the conversion by assigning each place in the source base the hexadecimal representation of its place value — before carrying out multiplication and addition to get the final representation. For example, to convert the number B3AD to decimal, one can split the hexadecimal number into its digits: B (11₁₀), 3 (3₁₀), A (10₁₀) and D (13₁₀), and then get the final result by multiplying each decimal representation by 16^p (p being the corresponding hex digit position, counting from right to left, beginning with 0). In this case, we have that:

B3AD = (11 × 16³) + (3 × 16²) + (10 × 16¹) + (13 × 16⁰)

which is 45997 in base 10.

Most modern computer systems with graphical user interfaces provide a built-in calculator utility capable of performing conversions between the various radices, and in most cases would include the hexadecimal as well.

In Microsoft Windows, the Calculator utility can be set to Scientific mode (called Programmer mode in some versions), which allows conversions between radix 16 (hexadecimal), 10 (decimal), 8 (octal) and 2 (binary), the bases most commonly used by programmers. In Scientific Mode, the on-screen numeric keypad includes the hexadecimal digits A through F, which are active when "Hex" is selected. In hex mode, however, the Windows Calculator supports only integers.

As with other numeral systems, the hexadecimal system can be used to represent rational numbers, although repeating expansions are common since sixteen (10₁₆) has only a single prime factor; two.

For any base, 0.1 (or "1/10") is always equivalent to one divided by the representation of that base value in its own number system. Thus, whether dividing one by two for binary or dividing one by sixteen for hexadecimal, both of these fractions are written as 0.1. Because the radix 16 is a perfect square (4²), fractions expressed in hexadecimal have an odd period much more often than decimal ones, and there are no cyclic numbers (other than trivial single digits). Recurring digits are exhibited when the denominator in lowest terms has a prime factor not found in the radix; thus, when using hexadecimal notation, all fractions with denominators that are not a power of two result in an infinite string of recurring digits (such as thirds and fifths). This makes hexadecimal (and binary) less convenient than decimal for representing rational numbers since a larger proportion lie outside its range of finite representation.

All rational numbers finitely representable in hexadecimal are also finitely representable in decimal, duodecimal and sexagesimal: that is, any hexadecimal number with a finite number of digits also has a finite number of digits when expressed in those other bases. Conversely, only a fraction of those finitely representable in the latter bases are finitely representable in hexadecimal. For example, decimal 0.1 corresponds to the infinite recurring representation 0.19 in hexadecimal. However, hexadecimal is more efficient than duodecimal and sexagesimal for representing fractions with powers of two in the denominator. For example, 0.0625₁₀ (one-sixteenth) is equivalent to 0.1₁₆, 0.09₁₂, and 0;3,45₆₀.

The table below gives the expansions of some common irrational numbers in decimal and hexadecimal.

Powers of two have very simple expansions in hexadecimal. The first sixteen powers of two are shown below.

The word hexadecimal is composed of hexa-, derived from the Greek ἕξ (hex) for six, and -decimal, derived from the Latin for tenth. Webster's Third New International online derives hexadecimal as an alteration of the all-Latin sexadecimal (which appears in the earlier Bendix documentation). The earliest date attested for hexadecimal in Merriam-Webster Collegiate online is 1954, placing it safely in the category of international scientific vocabulary (ISV). It is common in ISV to mix Greek and Latin combining forms freely. The word sexagesimal (for base 60) retains the Latin prefix. Donald Knuth has pointed out that the etymologically correct term is senidenary (or possibly, sedenary), from the Latin term for grouped by 16. (The terms binary, ternary and quaternary are from the same Latin construction, and the etymologically correct terms for decimal and octal arithmetic are denary and octonary, respectively.)[26] Alfred B. Taylor used senidenary in his mid-1800s work on alternative number bases, although he rejected base 16 because of its "incommodious number of digits".[27][28] Schwartzman notes that the expected form from usual Latin phrasing would be sexadecimal, but computer hackers would be tempted to shorten that word to sex.[29] The etymologically proper Greek term would be hexadecadic / ἑξαδεκαδικός / hexadekadikós (although in Modern Greek, decahexadic / δεκαεξαδικός / dekaexadikos is more commonly used).

The traditional Chinese units of measurement were base-16. For example, one jīn (斤) in the old system equals sixteen taels. The suanpan (Chinese abacus) can be used to perform hexadecimal calculations such as additions and subtractions.[30]

As with the duodecimal system, there have been occasional attempts to promote hexadecimal as the preferred numeral system. These attempts often propose specific pronunciation and symbols for the individual numerals.[31] Some proposals unify standard measures so that they are multiples of 16.[32][33][34]

An example of unified standard measures is hexadecimal time, which subdivides a day by 16 so that there are 16 "hexhours" in a day.[34]