Convert text to binary
Encode any text (including emoji and accented chars) as 8-bit binary groups. UTF-8 encoded under the hood.
01001000 01100101 01101100 01101100 01101111 00100000 01110111 01101111 01110010 01101100 01100100
How to convert text to binary
Encodes via UTF-8 then formats each byte as an 8-bit string with leading zeros.
- 01
Paste text
Anything — ASCII, Unicode, emoji.
Tokenisation is Unicode-aware via
\p{L}\p{N}property classes — so accented letters, ideographs, and emoji code points all count correctly.textUTF-8Unicodecode pointsliveinput · textHello · UTF-8Hi
loaded · UTF-8UTF-8 · ready - 02
UTF-8 encoded
Each character becomes 1-4 UTF-8 bytes.
Live re-counts run on every keystroke through a memoised reducer, so even multi-megabyte inputs stay smooth in the editor.
UTF-8livememoisedoptionssnappybytes · optionsencoded · live72 105
options applied · livelive - 03
Bytes → bits
Each byte becomes 8 binary digits with leading zeros.
Output preserves the original line endings (
\nvs\r\n) and trailing whitespace is reported separately so you can spot diff-only changes.8-bitline endingswhitespacediff-cleanreproduciblebits · counted8-aligned · ready01001000 01101001
counted · livecounted - 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-sideexport · copiedready · done✓ Copied
shipped · ready to shipsuccess
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.
When to encode binary
Education, puzzles, debugging.
Teaching
Show how chars become bytes in CS101. 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-correctCTF creation
Encode flags for capture-the-flag puzzles. 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-cleanDemo encodings
Visual demo of UTF-8 vs ASCII. 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 countsFun fonts
Decorative binary in design. 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-awareRound-trip test
Verify your binary→text decoder is correct. 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-accurateCuriosity
What does 'I love you' look like in binary? 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.
losslessFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.