In and , the hexadecimal (also base 16 or hex) numeral system is a that represents numbers using a (base) of 16. Unlike the system representing numbers using 10 symbols, hexadecimal uses 16 distinct symbols, most often the symbols "0"–"9" to represent values 0 to 9, and "A"–"F" (or alternatively "a"–"f") to represent values from 10 to 15.
Hexadecimal numerals are widely used by computer system designers and programmers because they provide a human-friendly representation of values. Each hexadecimal digit represents four s (binary digits), also known as a (or nybble). For example, an 8-bit can have values ranging from 00000000 to 11111111 in binary form, which can be conveniently represented as 00 to FF in hexadecimal.
In mathematics, a subscript is typically used to specify the base. For example, the decimal value would be expressed in hexadecimal as . In programming, a number of notations are used to denote hexadecimal numbers, usually involving a prefix. The prefix

00000000 57 69 6b 69 70 65 64 69 61 2c 20 74 68 65 20 66
00000010 72 65 65 20 65 6e 63 79 63 6c 6f 70 65 64 69 61
00000020 20 74 68 61 74 20 61 6e 79 6f 6e 65 20 63 61 6e
00000030 20 65 64 69 74 0a

_{10} is decimal 159; 159_{16} is hexadecimal 159, which is equal to 345_{10}. Some authors prefer a text subscript, such as 159_{decimal} and 159_{hex}, or 159_{d} and 159_{h}.
introduced the use of a particular typeface to represent a particular radix in his book ''The TeXbook''. Hexadecimal representations are written there in a :
In linear text systems, such as those used in most computer programming environments, a variety of methods have arisen:
* (and related) shells, assembly language and likewise the (and its syntactic descendants such as , , , , , , and ) use the prefix _{16}). Similarly, uses Z'ABCD'.
* and enclose hexadecimal numerals in based "numeric quotes":

_{10} on ten fingers. Another system for counting up to FF_{16} (255_{10}) is illustrated on the right.

_{10} and so on.
Hexadecimal can also be used to express the exact bit patterns used in the , so a sequence of hexadecimal digits may represent a or even a value. This way, the negative number −42_{10} can be written as FFFF FFD6 in a 32-bit (in ), as C228 0000 in a 32-bit register or C045 0000 0000 0000 in a 64-bit FPU register (in the ).

_{10}).
This example converts 1111_{2} to base ten. Since each 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_{2} = 1_{10}
* 0010_{2} = 2_{10}
* 0100_{2} = 4_{10}
* 1000_{2} = 8_{10}
Therefore:
With little practice, mapping 1111_{2} to F_{16} in one step becomes easy: see table in . 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.

_{16} = 11 32 23 11 02_{4}.
The (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.

_{i}h_{i−1}...h_{2}h_{1} be the hexadecimal digits representing the number.
# i ← 1
# h_{i} ← d mod 16
# d ← (d − h_{i}) / 16
# 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 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 .
function toHex(d)
function toChar(n)

_{10}), 3 (3_{10}), A (10_{10}) and D (13_{10}), 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:
which is 45997 in base 10.

_{16}) 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 or dividing one by sixteen for hexadecimal, both of these fractions are written as ^{2}), fractions expressed in hexadecimal have an odd period much more often than decimal ones, and there are no s (other than trivial single digits). Recurring digits are exhibited when the denominator in lowest terms has a not found in the radix; thus, when using hexadecimal notation, all fractions with denominators that are not a result in an infinite string of recurring digits (such as thirds and fifths). This makes hexadecimal (and binary) less convenient than 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, and : 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.1 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_{10} (one-sixteenth) is equivalent to 0.1_{16}, 0.09_{12}, and 0;3,45_{60}.

IBM System/360 FORTRAN IV Language

(1966), p. 13.
As noted above, alternative notations were used by (1960) and The Pacific Data Systems 1020 (1964). The standard adopted by IBM seems to have become widely adopted by 1968, when Bruce Alan Martin
in his letter to the editor of the complains that
:"With the ridiculous choice of letters A, B, C, D, E, F as hexadecimal number symbols adding to already troublesome problems of distinguishing octal (or hex) numbers from decimal numbers (or variable names), the time is overripe for reconsideration of our number symbols. This should have been done before poor choices gelled into a de facto standard!"
Martin's argument was that use of numerals 0 to 9 in nondecimal numbers "imply to us a base-ten place-value scheme":
"Why not use entirely new symbols (and names) for the seven or fifteen nonzero digits needed in octal or hex. Even use of the letters A through P would be an improvement, but entirely new symbols could reflect the binary nature of the system".

`0x`

is used in which would denote this value as `0x`

.
Hexadecimal is used in the transfer encoding Base16, in which each byte of the is broken into two 4-bit values and represented by two hexadecimal digits.
Representation

