Text to binary (and binary to text)

What text-to-binary conversion is

Computers do not store letters — they store numbers, and those numbers live in binary, a system built from just two digits, 0 and 1. Each digit is a bit, and eight bits make one byte. Converting text to binary means taking every character, looking up the number that stands for it, and writing that number in base 2 across eight positions.

This tool works both ways. In Text → Binary you type a phrase and get the stream of bits, with each byte separated by a space so it stays readable. In Binary → Text you paste those bits back and recover the original message. It also lists every character with its decimal and hexadecimal value, so you can see exactly where the numbers come from.

How the conversion works

The heart of it is encoding. This tool uses UTF-8, the standard of the web, through TextEncoder. In UTF-8 the basic ASCII characters (English letters, digits, common punctuation) take a single byte, while accented vowels, an “ñ”, or an emoji take between 2 and 4 bytes. Every byte is always printed as 8 bits, padded with leading zeros when needed.

To go back, spaces are ignored, the bits are grouped eight at a time, each group becomes one byte, and TextDecoder rebuilds the text. If the bit count is not a multiple of 8, if characters other than 0 and 1 appear, or if the bytes are not a valid UTF-8 sequence, you get a clear warning instead of a garbled result.

Look at the last row: the é needs two bytes in UTF-8 (11000011 10101001), even though it is a single letter on screen.

Worked example

Let’s convert the word Hi.

1. Uppercase H has code 72. In binary, 72 is 1001000; padded to eight positions it becomes 01001000.
2. Lowercase i has code 105. In binary, 105 is 1101001; padded to eight positions it becomes 01101001.
3. Joining both bytes with a space gives 01001000 01101001.

Now the reverse: take 01001000 01101001, group into bytes, 01001000 is 72 (H) and 01101001 is 105 (i), so we get Hi back. The round trip matches, which is the proof that the conversion is correct.

Frequently asked questions

Why always eight bits per byte?

A byte is eight bits by definition, so even when the number fits in fewer positions it is padded with leading zeros. Keeping a fixed width lets you split the stream back into bytes without ambiguity: you know a new character starts every eight digits.

What about accents, “ñ”, and emojis?

They are handled correctly because the tool works in UTF-8. An accented vowel or an “ñ” takes two bytes, and an emoji usually takes four. That is why the byte count can be larger than the number of letters you see on screen; the tool shows both counters.

Can I paste binary without spaces?

Yes. When decoding, all spaces and line breaks are stripped before grouping, so it does not matter whether the bytes arrive separated or joined. The only requirements are that the total bit count is a multiple of eight and that only zeros and ones are present.

Is binary the same as encryption?

No. Binary is just another way of writing the same numbers; anyone can reverse it instantly, exactly as this page does. It hides and protects nothing. To protect information you use encryption or hashing algorithms, not a simple change of base.

Is my text sent to a server?

No. The whole conversion happens in your browser with TextEncoder and TextDecoder. Nothing you type leaves your device, so you can use it with private data without worry.