Input
Mode:
Output
Formatted result will be displayed here
Hex encoding serializes each byte of input as two hexadecimal characters, producing a printable representation of arbitrary bytes without loss. For text, the bytes are the UTF-8 encoding of each character, so every codepoint maps deterministically to one or more byte pairs. This tool emits lowercase hex without separators by default, and it can insert spaces or colons if you need a format that is easier to read by eye.
Convert a textual sample into the hex bytes a byte-level protocol expects, then paste into a wire test harness.
Ciphers usually take hex-encoded input. Encode your plaintext first to keep test inputs free of whitespace ambiguity.
Seeing the exact bytes clarifies whether a mojibake issue is UTF-8 vs Latin-1 or something more exotic.
Embedded tooling often accepts hex dumps. Prepare firmware payloads by encoding a readable text template.
No for decoding; upper and lower case hex digits are both accepted. Encoding defaults to lowercase for consistency with most dumps.
Exactly twice the byte length of the input, since each byte becomes two hex characters. UTF-8 multi-byte characters therefore grow several-fold.
Yes, toggle space or colon separators to mimic xxd or wireshark style dumps for easier reading.
The tool reads input as text. For real binary data, upload to a dedicated hex viewer or run xxd locally.