Written representation

In most current use cases the letters A–F or a–f represent the values 10–15, while the 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 used. s 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 each 8-bit is a 2-digit hex number, with spaces between them, while the 32-bit offset at the start is an 8-digit hex number.Distinguishing from decimal

In contexts where the 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`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 control character; `"\x1B[0m\x1B[25;1H"`

is a string containing 11 characters with two embedded Esc characters. To output an integer as hexadecimal with the function family, the format conversion code `%X`

or `%x`

is used.
* In s (including s), are written as hexadecimal pairs prefixed with `%`

: http://www.example.com/name%20with%20spaces

where `%20`

is the code for the character, code point 20 in hex, 32 in decimal.
* In and , characters can be expressed as hexadecimal s using the notation `&#x''code'';`

, for instance `’`

represents the character U+2019 (the right single quotation mark). If there is no the number is decimal (thus `’`

is the same character).
* In the standard, a character value is represented with `U+`

followed by the hex value, e.g. `U+20AC`

is the (€).
* in HTML, and 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`

. CSS also allows 3-hexdigit abbreviations with one hexdigit per component: #FA3 abbreviates #FFAA33 (a golden orange: ).
* In (e-mail extensions) 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).)
* In Intel-derived s and Modula-2, hexadecimal is denoted with a suffixed or : `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`

. Some other implementations (such as NASM) allow C-style numbers (`0x42`

).
* Other assembly languages (, ), , , some versions of (), , and use `$`

as a prefix: `$5A3`

.
* Some assembly languages (Microchip) use the notation `H'ABCD'`

(for ABCD`16#5A3#`

. For bit vector constants uses the notation `x"5A3"`

.
* 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 language uses the prefix `16r`

: `16r5A3`

* and the and its derivatives denote hex with prefix `16#`

: `16#5A3`

. For PostScript, binary data (such as image s) can be expressed as unprefixed consecutive hexadecimal pairs: `AA213FD51B3801043FBC`

...
* uses the prefixes `#x`

and `#16r`

. Setting the variables *read-base* and *print-base* 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.
* , , and prefix hexadecimal numbers with `&H`

: `&H5A3`

* and use `&`

for hex.
* and 92 series uses a `0h`

prefix: `0h5A3`

* 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 () and midrange computers () running the traditional OS's (, , , , ) is `X'5A3'`

