Hex to UTF-8 converter

Hex to UTF-8 Converter: Free Online Hexadecimal to Text Decoder

Convert raw hexadecimal byte sequences into human-readable UTF-8 text instantly with our free online tool. Whether you are inspecting database records, analyzing network packets, or fixing garbled character encodings, this converter decodes base-16 strings into precise Unicode characters, symbols, and emojis in real time.

How to Convert Hexadecimal to UTF-8 Text

We have designed the interface to be intuitive so you can get your results immediately:

1. Input Your Data: Paste your Hex string (e.g., 4A 6F 79) or plain text into the main text area.
2. Select Direction:
   • Hit “Convert to UTF-8” if you are trying to read a Hex code.
   • Hit “Convert from UTF-8” if you want to turn text into code.
3. Customize (For Output): If you are generating Hex, choose your preferred format using the radio buttons (Standard spaces, \x prefix for code, or continuous strings).
4. Copy Result: Use the “Copy to Clipboard” button to grab the converted data without selecting it manually.

Real-World Example

To verify the tool’s accuracy, try these inputs:

Example 1: Decoding (Hex to Text)

• Input: 57 6F 72 64 50 72 65 73 73
• Output: WordPress

Example 2: Encoding (Text to Hex)

• Input: Sitemap
• Output (Standard): 53 69 74 65 6D 61 70
• Output (Escaped): \x53\x69\x74\x65\x6D\x61\x70

How Hex to UTF-8 Conversion Works

Hexadecimal (base-16) is a compact way to represent binary computer data using numbers (0–9) and letters (A–F). Each hex digit represents four bits (a nibble), meaning two hex digits represent one full 8-bit byte.

UTF-8 (Unicode Transformation Format – 8-bit) is the standard character encoding used across more than 95% of the web. Unlike fixed-width character sets, UTF-8 uses a variable-length encoding scheme that stores each character in 1 to 4 bytes:

• 1 Byte (ASCII Compatibility): Standard English characters, numbers, and basic punctuation use a single byte (0x00 to 0x7F).
• 2 Bytes: Accented European letters, Greek, Cyrillic, Hebrew, and Arabic characters use two bytes (starting with 0xC2–0xDF).
• 3 Bytes: Asian scripts (Chinese, Japanese, Korean), Indian scripts (Devanagari), and currency symbols use three bytes (starting with 0xE0–0xEF).
• 4 Bytes: Emojis, mathematical notation, and rare historical scripts use four bytes (starting with 0xF0–0xF7).

During decoding, the tool inspects the leading bits of each hex byte. If a byte starts with a prefix indicating a multi-byte sequence, it groups the following continuation bytes (which always fall between 0x80 and 0xBF) to reconstruct the original Unicode character.

Need the reverse process? If you need to convert plain text or international characters into raw hexadecimal byte streams, use our UTF-8 to Hex Converter.

Hex to UTF-8 Conversion Reference Table

Here are common examples showing how hex byte sequences translate into UTF-8 text across different languages and character types:

Hex Input	UTF-8 Text Output	Byte Length	Description / Language
48 65 6C 6C 6F	Hello	5 Bytes	Standard English ASCII text
C3 A9	é	2 Bytes	Latin small letter e with acute
E2 82 AC	€	3 Bytes	Euro currency symbol
E4 B8 AD E6 96 87	中文	6 Bytes (3 per char)	Chinese characters (“Chinese language”)
F0 9F 98 80	😀	4 Bytes	Grinning face emoji
CE A9	Ω	2 Bytes	Greek capital letter Omega

Real-World Developer Use Cases

1. Fixing Database Encoding Errors & “Mojibake”

When moving database tables between MySQL or PostgreSQL instances, incorrect character set migrations often create garbled text (known as Mojibake). For example, seeing café instead of café means UTF-8 bytes were misinterpreted as single-byte ISO-8859-1 text. Decoding the raw hex bytes directly reveals the original text.

2. Inspecting API Payloads and Log Files

APIs, webhooks, and legacy backend services frequently pass non-ASCII data in hex-encoded strings. Decoding hex bytes lets you inspect multi-language customer names, localized addresses, and raw payload contents without running complex scripts.

3. Malware Analysis and Security Auditing

Cybersecurity analysts examine raw binary files and packet captures using hex dumps. Converting hex segments back to UTF-8 strings helps identify embedded URLs, hidden commands, and readable text strings inside suspicious files.

Frequently Asked Questions

1. What is the difference between Hex-to-UTF-8 and Hex-to-ASCII conversion?

Hex-to-ASCII only decodes basic English characters, numbers, and symbols matching byte values from 0 to 127 (0x00–0x7F). Hex-to-UTF-8 supports all 149,000+ characters in the Unicode standard—including multi-byte international characters, accented letters, and emojis.

2. Why do I see strange replacement characters like ” in the output?

The replacement character “ (U+FFFD) appears when a hex byte sequence is invalid or incomplete according to UTF-8 rules. This happens if bytes are missing, corrupted, or if the source data was encoded in a different character set like Windows-1252 or Latin-1.

3. Can this tool decode emojis and symbols?

Yes. UTF-8 represents emojis using 4-byte hexadecimal sequences. For example, pasting F0 9F 9A 80 will decode into the rocket emoji (🚀).

4. What hex formatting prefixes does the input accept?

The converter supports standard hex strings (48656C6C6F), space-delimited bytes (48 65 6C 6C 6F), 0x prefixes (0x48 0x65), and \x escape codes (\x48\x65).

5. Is my data kept private when converting?

Yes. All conversion logic runs locally in JavaScript inside your browser. No hex data or decoded text is ever sent to or stored on our servers.

6. How does UTF-8 know how many bytes belong to one character?

UTF-8 uses prefix bits in the first byte of a sequence. A leading 0 means 1 byte. 110xxxxx indicates 2 bytes, 1110xxxx indicates 3 bytes, and 11110xxx indicates 4 bytes. Following bytes always start with 10xxxxxx.

7. Does case matter when entering hexadecimal values?

No. Hexadecimal values are case-insensitive. You can enter 4a 6f 68 6e or 4A 6F 68 6E, and both will decode accurately.

8. Why are non-English characters longer in hex format?

English characters fall within the 1-byte ASCII range (0x00–0x7F). Non-English characters require multi-byte sequences (2 to 4 bytes) in UTF-8 to represent thousands of unique global language scripts, making their hex outputs longer.