Hex to text converter
Read hexadecimal bytes as text, or turn a message into hex. Check the result, then copy it or save a TXT file.
UTF-8 text bytes, with two hex digits per byte. No account needed. Encoding is not encryption.
Up to 1,000 bytes (2,000 hex digits) and 6,000 input units including whitespace. No silent shortening.
Use two hex digits per byte. Uppercase or lowercase, compact or separated by ordinary spaces, tabs or line breaks. Changing direction keeps your typed input.
Your decoded text
3 UTF-8 bytes. Two hex digits per byte.
UTF-8 text only, not arbitrary binary files or encryption. Copy and TXT contain this result, without labels or an added newline.
Actual copyable examples
- Text: Hi! (3 bytes)
- 48 69 21
- Text: café (5 bytes)
- 63 61 66 C3 A9
Paste either hex result into Hex to decode. The accented letter in the second example uses two UTF-8 bytes: C3 A9, not E9.
Hex bytes are not character numbers
Hexadecimal uses digits 0-9 and letters A-F. Two hex digits represent one eight-bit byte. ASCII characters have the same values in UTF-8: 41 is A, 20 is a space and 0A is a line feed. Other Unicode characters can need several bytes.
This tool reads a sequence of UTF-8 bytes, not a single base-16 number, Unicode code points, UTF-16 or a hex dump with addresses. For example, an emoji code point is not the same as its UTF-8 byte sequence. Bytes from Latin-1 or another encoding can mean something else.
Decode uppercase or lowercase pairs, compact like 486921 or separated like 48 69 21. Ordinary spaces, tabs and line breaks may separate complete bytes; 4 8 is rejected. Remove 0x or \x prefixes, commas and addresses first. Odd groups and invalid UTF-8 produce an error, not partial text or replacement characters.
Encoding emits uppercase pairs separated by spaces. Those separators do not add spaces to decoded text. Your original spaces, tabs and line breaks are encoded as bytes. Browser text fields normally normalize CRLF or lone CR endings to LF; a literal leading U+FEFF is retained.
See RFC 4648, base 16 for the byte notation and RFC 3629, UTF-8 for the text encoding. The whitespace allowance is this tool's input convenience, not a claim about every base-16 decoder.
Limits, exports and data handling
Encode or decode up to 1,000 UTF-8 bytes. Hex input also has a 6,000-unit limit including whitespace. Accents and emoji use more bytes than ordinary ASCII letters. Incomplete Unicode, control characters other than tabs and line breaks, and bidirectional formatting controls are rejected without removing them. Your input is never silently shortened.
Changing direction keeps your typed input. Copy and UTF-8 TXT contain only the current result, without labels or an added final newline. Clipboard and receiving editors may adapt line endings. If copying fails, select the raw result or download TXT. Export before leaving; no draft is saved automatically.
Input stays in this page's memory, not links, saved settings or analytics events. Site resources and analytics still make requests; see data handling. Hex does not hide a secret safely; do not treat it as encryption.
Need zeros and ones instead? Use the binary translator. Inspect unusual characters with the Unicode inspector, or turn words into banners with Text to ASCII.