, and is used in Assembler, , , , 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 can be written as eight groups of four hexadecimal digits (sometimes called s), where each group is separated by a colon (`:`

). This, for example, is a valid IPv6 address: or abbreviated by removing zeros as (es are usually written in decimal).
* s are written as thirty-two hexadecimal digits, often in unequal hyphen-separated groupings, for example .
Other symbols for 10–15 and mostly different symbol sets

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 to denote the values 10–15 as , , , , and . * The (1950) and (1956) computers used the lowercase letters ''u'', ''v'', ''w'', ''x'', ''y'' and ''z'' for the values 10 to 15. * The and (1952) computers (and some derived designs, e.g. ) used the uppercase letters ''K'', ''S'', ''N'', ''J'', ''F'' and ''L'' for the values 10 to 15. * The Librascope (1956) used the letters ''F'', ''G'', ''J'', ''K'', ''Q'' and ''W'' for the values 10 to 15. * On the (1956) computer, hexadecimal numbers were written as letters ''O'' for zero, ''A'' to ''N'' and ''P'' for 1 to 15. Many machine instructions had mnemonic hex-codes (''A''=add, ''M''=multiply, ''L''=load, ''F''=fixed-point etc.); programs were written without instruction names. * The (1957) used the lowercase letters ''b'', ''c'', ''d'', ''e'', ''f'', and ''g'' whereas the 100 (1967) used the uppercase letters ''B'', ''C'', ''D'', ''E'', ''F'' and ''G'' for the values 10 to 15. * The (1960) used the letters ''S'', ''T'', ''U'', ''V'', ''W'' and ''X'' for the values 10 to 15. * The computer NEAC 1103 (1960) used the letters ''D'', ''G'', ''H'', ''J'', ''K'' (and possibly ''V'') for values 10–15. * The Pacific Data Systems 1020 (1964) used the letters ''L'', ''C'', ''A'', ''S'', ''M'' and ''D'' for the values 10 to 15. * New numeric symbols and names were introduced in the notation by in 1968. This notation did not become very popular. * Bruce Alan Martin of considered the choice of A–F "ridiculous". In a 1968 letter to the editor of the , he proposed an entirely new set of symbols based on the bit locations, which did not gain much acceptance. * Some decoder chips (i.e., 74LS47) show unexpected output due to logic designed only to produce 0–9 correctly.Verbal and digital representations

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 (' for the first power, ' for the first power, ', ' and ' for the first three 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 , the , or a similar ''ad-hoc'' system. In the wake of the adoption of hexadecimal among programmers, Magnuson (1968) suggested a pronunciation guide that gave short names to the letters of hexadecimal – for instance, "A" was pronounced "ann", B "bet", C "chris", etc. Another naming system was elaborated by Babb (2015), off a TV series as a joke. Yet another naming-system was published online by Rogers (2007) 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. Systems of counting on have been devised for both binary and hexadecimal. suggested using each finger as an on/off bit, allowing finger counting from zero to 1023Signs

The hexadecimal system can express negative numbers the same way as in decimal: −2A to represent −42Hexadecimal exponential notation

Just as decimal numbers can be represented in , 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 . 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 . Hexadecimal exponential notation is required by the binary floating-point standard. This notation can be used for floating-point literals in the edition of the . Using the ''%a'' or ''%A'' conversion specifiers, this notation can be produced by implementations of the ' family of functions following the C99 specification and (IEEE Std 1003.1) standard.Conversion

Binary conversion

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 (4Other simple conversions

Although (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 2Division-remainder in source base

As with all bases there is a simple 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 hConversion through addition and multiplication

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 (11Tools for conversion

Many computer systems provide a calculator utility capable of performing conversions between the various radices frequently including hexadecimal. In , the utility can be set to Scientific mode (called Programmer mode in some versions), which allows conversions between radix 16 (hexadecimal), 10 (decimal), 8 () and 2 (), the bases most commonly used by programmers. In Scientific Mode, the on-screen includes the hexadecimal digits A through F, which are active when "Hex" is selected. In hex mode, however, the Windows Calculator supports only integers.Elementary arithmetic

Elementary operations such addition, subtraction, multiplication and division can be carried out indirectly through conversion to an alternate , such as the commonly-used decimal system or the binary system where each hex digit corresponds to four binary digits. Alternatively, one can also perform elementary operations directly within the hex system itself — by relying on its addition/multiplication tables and its corresponding standard algorithms such as and the traditional subtraction algorithm.Real numbers

Rational numbers

As with other numeral systems, the hexadecimal system can be used to represent s, although are common since sixteen (10`0.1`

. Because the radix 16 is a (4Irrational numbers

The table below gives the expansions of some common s in decimal and hexadecimal.Powers

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

The traditional were base-16. For example, one jīn (斤) in the old system equals sixteen s. The (Chinese ) can be used to perform hexadecimal calculations such as additions and subtractions. As with the 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. Some proposals unify standard measures so that they are multiples of 16. An early such proposal was put forward by in ''Project of a New System of Arithmetic, Weight, Measure and Coins: Proposed to be called the Tonal System, with Sixteen to the Base'', published in 1862. Nystrom among other things suggested , which subdivides a day by 16, so that there are 16 "hours" (or "10 ''tims''", pronounced ''tontim'') in a day. The word ''hexadecimal'' is first recorded in 1952. It is in the sense that it combines ἕξ (hex) "six" with ate ''-decimal''. The all-Latin alternative ' (compare the word ' for base 60) is older, and sees at least occasional use from the late 19th century. It is still in use in the 1950s in documentation. Schwartzman (1994) argues that use of ''sexadecimal'' may have been avoided because of its suggestive abbreviation to ''sex''. Many western languages since the 1960s have adopted terms equivalent in formation to ''hexadecimal'' (e.g. French ''hexadécimal'', Italian ''esadecimale'', Romanian ''hexazecimal'', Serbian ''хексадецимални'', etc.) but others have introduced terms which substitute native words for "sixteen" (e.g. Greek δεκαεξαδικός, Icelandic ''sextándakerfi'', Russian ''шестнадцатеричной'' etc.) Terminology and notation did not become settled until the end of the 1960s. in 1969 argued that the etymologically correct term would be ''senidenary'', or possibly ''sedenary'', a Latinate term intended to convey "grouped by 16" modelled on ''binary'', ''ternary'' and ''quaternary'' etc. According to Knuth's argument, the correct terms for ''decimal'' and ''octal'' arithmetic would be ''denary'' and ''octonary'', respectively. 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". The now-current notation using the letters A to F establishes itself as the de facto standard beginning in 1966, in the wake of the publication of the manual for , which (unlike earlier variants of Fortran) recognizes a standard for entering hexadecimal constants.(1966), p. 13.

Base16 (transfer encoding)

Base16 (as a proper name without a space) can also refer to a belonging to the same family as , , and . In this case, data is broken into 4-bit sequences, and each value (between 0 and 15 inclusively) is encoded using 16 symbols from the character set. Although any 16 symbols from the ASCII character set can be used, in practice the ASCII digits '0'–'9' and the letters 'A'–'F' (or the lowercase 'a'–'f') are always chosen in order to align with standard written notation for hexadecimal numbers. There are several advantages of Base16 encoding: * Most programming languages already have facilities to parse ASCII-encoded hexadecimal * Being exactly half a byte, 4-bits is easier to process than the 5 or 6 bits of Base32 and Base64 respectively * The symbols 0–9 and A-F are universal in hexadecimal notation, so it is easily understood at a glance without needing to rely on a symbol lookup table * Many CPU architectures have dedicated instructions that allow access to a half-byte (otherwise known as a ""), making it more efficient in hardware than Base32 and Base64 The main disadvantages of Base16 encoding are: * Space efficiency is only 50%, since each 4-bit value from the original data will be encoded as an 8-bit byte. In contrast, Base32 and Base64 encodings have a space efficiency of 63% and 75% respectively. * Possible added complexity of having to accept both uppercase and lowercase letters Support for Base16 encoding is ubiquitous in modern computing. It is the basis for the standard for , where a character is replaced with a percent sign "%" and its Base16-encoded form. Most modern programming languages directly include support for formatting and parsing Base16-encoded numbers.See also

* , (content encoding schemes) * * * * * (BBP) *References

{{reflist, refs= {{cite web , title=Computer Arithmetic , at=The Early Days of Hexadecimal , author-first=John J. G. , author-last=Savard , date=2018 , orig-year=2005 , work=quadibloc , url=http://www.quadibloc.com/comp/cp02.htm , access-date=2018-07-16 , url-status=live , archive-url=https://web.archive.org/web/20180716102439/http://www.quadibloc.com/comp/cp02.htm , archive-date=2018-07-16 {{cite book , title=G15D Programmer's Reference Manual , chapter=2.1.3 Sexadecimal notation , publisher=, Division of , location=Los Angeles, CA, USA , page=4 , url=http://bitsavers.trailing-edge.com/pdf/bendix/g-15/G15D_Programmers_Ref_Man.pdf , access-date=2017-06-01 , url-status=live , archive-url=https://web.archive.org/web/20170601222212/http://bitsavers.trailing-edge.com/pdf/bendix/g-15/G15D_Programmers_Ref_Man.pdf , archive-date=2017-06-01 , quote=This base is used because a group of four bits can represent any one of sixteen different numbers (zero to fifteen). By assigning a symbol to each of these combinations we arrive at a notation called sexadecimal (usually hex in conversation because nobody wants to abbreviate sex). The symbols in the sexadecimal language are the ten decimal digits and, on the G-15 typewriter, the letters u, v, w, x, y and z. These are arbitrary markings; other computers may use different alphabet characters for these last six digits. {{cite web , title=ILLIAC Programming – A Guide to the Preparation of Problems For Solution by the University of Illinois Digital Computer , author-first1=S. , author-last1=Gill , author-first2=R. E. , author-last2=Neagher , author-first3=D. E. , author-last3=Muller , author-first4=J. P. , author-last4=Nash , author-first5=J. E. , author-last5=Robertson , author-first6=T. , author-last6=Shapin , author-first7=D. J. , author-last7=Whesler , editor-first=J. P. , editor-last=Nash , edition=Fourth printing. Revised and corrected , date=1956-09-01 , publisher=Digital Computer Laboratory, Graduate College, , location=Urbana, Illinois, USA , pages=3–2 , url=http://www.textfiles.com/bitsavers/pdf/illiac/ILLIAC/ILLIAC_programming_Sep56.pdf , website=bitsavers.org , access-date=2014-12-18 , url-status=live , archive-url=https://web.archive.org/web/20170531153804/http://www.textfiles.com/bitsavers/pdf/illiac/ILLIAC/ILLIAC_programming_Sep56.pdf , archive-date=2017-05-31 {{cite book , title=ROYAL PRECISION Electronic Computer LGP – 30 PROGRAMMING MANUAL , publisher= , location=Port Chester, New York , date=April 1957 , url=http://ed-thelen.org/comp-hist/lgp-30-man.html#R4.13 , access-date=2017-05-31 , url-status=live , archive-url=https://web.archive.org/web/20170531153004/http://ed-thelen.org/comp-hist/lgp-30-man.html , archive-date=2017-05-31 (NB. This somewhat odd sequence was from the next six sequential numeric keyboard codes in the 's 6-bit character code.) {{cite web , title=Die PERM und ALGOL , url=http://www.manthey.cc/sites/seminars/src/History.pdf , author-first1=Steffen , author-last1=Manthey , author-first2=Klaus , author-last2=Leibrandt , date=2002-07-02 , access-date=2018-05-19 , language=de Positional numeral systems