Convert text into binary UTF8 bytes. See how letters, punctuation, and emoji become sequences of zeros and ones.
How to use
Enter text and copy the groups of eight digits. Spaces between groups separate bytes; spaces in your original text also have their own byte value.
Example
Hi becomes 01001000 01101001. The output can be decoded back with the binary to text tool.
FAQ
Is one group always one character?
No. Many Unicode characters use multiple UTF8 bytes. Keep all groups in order when decoding.
Related tools
A practical task
Use a short source with known spelling to verify the direction. OK becomes 01001111 01001011. Keep spaces between output bytes for inspection, but remember that an actual space inside the original message also has its own binary byte.
Another useful question
Can I treat the result as a number?
It is a sequence of encoded bytes, not one decimal quantity. Preserve byte order and widths when moving it into a decoder or example.
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. |