Binary to Text

What Binary to Text helps you do

Decode 8-bit binary groups back into UTF-8 text, ignoring spaces and separators. It is the reverse of text-to-binary and lets you read a binary string produced elsewhere. It is useful for fixtures, puzzles and bit-level debugging where the bytes are easier to inspect as text.

Decoding runs locally in your browser with no upload to Haivix.

How it works

Every character that is not 0 or 1 is removed, so separators do not matter. The remaining bits are split into bytes of eight, converted to numbers, and decoded as UTF-8. A bit count that is not a multiple of eight fails rather than guessing, and invalid UTF-8 sequences are reported instead of producing replacement characters.

How to use Binary to Text

1. Paste the binary groups, with or without separators.
2. Decode them into UTF-8 text.
3. If the tool reports a length error, check for a missing or extra bit.
4. Copy the recovered text.

When to use it

• Decode a binary string from a fixture or a puzzle.
• Verify that an encoder produced the expected bytes.
• Read a bit pattern as text when debugging.
• Recover a message from a binary-only field.
• Check the UTF-8 bytes behind a character.
• Compare an encoder's output with a known sample.
• Decode a short message hidden in a binary-only form.
• Check a byte sequence from a protocol trace.

When not to use it

• Do not use it for arbitrary binary files; it expects UTF-8 text bytes.
• Do not expect it to accept a bit count that is not a multiple of eight.
• Do not use it for compressed or encrypted data that is not text.

Example

The byte 01000001 decodes to the letter A. A longer string such as 01001000 01101001 decodes to Hi, and separators can be spaces, newlines or omitted entirely. An accented character occupies more than one byte in UTF-8, so it appears as several binary groups that must be kept together. If one bit is missing, the length check fails instead of silently shifting every later byte.

What you can do with Binary to Text

• Accept binary with or without spaces and line breaks.
• Group the bits into 8-bit bytes automatically.
• Decode the bytes as UTF-8 text.
• Reject a bit count that is not a multiple of eight.
• Report invalid UTF-8 instead of showing mojibake.
• Keep the input in the browser.
• Accept binary copied from a log or a fixture.
• Reject a truncated byte instead of guessing.

Example: read a binary fixture

Paste the binary string exactly as the fixture provides it. Spaces, newlines and other separators are ignored, so the grouping does not need to be perfect.

Decode and read the text. If the tool reports an invalid length, a bit was lost in the copy; compare the character count with the source.

Use the text-to-binary tool in the other direction to confirm a clean round trip.

What to know before you start

• Input length must be a multiple of eight; the tool does not pad or discard extra bits.
• It assumes UTF-8 byte sequences, so other encodings may not decode correctly.
• It is not a general binary-file decoder.
• It does not display hexadecimal or decimal values alongside the text.
• Very large inputs are limited by browser memory.

Common mistakes

• Pasting a bit count that is not a multiple of eight and assuming the decoder will pad it.
• Using UTF-16 or another encoding and expecting UTF-8 output.
• Dropping a leading zero when copying a byte.
• Treating the decoded text as safe to execute or trust.
• Assuming separators are required; they are ignored.
• Pasting a binary value with the leading zero stripped by a spreadsheet.
• Expecting the tool to repair a truncated byte.

Troubleshooting

If the tool reports a length error, count the bits. A missing zero is the usual cause.

If decoding fails on the UTF-8 step, the bytes may represent binary data rather than text.

If the text looks wrong, confirm that the source used UTF-8 and not Latin-1 or UTF-16.

If a character is missing, check whether the source used a multi-byte sequence that was copied partially.

If the output contains a replacement character, the bytes were not valid UTF-8; the source may be compressed or encoded differently.

If the text is unreadable, try the reverse tool to see what the encoder expected.

If the byte groups do not align, check for a missing leading zero in the source; the decoder does not re-align them.

Related standards and documentation

• UTF-8 is defined by the Unicode standard and RFC 3629.
• Each byte is eight bits; the tool does not guess a different width.