What hex formats are accepted?

Hex input can include 0x prefixes and be separated by spaces, colons, semicolons or commas. The converter strips those and reads the remaining digits as pairs (one byte each).

Does it support Unicode?

Yes. Bytes are decoded as UTF-8 and text is encoded as UTF-8, so accented characters, non-Latin scripts and emoji all convert correctly. A multi-byte character spans several hex pairs.

Why does my hex fail to decode?

Decoding uses strict UTF-8, so a byte sequence that is not valid UTF-8 is rejected rather than producing garbage. Check that you have an even number of hex digits and that the bytes form a real UTF-8 string.

How many hex digits per character?

Each byte is two hex digits. Plain ASCII letters are one byte (two digits). Accented Latin characters are usually two bytes, and emoji are typically four bytes, so they take four, eight, or more hex digits.

Is hex the same as ASCII codes?

For plain English text, yes — each character maps to its ASCII byte written in hex, e.g. A is 41. But this tool is UTF-8 aware, so it also handles characters beyond ASCII that have no single ASCII code.

Is my input uploaded?

No. Conversion runs entirely in your browser with built-in APIs — nothing is sent to any server.

What is the Hex to Text Converter?

Free hex to text converter that turns hexadecimal byte sequences into readable UTF-8 text and back again. Accepts 0x, spaces and separators. Runs entirely in your browser — nothing is uploaded. It runs free in your browser on Gera Tools, with nothing uploaded.

Hex to Text Converter

Name: Hex to Text Converter
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

Get one useful tool a week

Like this tool? Enter your email and we'll send you one genuinely useful Gera tool a week — plus a link to come back to this one. No spam, one-click unsubscribe any time.

Hex to text converter

Convert hexadecimal byte sequences into readable UTF-8 text, or encode text into hex. It is useful for reading hex dumps, debugging protocols and data files, or producing a hex representation of a string. Hex input is forgiving — 0x prefixes plus spaces, colons, semicolons and commas are all stripped automatically before decoding.

How it works

In Hex to Text mode the tool removes separators and prefixes, splits the remaining digits into pairs, reads each pair as one byte (0–255), and decodes the whole byte array as UTF-8 using the browser’s TextDecoder in strict mode — so invalid byte sequences are flagged rather than mangled. In Text to Hex mode it runs the reverse: TextEncoder turns the text into UTF-8 bytes, and each byte is written as a two-digit, zero-padded hex value.

Worked example — ASCII

Decoding 48 65 6c 6c 6f gives Hello:

Hex	Decimal	Character
48	72	H
65	101	e
6c	108	l
6c	108	l
6f	111	o

Multi-byte characters

Encoding café gives 63 61 66 c3 a9 — note that the é is two bytes (c3 a9) because UTF-8 uses two-byte sequences for characters outside ASCII (code points U+0080 to U+07FF). An emoji like 😀 takes four bytes (f0 9f 98 80). This is why the hex output length for a Unicode string can be longer than a simple character count would suggest.

Common use cases

Reading hex dumps: network captures, binary file inspections, and debugger output often show data as hex bytes. Paste them here to read the ASCII or UTF-8 content.
Debugging wire protocols: many protocols (SMTP responses, HTTP/1 headers, custom binary formats) can be examined by pasting the hex payload and reading the decoded text.
Producing test data: when you need a consistent hex encoding of a known string for a unit test or comparison, the Text to Hex direction gives a deterministic result.
CTF and security work: capture-the-flag challenges frequently hide flags in hex-encoded strings.

Why strict UTF-8 decoding matters

The tool decodes using strict mode, meaning an invalid byte sequence (such as an incomplete multi-byte character or a byte that is not valid in that position) produces an error rather than garbage or a replacement character. This is intentional: silent replacement can hide the fact that the input is not the encoding you think it is. If decoding fails, check that you have an even number of hex digits and that the bytes form a real UTF-8 sequence.

Everything runs in your browser with built-in TextEncoder and TextDecoder APIs — nothing is uploaded. For other encodings, try the Base64 decoder.