Text to Binary — Encode Plain Text as 8-Bit Binary Instantly
Our free text to binary encoder turns any message into a sequence of 8-bit binary bytes — one group of zeros and ones per character (for typical English, using ASCII codes). Type or paste on the left and the binary appears on the right in real time, with spaces between bytes so you can read and copy safely. To decode binary back into letters, use the Binary to Text converter . No signup, no server upload, no limits.
How to Convert Text to Binary
Step 1 — Find each character's code
In ASCII, every character you can type on a US keyboard maps to a number from 0 to 127 (basic ASCII) or up to 255 in extended ASCII. For example, capital H is 72, lowercase a is 97, and a space is 32. The tool does this lookup for you automatically.
Step 2 — Convert the number to base 2
Take the decimal code and express it in binary (base 2). Divide by 2 repeatedly and collect remainders, or use place values: each bit is a power of 2 from 2⁰ on the right through 2⁷ on the left for one byte.
Example for H (72): 64 + 8 = 72, so bits at positions 6 and 3 are 1 → 01001000.
Step 3 — Pad to 8 bits
Each character must occupy exactly one byte for simple ASCII-style encoding: pad with leading zeros on the left until the string is eight characters long. Then repeat for the next character and join bytes — often with a space between them for readability.
Text to Binary Conversion Reference
Use this table to check how common letters, digits, and symbols translate to decimal ASCII and 8-bit binary:
| Character | ASCII decimal | Binary (8-bit) |
|---|---|---|
| A | 65 | 01000001 |
| B | 66 | 01000010 |
| C | 67 | 01000011 |
| H | 72 | 01001000 |
| Z | 90 | 01011010 |
| a | 97 | 01100001 |
| b | 98 | 01100010 |
| z | 122 | 01111010 |
| 0 | 48 | 00110000 |
| 1 | 49 | 00110001 |
| 9 | 57 | 00111001 |
| Space | 32 | 00100000 |
| ! | 33 | 00100001 |
| ? | 63 | 00111111 |
Common Words in Binary
Quick reference for short words and phrases — paste any of the binary strings into our Binary to Text tool to verify:
| Text | Binary (8-bit bytes) |
|---|---|
| Hi | 01001000 01101001 |
| Yes | 01011001 01100101 01110011 |
| No | 01001110 01101111 |
| Hello | 01001000 01100101 01101100 01101100 01101111 |
| SOS | 01010011 01001111 01010011 |
| OK | 01001111 01001011 |
| A | 01000001 |
| Z | 01011010 |
| 0 | 00110000 |
| 1 | 00110001 |
What Is Binary Code?
Binary is how digital hardware represents information: each bit is either 0 or 1, matching two stable states in circuits (off/on). When you "encode" text to binary for learning or puzzles, you are exposing the same numeric representation the machine would use at the lowest level — grouped into bytes for each character in ASCII-style schemes.
Base 2 uses only two digits, unlike everyday base-10 decimals. Eight bits together give 256 distinct patterns (0–255), which is enough for extended ASCII and common control codes.
ASCII and Binary — How Text Becomes Bits
ASCII assigns a standard number to each letter, digit, and punctuation symbol. When you encode text to binary, you are really writing those numbers in base 2, one byte at a time. Extended ASCII and other encodings reuse the same idea but may assign different meanings above 127.
Unicode extends the idea to every writing system, but a single Unicode character may need more than one byte in UTF-8. This page focuses on a simple per–code-unit 8-bit view suitable for English and debugging — not a full UTF-8 serializer.
Binary vs Other Number Systems
The same numeric value can be written in different bases. The letter H (72) appears as 01001000 in binary, 48 in hex, and 110 in octal — all describe the same quantity:
| System | Base | Digits used | Example (number 72) |
|---|---|---|---|
| Binary | Base 2 | 0, 1 | 01001000 |
| Octal | Base 8 | 0–7 | 110 |
| Decimal | Base 10 | 0–9 | 72 |
| Hexadecimal | Base 16 | 0–9, A–F | 48 |
When to Use Text to Binary
Learning and puzzles
Students and hobbyists use text-to-binary to verify ASCII, practice base conversion, or build coded messages. Seeing each byte separated makes it easier to compare with textbook tables.
Debugging and documentation
Developers sometimes paste a short string to confirm what bytes would look like in a wire protocol or log dump. For production protocols, always use your language's real encoding APIs (UTF-8, etc.).
Frequently Asked Questions
Why are there spaces in the output?
Spaces separate each 8-bit byte so you can tell where one character ends and the next begins. You can remove spaces if you need a continuous bit string, as long as the total length stays a multiple of 8 for decoding with the Binary to Text tool.
Is this the same as UTF-8 binary?
Not exactly. This tool uses one byte per JavaScript character code unit (masked to 8 bits). UTF-8 can use multiple bytes per Unicode character; for strict UTF-8 bytes, use a dedicated encoder in your programming environment.
What is 01001000 in text?
The byte 01001000 is decimal 72, which is the capital letter H in ASCII — the first letter of "Hello" in binary.
How do I convert text to binary by hand?
Write down each character's ASCII decimal value, convert that number to binary by dividing by 2 and collecting remainders (or summing powers of 2), then pad to 8 bits. Repeat for every character in order.
What is the binary for "I love you"?
"I love you" in 8-bit ASCII-style encoding is: 01001001 00100000 01101100 01101111 01110110 01100101 00100000 01111001 01101111 01110101 — spaces in the message become their own byte (00100000).
How many different values can one byte represent?
One byte has eight bits, so there are 2⁸ = 256 possible patterns (0 through 255). Basic ASCII uses 128 of those codes; extended ASCII uses the full byte range.
Can every language be encoded in 8 bits per character?
Not with basic ASCII alone — it was designed for English. Unicode supports global scripts but often needs more than one byte per character in UTF-8. This converter shows a simple 8-bit slice per code unit for quick inspection, not full multilingual UTF-8 serialization.