Developer utility · binary to text converter
Binary to Text Converter
Decode binary bytes into readable UTF-8 text. Group binary into eight-bit bytes for predictable results, or enter a numeric binary value and review every equivalent format. It is useful for reversing a text-to-binary exercise or inspecting a short byte sequence without uploading it.
Up to 4,096 characters. No value is sent to a server.
Your conversion results will appear here.
Choose an input format, enter a value and select Convert to see binary, decimal, hex, octal and text results.
Use the tool
How to use this converter
- 1
Enter binary digits, grouping them into eight-bit bytes when decoding text.
- 2
Select Convert to validate and decode the UTF-8 bytes.
- 3
Copy the decoded text or any other result format.
Understand the result
How it works
The converter turns binary digits into bytes and passes them through a strict UTF-8 decoder. ASCII bytes such as 01001000 map directly to H, while a multi-byte sequence such as 11000011 10101001 is decoded together as é. Invalid byte sequences are reported instead of being silently replaced with a different character.
Practical notes
How binary bytes become readable text
Start by separating the bit stream into bytes. The sequence 01001000 01101001 becomes the byte values 72 and 105, which decode as H and i. The spaces are only separators; the same bytes can be pasted as 0100100001101001.
UTF-8 is variable-width: a character can occupy one to four bytes. A leading byte tells the decoder how many continuation bytes belong to the same character. The complete sequence must be present for decoding to succeed.
Practical notes
Why invalid UTF-8 is shown as an error
An arbitrary byte is still a valid number even when it is not valid text. For example, FF is a legitimate hexadecimal byte and 11111111 is a legitimate binary byte, but neither is a standalone valid UTF-8 character. RadixLab keeps the Binary, Decimal, Hex and Octal results and labels only the Text result as invalid.
This avoids quietly inserting the Unicode replacement character, which could make damaged or incomplete data look like a successful decode. When the input is intended to be ASCII or UTF-8 text, an explicit error is more useful than a guessed character.
- Use eight bits per byte for predictable text decoding.
- Keep all bytes in a multi-byte character together.
- Treat an invalid UTF-8 message as a byte-sequence issue, not as a failed binary-to-decimal conversion.
Quick reference
Examples
01001000 01101001
Hi
H followed by i
01000001
A
One UTF-8 byte
11000011 10101001
é
Two-byte UTF-8 sequence
Common questions
FAQ
How should binary text be grouped?
Use eight binary digits per byte, such as 01001000 01101001 for Hi.
What happens when binary is not valid UTF-8?
The converter shows a clear invalid UTF-8 error instead of claiming that replacement characters are the original text.
Can binary-to-text decode Unicode?
Yes, as long as the input bytes form a valid UTF-8 sequence.
Can I enter binary without spaces?
Yes. Spaces are ignored, but grouping the input into eight-bit bytes makes the text boundary easier to inspect.
Why does 11111111 not decode to a character?
It is a valid binary byte and equals 255, but it is not a complete valid UTF-8 sequence. The Text result reports INVALID_UTF8 while the numeric results remain available.