Simply paste your hexadecimal string into the left panel (Hexadecimal Input). The tool automatically cleans your input — removing spaces, 0x prefixes, commas, and line breaks — then instantly decodes it into readable text in the right panel. You can also type text in the right panel to encode it back to hex. The conversion happens in real-time as you type.

Our hex decoder is very flexible and accepts multiple common formats:

• Compact: 48656c6c6f (no separators)
• Space-separated: 48 65 6c 6c 6f
• 0x-prefixed: 0x48 0x65 0x6c 0x6c 0x6f
• Comma-separated: 48,65,6c,6c,6f
• Mixed: any combination of the above

The tool intelligently strips all non-hex characters before decoding.

Common reasons for conversion issues:

• Odd number of hex characters: After cleaning, hex strings must have an even length (each byte = 2 hex chars). Check for missing digits.
• Invalid characters: Only 0–9 and A–F (case-insensitive) are valid hex digits. Letters like G–Z are not allowed.
• Wrong encoding assumption: If the original text was encoded in a different charset (e.g., Latin-1, Shift-JIS) but is being decoded as UTF-8, you may see replacement characters (�).
• Truncated data: If the hex string is incomplete (partial UTF-8 sequence), the decoder will use replacement characters for invalid byte sequences.

Yes! This converter uses UTF-8 encoding via the browser's native TextEncoder and TextDecoder APIs. This means:

• Emojis like 😀 (U+1F600) are encoded as 4 bytes: f0 9f 98 80
• Accented characters like é are encoded as 2 bytes: c3 a9
• CJK characters like 中 are encoded as 3 bytes: e4 b8 ad
• Basic ASCII characters are 1 byte each

This makes the tool suitable for all languages and character sets supported by UTF-8.

Use the format options below the Text Output panel to customize how text is encoded to hex:

• Separator: Choose between spaces, no separator, or commas
• Case: Switch between lowercase (a-f) and uppercase (A-F)
• 0x prefix: Enable to add 0x before each byte (common in C/C++ and other programming languages)

Changes apply instantly — just toggle the options and the hex output updates immediately.

No, they are different encoding schemes:

• Hex (Base16): Each byte becomes 2 characters (0–9, A–F). Results in 2× expansion. Easy to read byte-by-byte.
• Base64: Each 3 bytes become 4 characters (A–Z, a–z, 0–9, +, /). Results in ~1.33× expansion. More compact but less human-readable.

Hex is preferred for debugging and when byte-level readability matters. Base64 is preferred for data transfer (email attachments, data URIs, JSON binary data) due to its compactness.

A hex dump (or hexdump) is a formatted view of binary data showing:

• The memory offset (address) on the left
• Hex bytes in the middle (usually grouped in 8 or 16 bytes per row)
• An ASCII preview on the right (printable characters shown, others as dots)

A hex string is just the raw hexadecimal digits without address offsets or ASCII preview columns. This tool works with hex strings — you can paste hex bytes from a dump (just the middle column) and it will decode them. You may need to remove the address and ASCII columns first.