Paste binary code, spaced or in one long string, and read it back as text, with broken bytes flagged honestly instead of padded or guessed.
Your files are processed in your browser, on your own device. Nothing is uploaded to a server.
This binary to text converter reads pasted binary code and turns it back into readable words. Paste the code with spaces between the bytes or as one long unbroken string, and the tool groups the bits into 8-bit bytes on its own, then decodes those bytes as UTF-8 text for you to read.
Paste the code, and read the words.
Text in a computer is stored as bytes, and each byte written in binary is eight digits long. Decoding runs that film backwards: take the bits eight at a time, read each group as a byte, then let UTF-8 turn the bytes back into characters.
A small example makes it plain. The code 01001000 01101001 is two bytes, 72 and 105, and those two bytes are the text “Hi”. Every longer message is the same trick repeated, byte after byte, which is why spacing never matters: the grouping comes from the count, not from the gaps.
UTF-8 does the character work because it is the encoding the web runs on. Plain English letters decode from single bytes, while accented letters and other scripts arrive as pairs, triples or quadruples of bytes that UTF-8 stitches back into one character each.
Decoders earn trust on the bad days, and this one will not pad your code or guess at scrambled output to make a result appear. Two failure cases are handled in the open.
If the bit count does not divide into whole bytes, there is a trailing part byte, and the tool flags it. Some decoders quietly pad that stub with zeros, which invents a character the sender never sent. Here you are told the code is incomplete, so you can go back and copy the missing digits.
If the bytes are complete but not valid UTF-8, you get a plain explanation and a pointer to the hex view on the Binary Translator page, where you can inspect the byte values themselves. Printing scrambled replacement characters as if they were the message would be a lie with good formatting.
That second case often means the code came from an older single-byte encoding, where one byte always meant one character. Such code may not decode cleanly as UTF-8, and the page says so up front rather than blaming your paste.
The decoding runs in your browser alone. Your code is never uploaded or stored, there is no account to make, and no limit on pastes.
Yes. The tool counts the bits and groups them into bytes of eight on its own, so an unbroken string decodes exactly like spaced code, as long as the total bit count divides by eight.
It is the text “Hi”. The first byte, 01001000, is 72, the code for H, and the second, 01101001, is 105, the code for i.
Because the bits do not divide into whole bytes. A leftover stub of digits means part of a byte went missing when the code was copied. The tool flags it instead of padding the gap with invented zeros.
The bytes were whole but do not form valid UTF-8, which usually means they were written under an older single-byte encoding. The hex view on the Binary Translator page lets you inspect the raw byte values instead.
No. Spaces and line breaks are ignored during grouping. Only the digits and their order carry the message.
No. Decoding happens on your device, in the browser. Nothing is uploaded, stored or shared, and you can paste as much code as you like.
Same rules as this one: free, in your browser, with nothing uploaded.
Exact age in years, months and days for any form.
Marks, discounts and change, worked out properly.
Body mass index from height and weight, with its range.
Monthly loan payment, total interest and full cost.
The final price after a discount, and what you saved.
Add or remove GST at the rate your invoice uses.
Add tax to a price or pull it back out.
Work out a tip and split a bill between people.