Binary to UTF-8 Decoder Online Free
Binary to UTF-8 Text Decoder handles emoji, CJK, accents, strips BOM, counts replacement chars. Free, client-side, instant, offline, secure.
Decode 8-bit binary bytes as UTF-8 text. Handles the full range: 1-byte ASCII, 2-byte accents (café), 3-byte CJK (ä¸), 4-byte emoji (😀). Optional UTF-8 BOM strip, replacement-char counting for corrupt input, runs entirely offline via TextDecoder.
How to Use Binary to UTF-8 Decoder Online Free
- Paste binary digits - space/newline-separated bytes or one continuous stream. The tool chunks continuous input into 8-bit bytes automatically. Non-binary characters are stripped with the default setting.
- Leave BOM-strip on unless you need to keep a BOM. When the first three decoded bytes are
EF BB BF(the UTF-8 BOM, indicating UTF-8 encoding), they’re removed - most downstream tools either don’t need the BOM or actively dislike it. - Check the stats for replacement chars. If
N ✱ replacementappears, N bytes couldn’t be decoded as valid UTF-8 and were replaced with U+FFFD (�). That usually means your source was mislabeled - try our Binary to ASCII or Binary to String tools with Latin-1 mode. - Watch codepoint vs byte count. Pure ASCII gives 1:1 bytes-to-codepoints. Accented chars = 2 bytes per codepoint. CJK = 3 bytes. Emoji = 4 bytes. The non-ASCII count confirms whether your data actually used multi-byte UTF-8.
- Verify with a known example.
11000011 10101001should decode toé.11110000 10011111 10011000 10000000should decode to😀. If you get replacement chars instead, your byte order or bit-grouping is off. - Copy or download. Copy writes the decoded string to clipboard; Download saves it as
decoded-utf8-<timestamp>.txtwith UTF-8 encoding.Ctrl+Enter/Cmd+Enterruns both in one step. - Fix non-binary input. If you see
âš N invalid, that many chunks were wrong-length or contained non-binary chars. Either clean the input or keep “Strip non-binary” on to silently drop junk characters.
Frequently Asked Questions
What does binary to UTF-8 decoding do?
It interprets your binary input as a sequence of bytes (8-bit groups) and applies UTF-8 decoding rules to produce Unicode text. UTF-8 uses 1 to 4 bytes per character depending on the code point.
How does the tool handle emoji?
Emoji are typically encoded as 4-byte UTF-8 sequences. The tool correctly decodes them by tracking the multi-byte signal bits and combining them into a single Unicode character.
What about combining characters and accents?
UTF-8 preserves combining characters like diacritics, vowel marks, and variation selectors. The tool decodes them correctly so rendered output matches the original text.
Does it count characters, bytes, and code points?
Yes. Stats show byte count (pre-decode), code point count (logical characters), and grapheme cluster count (user-visible characters) so you understand the text fully.
Is BOM handling included?
Yes. A leading 3-byte UTF-8 BOM (EF BB BF) is detected and stripped automatically. The result is clean text without the invisible marker.
Is my data secure?
Yes. All decoding happens in your browser. Your binary input and decoded text stay on your device.
Do you log anything?
No. The tool is fully client-side.
Is this tool free?
Yes, with no sign-up and no usage limits.
What happens with invalid UTF-8?
The tool reports the byte offset where decoding fails and shows the partial result, so you can spot corruption or wrong encoding (maybe Latin-1 was intended).
Can I paste binary with separators?
Yes. Spaces, commas, colons, and newlines are stripped before byte grouping.