ToolBark
Converters

Hex to Text Converter

Convert hex to readable text and text to hex instantly

Result

Result appears here…

Common ASCII → Hex reference
CharHexCharHexCharHex
A41N4E030
B42O4F131
C43P50 20
D44Q51!21
E45R52.2E
F46S53,2C
G47T54?3F
H48U55@40
I49V56#23
J4AW57$24
K4BX58%25
L4CY59&26
M4DZ5A*2A
About

The Hex to Text Converter lets you instantly decode hexadecimal values into human-readable UTF-8 text, or encode any text string back into hex. Whether you are debugging binary data, working with network packets, or reading encoded file contents, this free tool handles ASCII, extended Latin, and full Unicode — including emoji — with support for common hex formats like spaced pairs, 0x prefixes, and dash-separated bytes.

FAQ
What hex formats does this converter accept?+

When converting hex to text, the tool accepts hex bytes separated by spaces, commas, dashes, or 0x prefixes (e.g. '48 65 6C', '48-65-6C', '0x48 0x65 0x6C', or unseparated '48656C'). All separators are stripped automatically before decoding.

Does it support Unicode and emoji?+

Yes. The encoder uses the browser's native TextEncoder (UTF-8) and the decoder uses TextDecoder with strict mode, so every Unicode code point — including multi-byte characters like accented letters, CJK characters, and emoji — round-trips correctly.

What is the difference between hex encoding and Base64?+

Hex encoding represents every byte as exactly two hexadecimal digits (0–9, A–F), making it easy to read and edit byte-by-byte. Base64 encodes three bytes into four printable ASCII characters, producing a roughly 33% smaller output, which is why it is preferred for transferring binary data in emails or JSON.

Why does my hex decode to garbled text?+

The hex bytes may represent a non-UTF-8 encoding such as Latin-1 or Windows-1252, or the bytes may be raw binary data rather than text. This tool strictly decodes UTF-8. If you see an error about invalid UTF-8, the source bytes likely come from a different character encoding.

Related tools