Hex to Text
Decode hexadecimal bytes as strict UTF-8 or encode text as hex. Check byte positions, keep a leading BOM and download the exact output locally.
Use hexadecimal digits with optional spaces, line breaks, commas or dashes and a leading 0x. Complete UTF-8 is decoded without discarding a leading BOM.
Hex to Text: how to use it
- Choose Hex to text or Text to hex. Paste input, load a UTF-8 file, or select Load example.
- Select Convert. Check a reported character or byte position if the input is incomplete or invalid.
- Copy or download the result. Use result as input reverses the direction and retains the original string for the next conversion.
Limits and notes
Use up to 1 million input characters and 256 KiB of UTF-8 bytes. Hex accepts upper and lower case, ASCII spaces and line breaks, commas, dashes, and one leading 0x. Each byte needs two hex digits. Decoding retains a leading BOM, control bytes and original line endings. The downloaded text preserves exact bytes. Input file imports accept up to 1 MB of valid UTF-8.
How your privacy works →Hex to Text: common questions
Does a valid hex string always decode to text?
The hex alphabet can represent any bytes. This tool requires those bytes to form complete UTF-8 and reports the first bad byte sequence.
Why does an emoji use several hex pairs?
Each pair represents one byte. UTF-8 can use several bytes for one Unicode code point, and a visible emoji can use several code points.
Why does the result say the BOM is retained?
The bytes EF BB BF at the start become U+FEFF and are kept in the downloaded text. An editor may display no visible character for it.