Convert text to hexadecimal

Text and hexadecimal are two useful views of the same UTF-8 data. Decode mode deliberately rejects odd-length strings, non-hexadecimal characters, and byte sequences that are not valid UTF-8, preventing silent padding or replacement characters from changing the original information.

Convert readable text into hexadecimal bytes

Choose encode mode and enter the exact text you want to inspect or transport. Encode is the default, so a request containing only the text field is enough for the common text-to-hexadecimal operation. The converter serializes the JavaScript string as UTF-8 and writes every resulting byte as exactly two lowercase hexadecimal digits.

For example, basic Latin letters usually occupy one byte each, while accented characters, non-Latin scripts, and emoji use multiple bytes. That distinction matters because hexadecimal represents encoded bytes, not visual characters or abstract Unicode code points. The response includes the original text, the continuous hex string, the number of UTF-8 bytes, the resolved mode, and the encoding name.

Preserve whitespace in the input when it matters: spaces, tabs, and line breaks are data and therefore receive their own byte values. An empty string is also valid and produces an empty hexadecimal string with a byte count of zero. Since the algorithm uses no network, clock, random value, or external state, repeated requests with the same string always return precisely the same result.

Decode hexadecimal safely back into UTF-8 text

Choose decode mode when the input field contains hexadecimal bytes rather than readable text. Supply one continuous string made only from digits zero through nine and letters a through f; uppercase letters are accepted and normalized to lowercase in the response. The converter first checks that the string has an even number of characters because every byte requires a complete pair of hexadecimal digits.

A value with three, five, or any other odd number of digits is rejected rather than guessed, padded, or truncated. It then rejects punctuation, prefixes, whitespace, separators, and letters outside the hexadecimal alphabet. These strict rules make malformed data visible and keep automated pipelines predictable.

Once parsing succeeds, the bytes are decoded with a fatal UTF-8 decoder. A byte sequence that cannot represent valid UTF-8 text returns an input error instead of inserting replacement symbols that could conceal corruption. The empty hexadecimal string is a valid zero-byte value and decodes to empty text.

If your source includes spaces or a leading zero-x marker, remove those decorations before submitting it.

Use deterministic conversion in tools and automated workflows

Use the browser form for quick debugging, teaching, copy-and-paste conversions, or checking what a visible string looks like at byte level. A practical test suite should include a plain ASCII example, a multibyte Unicode example, a successful reverse conversion, and at least one odd-length or illegal-character failure. Assert the byte count as well as the text and hex fields, because character length and UTF-8 byte length are not interchangeable.

Treat the conversion as an encoding view, not encryption: hexadecimal does not hide content, authenticate a sender, compress a message, or protect secrets. Anyone can reverse it. It is best used wherever exact byte visibility and reversible formatting are needed, including protocol documentation, database migrations, log analysis, interoperability checks, educational demonstrations, and troubleshooting discrepancies between systems.