dialpad Text to Binary Converter star

How It Works

Text is not converted to binary character by character — it is converted byte by byte, after first being encoded as UTF-8. That distinction matters because a single character does not always occupy a single byte. Type an ASCII character (the plain English letters, digits and punctuation, code points 0-127) and it fits in exactly one byte, so A becomes one 8-bit group: 01000001. Most non-English characters need more room. The Turkish dotted capital İ (Unicode U+0130) is encoded in UTF-8 as two bytes, not one: 11000100 10110000 — two separate 8-bit groups. An emoji like 😀 (U+1F600) needs four bytes: 11110000 10011111 10011000 10000000. This tool runs exactly that pipeline — text → UTF-8 bytes → one 8-bit binary group per byte, space-separated — so a word containing "İ", "ğ" or an emoji produces visibly more groups than a naive one-character-equals-one-byte assumption would predict.

The extra bytes are not arbitrary; they follow a fixed bit pattern that any UTF-8-aware decoder (including this tool, running the conversion in reverse) can recognize. The first byte of a multi-byte sequence starts with a run of 1-bits followed by a 0 that announces how many bytes make up the character — 110xxxxx means "2 bytes total," 1110xxxx means "3 bytes," 11110xxx means "4 bytes" — while every byte that follows it, a continuation byte, always starts with the fixed prefix 10xxxxxx. Reading 11000100 10110000 for İ: the decoder sees 110 (a 2-byte lead byte) followed by a byte starting 10 (exactly one continuation byte), confirms the sequence is complete, and reconstructs the single Unicode code point U+0130 from the remaining bits of both bytes combined. This is also why a stray or corrupted byte in the middle of a multi-byte character breaks decoding — the continuation-byte prefix has to line up, or the character can't be reassembled.

What You Should Know

Converting binary back to text reverses the same pipeline: 8-bit groups are read in order, regrouped into complete UTF-8 byte sequences by checking each leading byte's prefix to know how many continuation bytes belong with it, then decoded back into characters — so a correctly generated binary string always round-trips to the exact original text, Turkish characters and emoji included, not an approximation of it. This only works because the binary here is specifically UTF-8: binary produced by a different encoding (UTF-16, or a single-byte Turkish encoding like ISO-8859-9/Windows-1254) uses different byte counts and bit patterns for the same characters, and pasting it here will decode to the wrong text or fail outright — it is not a universal binary-to-text tool, it is a UTF-8 one. Because the whole conversion runs client-side in the browser, no text or binary you type is ever sent anywhere.