Paste text and convert it to UTF-8 binary (8-bit groups) in your browser - no upload and no account. Use Text to binary to encode, or Binary to text to decode groups back into characters.
Binary Text Converter
Paste text and convert it to UTF-8 binary (8-bit groups) in your browser - no upload and no account.
Key features
- Use Text to binary to encode, or Binary to text to decode groups back into characters.
- Output updates as you type on the encode path; Copy puts the current result on the clipboard.
- Spaces and newlines between bit groups are ignored on decode; incomplete 8-bit groups show a clear error.
When to use it
Prefer this for class demos, protocol notes, or quick checks of how a short string looks as bytes.
Binary Text Converter vs Number Base Converter
| Tool | What it converts |
|---|---|
| Binary Text Converter | UTF-8 text to 8-bit binary groups and back - text encoding. |
| Number Base Converter | Distinct tool for integer radix notation such as 255 to 0xFF, not text encoding. |
What decode does with stray characters between the groups
Binary to text does not only skip spaces and newlines - it drops every character that is not a literal 0 or 1 before it counts the bits. Paste a comma-separated list, a line with stray punctuation, or groups copied out of a table with extra formatting, and the tool reads only the 0s and 1s and ignores everything else in between. "01001000, 01101001" and "01001000 01101001" decode to the exact same result, because the commas are discarded the same way spaces are.
| What you paste | What decode does |
|---|---|
01001000 01101001 | Reads 16 clean bits, decodes to Hi. |
01001000, 01101001 | Drops the comma, reads the same 16 bits, decodes to Hi. |
0100 | Only 4 bits survive - not a multiple of 8, so the tool shows a "Need complete 8-bit groups" error instead of guessing. |
Binary Text Converter vs Base64 Encoder
Both tools turn text into another representation entirely in your browser, but the output serves a different purpose. Binary Text Converter spells out every bit, so the result is roughly 8 to 9 times longer than the original text - useful for seeing exactly how a string looks byte by byte. Base64 Encoder packs the same bytes into a compact set of letters, digits, and a few symbols, closer to 1.3 times the original length - the form you would actually paste into a data URI, a JSON field, or a URL. Base64 Encoder runs the same way this tool does, entirely in your browser, so comparing the two does not send your text anywhere either.
| Text | Binary Text Converter output | Base64 Encoder output |
|---|---|---|
Hi | 01001000 01101001 (17 characters) | SGk= (4 characters) |
Hello, world! | 116 characters | SGVsbG8sIHdvcmxkIQ== (20 characters) |
Privacy
The text you encode to binary and the bit groups you decode back to characters live only in this tab while you work - the converter keeps no history, so nothing you convert carries over to your next visit.
Frequently Asked Questions
What does Binary Text Converter do?
Paste text and convert it to UTF-8 binary (8-bit groups) in your browser - no upload and no account. Use Text to binary to encode, or Binary to text to decode groups back into characters.
Does my text leave this device?
No. Encoding and decoding run locally in your browser. Nothing you paste is saved between visits.
How is this different from Number Base Converter?
Number Base Converter changes integer notation (for example decimal 255 to hexadecimal FF). This tool encodes and decodes UTF-8 text as 8-bit binary groups, not integer radix values.
Does Binary Text Converter handle emoji and other multi-byte characters correctly?
Yes. Encoding uses the browser's built-in UTF-8 encoder on the whole input, so a multi-byte character such as an emoji becomes its full sequence of 8-bit groups (four groups for a typical emoji), and decoding those groups back returns the exact same character.
Why did decoding show a strange "�" symbol instead of my text?
That symbol (the Unicode replacement character) appears when your 0s and 1s form complete 8-bit groups but the resulting bytes are not a valid UTF-8 sequence - for example a stray continuation byte with no matching lead byte. The tool does not treat this as an error the way it does for an incomplete group; it substitutes the replacement character for each bad byte and shows the rest of the decode normally. Double-check that you copied every group in the original order and did not drop or duplicate one.
Why does every group show 8 digits, even for a small byte value?
Each group is always padded with leading zeros to a fixed 8-digit width. The letter "A" is byte value 65, whose raw binary is 1000001 (7 digits), but the tool pads it to "01000001" so every group lines up the same way. If you convert a byte by hand and get one digit fewer than the tool shows, add a leading zero rather than assuming a mistake.