FontVibe's Binary Decoder turns binary code back into readable text — paste it however you have it: space-separated 8-bit bytes, comma-separated, or one long block with no separators at all, and it decodes automatically. Unlike a basic converter that only accepts neatly spaced bytes, this decoder auto-detects a continuous run and regroups it into 8-bit chunks (falling back to 7-bit ASCII grouping when needed), so you can decode binary copied from a puzzle, a CTF challenge, or a message someone sent you even when the formatting is messy. Need to go the other way? Toggle the direction to encode text instead.
Most binary-to-text tools expect your input already formatted as neat, space-separated 8-bit bytes — paste anything else and they either error out or return garbage. This one is built to decode binary the way people actually paste it:
- Spaced: `01001000 01101001` — the standard format, decodes directly. - Unspaced: `0100100001101001` — one continuous run, common when binary code is copied from a puzzle or CTF site. Auto-chunked into 8-bit bytes. - Comma- or line-separated: treated the same as spaces. - 7-bit ASCII: some sources omit the leading zero-pad bit; the 7-bit grouping is detected and used automatically.
Whichever format you paste, a small note under the result tells you how your input was interpreted, so you're never guessing.
Need to encode text instead? Head to the full Binary Translator, which handles both directions, or the Binary Code Translator if you also need number bases. Prefer a different code? Try Morse Code Translator or Braille Translator.
Both sides of this tool are plain ASCII: the digits 0 and 1 and spaces going in, ordinary text coming out. Nothing you paste in or copy out will ever show up as a "tofu" box or blank glyph, on any device, browser or app.
That puts it in the same high-compatibility tier as the Morse Code Translator — both rely only on universal ASCII characters rather than a specialised Unicode block. The Braille Translator, by contrast, uses the dedicated Unicode Braille Patterns block (U+2800–U+28FF), which not every system font includes — older Android builds and some app webviews can render it as empty boxes.
For a decoder, though, rendering is rarely the thing that breaks. Input format is: most tools reject anything that isn't perfectly space-separated. The auto-detection here exists specifically to remove that failure point.