About Binary to Text
Binary to text groups a bit string into eight-bit chunks, turns each chunk back into its byte, and interprets the resulting byte sequence as UTF-8. It is the inverse of Text to Binary, and it is the tool you reach for when you have a bit pattern in front of you and need to know what it says.
The eight-bit grouping is the only part that requires judgement. Most binary dumps insert spaces between bytes, which makes the boundaries explicit; when the input arrives as one unbroken string of digits, the tool splits it every eight bits from the left, which is the convention that matches how the data was originally written.
The practical value is in diagnosing text that has already gone wrong. When a file renders as mojibake, converting the bytes back to binary and checking them group by group shows whether the problem is a wrong byte, a broken multi-byte sequence, or simply text that was never UTF-8 to begin with.
How to use Binary to Text
- 1 Paste the binary digits, with or without spaces between bytes.
- 2 Read the recovered text, which replaces the output area as soon as the input parses.
- 3 If the result is unreadable, check whether the grouping is correct — an off-by-one shift changes every character.
Frequently asked questions
The output is unreadable. What went wrong?
Usually the split point. If the bit string was not grouped on byte boundaries from the start — for example a leading bit was dropped somewhere — every subsequent group is shifted and every character decodes wrongly. Verify the total bit count is a multiple of eight.
Why did three groups produce one character?
Because that character is three bytes long in UTF-8. Non-Latin scripts expand to multiple bytes per character, so the number of groups reflects the byte count of the UTF-8 encoding rather than the number of visible characters.
Can it handle a bit string without any spaces?
Yes. The digits are split every eight from the left, which reproduces the original byte sequence as long as the string starts on a byte boundary and nothing was inserted or removed.
What is the difference between binary here and binary in a file?
None in principle — both are sequences of bytes. The difference is only in presentation: here each byte is written out as its eight binary digits in text form so it can be read and edited by eye.
Free, online, and private
Free to use
Binary to Text is completely free. There is no account to create, no login, and no hidden charge or usage limit.
Runs online in your browser
It is a free online tool that runs entirely in your browser. Nothing to download or install — open the page and start using it right away.
Your data stays private
All processing happens locally on your device. Your input is never uploaded, stored, or tracked, so it never leaves your browser.
How Binary to Text behaves in detail
These are the specifics of this implementation — the exact ranges, defaults and fixed settings you are working with.
| Parameter | Value |
|---|---|
| Token pattern | greedy runs of hex digits (0-9, a-f, A-F) |
| Value ceiling | 255 — a larger token is dropped from the byte stream entirely |
| Digit grouping | not enforced: 1001000 and 01001000 both decode to the byte 72 |
| Byte decoding | TextDecoder as UTF-8, so invalid sequences become replacement characters |
| Separators | any non-hex character works as a separator, and none is required |
Compiled from the implementation of this tool and checked against it by itoolnet.
What Binary to Text does not do
Knowing the edges of a tool saves more time than another list of its features. These are the cases where it will not do what you might expect.
- The token pattern is greedy and no grouping rule is enforced, so eight-bit groups typed without spaces are read as one long number: 0100100001101001 exceeds the 255 ceiling and is discarded, leaving empty output instead of Hi.
- Bytes are decoded as UTF-8, so a stream that was never UTF-8 — Latin-1, GBK, or binary data — comes back as U+FFFD replacement characters. The original bytes cannot be recovered from what this tool prints.
- A token such as 210 begins with a digit that is invalid in base 2, so parseInt returns NaN, the filter drops it and the output simply gets shorter. Mistyped binary therefore fails silently rather than raising an error.
Tested and documented by itoolnet, the team that builds and maintains this site.