What Is the Binary Text Converter?
Encode a text selection as UTF-8 bytes written in binary, or decode those bytes back to text. Every byte is eight bits; a Unicode character can use several bytes. Explicit direction controls keep literal strings such as 01000001 from being decoded by accident. This is text encoding, not encryption or executable machine code.
How to Use the Binary Text Converter
- Choose Text to Binary or Binary to Text before entering the selection.
- For encoding, choose Spaced Binary, Continuous Binary, Prefixed Binary or Binary with Extra Spaces. These are presentations of the same bytes.
- For decoding, provide complete bytes in the documented notation. If an error appears, repair the input or check its original encoding; no partial result is shown.
- Read the full output, then use Copy Binary or Copy Text. If Copy fails, select the output and copy manually. Random supplies a mode-specific fixture; Clear resets input and feedback.
How the Binary Text Converter Works
Encoding uses TextEncoder after checking for unpaired UTF-16 surrogates. It writes each UTF-8 byte as an eight-bit group. The UTF-8 specification describes one-to-four-byte scalar encodings. ASCII values fit in seven bits and use one byte in UTF-8; storing A as 01000001 does not mean every letter needs one byte.
The decoder validates notation first, then uses TextDecoder with fatal error handling. Malformed sequences cause an error instead of replacement characters. A leading U+FEFF is deliberately retained. The helper round trip preserves valid scalar strings within the limits, including source normalization and line-ending characters; textarea and clipboard behavior are separate from that guarantee.
Binary Text Converter Example
| Text or code point | Spaced Binary | Bytes |
|---|---|---|
A, U+0041 | 01000001 | 1 |
é, U+00E9 | 11000011 10101001 | 2 |
Ā, U+0100 | 11000100 10000000 | 2 |
| Grinning face, U+1F600 | 11110000 10011111 10011000 10000000 | 4 |
In Binary to Text, 0b11000011 0b10101001 produces é. Nine-bit input 010000010 is rejected as incomplete bytes. The complete byte 11111111 is rejected as invalid UTF-8. A complete byte sequence can still have the wrong encoding for this decoder.
When to Use the Binary Text Converter
Encoding lessons
Compare an ASCII letter with accented or supplementary characters. Distinguish a code point from its encoded bytes.
Known UTF-8 exercises
Inspect a bounded snippet when its encoding is declared. Other encodings need a decoder that supports them.
Reproducible puzzles
Generate a bit-string clue and tell the reader to decode UTF-8. Encoding alone does not protect confidential information.
Common Mistakes
- Guessing direction from the digits. Choose the mode explicitly; encoding 01000001 treats all eight digits as text.
- Deleting invalid symbols or accepting a partial final byte. Fix the notation instead; the decoder rejects commas, arbitrary punctuation and incomplete groups.
- Assuming all byte sequences are UTF-8. A single E9 byte is not the UTF-8 encoding of é.
- Treating a byte count as a grapheme count or platform character limit. Control characters may be invisible.
Tips for Better Results
Keep the original, declare UTF-8 when sharing and check the complete output. Spaced Binary makes byte boundaries visible. Continuous Binary is compact; Prefixed Binary adds a 0b marker to each byte. Prefixes describe this notation and do not turn the whole result into executable code. Read the Binary Code reference for bit arithmetic and the difference between encoded text and CPU instructions.