Text to Binary Converter — ASCII Encoding

How Text to Binary Conversion Works

Converting text to binary is a two-step process: first map each character to its numeric codepoint using an encoding standard, then convert that number to its base-2 representation. For English letters and punctuation, the mapping comes from ASCII, which assigns uppercase A to 65, uppercase B to 66, the digit 0 to 48, space to 32, and so on, as tabulated in the original 1963 ANSI X3.4 standard. Converting 65 to binary gives 1000001, and padding to 8 bits gives 01000001. For characters outside the ASCII range, the tool uses UTF-8 encoding, which assigns one to four 8-bit bytes per character per RFC 3629. Reversing the process is just as simple: split the binary string into 8-bit groups, interpret each group as a number in base 2, and look up the corresponding character. For related tools see our hex to decimal converter and binary calculator.

The Conversion Formula

For a character c with codepoint n, the binary representation is produced by dividing n by 2 repeatedly and reading the remainders from bottom to top: n = q_1 * 2 + r_1, q_1 = q_2 * 2 + r_2, and so on until the quotient is zero. The binary string is r_k r_{k-1} ... r_1, left-padded with zeros to the target width. For example, the letter H is codepoint 72; dividing gives 72 = 36*2+0, 36 = 18*2+0, 18 = 9*2+0, 9 = 4*2+1, 4 = 2*2+0, 2 = 1*2+0, 1 = 0*2+1, reading the remainders top to bottom gives 1001000, and padding to 8 bits gives 01001000. The word "Hi" becomes 01001000 01101001, which is the 8-bit binary for codepoint 72 followed by codepoint 105. In JavaScript, the one-line conversion is text.split('').map(c => c.charCodeAt(0).toString(2).padStart(8, '0')).join(' '), which is exactly what this tool runs internally.

Key Terms You Should Know

Bit: a single binary digit, 0 or 1; the smallest unit of data. Byte: a group of 8 bits that can represent 256 distinct values (0 to 255). ASCII: the 7-bit encoding standard for 128 English-language characters, published as ANSI X3.4-1986. Unicode: the universal character set with over 149,000 code points covering nearly every written language. UTF-8: the variable-width encoding of Unicode that uses 1 to 4 bytes per character and is backward-compatible with ASCII. Codepoint: the integer value assigned to a character in a given encoding standard. Big-endian / little-endian: the two ways of ordering bytes within a multi-byte integer; UTF-8 is endian-free because it is a stream of bytes. Control character: an ASCII character in the range 0 to 31 that represents commands like tab, newline, or null terminator rather than printable text.

ASCII Reference Table

The table below shows common ASCII characters with their decimal, hex, and 8-bit binary representations from the Unicode Consortium's Basic Latin block. These values have been unchanged since 1967 and form the foundation of nearly every text file, source code file, and network protocol ever written. Note that lowercase letters are exactly 32 higher than their uppercase counterparts (0x20 difference), which makes case conversion a simple bit flip.

Practical Examples

Example 1 — Encoding the word "Hello": H is 01001000, e is 01100101, l is 01101100, l is 01101100, o is 01101111, which concatenates to 01001000 01100101 01101100 01101100 01101111 in space-separated form. The total length is 5 characters times 8 bits equals 40 bits or 5 bytes. Example 2 — Decoding a binary message: The string 01010111 01101001 01101011 01101001 decodes byte by byte to 87, 105, 107, 105, which maps to W, i, k, i, spelling "Wiki". Example 3 — Measuring file size: A plain-text file containing the word "test" (4 characters) is 4 bytes or 32 bits on disk when stored as ASCII or UTF-8, but the same word stored as UTF-16 would be 8 bytes because UTF-16 uses at least 2 bytes per character. Most modern systems default to UTF-8 because it is the most space-efficient for Western text and still supports the full Unicode range.

Tips and Best Practices

Use 8 bits per byte: 7-bit mode only works for plain ASCII and breaks on any accented or non-English character; stick to 8-bit unless you specifically need legacy behavior. Include spaces as separators: space-separated binary is much easier to read and debug than an unbroken stream of 1s and 0s. Watch for whitespace when decoding: binary-to-text will fail if the input has extra characters or mixed separators; this tool normalizes whitespace automatically. Handle UTF-8 multi-byte characters correctly: emoji and non-Latin scripts require 2 to 4 bytes per character, and all bytes must be decoded as a group. Do not confuse binary with other bases: 01000001 is binary for 65, but 41 is hex for 65; keep the base explicit. For cryptographic use, prefer hex: binary strings are unwieldy for keys and hashes; hex is the standard in security contexts. Use this tool for learning, not encryption: converting text to binary is not encryption; it is a reversible encoding anyone can undo.