Text To Binary Converter

Every letter you type is stored as a number, and every number as bits. This converter shows you that hidden layer: type any text and it returns the binary code for each character, eight bits at a time. It is a favourite for computing lessons, puzzle design and programming practice, because it turns the abstract claim "computers store text as numbers" into something you can watch happen character by character.

Quick Answer

Each character is replaced by its character-code value written in binary, almost always as an 8-bit byte. In the standard ASCII/UTF-8 encoding, "H" is code 72, which is 01001000, and "i" is code 105, which is 01101001 — so the word "Hi" becomes 01001000 01101001.

From Characters to Codes to Bits

Computers cannot store a letter; they can only store numbers. The bridge is an encoding table that assigns each character a code. ASCII, the oldest and still the foundation, gives capital A the code 65, lowercase a the code 97, the digit 0 the code 48 and a space the code 32. Modern text uses UTF-8, which keeps every ASCII character at exactly the same code and the same single byte, then extends the scheme to cover every other writing system with sequences of two to four bytes for characters beyond ASCII's 128.

Once a character is a number, writing it in binary is mechanical: express the code in base two and pad it to eight bits. The padding is not decoration — fixed-width bytes are how the computer knows where one character ends and the next begins when the codes are streamed back to back. Reading the result in reverse, a machine takes eight bits, looks up the code, and prints the character. Copy any binary output from this page into a binary-to-text decoder and you will get your exact text back, because the process is a lookup, not a compression or a cipher.

The numbers themselves hold a few patterns worth seeing. Uppercase and lowercase letters differ by exactly 32 — A is 65 and a is 97 — which in binary is a single bit, the 32s bit. That is not a coincidence: early designers arranged it so that case conversion is a one-bit operation. Digits 0–9 occupy codes 48–57, so a digit's code minus 48 is the digit's value, another deliberate arrangement.

How to Use the Text to Binary Converter

1. Type or paste the text you want to encode — a word, a sentence, or a longer passage.
2. Read the output as a stream of 8-bit groups; each group is one character of your input, in order.
3. Count the groups to check the conversion: the number of bytes should equal the number of characters for ordinary English text.
4. Use the space byte, 00100000, to find word boundaries when you are decoding someone else's binary by eye.
5. For accented letters, emoji or other non-English characters, expect two or more bytes per character — that is UTF-8 doing its job, not an error.
6. Copy the binary exactly if it will be decoded elsewhere; a single flipped bit changes the character it decodes to.

Worked Example: Encoding the Word "Cat"

Encode "Cat" letter by letter. C is code 67: 64 + 2 + 1, so its bits are 01000011. The letter a is code 97: 64 + 32 + 1, giving 01100001. And t is code 116: 64 + 32 + 16 + 4, giving 01110100. The full binary for "Cat" is therefore 01000011 01100001 01110100 — three bytes, 24 bits. Check the first byte by place value: 64 + 2 + 1 = 67, and code 67 in the table is C. The same method scales to anything: "Hi" from the quick answer, a whole sentence, or this paragraph, which would run to thousands of bits and is exactly why nobody writes text in binary by hand when a converter will do it in a blink.

Encoding Traps and Misunderstandings

The first misunderstanding is treating this as encryption. It is not secret and not safe for anything private: the code table is public, universal, and reversed by any decoder instantly. It is an encoding — a way of writing text, not of hiding it. Second, character counts deceive: an emoji may look like one character and occupy four bytes, and some accented letters can be stored as a letter plus a combining accent, two codes for one visible character. If byte counts seem to disagree with character counts, that is the usual reason.

Case sensitivity is the third trap. "Cat" and "cat" differ in the very first byte (C is 01000011, c is 01100011), so binary copied from one will never decode to the other. Finally, keep the grouping when you copy results: without the eight-bit boundaries, a long stream of bits can be re-split at the wrong offset — though happily, UTF-8 is designed so that decoders can resynchronise after at most a few bytes if a stream is damaged.

Decoding a byte stream by eye is a skill worth practising on short strings, because it teaches you to spot the landmarks. Take 01000001 01100001: the first byte's place values give 64 + 1 = 65, the code for A; the second gives 64 + 32 + 1 = 97, the code for a — so the stream reads "Aa", and you can see the single case bit flip between them. Multi-line text hides one more character: the line break itself, code 10, byte 00001010, which is why pasted paragraphs produce bytes that do not correspond to any visible letter. Once you expect it there, its absence from the visible text stops looking like an error and starts looking like structure.

Related Code and Number Tools

Once text becomes numbers, the number tools take over: the Binary Converter translates the numeric values themselves between binary, decimal, hex and octal, and the Hex Converter shows the compact base-sixteen form that programmers use for the same bytes — each character is exactly two hex digits. The rest of the site's conversion tools are gathered in the converters section.