Hexadecimal Translator

For text to hex, keep English as the source and enter the message itself. For hex to text, use the swap button and paste byte pairs such as 48 69. The input direction matters: entering 48 69 in text mode encodes the digits, spaces and letters you typed rather than interpreting them as two bytes. Check the labels above the box before pressing Translate.

A result from text mode can be pasted into reverse mode. The Hexadecimal Translator preserves the spaces and line breaks within the decoded text; the spaces separating hexadecimal bytes are formatting and are not part of that message.

Each pair represents a value from 00 to FF. The decoder accepts a compact sequence or byte groups separated by whitespace, commas, colons or hyphens. A byte group may start with 0x. Uppercase and lowercase hexadecimal letters mean the same values. An odd number of digits is incomplete: do not add a zero automatically, because putting it before or after the digit produces different bytes.

The Hexadecimal Translator rejects unexpected letters and punctuation instead of quietly skipping them. Copy only the byte sequence from a dump. Remove addresses, line counters and the readable-text column before decoding.

The inspector shows both labels because they answer different questions. A Unicode code point identifies a character; UTF-8 describes the bytes used to store it. Basic ASCII characters need one byte, while many accented letters and symbols need several. A visible emoji can also combine several code points. Read every inspector row when comparing a copied symbol with a byte sequence.

Use the Hexadecimal Translator on the complete text first, then inspect a shorter fragment below. This helps locate the character that changed without treating every pair of digits as a separate letter.

An invalid UTF-8 result often means a byte is missing, a multi-byte character was cut in half, or the source uses another encoding. Recopy the complete sequence and check the exporting application. If it says UTF-16 or a legacy encoding, this page does not reinterpret it as UTF-8. A byte value can be valid hexadecimal and still be invalid at that position in a UTF-8 string.

The Hexadecimal Translator reports invalid UTF-8 instead of replacing damaged data with an unreadable replacement character. Do not repeatedly remove bytes until an error disappears; the remaining text could have a different meaning.

Converting the number 255 to base sixteen gives FF. Encoding the text “255” instead produces three character bytes. This page performs the second kind of operation: text encoding. For a file size, memory address or arithmetic exercise, first decide whether your task is about a numeric value or the characters used to write it. That distinction prevents apparently contradictory conversion results.

A Hexadecimal Translator result is also not a colour picker, encryption scheme or file decompressor. It can expose a readable text fragment from a larger dump, but only when that fragment really contains UTF-8 text.

The output uses uppercase pairs separated by spaces so byte boundaries remain easy to inspect. If another application needs a continuous string, remove the separators after copying; retain every pair in its original order. Keep your original text beside the byte string when preparing a puzzle or comparing application logs. A line break in a message is a stored character, unlike a separator between displayed bytes.

For longer material, work in complete short sections within the 500-character input limit. Hexadecimal Translator input limits apply to what you paste, so a long byte sequence may need smaller sections than its decoded sentence.