Text to Binary Converter

Text to binary converter

This converter turns any text into its binary representation, encoding characters as UTF-8 and showing every byte as eight binary digits separated by spaces. It is useful for learning how computers store text, for puzzles and capture-the-flag (CTF) challenges, and for inspecting exactly which bytes a given string produces under UTF-8.

Why UTF-8 and why 8 bits per byte

UTF-8 is the dominant text encoding on the web and in most modern operating systems. It is variable-width: ASCII characters (U+0000 to U+007F) use a single byte, accented Latin letters use two bytes, most CJK characters use three bytes, and emoji typically use four bytes.

A byte is always 8 bits. Writing each byte as an 8-digit binary number — padding with leading zeros when needed — keeps the output consistent and makes it easy to split the string back into individual bytes by splitting on spaces.

How the encoding works

1. Take the text and encode it to its UTF-8 byte sequence.
2. Convert each byte to its base-2 representation.
3. Left-pad to 8 digits (so the byte value 7 becomes 00000111 rather than 111).
4. Join the 8-bit groups with single spaces.

Common character reference

Worked example

The word Cat encodes as:

• C = 67 → 01000011
• a = 97 → 01100001
• t = 116 → 01110100

Result: 01000011 01100001 01110100

An emoji like 😊 (U+1F60A) encodes to four UTF-8 bytes and appears as four 8-bit groups.

Reversing the conversion

To decode binary back to text: split on spaces to recover individual bytes, convert each 8-bit group from base 2 to a decimal number, then interpret the byte sequence as UTF-8. The companion binary-to-text converter on this site does this automatically.

Everything runs in your browser — nothing you type is uploaded or stored.

From ASCII to UTF-8: why the byte values are what they are

The byte values this tool produces are not arbitrary — they descend from ASCII, the 1963 seven-bit code that fixed A at 65 and a at 97, and survive unchanged inside UTF-8, which was designed so that every ASCII character keeps its exact ASCII byte. Characters beyond ASCII use multi-byte sequences defined by RFC 3629: é becomes two bytes (11000011 10101001), CJK characters three, emoji four. The leading bits of each byte encode its role — 0xxxxxxx is standalone ASCII, 110xxxxx starts a two-byte sequence, 10xxxxxx continues one — which is why UTF-8 text can be decoded even when you start reading mid-stream. The full character-to-codepoint mapping is maintained by the Unicode Consortium.

Why exactly 8 bits, and what “bit order” means here

Bytes were not always eight bits — early machines used 6- and 7-bit units — but the octet won completely, and modern standards define network data in octets. Within each octet shown by this tool, the most significant bit is written first (leftmost), matching how binary numbers are written in mathematics: 01000001 is 64 + 1 = 65 = A. Endianness — the byte order controversy in multi-byte numbers — does not apply to UTF-8 text, which is a byte sequence with a defined order regardless of CPU architecture. That is one of the practical reasons UTF-8 displaced UTF-16 on the web.

What binary text is actually used for

Beyond the classroom, spelled-out binary shows up in CTF puzzles and geocaching ciphers (a string of 8-bit groups is one of the most common puzzle encodings), in teaching how encodings and code points relate, and in debugging encoding bugs — comparing the binary of a string that “looks right” against one that behaves wrongly reveals invisible characters (non-breaking spaces, zero-width joiners) instantly. For compact binary representation of real data, hexadecimal is the working notation — each byte is two hex digits instead of eight bits — which is why hex dumps, not bit dumps, are what debuggers show.

Reading binary faster with the 128/64/32 trick

To decode a byte by eye, memorise the place values 128, 64, 32, 16, 8, 4, 2, 1 and add up the positions holding a 1: 01001101 is 64+8+4+1 = 77 = M. With ten minutes of practice, short words become readable without a tool — and, more usefully, the trick makes encoding errors visible: any “byte” with fewer or more than eight digits, or a leading 11 continuation pattern with no 110/1110 lead byte before it, cannot be valid UTF-8, which is often the fastest way to spot where a puzzle or a corrupted string went wrong.

For longer messages, note that spelled-out binary inflates size eightfold plus separators — a 100-character sentence becomes nearly 900 characters of bits — which is why binary text is a teaching and puzzle format, never a storage one.