Skip to content
Lizely

Text to Binary Converter

Encode text as visible 8-bit UTF-8 binary bytes or decode strictly formatted binary back to valid Unicode text.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Choose Text to UTF-8 binary or UTF-8 binary to text.
  2. 2.Enter text or exact 8-bit byte groups separated by one space.
  3. 3.Select Convert and verify the byte count or decoded text before copying it elsewhere.

About Text to Binary Converter

Text to Binary Converter makes the byte representation explicit. In Text to UTF-8 binary mode, it encodes the entered Unicode string with the browser's standards-based TextEncoder and prints every byte as exactly eight zero-padded bits separated by one space. In UTF-8 binary to text mode, it accepts that same strict format and decodes the bytes with a fatal UTF-8 decoder. Input and output stay in the current tab and are not sent to Lizely.

Binary text is often ambiguous unless the character encoding and grouping rule are named. This tool does not present a Unicode code point as though it were always one byte. ASCII A is one byte, é uses two UTF-8 bytes, the euro sign uses three, and a supplementary emoji such as 😀 uses four. The output therefore represents encoded bytes, not JavaScript UTF-16 code units, glyph pixels, abstract bits without grouping, or a base-2 rendering of each Unicode scalar value.

Encoding accepts up to 20,000 UTF-16 code units. Decoding accepts up to 180,000 input characters and requires groups matching eight binary digits separated by exactly one ordinary space. It rejects prefixes such as 0b, commas, tabs, multiple spaces, seven-bit groups, nine-bit groups, leading or trailing whitespace, and any character other than 0 or 1. Values are never padded, trimmed, guessed, or silently discarded.

The decoder uses fatal UTF-8 validation. A byte sequence that is structurally well grouped can still be invalid text—for example, a lone leading byte without its continuation. Invalid, overlong, surrogate, or out-of-range sequences fail with a clear error rather than being replaced by the Unicode replacement character. This makes the reverse operation useful for checking exact UTF-8 byte strings while avoiding a false round trip.

Eight independent golden cases cover ASCII, a word, two-byte Latin text, a three-byte currency sign, a four-byte emoji, CJK text, a line-feed control byte, and a mixed-width string. The expected bytes are written independently of the implementation. Tests also cover maximum input budgets, invalid grouping, repeated spaces, incomplete UTF-8, and byte counts.

This is an encoding utility, not encryption. Binary output contains the same information as the original text and offers no secrecy, authentication, integrity, compression, or password protection. Anyone can decode it. It also does not parse numeric binary values, machine instructions, files, images, Base64, hexadecimal, Morse code, or custom legacy character sets. Use the neighboring tools when those are the real intent.

Copy or store the result only in systems that preserve ordinary spaces and line content exactly. Chat clients and rich-text editors may collapse spaces or insert line breaks, which would make strict decoding fail. For protocol, source-code, or forensic work, verify the actual byte sequence with the specification and the destination system rather than relying on how a font draws the output.

Methodology & sources

Limit text to 20,000 UTF-16 code units, encode it with the WHATWG UTF-8 TextEncoder, serialize each byte as eight base-2 digits, and join bytes with one ASCII space. For decoding, require the exact regular language [01]{8}( [01]{8})*, limit serialized input to 180,000 code units, parse every group as one byte, and use a fatal UTF-8 TextDecoder so malformed sequences fail without replacement. Eight independent Unicode golden cases span one- through four-byte encodings and mixed input.

Frequently asked questions

Does one character always become eight bits?
No. The output shows UTF-8 bytes. ASCII uses one byte, while many accented, CJK, symbol, and emoji characters use two to four bytes.
Why must binary groups contain exactly eight bits?
The decoder operates on bytes. Exact grouping prevents ambiguous padding, trimming, or guessing.
What happens with invalid UTF-8 bytes?
Decoding fails. The tool uses fatal validation and does not replace malformed bytes with a replacement character.
Is binary text encrypted?
No. It is a reversible representation of the same information and provides no confidentiality or security.

Related tools

Encoding & Crypto guides

View all