Hex dumps show binary data as pairs of hexadecimal digits, one pair per byte. Reading hex directly is a core skill in systems programming, CTF challenges, network protocol debugging, and digital forensics. This tool decodes hex byte sequences to readable text and encodes text to hex, supporting ASCII and UTF-8 character sets.
Network packet captures, binary file headers, and memory dump tools all show data in hex. The HTTP/2 frame header, for example, is 9 bytes — shown in Wireshark as 00 00 17 01 04 00 00 00 01. A hexdump like 48 65 6C 6C 6F decodes to "Hello" (H=0x48, e=0x65, l=0x6C, l=0x6C, o=0x6F). This tool handles any hex sequence, with or without spaces, and with any common prefix format.
A representation of binary data where each byte is shown as two hexadecimal digits. The xxd, hexdump, and Wireshark tools all produce hex dumps. The format is universally readable across languages and platforms.
Characters with ASCII values below 32 or above 126 are non-printable. The tool shows them as their C-style escape sequences (\n, \t) where known, or as \xHH for others.
Yes — enable UTF-8 mode. UTF-8 characters above U+007F use multi-byte sequences: 2 bytes for U+0080–U+07FF, 3 bytes for U+0800–U+FFFF, 4 bytes for U+10000+. The decoder assembles these correctly.
Many CTF challenges provide hex-encoded ciphertext, shellcode, or flags. Paste the hex and decode to text. If the result is still binary, try further decoding (Base64, XOR, etc.).
See also the Binary to Text converter, ASCII Table, and the XOR Encryptor.