How is text converted to hex?

The text is encoded as UTF-8 bytes, and each byte (0 to 255) is written as exactly two hexadecimal digits. The letter A is byte 65, which is 41 in hex. A space is byte 32, which is 20.

How does the decoder handle spacing and prefixes?

The decoder removes spaces, newlines, and any 0x prefixes, then reads the remaining digits in pairs. As long as the digit count is even, it reconstructs the bytes and decodes them as UTF-8.

Why do some characters take more than two hex digits?

Characters outside ASCII are multiple UTF-8 bytes. Each byte is two hex digits, so an accented letter may be four digits and an emoji as many as eight, since UTF-8 uses up to four bytes per character.

What if the hex is malformed?

If the input contains non-hex characters, or has an odd number of digits, the tool reports the error rather than guessing. This prevents silently corrupting the decoded text.

Is the conversion lossless?

Yes. Encoding to hex and decoding back returns the original string exactly, because UTF-8 byte values map directly to two hex digits each with no information lost.

Hex Text Converter — Gera Tools

Hexadecimal is the standard compact way to show raw bytes. This converter turns text into a UTF-8 hex byte stream and decodes hex back into readable text.

How it works

For encoding, the text is converted to UTF-8 bytes. Each byte from 0 to 255 is written as two hex digits:

byte 65 (A)  -> 41
byte 32 ( )  -> 20
byte 255     -> FF

For decoding, the input is normalised by stripping whitespace and any 0x prefixes, then the digits are read in pairs. Each pair is parsed as a byte and the byte array is decoded as UTF-8 into the original text.

Example and notes

The word Hi is bytes 72 and 105, giving hex 48 69. ASCII characters are always two hex digits; characters beyond ASCII use several UTF-8 bytes and so appear as several hex pairs. When decoding, the total number of hex digits must be even — an odd count means a byte is incomplete, so the tool flags it instead of dropping a nibble.