Text To Hex
Text To Hex — runs in your browser. Inputs are not stored.
Text ↔ hex (UTF-8)
Converts UTF-8 bytes to hexadecimal. Input stays in the browser only.
How to use
- Put plain text or a hex string in Input. Hex may include spaces or colons.
- To view a sentence as bytes, press Text → hex. Each byte becomes two lowercase hex digits, separated by spaces.
- To turn hex back into text, press Hex → text. Only digits and A–F are kept and parsed as an even-length string.
- An odd length or leftover non-hex characters produces a format-error message.
- Reset clears input and output. Conversion uses only the browser’s UTF-8 encoder/decoder.
- A
0xprefix copied from a packet capture or editor is not hex—delete it and leave only the digits.
Key concepts
Text ↔ hex encodes characters as UTF-8 bytes, then shows each byte as two hex digits. ASCII letters and digits are usually one byte, so the tokens stay short; Hangul syllables are typically three bytes, so the hex is longer. Use it to make protocol dumps, binary logs, debug notes, or simple payloads easier to read. Output is lowercase with a space between bytes.
On decode, every non-hex character (spaces, colons, newlines) is discarded and only 0–9a–f remain. An odd remaining length means a leftover nibble and is an error. Results are always decoded as UTF-8, so an EUC-KR or CP949 dump from Windows Notepad can garble Hangul. This is not the same as converting integers (255 ↔ FF). Input is not sent to a server.
Example
A is 41, and 가 is UTF-8 ea b0 80. Hex → text on 48 65 6c 6c 6f or 48:65:6c:6c:6f yields Hello. Running the same value through Text → hex again returns a space-separated lowercase dump so you can check a round trip. Strip any 0x prefix from debug logs before converting.
Related: Text ↔ binary · Text → decimal · Base converter
Frequently asked questions
How many bytes is Hangul when converting text to hex?
A complete Hangul syllable is usually 3 bytes in UTF-8, so six hex digits (three tokens with spaces). Old Hangul made of jamo only can have a different length.
Can I paste spaces and colons into the hex converter?
Yes. On decode, only hex digits are kept; spaces, colons, and line breaks are dropped so packet dumps are easy to paste.
Are uppercase F and lowercase f the same?
Input is case-insensitive. Text → hex output is two lowercase digits per byte.
Why is odd-length hex an error?
One byte is two digits, so an odd length leaves a leftover nibble. Pad a leading 0 to make the length even, then convert again.
Will EUC-KR hex still show Hangul?
This tool decodes UTF-8 only. EUC-KR or CP949 dumps from Windows Notepad or older boards can display garbled characters.
Is text-hex conversion data left on a server?
No. TextEncoder/TextDecoder build the bytes only in this tab.
Last reviewed: 2026-09-04