Text to Hex Calculator - Encode Text to Hex Bytes

A text to hex calculator turns every character of a text string into its 2-digit hexadecimal byte, so the same word reads as ASCII on the screen and as a hex byte string in source code, log lines, packet captures, and database dumps. The calculator handles any 7-bit ASCII character and reports bytes that fall outside that range so the user can swap to a UTF-8 tool for accented letters, CJK characters, or emoji.

Use this calculator when the destination of the text is something other than a human reader. Print logs, hard-coded byte arrays, low-level protocol headers, color codes, and short identifiers all want the text rendered as hex bytes, and typing the encoding by hand invites off-by-one errors. The calculator gives a quick, reproducible byte string for the same characters every time the form is reloaded, and the byte, character, and hex length counters give a fast cross-check against a documented byte boundary.

• • Building a hex string for a log line: Type the message, pick 0x prefix or contiguous, and copy the byte string into the source code.
• • Encoding a fixed string for a database column or header: Encode a short identifier or magic number once and reuse the same bytes across tests and seed data.
• • Round-tripping a string through the hex to text decoder: Encode a known string, paste the bytes into the matching tool, and confirm the round trip.
• • Reading hex dumps and packet captures: Match a printed log line to its source characters by encoding the same phrase in a known separator and comparing byte-for-byte.

The calculator covers the same 0x00-0x7F range that the existing Hex to Text Converter reads back, so any string that encodes cleanly here will decode cleanly there.

The encoder reads each character of the input string, looks up its UTF-16 code unit, writes the value in base 16, and pads the result to 2 hex digits. The bytes are then joined with the chosen separator and case policy.

• textInput: The text string to encode. Empty string returns an empty hex output with all counts at zero.
• byteFormat: How the bytes are joined: contiguous, space-separated, colon-separated, or 0x-prefixed.
• letterCase: Either keeps the natural case, lower forces a-f, upper forces A-F.
• hexOutput: The encoded hex string in the chosen format.
• byteCount: Number of 2-digit hex bytes in the encoded output.
• characterCount: Number of characters in the text input.
• hexLength: Number of hex digits in the contiguous form (2 times the byte count).

Bytes above 0x7F are skipped and listed in the warning so the user can see exactly which character did not encode; multi-byte UTF-8 characters such as accented letters and emoji have a code unit above 0x7F.

According to ECMA International ECMA-6, the printable ASCII letters occupy the 7-bit codes 65-90 for uppercase and 97-122 for lowercase, which is why 'A' encodes to 0x41 and 'a' encodes to 0x61. The MDN String.fromCharCode reference documents that charCodeAt returns the UTF-16 code unit and fromCharCode builds a string from those code units, the same byte-or-2-byte value the calculator encodes to hex.

Four small ideas explain every result the text to hex calculator shows.

These four ideas line up with what the calculator does: read one character, write its code point in base 16, pad to 2 hex digits, and warn on any byte that does not fit. The ASCII converter reads the matching numeric value for the same character on the same screen, which is useful when the same byte also needs a decimal, binary, or octal code in a spec or table.

Five short steps cover the common workflow without any setup.

1. 1 Type or paste the text: Type the source string in the Text Input box. Letters, digits, punctuation, and whitespace are encoded exactly as they appear; empty input returns an empty hex output.
2. 2 Pick a byte format: Use Space-separated for log lines, Colon-separated for readability, 0x prefix for source code literals, and Contiguous for hash digests and short identifiers.
3. 3 Pick an output letter case: Use Either to keep the natural case. Use Lower to force a-f and Upper to force A-F on every byte.
4. 4 Read the hex output and counts: Hex Output shows the encoded string, Byte Count the number of 2-digit bytes, Character Count the input length, and Hex Length the number of hex digits in the contiguous form.
5. 5 Copy the result or fix the warning: If the warning row reports a skipped character, swap to a UTF-8 encoder for that character or remove it from the input before retrying.

Type Hi! in the Text Input box with Byte Format at Space-separated and Output Case at Either. The Hex Output row reads 48 69 21 and the counts read 3, 3, 6. The same source string also encodes into 0/1 bytes through the matching binary to text converter when the destination needs a bit-level string instead of hex bytes.

A purpose-built text to hex calculator keeps the byte encoding, the case policy, and the separator format in one place.

• • 4 separator formats in one tool: Contiguous, space, colon, and 0x-prefixed bytes share the same selector, covering hash digests, log lines, packet captures, and source code literals.
• • Strict 7-bit ASCII validation: Any character outside the 0x00-0x7F range is skipped and listed in the warning with its code point, so the encoded string never silently drops bytes.
• • Visible byte, character, and hex counts: The counts appear next to the encoded string for a one-step cross-check against a documented byte boundary or header length.
• • Case policy on the output: Either, Lower, and Upper case modes handle natural-case logs, forced-lowercase digests, and forced-uppercase headers with the same selector.
• • Runs entirely in the browser: charCodeAt(0) and toString(16) run on the typed string, so the input never leaves the page and the encoded output updates as soon as a character is typed or removed.

When the encoded string is the start of a base64 message, the matching base64 encoder decoder turns the same byte string into a different alphabet without retyping the source.

Three variables determine what the encoded string looks like, and three limitations tell you when to reach for a different tool.

• • The encoder is 7-bit ASCII only. It does not handle Unicode code points above 0x7F, multi-byte UTF-8 sequences, or emoji. For full Unicode support, swap to a UTF-8 encoder.
• • Bytes above 0x7F are skipped and listed in the warning, but the rest of the input is still encoded.
• • The encoder does not reverse the separator format. A 0x-prefixed output is not recoverable as a contiguous run, so copy the encoded string in the format the destination expects.

According to IETF RFC 4648, base16 (hex) encoding uses the alphabet 0-9 and A-F (case-insensitive), which is why the same byte can be written as 48, 4A, 4a, or 4A and still decode to the same character.

When the encoded string is the payload of a fixed-size message header, the data storage converter turns the byte count into KB, MB, and GB so the storage cost of the encoded string is easy to estimate next to the rest of the file.