Text Tools·4 min read

How Binary Encoding Works, From Text to Bits

Underneath every string you've ever typed sits a row of numbers, and underneath those numbers sit bits. Once you see the steps, you can check them by hand: each character maps to a code, each code is written in base 2, and eight digits per byte is the convention that makes the stream readable. The Text to Binary Converter lets you verify every step in both directions. This article walks the full path from the letter A to 01000001 and back.

Open the free Text to Binary Converter All insights

How binary encoding works in three moves

Character, number, bits.

Text to bits is a two step translation with one formatting rule. Step one: every character has an agreed number. In ASCII, capital A is 65, capital B is 66, a space is 32, and the digit 0 is 48. Step two: write that number in base 2, where each position is worth double the one to its right. The formatting rule: pad to eight digits with leading zeros, because computers store text in eight bit bytes.

That's the whole system. Nothing about it is mysterious once you see that binary is just a different way of writing the same numbers, the way 65 and LXV name the same quantity. The encoding table is the agreement; the bits are bookkeeping.

ASCII to binary by hand: the letter A

One character, worked in full.

Working one letter by hand cements it. Take A, code 65. The bit positions in a byte are worth 128, 64, 32, 16, 8, 4, 2, and 1. Is 65 at least 128? No, write 0. At least 64? Yes, write 1 and keep the remainder 1. The 32, 16, 8, 4, and 2 positions all get 0, and the final 1 position gets 1. Reading the digits off: 01000001.

Verify it in the tool: choose Text to Binary, type A, and 01000001 comes back. Try lowercase a, code 97, and you get 01100001. The only difference is the 32 position flipping on, which is exactly why upper and lower case letters sit 32 apart in the table. The Character breakdown table under the output shows each character's code point, its UTF-8 bytes in hex and the same bytes in binary, so you can check your working one row at a time.

A worked binary conversion: the word Hi

Two bytes, round tripped.

Multi character text just concatenates the recipe. H is code 72, which is 64 plus 8, so its byte is 01001000. Lowercase i is 105, which is 64 plus 32 plus 8 plus 1, giving 01101001. The word Hi therefore encodes as 01001000 01101001, and pasting exactly that into the tool with Binary to Text selected returns Hi. The Swap button does the same round trip in one click, moving the output into the input and flipping the direction.

The round trip is the real lesson. Encoding and decoding are perfect mirrors, so any message survives the loop unchanged. When a decode comes back as gibberish, the bits were wrong, not the system, and the culprit is almost always grouping or a typo rather than the math.

Reading binary output without losing your place

Patterns that make bits legible.

Binary gets much easier to read once you spot the prefixes. In eight bit ASCII, every uppercase letter starts with 010, every lowercase letter starts with 011, and every digit starts with 0011. Scan a stream of bytes and you can tell letters from numbers before decoding a single one.

Two more habits help. Count bytes to estimate length: at eight bits plus a space per character, a 27 character sentence is around 243 characters of binary, which the tool's character count confirms. And when hunting for a specific letter, remember the case bit: if you know A is 01000001, then a is the same pattern with the third bit flipped.

Binary conversion mistakes that garble the text

Where round trips go wrong.

Almost every failed decode traces back to one of these.

Uneven runs. The decoder accepts bytes with or without spaces, so 0100100001101001 still gives Hi, but an unbroken run must be a multiple of 8 bits. Drop one digit and the tool tells you the run length is off.
Dropped leading zeros. 65 in minimal binary is 1000001, seven digits. Separated by spaces it still decodes as A, but glued into a run without its leading zero it leaves the run one bit short, and the byte boundaries after it are lost.
Letter O instead of zero. The decoder rejects the input and names the character in the error, which makes this the easiest mistake to fix.
Expecting one byte per character. The converter writes real UTF-8, so é becomes two bytes, 11000011 10101001, and most emoji take four. Bytes that aren't valid UTF-8 are read as one Latin-1 character each, with a note saying so.

Practice tips for text to binary fluency

Small drills, fast payoff.

Drill with words you can verify. Encode your own name by hand, then check it in the tool; disagreements point straight at the position you miscounted. Predict before you press: guess the first three bits of each character from its case, then confirm. And use the round trip as a self test, encoding on paper and decoding with Binary to Text so the tool grades your work. When you need the output in a particular shape, the Byte separator menu joins bytes with a space, nothing, a comma or a new line.

Text to Binary Converter next to ASCII Table and Base64

Three views of the same bytes.

The ASCII Table is the reference this whole process leans on: when you can't remember whether a comma is 44 or 46, that's the lookup. Base64 Decode and Encode solves a different problem, packing binary data into 64 text safe characters for transport, so its output is dense and unreadable where binary strings are long and legible.

For another take on encoding text as signals, the Morse Code Translator maps the same alphabet to variable length dots and dashes instead of fixed eight bit bytes, and comparing the two systems is a compact lesson in why fixed width won.

Try it now

Open Text to Binary Converter

The tool is one click away. No sign up, no upload, no payment.

Open Text to Binary Converter

Write a review