Quick start
-
Pick mode
Encode or decode.
-
Enter input
Text or hex string.
-
Copy result
Output updates live.
Encode UTF-8 text to hexadecimal or decode hex back to text. Handy for hash bytes, protocol fields, and embedded dev.
Privacy: processed locally, never uploaded.
↓ Paste in the input area below to see results instantly
Convert text to hex and back using UTF-8—handy for binary debugging.
Input
Output
48656c6c6f
Decoding ignores whitespace; length must be even. Processed locally.
Encode UTF-8 text to hexadecimal or decode hex back to text. Handy for hash bytes, protocol fields, and embedded dev.
Pick mode
Encode or decode.
Enter input
Text or hex string.
Copy result
Output updates live.
Hex length must be even; spaces are ignored.
Encode text or bytes to hex and decode back, with spacing and case options for logs and protocol fields.
Use when inspecting HMAC inputs, comparing hash preimages, or debugging encoding mismatches.
When debugging network protocols, developers often convert raw packets to hexadecimal for analysis. For example, capturing a TCP packet containing 'Hello' yields '48656C6C6F' in this tool. Conversely, pasting this Hex value restores the original text.
In embedded systems, device logs often output in Hex format. For sensor data like 0x41 0x42, decoding reveals 'AB'. Note that non-ASCII characters (e.g., Chinese) encode to multi-byte sequences — '测' becomes E6B58B.
Input
Hello
Output
48656c6c6f
Stripped when decoding.
No.
Hex represents each byte as 0-9/A-F (e.g., 'A'=41), doubling size. Base64 uses 64 characters with ~33% size increase, better for binary transfers. Hex is more human-readable for debugging.