TOOL GUIDE · TEXT AND BYTES
How text becomes hexadecimal
Hexadecimal is base-16 notation, using digits 0–9 and letters A–F. One byte can be shown by two hex digits from 00 to FF. This tool first encodes the entered text as UTF-8 bytes, then prints each byte as two lowercase hex digits separated by spaces.
Character count is not byte count. A visible emoji or a letter outside basic Latin may take several UTF-8 bytes, so its hexadecimal form contains multiple pairs. Different source encodings produce different byte sequences for the same displayed text. The operation assumes UTF-8 because that is the common web default.
Hex describes bytes, not their meaning
The byte sequence could represent text, a file header, a color value, a protocol field, or arbitrary binary. The hex string alone does not identify which interpretation is correct. Byte order and the application’s data format may matter for multi-byte numeric values.
Converting sensitive data to hex does not make it private; anyone can decode the pairs. Do not use hexadecimal as encryption or secret storage. If the source is a binary file, use a binary-capable workflow rather than pasting a text approximation.
Verify a conversion
Use the paired Hex to Text converter on a harmless example and compare the recovered text. Whitespace between byte pairs is for display; the decoder accepts whitespace and requires an even number of hexadecimal digits. Read more about text/byte boundaries in the data basics reference.
The conversion uses local browser APIs and does not upload your text to a FormatInstant processing service.
