Binary Code to English
Decode binary into readable text and find out why a sequence fails. Use UTF-8 for eight-bit bytes or strict seven-bit ASCII for a seven-bit source. Decoding recovers the original language; it does not translate it into English.
On this page
| Character | Decimal bytes | Hex bytes | Binary bytes |
|---|---|---|---|
| H | 72 | 48 | 01001000 |
| e | 101 | 65 | 01100101 |
| l | 108 | 6C | 01101100 |
| l | 108 | 6C | 01101100 |
| o | 111 | 6F | 01101111 |
Decode a complete message
Paste 01001000 01101001 with UTF-8 selected. The first byte is decimal 72, which is H; the second is 105, which is i. The output is Hi, with the original capitalization.
Spaces, commas, and line breaks may separate groups. The decoder removes these separators and regroups the remaining bits using the selected encoding. It does not silently add missing bits.
| Binary byte | Decimal | ASCII / UTF-8 |
|---|---|---|
| 01001000 | 72 | H |
| 01101001 | 105 | i |
Choose the encoding before guessing
For A, seven-bit ASCII is 1000001; eight-bit storage is 01000001. Select the matching option rather than adding a zero to an unknown group. Extra zeroes can alter the boundaries of a longer stream.
The bytes 11000011 10101001 decode together as é in UTF-8. A byte above 127 is not automatically a separate letter. Latin-1, UTF-16, encrypted data, and executable files are not detected automatically by this text tool.
What an error actually means
The UTF-8 decoder is strict: malformed bytes produce an error and no partial output. It does not replace bad bytes with �. If the source really contains U+FFFD, its valid UTF-8 bytes can still decode to that character.
A valid result does not prove the intended encoding. Check it against the source message or protocol.
| Input | Interpretation | Next step |
|---|---|---|
| 101 | Incomplete UTF-8 byte | Use the number tool if the intended value is 5 |
| 1000001 | Seven-bit ASCII A | Select Strict ASCII · 7 bits |
| 11111111 | 255, not valid UTF-8 by itself | Check the source encoding |
| 00001010 | Line feed | Inspect control values if output looks blank |
Recover text without uploading it
Conversion runs locally. Copy and TXT retain the complete result; the inspector shows its first 24 code points. Input accepts up to 20,000 UTF-16 code units, including separators.
For a screenshot, first extract and check the bits with the image tool. An OCR result needs checking even when it forms valid UTF-8.
Frequently asked questions
What binary code spells hello?
In ASCII or UTF-8, lowercase hello is 01101000 01100101 01101100 01101100 01101111. Uppercase HELLO is 01001000 01000101 01001100 01001100 01001111. Paste either sequence with UTF-8 selected to check it. Each group here represents one letter, and capitalization is part of the encoded data.
PermalinkCan I decode binary without spaces, or with commas and line breaks?
Yes. This text decoder removes whitespace and commas, then reads the remaining bits in the selected group width. A continuous UTF-8 stream must contain complete eight-bit bytes. Underscores, hyphens, and a 0b prefix are not accepted here. Check separators against the source rather than deleting unfamiliar characters indiscriminately.
PermalinkWhy does 1000001 fail in UTF-8 mode even though it means A?
1000001 is the seven-bit ASCII representation of A, but UTF-8 requires complete eight-bit bytes. Select Strict ASCII · 7 bits if that is the source format. The eight-bit representation is 01000001. Do not pad an unknown multi-character stream blindly: adding zeroes in the wrong positions changes its character boundaries.
PermalinkWhat should I do when the final group needs more bits?
Check for an omitted digit, a truncated copy, or the wrong group width. For UTF-8, the total after removing separators must be divisible by eight; seven-bit ASCII requires divisibility by seven. The tool reports how many bits are missing but cannot know their values. Recover them from the source instead of adding guessed zeroes.
PermalinkWhy is invalid UTF-8 rejected instead of showing a replacement character?
The decoder uses strict UTF-8 validation and rejects malformed input as a whole, with no partial text. For example, 11111111 is not a valid UTF-8 byte by itself. Check the bits and source encoding. A genuine replacement character, U+FFFD, can still appear if its valid UTF-8 bytes were present in the original message.
PermalinkWhy does valid binary produce blank-looking text?
Valid bytes can represent spaces or non-printing controls rather than visible letters. For example, 00100000 is a space, 00001001 is a tab, and 00001010 is a line feed. Inspect the byte values and code-point rows before concluding that output is missing. Copying or downloading preserves these characters even when they are hard to see.
PermalinkDoes Binary Code to English translate every message into English?
No. The decoder recovers the text's original language. English ASCII bytes decode to English, while valid UTF-8 can decode to Chinese, accented text, or emoji. Language translation is a separate operation. This tool also does not automatically detect Latin-1, UTF-16, encryption, or the contents of an executable file.
PermalinkThe result is readable but wrong. Does that mean the decoder failed?
Not necessarily. A changed bit can produce a different valid letter: 01101001 is i, while 01101000 is h. Check transcription, case, byte boundaries, and the source's encoding. If the input came from OCR, compare every digit with the image. Valid text proves that the bytes can be decoded, not that they were copied correctly.
PermalinkHow much binary can I decode, and what if Copy is blocked?
The input field accepts up to 20,000 UTF-16 code units, including separators. The inspector shows the first 24 code points, but the output and TXT download contain the full decoded result. If the browser blocks clipboard access, select and copy the result manually or use Download TXT. Conversion itself runs locally.
Permalink↑ Back to the converter · Page contents
Sources & verification
Reference material used for this explanation. The examples are reproducible with the tools on this site; see how they are checked.
Found a mismatch? Send a correction with a source.