Text to Binary

What this tool does

This tool converts text into binary code — the sequence of 8-bit bytes (each written as eight 0s and 1s) that represents the text at the bit level. It runs entirely in your browser, with an option to separate each byte with a space for readability.

When you need it

• Learning or teaching how computers represent characters as bits, a common exercise in introductory programming and computer science courses.
• Building a "binary code" puzzle, escape-room clue, or novelty message where the answer is meant to be manually decoded.
• Cross-checking a byte-level representation of text against a reference when debugging low-level encoding or serialization code.
• Satisfying curiosity about what a specific word or sentence "looks like" at the bit level, byte by byte.

How the conversion works

1. Text is encoded as UTF-8 bytes first, exactly as with Base64 and hex encoding. A plain ASCII character like A is always one byte; accented letters, many symbols, and emoji take two to four bytes each.
2. Each byte is written as exactly 8 binary digits, padded with leading zeros where needed — so the letter A (byte value 65) becomes 01000001, not the shorter 1000001.
3. With the space delimiter on, each 8-bit group is separated by a single space, matching how binary is conventionally displayed for readability. With it off, all the bits run together into one continuous string, useful for pasting into code that expects a single binary literal.
4. Byte count, not character count, determines output length. A 5-character string with one multi-byte character produces more than 5 groups of 8 bits — the tool reports the exact input byte count alongside the binary output so this is never ambiguous.

Why this matters beyond novelty

Seeing text as binary makes concrete something that's otherwise abstract: a computer never "sees" the letter A, only the byte value 65, and everything above the bit level — characters, encodings, file formats — is a convention for interpreting those bits consistently. Working through a short example by hand, or checking one against this tool, is a fast way to build real intuition for how text encoding actually works, which pays off when debugging encoding mismatches, mojibake, or protocol-level issues later.

Things to check after converting

• If you're comparing this output against a reference binary representation from another tool or textbook, make sure both are using the same text encoding (UTF-8 is standard, but older material sometimes assumes ASCII or Latin-1, which agree with UTF-8 only for the first 128 characters).
• A one-character input producing more than one 8-bit group is expected and correct for any character outside basic ASCII — it is not a bug.
• Binary and hex encode the exact same information at different densities; hex is more compact (2 characters per byte vs. 8), while binary shows every individual bit explicitly.

Limits

Input is capped at 2 MB of text. To reverse this conversion, use the companion Binary to Text tool, which accepts the same space-separated or continuous binary format this tool produces.