Hex encoding

Revision as of 01:17, 29 August 2014

Hex encoding is a transfer encoding in which each byte is converted to the 2-digit base-16 encoding of that byte (preserving leading zeroes), which is then usually encoded in ASCII. It is inefficient, but it is a simple, commonly-used way to represent binary data in plain text.

It is not a formal standard, so the term hex encoding may have other meanings, and the format described in the article may have other names.

Most hex encoders use uppercase letters ("A" through "F"), but lowercase ("a" through "f") is not uncommon, and hex decoders typically support both. Whitespace characters may be allowed, and ignored.

The most significant hex digit almost always comes first, but variants in which the least significant digit comes first do exist, for example ASCII Encoded HP 48 Object.

The distinction between hex encoding and base-16 (hexadecimal) is not always clear. If you interpret a datastream as a single (probably huge) number, and write that number in base-16, it can, with suitable conventions, be equivalent to hex encoding. For example, consider the way that cryptographic hashes are usually written.

The earliest versions of BinHex used a form of hex encoding, but the program later evolved to a different encoding based on base 64 instead of base 16 (similar to Base64 encoding but with a different set of characters).

Examples

The hex encoding of the ASCII string "hijkl", followed by a newline character ("\n"), is "68696A6B6C0A".

A perl one-liner to do hex encoding:

perl -ne 'print uc(unpack("H*",$_))' original.bin > encoded.txt

And decoding:

perl -ne 'print pack("H*",$_)' encoded.txt > decoded.bin

Links

• Ten Minute Tutor: Hex (Base16) encoding
• Online Hex Encoder
• Online Hex Decoder
• RFC 4648: The Base16, Base32, and Base64 Data Encodings
• RFC 3548: The Base16, Base32, and Base64 Data Encodings (obsolete)