Binary Text Converter

How to use Binary Text Converter

1. Paste text to convert it to binary, or binary to convert it back.
2. Separators can be spaces, commas or newlines — all are accepted when decoding.
3. Copy the result.
4. Encoding is UTF-8, so output matches what other correct tools produce.
5. Decoding needs a whole number of eight-bit groups; a truncated stream cannot be read.
6. Everything runs in your browser.

Reading binary by eye

Each group of eight is one byte, most significant bit first. 01001000 is 72, capital H. The ASCII ranges are worth recognising: uppercase letters run 01000001 to 01011010 (65–90), lowercase 01100001 to 01111010 (97–122), and digits 00110000 to 00111001 (48–57). Notice that uppercase and lowercase differ only in the third bit — 65 and 97 are 32 apart, which is a single bit — and that is why older code converted case with a bitwise operation rather than a lookup.

Bytes, not characters

Anything outside ASCII takes more than one byte in UTF-8: two for most accented European letters and Cyrillic, three for Devanagari and CJK, four for emoji. So the number of eight-bit groups is not the number of characters you typed, and a decoder has to reassemble multi-byte sequences rather than treating each group as one character. A converter that got that wrong would turn any non-English text into mojibake on the round trip.

Where this is actually used

Teaching, mostly — seeing text as bits makes character encoding concrete in a way no explanation does. Puzzle hunts and capture-the-flag challenges, where binary is a standard first layer. And occasionally real debugging: when two strings look identical but compare unequal, the binary shows you the byte-order mark, the non-breaking space, or the Windows line ending that you cannot see on screen.