Translate binary code into readable English text — or English into binary — instantly in your browser. Supports ASCII, UTF-8, multi-byte characters, and continuous binary (no spaces required).

This converter requires JavaScript. Please enable it to use the tool.

Binary ⇄ English Translator

Mode:

Options:Separator Encoding

Input

0 / 100,000 chars

Output

How binary translates to English

Computers store text by mapping each character to a number — the UTF-8 standard. The capital letter A maps to 65, which in binary is 01000001. The translator reverses this: it reads 8 bits at a time, looks up the number, and prints the matching character.

ASCII vs UTF-8

ASCII (American Standard Code for Information Interchange) was the original scheme — 128 characters, each one byte. UTF-8 is a backwards-compatible extension that adds support for every language on earth. English letters look identical in both; non-English characters take 2–4 bytes in UTF-8.

Reference: common characters

Character	Decimal	Binary (UTF-8)
A	65	`01000001`
a	97	`01100001`
0	48	`00110000`
space	32	`00100000`
!	33	`00100001`
中	—	`11100100 10111000 10101101`

How to use

Paste binary code (with or without spaces) into the Input box. Or upload a .txt via the Open file button.
The English translation appears instantly in Output. Each 8 bits decodes to one ASCII character; non-English characters use 2-4 bytes (UTF-8).
Need the other direction? Click Text → Binary mode (or hit the Swap button), type English, and binary appears.
Click Copy to copy the result. All processing is local in your browser.

Real-world use cases

CTF and security challenges. Flags hidden inside long bit strings drop straight into a binary to text decoder and reveal the plaintext.
Teaching character codes. Beginners get "a letter is just a number" much faster once they see 'A', 65, and 01000001 line up.
Embedded and protocol debugging. Firmware logs, UART captures, and network frames are easier to read when a quick translation tells you whether a byte is printable ASCII.
Coded messages and retro art. Cards, escape rooms, and tattoos that spell "hello" in bits all start with the same encoding step.
Explaining Unicode. Showing why 'A' takes one byte and 中 takes three makes UTF-8's design click.
Intro numeric exercises. Switching between binary, decimal, and hex is a standard warm-up for bit-level work.

A short history of binary text encoding

The idea of encoding letters with two symbols is older than computers. In 1605, Francis Bacon described a cipher that represented each letter of the alphabet with a five-character sequence of A's and B's — effectively a 5-bit binary code, two and a half centuries before any electrical circuit existed to run it.

The mathematical foundation arrived in 1854, when George Boole published the algebra of logic that now bears his name: AND, OR, and NOT operating on two values, true and false. Almost a century later, in 1937, Claude Shannon's master's thesis showed that Boolean algebra could describe the behaviour of relay circuits — closed switches as 1, open switches as 0 — connecting pure logic to physical hardware and laying the groundwork for digital computing.

Text standardisation followed in 1963 with ASCII, which fixed the English alphabet, digits, and control characters in a 7-bit table. ASCII solved one problem and exposed another: the rest of the world's writing systems did not fit. The answer came in 1993, when Ken Thompson and Rob Pike designed UTF-8 — a variable-length encoding that keeps ASCII bytes unchanged and uses 2-, 3-, or 4-byte sequences for everything else. Today UTF-8 is the default on the web, in source files, and in virtually every modern protocol.

Worked examples

The decoder reads bytes left to right. A few inputs done by hand make the pattern obvious:

"Hi" → two bytes

H = 72 = 01001000, i = 105 = 01101001. Result: 01001000 01101001 (or 0100100001101001 with the space dropped).

"Hello" → five bytes

H=72, e=101, l=108, l=108, o=111 — giving 01001000 01100101 01101100 01101100 01101111. One byte each, since every letter is in ASCII range.

"😀" → four bytes

U+1F600 sits outside ASCII, so UTF-8 uses 4 bytes: 11110000 10011111 10011000 10000000. The leading 11110 means "four bytes total" and each continuation starts with 10. Split one of these bytes off and neither half decodes on its own.

Broken input: 01001

Only five bits — not a multiple of eight. The translator stops at the bad position instead of guessing. Drop the stream into Binary Decode to inspect bit groups when this happens.

Common pitfalls

ASCII table vs UTF-8 table. ASCII only covers 0-127; anything beyond that (emoji, CJK, accented letters) needs UTF-8 or it turns into mojibake.
Whitespace eaten on paste. Chat apps and PDFs sometimes strip spaces, leaving a continuous string whose length is not a multiple of 8. Recount the bits before blaming the decoder.
Endianness. Bit order inside a byte is fixed, but byte order in multi-byte words flips between little- and big-endian systems. Rare for per-character translation, common when reading binary files.
Mistaking binary for BCD. 00100111 is 39 in plain binary but "2" and "7" in BCD. The two formats are not interchangeable.
Base mix-up. 41 in hex, 01000001 in binary, and 65 in decimal all denote the letter A. A lot of "broken output" is just hex being read as decimal.

Frequently asked questions

How does binary translation work?

Each English character maps to an 8-bit binary code via UTF-8 encoding. The translator groups your binary input into 8-bit chunks, looks up each chunk in the UTF-8 table, and reassembles the text. Spaces between bytes are optional.

What is the difference between ASCII and UTF-8 binary?

ASCII covers only the first 128 characters and uses exactly 8 bits per character. UTF-8 extends this to all Unicode characters; English letters still use 8 bits, but characters like 中 use 24 bits (3 bytes) and emoji like 😀 use 32 bits (4 bytes).

Why does my translation come out as gibberish?

Most often the binary length is not a multiple of 8 (each byte must be 8 bits), or your input contains non-binary characters. The tool reports the exact position of any invalid character. If everything looks correct but it still fails, your data may not be UTF-8 — try Binary → Decimal to inspect the raw numbers.

Can I translate binary with no spaces?

Yes. The tool accepts continuous binary like 0100100001101001 (must be a multiple of 8 bits) and splits it into bytes automatically.

Is there a limit on input size?

Up to 100,000 characters per conversion. For larger inputs, split into batches.

Can the translator handle emoji and Chinese characters?

Yes. UTF-8 covers all of Unicode: CJK characters take 3 bytes (24 bits) and emoji take 4 bytes (32 bits). If a paste cuts a multi-byte character in half, the decoder flags the position rather than silently emitting garbage.

How is binary different from binary-coded decimal (BCD)?

Plain binary reads the whole byte as one base-2 number (0–255). BCD stores one decimal digit per nibble, so 0010 0111 in BCD means the digits "2" and "7", not 39. This tool works in plain binary, not BCD.

Is binary the same as hexadecimal?

No, but one hex digit equals 4 bits, so they map cleanly: 01000001 in binary is 41 in hex (the letter A). If a value labelled 41 surprises you, check whether it is hex or decimal before blaming the translator.