The sequence 48 65 6c 6c 6f decodes to Hello in UTF-8. If you encounter it in a computing exercise or a log, hexadecimal bytes are a useful hypothesis. Characters drawn only from 0–9 and a–f are a clue, however, not proof of an encoded message.

Hex and UTF-8 do different jobs

Hex writes a byte as two digits from 00 to ff. The value 48 is decimal 72; in UTF-8, that byte represents H.

Layer Hello example What it represents
Hex notation 48 65 6c 6c 6f Written byte values
Byte sequence Five bytes The underlying data
UTF-8 text Hello Those bytes interpreted as characters

Converting the integer 41 from base 16 to base 10 gives 65. Decoding byte 41 as UTF-8 gives A. Use the number base converter for the first task and the Hex-to-text converter for the second.

Decode Hello and check the reverse conversion

  1. Open the Hex-to-text converter and choose Hex → UTF-8.
  2. Enter 48 65 6c 6c 6f and select Convert.
  3. Check that the output is Hello and the byte count is five.
  4. Choose UTF-8 → Hex, enter Hello, and convert to recover the byte notation.

Uppercase 6C and lowercase 6c mean the same value. Tools Hub also accepts 48656c6c6f without separators. ASCII spaces, newlines and tabs are removed; commas and full-width spaces are not.

One character can require several bytes

The character 猫 becomes e7 8c ab in UTF-8. That is one character, three bytes and six Hex digits excluding separators. These counts describe different things.

Do not decode each byte independently as a character. Reassemble the complete byte sequence first, then interpret it as UTF-8. A Unicode code point is also a different representation: U+732B identifies this character, but its UTF-8 bytes are e7 8c ab. Entering 732b as UTF-8 bytes will not produce 猫.

Troubleshoot conversion errors

Input or symptom Explanation Next check
486 An odd number of Hex digits cannot form complete bytes Check the original for a missing digit
0x48 0x65 This tool does not accept 0x prefixes Enter 48 65
48,65 A comma is not a Hex digit Replace separators with ASCII spaces
ff Valid Hex, but invalid UTF-8 Check the original encoding or file type
Readable but meaningless output The assumed format or conversion order may be wrong Revisit the instructions and original data

Invalid UTF-8 produces a warning and a Hex byte view. The tool does not silently replace invalid bytes with � and report success. Shift_JIS text, images and compressed data require software that understands those formats.

Continue with a deliberate next step

Keep the original input and record each transformation. If the output resembles Base64, compare it with the Base64 guide before treating it as another encoded layer.

Try e7 8c ab in the Hex-to-text converter and confirm that it produces 猫 using three UTF-8 bytes.