Binary Translator, Text to Binary Code and Back
Convert text to binary and binary back to text instantly, with decimal, hexadecimal and octal modes, full UTF-8 support, custom delimiters and copy buttons.
Loading Binary Translator, Text to Binary Code and Back… If nothing happens, please enable JavaScript.
Every piece of text your computer stores or sends is ultimately a sequence of binary digits, and this binary translator shows you exactly what that sequence looks like. Type or paste any text and it is instantly converted to binary code, one group of ones and zeros per byte; paste binary and it is decoded back to readable text just as fast, in both directions, live as you type. Alongside binary, the converter also offers decimal, hexadecimal and octal modes, so you can inspect the same bytes in whichever numeral system suits your task, whether that is a programming exercise, a networking class, a CTF puzzle or plain curiosity about how computers represent language.
Frequently asked questions
How does the text to binary conversion work?
How do I convert binary back to text?
Why does one character sometimes produce more than one byte?
What does the 8-bit padding option do?
Can I decode binary that has no spaces in it?
What is the difference between binary, decimal, hexadecimal and octal modes?
Does this translator support emoji and non-English languages?
What is ASCII and how does it relate to UTF-8?
Why am I getting an 'invalid UTF-8 sequence' error when decoding?
Is my text sent to a server?
About Binary Translator, Text to Binary Code and Back
The reason text can become numbers at all is character encoding, and its history explains most of what you will see in the output. In 1963 the ASCII standard assigned a 7-bit number to each English letter, digit and punctuation mark, so the letter A became 65, or 01000001 in binary. ASCII worked well for English but had no room for accented letters, Cyrillic, Chinese or emoji, which led to a chaotic era of incompatible regional code pages. Unicode solved the chaos by giving every character in every writing system a unique code point, and UTF-8, designed by Ken Thompson and Rob Pike in 1992 on a New Jersey diner placemat, became the dominant way to store those code points as bytes. UTF-8 keeps every ASCII character as a single identical byte, while other characters use two, three or four bytes, which is why it now powers over 98 percent of the web.
This converter is fully UTF-8 aware. Text is encoded with the browser's native TextEncoder, so an accented é correctly produces two bytes (11000011 10101001) and an emoji like 🙂 produces four, exactly as they would be stored in a file or transmitted over a network. Decoding uses TextDecoder in strict mode: if the bytes you paste do not form a valid UTF-8 sequence, you get a clear error instead of silently corrupted characters. You can choose the delimiter between bytes (space, nothing at all, or any custom string), toggle 8-bit zero padding, and watch the live character and byte counts, which also make multi-byte characters easy to spot. Copy buttons on both sides move the result to your clipboard in one click.
Binary-to-text conversion has plenty of practical uses. Developers use it to debug encoding problems, inspect network payloads and understand why a string's byte length differs from its character count. Students use it to learn positional notation and two's complement foundations. Puzzle designers and escape-room creators hide messages in binary, and the classic "01001000 01101001" greeting still circulates in forums and T-shirts. Because the whole tool runs client-side in your browser, nothing you type is ever uploaded: your text and its binary form stay on your device, and the converter keeps working even with the network disconnected.
Why Eight Bits Won: A Short History of the Byte
The word "bit" (binary digit) was coined by statistician John Tukey in 1947, and the "byte" was named by IBM engineer Werner Buchholz in 1956 during the design of the STRETCH supercomputer, deliberately misspelled from "bite" so nobody would confuse it with "bit". Early computers disagreed wildly about how big a byte should be: machines shipped with 6-bit, 7-bit and 9-bit characters, and some scientific computers addressed memory in 36-bit words. It was IBM's System/360, launched in 1964, that standardized the 8-bit byte across an entire product line. Eight bits gave 256 values, enough for ASCII plus extras, and it was a convenient power of two; the rest of the industry followed, and by the 1970s the 8-bit byte was simply how computers worked.
Character encoding took far longer to settle. For decades every language region had its own incompatible "code page": the byte 0xE9 meant é in Western Europe, щ in some Cyrillic sets and a completely different symbol in Japan, which is why old emails and web pages sometimes displayed as mojibake, garbled nonsense text. The fix was sketched in September 1992, when Ken Thompson and Rob Pike of Bell Labs worked out the UTF-8 scheme, famously writing the design on a placemat in a New Jersey diner. Their encoding was self-synchronizing, sorted correctly, and left every ASCII file untouched. Google's crawl data showed UTF-8 overtaking all other encodings on the web around 2008, and today it accounts for over 98 percent of all pages.
Binary text has also earned a place in popular culture. The Pioneer plaques and Voyager golden records use binary to encode fundamental quantities for any aliens who might find them. Movie posters and album covers regularly hide binary messages: the poster for The Matrix Reloaded, Coldplay's X&Y cover art (which uses the Baudot code, an ancestor of ASCII), and countless video game easter eggs. And in 1974, the Arecibo message beamed 1,679 bits toward the star cluster M13, 1,679 being the product of two primes so that any recipient could arrange the bits into a 73 by 23 image, humanity's first deliberate binary postcard to the stars.