How to convert hex to readable text
- Keep the Input mode on Hex.
- Paste bytes separated by spaces, commas, colons, or hyphens. A
0xprefix is accepted. - Select the bytes to decode, or choose All for the complete input.
- Read the ASCII and UTF-8 rows in Representations, then copy the exact output you need.
48 65 6C 6C 6F 2C 20 42 69 74 70 65 65 6B 21The example above decodes to Hello, Bitpeek! in both ASCII and UTF-8.
UTF-8 and ASCII are not interchangeable
ASCII maps printable values from 20 through 7E directly to characters. Bitpeek displays other single-byte values as dots in the compact ASCII column.
UTF-8 uses one to four bytes per Unicode code point. The UTF-8 representation therefore decodes the selected sequence as a whole and escapes control characters such as line feed, carriage return, tab, and NUL.
Invalid or incomplete byte sequences
Hex input must contain complete two-digit bytes. An incomplete final nibble is rejected rather than guessed. If the bytes are valid hex but not valid UTF-8, the text preview includes � replacement markers and the editor warns before text-mode editing.
Switching to Text mode and editing invalid UTF-8 can replace undecodable bytes. Keep the original hex input or file available when byte preservation matters.
Convert the same bytes without re-entering them
The Input tabs reformat the current byte array as hex, binary, decimal, UTF-8 text, or Base64. The interpretation panel also keeps these representations together for the selected range, making it easier to compare encodings without using separate converters.
Local processing and privacy
The Hex to text workflow opens the same Bitpeek browser workspace. Selected file bytes, file names, pasted input, searches, edits, hashes, and comparison data are processed in local browser memory and are not sent to a Bitpeek server.
The static guide itself can be read without opening a file or creating an account.
Frequently asked questions
Does hex text have an endianness?
A raw byte sequence has a fixed order. Endianness matters when multiple bytes are interpreted as a number, not when UTF-8 decodes the bytes in sequence.
Why do some bytes appear as dots in ASCII?
The compact ASCII view uses dots for control bytes and values outside printable ASCII so table alignment remains stable.
Can I convert text back to hex?
Yes. Choose Text input mode, enter UTF-8 text, then switch to Hex or copy the Hex representation for the encoded bytes.