Convert binary bytes into readable text. Decode sequences of zeros and ones to inspect how UTF8 text is stored.
How to use
Paste groups of eight binary digits, with spaces or without them. Every byte must be complete and the full sequence must represent valid UTF8.
Example
01001000 01101001 decodes to Hi. A seven digit group is incomplete and causes an error.
FAQ
Why does an emoji need several groups?
UTF8 uses several bytes for many characters. Keep the full sequence instead of decoding one byte at a time.
Related tools
A practical task
Inspect a byte sequence in groups before decoding it. For OK, the bytes are 01001111 and 01001011. If a group has fewer than eight bits, restore the original source rather than guessing where to add zeros.
Another useful question
Can I paste signed decimal numbers?
No. This input expects binary digits representing bytes. Decimal byte values must first be written in base two with their complete eight bit width.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Binary notation | Binary uses only 0 and 1. Keep byte boundaries intact when inspecting encoded text. A missing digit shifts the following bits, so a string of plausible looking zeros and ones can still fail decoding. |
| A complete byte | A byte holds a value from 0 through 255. Binary writes that value with eight digits; hexadecimal writes it with two. Leading zeros are part of that fixed width representation and must stay in place. |
| UTF8 bytes | UTF8 encodes characters as bytes. Basic Latin letters use one byte each, while many accented letters and other scripts use more. A byte count therefore differs from a visible character count. |
| Code points | A Unicode code point identifies a character or a component of one. A letter followed by a combining accent contains two code points even when the screen displays one accented letter. |
| Encoding and encryption | Encoding changes how data is represented so another system can read it. It does not require a secret key. Encryption protects information with a key, while hashing produces a digest for a different purpose. |
| Similar looking text | Two strings can look identical but use different Unicode sequences. An accented letter can be stored directly or as a letter plus an accent. Visual similarity alone does not establish byte equality. |
| Line endings | A line break can use LF or CRLF. They look similar in an editor but contain different characters. Byte comparisons and checksums depend on the exact representation, including a final line break. |
| Hexadecimal notation | Hexadecimal uses digits 0 through 9 and letters A through F. Letter case does not change the byte value. Text stored as hex still needs a character encoding before its bytes can be read as words. |