Hex Encoder/Decoder converts text to its hexadecimal byte representation, or hex back to text, in your browser, so you can read or construct binary-looking values by hand.
How to read the result
The output is one continuous lowercase hex string, two digits per byte. Decoding ignores spaces and line breaks, expects an even number of hex digits and reports an error otherwise, or when the bytes are not valid UTF-8 text.
Defender tips
- Hex dumps make it easier to compare a payload you are testing against what shows up in logs, packet captures or a debugger, where binary data is usually rendered in hex already.
- When reading protocol fields (a magic number, a length prefix, a flag byte), hex is often faster and less error-prone than trying to interpret raw bytes as text.
FAQ
Does case matter (uppercase vs lowercase hex)?
No, both represent the same value. Decoding accepts either; the encoded output is always lowercase.
What character encoding is assumed for text?
UTF-8, which covers plain ASCII input identically to older single-byte encodings but also correctly represents multi-byte characters.
Why does decoding an odd-length string fail?
Hex represents whole bytes as pairs of digits; an odd number of digits cannot map to whole bytes, so it is rejected rather than silently guessed.