Text to Binary Converter

Type or paste text into the input panel. Conversion happens immediately, so there is no Convert button and no file upload step.

The UTF-8 binary panel shows one eight-digit group for every encoded byte. Use its copy control to copy the complete binary sequence, including spaces between byte groups.

The hexadecimal section shows the same bytes in base 16. Open the character and byte inspector when you need to see which Unicode code point produced each sequence.

ASCII covers 128 values and assigns one byte to familiar English letters, digits, punctuation, spaces, and control characters. UTF-8 preserves those same byte values, so ASCII text produces the expected one-byte binary codes.

The difference appears when text contains characters outside ASCII. Accented letters, Greek, Arabic, Devanagari, Chinese characters, symbols, and emoji are encoded as valid multi-byte UTF-8 sequences rather than being removed, replaced with an arbitrary question mark, or forced into an eight-bit ASCII table.

This is why the tool can serve common ASCII-to-binary searches while still producing correct Unicode output for modern text.

Unicode assigns an abstract code point to each encoded character. UTF-8 serialises each valid Unicode scalar value as a sequence of one, two, three, or four bytes.

Code points in the ASCII range use one byte. Higher code points use additional bytes, with leading-bit patterns that identify the first byte and continuation bytes.

The converter passes the string to TextEncoder and displays the resulting Uint8Array directly, so the output reflects the browser's UTF-8 encoding rather than a hand-maintained lookup table.

Surrogate code points are not Unicode scalar values and cannot be encoded directly in well-formed UTF-8. If the JavaScript string contains an unpaired UTF-16 surrogate, TextEncoder replaces it with U+FFFD and the interface reports that replacement.

Binary and hexadecimal are two representations of the same byte sequence. A byte such as hexadecimal 48 is binary 01001000; changing the number base does not change the encoded data.

The UTF-8 byte count measures encoded storage length. The bit count is always eight times that byte count because every displayed group represents one byte.

The interface's Code points metric counts Unicode scalar values after TextEncoder's lone-surrogate replacement step. It can differ from both byte count and the number of visible symbols a person perceives on screen.

Open the inspector to map each input code point to its Unicode notation, hexadecimal UTF-8 bytes, and binary UTF-8 bytes.

This is useful when a word contains a mix of one-byte ASCII characters and multi-byte Unicode characters, or when two pieces of text look similar but produce different bytes.

For performance, the table shows at most 200 code points. The main binary and hexadecimal outputs still include every byte from the accepted input.

These terms describe different layers of text. A Unicode code point is an assigned numeric value such as U+0041 for A. JavaScript strings are internally organised as UTF-16 code units. UTF-8 is the byte encoding produced by this converter.

A user-perceived character, formally called an extended grapheme cluster, can contain more than one code point. For example, a letter followed by a combining accent can display as one symbol while the inspector shows two rows.

Some emoji sequences also join several code points with variation selectors or zero-width joiners. The tool intentionally exposes the underlying code points and bytes instead of pretending every visible symbol is one encoded value.

Whitespace is encoded data. A space produces byte 20 in hexadecimal, a horizontal tab produces 09, and a line feed produces 0A.

The input panel preserves line breaks. The Lines metric recognises LF, CRLF, and CR separators, while the inspector gives common invisible characters readable labels.

Invisible differences matter when debugging source files, copied text, protocols, command output, and data that fails an exact byte comparison.

Unicode can represent visually similar text with different code-point sequences. The precomposed character é uses U+00E9 and encodes as C3 A9 in UTF-8.

The decomposed sequence e followed by combining acute accent uses U+0065 U+0301 and encodes as 65 CC 81. The two versions can look alike while differing in code-point count, byte count, hexadecimal output, and binary output.

The converter does not normalise text before encoding. It preserves the sequence represented by the JavaScript input so users can observe those differences.

Students can compare letters, numbers, spaces, accented text, scripts, and emoji to understand variable-width character encoding.

Developers can verify UTF-8 examples, inspect copied text, compare a known hex dump, prepare test fixtures, or explain why a database, file, API, or protocol reports a specific byte length.

The tool is an encoder and teaching aid. It is not encryption, compression, hashing, a binary file viewer, or a way to hide sensitive information.

The text field accepts up to 10,000 UTF-16 code units. This browser-level length can differ from the displayed code-point count because supplementary Unicode code points use two UTF-16 code units.

A 10,000-unit input can produce substantially more than 10,000 UTF-8 bytes when it contains multi-byte characters. Binary output is therefore placed in a scrollable region rather than expanding without limit.

Binary and hexadecimal have separate copy controls. Copying writes only the selected output to the clipboard and does not submit the input to a server.

Encoding uses TextEncoder inside the browser. The tool does not send text to an API, create an account record, upload a file, or place the input into a shareable URL.

The page calculates output from the current input state. Clearing the field removes the visible input and derived results from the component.

Browser extensions, clipboard managers, device policies, and the browser itself are outside the tool's control, so avoid processing secrets on devices or browsers you do not trust.