Every letter you type is a number wearing a costume, and binary is that number written the way computers store it — in base 2. Paste text into this translator and it converts each character to its binary representation, byte-style groups of eight bits (or wider where the character demands it), space-separated and ready to copy.
How It Works
The translator takes each character's Unicode code point — the standard number assigned to that character — and writes it in base 2, padded to a minimum of eight bits:
For the characters of ordinary English text, the code point is the classic ASCII code, so the familiar table applies:
| Character | Code | Binary |
| --- | --- | --- |
| A | 65 | 01000001 |
| a | 97 | 01100001 |
| 0 | 48 | 00110000 |
| Space | 32 | 00100000 |
| ! | 33 | 00100001 |
Worked Example — "Nerdy"
- N = 78 = 64+8+4+2 →
01001110 - e = 101 →
01100101 - r = 114 →
01110010 - d = 100 →
01100100 - y = 121 →
01111001
Output: 01001110 01100101 01110010 01100100 01111001
And "Hi" becomes 01001000 01101001 — two characters, two bytes, sixteen bits.
The Unicode Honesty Section
Because the translator works from code points rather than bytes, two behaviors deserve to be understood rather than discovered. Characters beyond basic ASCII produce wider groups. The letter é (code point 233) yields 11101001 — still 8 bits — but an emoji like 😀 (code point 128,512) needs 17 bits and returns a 17-digit group. The padding is a minimum of 8, not a fixed width. This is not UTF-8 encoding. UTF-8 stores é as two bytes (11000011 10101001) and emoji as four; this tool shows the character's own number in binary — the right thing for learning how characters are numbered and for puzzles, encodings-by-code-point, and digital-logic exercises, but not a byte-level dump of a file. For the reverse journey (binary back to text), use the Binary to Text converter; for text as a transport encoding, the Base64 encoder is the developer's usual tool.
What It Is Used For
Teaching and learning how computers represent text (the moment "A = 01000001" clicks, character encodings stop being magic); encoding messages for puzzles, games, and classroom exercises; checking what a character's code actually is before debugging an encoding bug; and generating binary text for design and social posts. It is a translator for characters, deliberately: raw binary files — images, executables, audio — contain byte sequences that are not text at all, and no character translator can render them meaningfully.
Frequently Asked Questions
Why groups of eight bits?
Because the byte — 8 bits, 256 possible values — is computing's standard container for a character, sized to hold the ASCII set with room to spare. Grouping output in eights lets you read binary as the bytes a computer would store, and count characters by counting groups for plain English text.
Can I convert binary back to text here?
This tool runs text → binary. The reverse direction lives in the companion Binary to Text converter, which parses space-separated binary groups back into characters. Splitting the directions keeps each tool's input validation honest.
Why did my emoji produce more than 8 bits?
Because its code point is larger than 255. The first 256 code points fit in 8 bits; the rest of Unicode's million-plus characters need wider binary numbers, and the translator prints the full number rather than truncating it — truncating would silently change the character.