Convert text to its binary representation or read binary back as text. Eight bits per byte, UTF-8 throughout, with the byte count shown beside the characters.
Waiting for text
Text is encoded as UTF-8 bytes, then written in binary. The answer depends on the encoding, so this one is named.
The result appears here
Every byte of the UTF-8 encoding, written in binary.
Binary to Text runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Every byte written as eight bits, and every byte produced by encoding the text as UTF-8. The encoding is named for the same reason it is named on the hex converter: the binary of a string is undefined until you say how the string becomes bytes, and the answer for anything outside ASCII differs sharply between encodings.
Eight bits per byte, always, including the leading zeros. A capital A is 01000001 rather than 1000001. The leading zeros are not decoration — they are what makes the stream readable in fixed-width groups and what lets a decoder know where one byte ends and the next begins. Dropping them is the single most common reason a binary string will not decode.
Which is why a bit count that is not a multiple of eight is rejected with the count rather than padded. Padding would produce a plausible result from a damaged input, and a plausible wrong answer is the worst kind.
Decoding ignores spaces, colons, commas, hyphens and underscores between groups, so a stream copied with any grouping at all works. Anything else — a stray letter, a two, a full stop — is an error, because binary is only zero and one and silently skipping a character would change the bytes.
Decoding is strict about UTF-8 as well: bytes that are not a valid sequence are refused rather than decoded with replacement characters. Nothing is uploaded, and the conversion runs entirely in the page.
Because a byte is eight bits and the leading zeros are part of it. Writing A as 1000001 instead of 01000001 breaks the fixed width that lets a decoder find the byte boundaries, and it is the usual reason a binary string will not decode.
Either it contains something other than zero, one and a separator, or the bit count is not a multiple of eight. Both are reported with the reason. A count that is not a multiple of eight usually means a leading zero was dropped from one group.
UTF-8. For plain ASCII that is one byte per character; for accented letters, other scripts and emoji it is two to four, which is why the byte count can be several times the character count.
No. The bytes are decoded strictly as UTF-8, so anything that is not a valid sequence is refused rather than turned into replacement characters. For inspecting arbitrary bytes, the hex converter is the better view.
No. This writes bytes as the characters zero and one, which is a readable representation of them. A binary file contains the bytes themselves, and is several times smaller as a result.
No. The conversion runs in your browser and nothing is sent to a server or to analytics.