What Text Looks Like Underneath
Every character you read is stored as a number, and every number is stored as bits. Converting text to binary makes that visible: the letter A becomes 01000001, which is 65 in decimal and 0x41 in hexadecimal, the same value in three notations.
This converter goes both ways, turning text into binary and binary back into readable text, which is useful for teaching, for puzzles, and for checking what a byte sequence actually contains.
How to Convert Text and Binary
The tool detects which direction you want from what you paste.
- Paste text to see its binary representation, with each character as a group of bits.
- Or paste binary, groups of eight digits separated by spaces, to convert it back into text.
- Check the grouping if a conversion back fails. Binary text is conventionally written in bytes of eight bits, and a stray digit will shift everything after it.
- Note that non-English characters produce more than eight bits each, because UTF-8 encodes them across two to four bytes.
- Use the result for what it is: a demonstration of encoding rather than a way to hide anything, since binary is trivially readable by anyone who wants to.
Why Some Characters Take More Bytes
ASCII covers the English alphabet, digits and common punctuation in a single byte each, which is why English text converts to neat groups of eight bits. UTF-8 extends that to every character in Unicode while keeping ASCII unchanged, at the cost of variable length: accented Latin letters take two bytes, most Asian characters take three, and emoji generally take four.
That variability explains a lot of everyday behaviour. It is why a text field that counts bytes rather than characters rejects a name with an accent sooner than one without, why an emoji costs several characters of a message limit, and why truncating a string at a fixed byte position can slice a character in half and produce the replacement symbol.
Characters and Their Encodings
The same characters shown as decimal, hexadecimal and binary, with the byte count UTF-8 uses.
| Character | Decimal | Hex | Binary | UTF-8 bytes |
|---|---|---|---|---|
| A | 65 | 0x41 | 01000001 | 1 |
| a | 97 | 0x61 | 01100001 | 1 |
| 0 | 48 | 0x30 | 00110000 | 1 |
| space | 32 | 0x20 | 00100000 | 1 |
| é | 233 | 0xE9 | 11000011 10101001 | 2 |
| 한 | 54620 | 0xD55C | three bytes | 3 |
| 😀 | 128512 | 0x1F600 | four bytes | 4 |
Notice that A is 65 and a is 97, exactly 32 apart. That gap is a single bit, which is why changing letter case in ASCII is a bitwise operation rather than a lookup, and why the digits start at 48 rather than 0.
Binary Is Not Encryption
Text converted to binary is not hidden in any meaningful sense. The conversion is public, reversible and requires no key, so anyone who recognises the pattern can read it in seconds. Using it to obscure a password or a message provides no protection at all, only the appearance of it.
What it is genuinely useful for is understanding. Seeing that a character is a number, that the number is bits, and that the bit pattern for A differs from a by one position makes the layer underneath text concrete in a way an explanation does not. That is why it turns up in teaching material and puzzles far more than in anything operational.