Binary to Text
Binary to Text trims the input, splits it on whitespace, requires every token to contain exactly eight binary digits, and decodes the resulting bytes as UTF-8. There is no continuous-bitstream mode or separator other than whitespace. Malformed UTF-8 may display replacement characters instead of raising an error.
Runs locally — files stay on your deviceCan I paste one continuous string of bits?
Not for multiple bytes; each eight-bit group must be separated by whitespace.
Byte framing must be explicit
Binary digits become text only after they are grouped into bytes and interpreted with a character encoding.
How it works
Whitespace defines tokens, a regular expression validates exactly eight 0/1 digits per token, and TextDecoder interprets the byte array as UTF-8.
Key concepts
Whitespace is required between bytes
Spaces, tabs, or line breaks can separate groups.
UTF-8 sequences span groups
Several bytes can form one character.
When to use it
- Decode output from Text to Binary.
- Read a small UTF-8 byte sequence.
- Check a teaching example with explicit byte groups.
When not to use it
- Do not use variable-width groups.
- Do not expect ASCII-only validation.
- Do not assume replacement-free UTF-8.
Worked examples
ASCII A
- Input
01000001- Expected output
A
One byte maps directly.
Romanian ă
- Input
11000100 10000011- Expected output
ă
Two groups form one UTF-8 character.
Seven bits
- Input
1000001- Expected output
Error
Every token must have eight digits.
Common mistakes
Omitting separators
A 16-bit token fails validation. Correction: Insert whitespace every eight bits.
Using 2 prefixes
0b syntax is unsupported. Correction: Provide only bits.
Ignoring �
Bytes were invalid UTF-8. Correction: Verify source encoding.
Best practices
- Keep exact eight-bit framing.
- State the source character encoding.
- Treat decoded content as untrusted.
Related operations and differences
Base64 Decoder
Choose Base64 Decoder when you need to decode Base64 into readable text.; use Binary to Text specifically for binary decode.
Hex to Text
Choose Hex to Text when you need to decode hexadecimal bytes into text.; use Binary to Text specifically for binary decode.
Text to Binary
Choose Text to Binary when you need to encode text as 8-bit binary groups.; use Binary to Text specifically for binary decode.
Base64 Encoder
Choose Base64 Encoder when you need to encode text as Base64 in your browser.; use Binary to Text specifically for binary decode.
ROT13 Decoder
Choose ROT13 Decoder when you need to decode ROT13 text locally.; use Binary to Text specifically for binary decode.
Text to Hex
Choose Text to Hex when you need to encode UTF-8 text as hexadecimal.; use Binary to Text specifically for binary decode.
Limitations and privacy
- Whitespace-separated eight-bit groups only; no continuous stream, 0b prefixes, alternate charset, strict UTF-8 mode, binary file output, or partial recovery.
The entered value is transformed locally in this browser and is not sent to the Toolbox server.
Copying or pasting sensitive output into another service is a separate disclosure decision.
Frequently asked questions
Can line breaks separate bytes?
Yes.
Can groups contain fewer than eight bits?
No.
Why is � shown?
The bytes did not form valid UTF-8.
Is empty input accepted?
No, it produces an invalid empty group.