Convert Hexadecimal to UTF-8

ASCII tools read every byte as a single character (0-127 only; 128-255 give garbage or Latin-1). This tool uses real UTF-8 multi-byte parsing: C3 A9 becomes é (one code point, two bytes), not é (two characters). That matters the moment non-English text is involved.

Yes. Emoji use 4-byte UTF-8 sequences in the supplementary plane. F0 9F 98 80 decodes to 😀 (U+1F600). The breakdown panel shows the 11110xxx 10xxxxxx 10xxxxxx 10xxxxxx pattern so you can see how the 21-bit code point is packed across 4 bytes.

For each code point: the rendered character, a 1B/2B/3B/4B tag for byte count, the Unicode code point (U+XXXX), the raw hex bytes, and the UTF-8 bit pattern (e.g., 1110xxxx 10xxxxxx 10xxxxxx for 3-byte). First 60 code points are shown to keep the page responsive.

With “Fatal” off (default): invalid bytes become uFFFD (the Unicode replacement character �). With “Fatal” on: the decode throws, and the line is flagged with “invalid UTF-8 at byte N” – useful when validating externally-sourced hex.

Yes. The normalizer strips 0x, 0X, x, #, commas, underscores, and all whitespace. 0x48, 0x65, 0x6C and x48x65x6C and 48_65_6C all decode identically to Hel.

The Byte Order Mark (EF BB BF) is a 3-byte prefix some editors add to UTF-8 files. It’s invisible when rendered but bytes 1-3 of your hex will look “off”. Strip-BOM on (default) silently removes it; off leaves it as uFEFF at the start of output.

No. Everything runs in your browser – the TextDecoder is built into JavaScript. No fetch, no XHR, no analytics on the hex. Open DevTools → Network, decode anything, watch zero requests fire. Safe for credentials, PII, or proprietary byte streams.

Yes. Once the page (HTML/CSS/JS, under 20 KB total) loads, pull your Ethernet cable or hit airplane mode – every subsequent decode runs locally. Perfect for air-gapped systems or when debugging on a train.

Typical inputs decode in under 50 ms. A 10,000-byte hex string decodes in about 5 ms on a modern laptop. The breakdown panel caps at 60 rows to keep DOM work fast on very large batches; the output textarea and stats still reflect the full decoded text.

Use the companion UTF-8-to-Hex encoder in the same category. That tool accepts any Unicode text – emoji, CJK, Arabic – and outputs the corresponding hex byte sequence, with the same 4-format options (continuous, spaced, 0x-prefixed, x-prefixed) available here.