Calcoid

Text to Binary Converter

Convert text to and from binary representation. Supports ASCII and full UTF-8, with 7-bit or 8-bit byte modes and custom separators.

Convert text to binary (or back)
Conversion mode

Encoded as UTF-8. In 7-bit mode, non-ASCII characters (above code point 127) are rejected.

Binary output

01001000 01101001

Characters

2

Bytes

2

Bits

16

Frequently Asked Questions about the Text to Binary Converter

Why does the same character take different numbers of bytes in UTF-8?
UTF-8 is a variable-length encoding. ASCII characters (codepoints 0 to 127, the standard English alphabet plus common punctuation) fit in a single byte. Latin-1 supplement (accented characters like a-umlaut or n-tilde) takes two bytes. Most other scripts (Cyrillic, Greek, Hebrew, Arabic) also take two bytes. CJK ideographs (Chinese, Japanese, Korean) take three bytes. Emoji and rare scripts take four bytes. The 8-bit mode of the converter respects these multi-byte sequences, so an emoji entered into the encoder produces 32 bits, not 8.
Why is the letter A binary 01000001 and not 11000001?
A is decimal 65 in ASCII, which is binary 01000001. The order is most-significant bit first (big-endian), matching how humans write numbers (the leftmost digit is worth the most). Bit 7 (the leftmost) is 0 because A is below 128 in ASCII. The capital A is followed by B (01000010), C (01000011), and so on, incrementing by 1 each letter, all the way up to Z (01011010). Lowercase letters start at a = 97 (01100001).
What is the difference between 7-bit and 8-bit modes?
Original ASCII uses 7 bits per character (codepoints 0 to 127), which covers the basic English alphabet, digits, and common punctuation. The 8-bit mode pads each ASCII byte with a leading zero to fit standard byte boundaries and additionally supports the full Latin-1 / UTF-8 character set. Use 7-bit mode for compact ASCII-only output (telegraph, very old protocols) and 8-bit mode for anything modern, including UTF-8 multi-byte sequences.
Why does my decoded text look like garbage?
The most common cause is a mismatch between the encoding the binary was created with and the decoder setting. If the binary string was produced as 8-bit UTF-8 but you decode it as 7-bit ASCII, any byte with the high bit set will be rejected or mangled. The separator matters too: if the encoder used commas but the decoder expects spaces, the chunks won't align and the output collapses. Try toggling the separator and bit mode until the output reads like the original.
How do I compute the number of bits in a string of text?
In 8-bit mode, the bit count is the byte count times 8, and the byte count depends on which characters are present. Pure ASCII text gives 1 byte per character, so a 10-character string is 80 bits. Mixed text with one emoji jumps significantly: an emoji is typically 4 bytes (32 bits) on its own. The converter shows both the character count and the byte count so you can see where the extra bytes come from. In 7-bit mode, only ASCII is allowed and the bit count is exactly characters times 7.

Related Calculators

More calculators in "Tech"

See all 98 calculators in "Tech"