بائنری مترجم

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.