8-bit aligned · UTF-8 decode

Decode binary back to text

Convert 0s and 1s back to UTF-8 text. Strips whitespace automatically — input must be a multiple of 8 bits.

Binary → Text Workspace
Input size
98 B
88 bits
Decoded chars
11
UTF-8
Bytes
11
/ 8
Status
OK
8-bit aligned
input · binary
output · text
Hello world
Quick Start

How to decode binary

Strips whitespace, splits into 8-bit groups, decodes as UTF-8.

  1. 01

    Paste binary

    Any whitespace separator works.

    Tokenisation is Unicode-aware via \p{L}\p{N} property classes — so accented letters, ideographs, and emoji code points all count correctly.

    bitsUTF-8Unicodecode pointslive
    input · textraw · UTF-8
    01001000
    loaded · UTF-8UTF-8 · ready
  2. 02

    Auto-grouped

    Whitespace stripped, then chunked 8 bits at a time.

    Live re-counts run on every keystroke through a memoised reducer, so even multi-megabyte inputs stay smooth in the editor.

    8-bitlivememoisedoptionssnappy
    groups · optionsbytes · live
    01001000 → H
    options applied · livelive
  3. 03

    UTF-8 decoded

    Bytes are decoded as UTF-8 — multi-byte characters work.

    Output preserves the original line endings (\n vs \r\n) and trailing whitespace is reported separately so you can spot diff-only changes.

    UTF-8line endingswhitespacediff-cleanreproducible
    decode · countedtext · ready
    Hello world
    counted · livecounted
  4. 04

    Copy or download

    One click.

    Copy writes via the Async Clipboard API; downloads ship as text/plain; charset=utf-8 — nothing leaves your tab.

    copyclipboardtext/plainblobclient-side
    export · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Text-processing fundamentals worth knowing

Tokenise with Unicode classes

Use \p{L}\p{N} with the u flag so accents, ideographs, and emoji count properly.

Normalise line endings

Convert \r\n to \n before diffing or hashing — Windows-vs-Unix endings produce phantom changes.

Mind invisible characters

Zero-width joiners, BOMs, and non-breaking spaces look identical to ASCII space. Strip them before comparison or storage.

Stream don’t slurp

For multi-megabyte text, iterate line-by-line rather than loading everything to memory — keeps the tab responsive.

Choose collation deliberately

Default JS sort is code-point order, not human alphabetical. Use Intl.Collator for locale-aware sorting.

Re-run after normalisation

NFC vs NFD changes byte length but not visible glyphs. String.prototype.normalize() before counts and comparisons.

Use Cases

When to decode binary

Educational, debugging, or just for fun.

CTF challenges

Decode binary clues in capture-the-flag. Tokenisation uses Unicode property classes (\p{L}, \p{N}) with the u flag so accents, ideographs, and emoji code points all count correctly. Surrogate-pair-aware counts mean 🚀 weighs 1, not 2.

Unicode-correct

Teaching

Demonstrate how text becomes bytes in CS classes. Result updates as you type — paste and watch totals settle in milliseconds even on multi-megabyte inputs. Heavy work runs through a memoised reducer so the editor never janks.

diff-clean

Byte-level debugging

Confirm encoding correctness when inspecting buffers. Output normalises line endings to LF for clean diffs across platforms. Windows-vs-Unix CRLF mismatches disappear, which keeps git blame honest and review comments focused on real changes.

instant counts

ASCII art reversal

Decode binary ASCII art puzzles. Code-point counts are stable across NFC/NFD normalisation. Pair with the Reading Time Calculator to layer scan-time on top of raw counts, useful for editorial budgets and SEO meta-description limits.

platform-aware

Curiosity

See what a phrase looks like in binary. All processing runs client-side — paste sensitive or pre-publish copy without it leaving the tab. The clipboard API writes UTF-8 text/plain so it survives transit to any editor or CMS.

code-point-accurate

Round-trip test

Verify Text → Binary → Text returns identical input. Same input plus same options always produces identical output, so the tool is safe to embed in CI scripts or doc-generation pipelines without race conditions.

lossless
FAQ

Frequently asked questions

Any whitespace — single space, multiple spaces, tabs, newlines. All non-0/1 characters are ignored.
Returns an error. Make sure each byte is 8 bits long.
Yes — runs through TextDecoder('utf-8') which handles continuation bytes correctly.
No. All decoding runs locally.
For Base64 / Hex / URL encoding, see the Encoding category.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!