The Binary to Text Converter decodes space-separated 8-bit binary groups into UTF-8 text, and encodes text back into binary, showing every byte three ways as it goes: its binary form, its decimal value, its hexadecimal value, and the character it represents. It is built for the moment a log, a puzzle, a CTF challenge, or a homework problem hands you a wall of ones and zeros and you need to know what they say.
How It Works
In binary-to-text mode, each group must be exactly eight bits; the groups parse as base-2 integers (bytes), and the byte sequence is then decoded as UTF-8 with strict error checking, so an invalid sequence is rejected rather than silently mangled. In text-to-binary mode, your text is encoded to its UTF-8 bytes, each byte is printed as eight binary digits with leading zeros, and the groups are joined with spaces.
Worked examples
Decoding 01001000 01101001 returns Hi: 01001000 is decimal 72, hex 48, the letter H; 01101001 is decimal 105, hex 69, the letter i. Encoding runs the same table backwards. The example that teaches the most is a non-English character: é is two bytes in UTF-8 (C3 A9), so it encodes as 11000011 10101001, two binary groups for one visible character, and the euro sign € takes three bytes (E2 82 AC), 11100010 10000010 10101100. This is why the breakdown table exists: for plain ASCII, bytes and characters are the same count, and the moment they diverge, the table shows you exactly where and why.
Reading the breakdown table
Each row is one byte. The decimal column is the byte's value (0 to 255), the hex column is the same value in base 16 (the form programmers usually quote), and the character column shows the printable ASCII glyph for bytes 32 to 126 and a middle dot for everything else, including the continuation bytes of multi-byte UTF-8 characters, which have no standalone glyph. When a pasted message decodes into gibberish dotted with middle dots, the usual diagnosis is that the bytes were never UTF-8 text at all: they may be a different encoding (Latin-1 text decodes wrong precisely this way), UTF-16 data with its tell-tale alternating zero bytes, or raw binary from a file, none of which this converter claims to interpret.
Input rules and the errors they produce
The converter is deliberately strict, because silent correction hides real problems. Groups of any length other than eight are rejected (a stream of bits without spaces must be split into bytes yourself first, since a missing or extra bit anywhere shifts every boundary after it); characters other than 0, 1, and whitespace are rejected; and byte sequences that are not valid UTF-8 are rejected with that specific message rather than decoded approximately. That strictness is the difference between a converter and a guesser: an encoding error upstream should surface here, loudly, instead of propagating as corrupted text.
Where binary text actually appears
Nobody writes prose in binary, so the inputs that reach this tool come from machines and teaching: protocol dumps and packet captures learning exercises, embedded and IoT logs, QR and barcode payload inspection, steganography and CTF puzzles (where binary is often a layer over Base64 or hex, so a decode that yields more encoded-looking text is progress, not failure), and computer-science coursework on number systems, for which the sibling Number Base Converter on this site handles the general case. If your binary decodes to hex-looking text (pairs like 48 65 6C), decode that hex layer next; layered encodings are the norm in puzzles precisely because each layer is trivial alone.
Limitations
A byte-level UTF-8 text converter, not a binary file tool: it does not detect encodings, interpret file formats or headers, handle UTF-16 or legacy code pages, or accept unspaced bit streams. Very large pastes are bounded by the browser. Nothing you enter is uploaded or stored; conversion happens locally.
Frequently Asked Questions
Why must the groups be exactly 8 bits?
Because a byte is the unit of text encoding: UTF-8 is defined over bytes, so the converter needs byte boundaries to decode. Seven-bit groupings belong to historical ASCII transmission formats, and regrouping them into eights is a manual step that changes the meaning entirely.
My binary decodes to nonsense characters. What is wrong?
Most often the source was not UTF-8: it may be a different character encoding, compressed or encrypted data (which looks random by design), or the bits may be shifted by one position from a dropped digit, which garbles everything downstream of the error. Check the source's stated encoding first.
Can it convert a binary file, like an image?
No. It converts text expressed as binary digits. An image file's bytes include non-UTF-8 sequences that the strict decoder rejects, by design. File-to-text encodings such as Base64 (see the Image to Base64 tool) are the right vehicle for binary files.