Skip to content
clickidy
🎯 ALL GAMES
CODES · TRANSLATOR

Binary Translator

Text to 8-bit binary and back. 01100011 01101100.

8-bit ASCII. Each character becomes eight ones and zeros.

ENCODING →
BINARY01100011 01101100 01101001 01100011 01101011 01101001 01100100 01111001

THE HISTORY ◢

Binary writes every character as a run of 0s and 1s, the only two states a digital circuit needs. The scheme used here is ASCII, standardised in 1963, which gives each letter, digit and symbol its own 7-bit code, written here padded to eight bits a character - the layer sitting underneath essentially all the text a computer stores.

THE LONG ANSWER ◢

Two steps. Every character is assigned a number, and that number is written in base 2. That is genuinely all of it, and the only reason it feels like more is that both steps are invisible.

The number is not arbitrary. It was fixed by a committee in 1963 and we are all still using it.

Key Takeaways

  • Text becomes binary by looking each character up in a table to get a number, then writing that number in base 2.
  • ASCII, published as ASA X3.4-1963, defined 128 characters in 7 bits: 95 printable and 33 control codes.
  • Bytes are 8 bits, so 7-bit ASCII is normally padded with a leading zero, which is why you see 01000001 rather than 1000001.
  • UTF-8 replaced ASCII as the web's dominant encoding in December 2007 but kept the first 128 codes identical, so plain ASCII is still valid UTF-8 today.

A worked example

Take the capital letter A.

Two toggle switches, one up and one down, standing for the two states binary records.

Look it up in the ASCII table: A is 65. Write 65 in base 2: 1000001. Pad it to a full byte with a leading zero: 01000001.

Decoding runs backwards. Split the stream into 8-bit chunks, read each as a number, look the number up. 01000001 is 65, and 65 is A.

Try it on a word. "Hi" is H (72) and i (105), so 01001000 01101001. Every space you see in binary output is there for your benefit, not the computer's. The machine sees an unbroken run of bits and knows to take them eight at a time.

Why is A 65?

Because of a decision made over three years by a standards committee, and the numbers are less random than they look.

Work began on 6 October 1960 at the first meeting of the American Standards Association's X3.2 subcommittee, and the result was published as ASA X3.4-1963. It defined 128 characters in seven bits: 95 printable ones and 33 control codes inherited from teletype machines.

The ordering has deliberate structure. Capital A is 65 and lowercase a is 97, exactly 32 apart, which is one bit. Flipping a single bit switches case. Digit 0 is 48, so the digits run 48 to 57 in order and converting a digit character to its value is a subtraction. None of that is coincidence; it made the hardware of the era simpler.

Why 8 bits if ASCII only needs 7?

Because computers settled on the byte, and a byte is eight bits.

Seven bits gives 128 values, which was enough for American English and no accented characters at all. The eighth bit was spare, and through the 1980s everyone spent it differently: various systems used the upper 128 slots for accented letters, box-drawing characters or symbols, and none of them agreed. A document written in one place looked like nonsense in another.

That mess is what Unicode was created to end, and UTF-8 is how it reached the web. UTF-8 is variable-width: one byte for the original ASCII range, two to four bytes for everything else. Its key design decision was backwards compatibility. The first 128 codes are byte-for-byte identical to ASCII, so every ASCII file was already a valid UTF-8 file on the day UTF-8 appeared.

UTF-8 passed ASCII as the most common encoding on the web in December 2007. The 1963 table did not get replaced so much as absorbed.

A row of eight squares, some filled and some empty, standing for the eight bits of a byte.

What can you actually do with this?

Not encryption, to be clear about it. Binary is an encoding, not a cipher: there is no key, and anyone can reverse it in seconds. Writing a message in binary hides it from nobody.

What it is useful for is seeing the layer underneath. Text on a computer is numbers, and numbers are bits, and it is the same eight-bit chunk whether it came from a keyboard, a file or a network. Once that clicks, a lot of otherwise confusing things about computers stop being confusing.

Frequently Asked Questions

How do you convert text to binary by hand?

Look each character up in the ASCII table to get its number, convert that number to base 2, and pad to eight digits with leading zeros. A is 65, which is 1000001 in binary, written as 01000001. Reverse the steps to decode.

Why is the letter A represented as 01000001?

Because ASCII assigns capital A the number 65, and 65 in base 2 is 1000001, padded to a byte with a leading zero. The table was fixed in ASA X3.4-1963 and the assignments have not changed since.

What is the difference between ASCII and UTF-8?

ASCII defines 128 characters in 7 bits, enough for English. UTF-8 is variable-width, covering every Unicode character in one to four bytes, and it kept ASCII's first 128 codes identical. Every ASCII file is therefore already valid UTF-8.

Is binary code a form of encryption?

No. Binary is an encoding, not a cipher. There is no key and no secret: anyone can convert it back instantly. It changes how text is represented, not who can read it.

Why is binary always shown in groups of eight?

Because computers work in bytes and a byte is eight bits. ASCII only needs seven, so a leading zero is added for the eighth. The spaces between groups are added for human readability; the machine reads an unbroken stream and simply takes it eight bits at a time.

Sources