Translates text to binary and binary back to text. The input is validated before decoding, so malformed binary is reported rather than turned into nonsense.
Text is encoded to UTF-8 first and each byte is written as eight binary digits, which means a character outside the basic Latin range produces two, three or four groups rather than one. Decoding reverses that: the input must contain only zeros, ones, spaces and line breaks, its length must be a multiple of eight, and the resulting bytes must form valid UTF-8. Each of those three conditions is checked separately and reported separately, because "that did not work" is not useful and knowing which rule failed usually points straight at the cause.
Working with binary text
-
One character is not always one byte:
UTF-8 uses one byte for basic Latin and up to four for other scripts and emoji, so the group count exceeds the character count for anything but plain English.
-
Length must be a multiple of eight:
a truncated paste is the usual reason it is not, and the error names that specifically rather than failing silently.
-
Not every byte sequence is valid text:
UTF-8 has structural rules, and bytes that break them are rejected instead of producing replacement characters.
-
Binary is not encryption:
it is the same information in another base, reversible by anyone in seconds and offering no confidentiality whatsoever.
Why decoding checks three things separately
The [msm_tool slug="binary-translator"] validates input before attempting to decode it, checking that it contains only zeros, ones, spaces and line breaks, that its length is a multiple of eight, and that the resulting bytes form valid UTF-8 — each condition checked and reported on its own, because "that did not work" points nowhere useful while knowing which specific rule failed usually points straight at the cause.
Bytes, not code units
Text is converted to UTF-8 bytes before encoding, which is a different unit from the UTF-16 code units the Binary/Hex Converter works with — the same emoji comes out as four groups here rather than two, because UTF-8 represents it as four bytes while UTF-16 represents the identical character as two code units. Both counts are correct; they simply describe different underlying encodings of the same character.
One character is not always one byte
UTF-8 uses a single byte for basic Latin characters and up to four bytes for other scripts and emoji, so the number of eight-digit groups in the output exceeds the character count for anything beyond plain English — a short line of mixed-script text can produce noticeably more groups than its character count would suggest.
Not every sequence of bits is valid text
UTF-8 has structural rules governing which byte sequences are legal, and bytes that violate those rules are rejected outright rather than silently turned into replacement characters or mangled output. A length that is a proper multiple of eight is necessary but not sufficient on its own — the bytes still have to actually form valid UTF-8 once assembled.
A representation, not a form of protection
Binary is the same information written in a different base, reversible by anyone within seconds and offering no confidentiality at all. Encoding something as binary hides it from a casual glance and nothing more substantial than that.