Text to Binary Converter
Pick a conversion, type or paste, and the result updates live. Nothing you enter leaves your browser.
Byte-accurate conversion, not just ASCII
Text → Binary and Text → Hex both start by encoding your text
with TextEncoder, which produces the exact UTF-8
bytes a browser or server would send over the network — then
each byte is formatted as 8-bit binary or 2-digit hex,
space-separated. Binary → Text and Hex → Text reverse the
process: each token is parsed back into a byte, and TextDecoder reassembles the original text.
Malformed tokens (wrong length, invalid characters) are caught
and reported instead of producing garbled output.
Worked example
Converting Hi! 👋 — 4 plain-ASCII characters plus a
waving-hand emoji — produces exactly:
Binary:
01001000 01101001 00100001 00100000 11110000 10011111 10010001 10001011
Hex:
48 69 21 20 f0 9f 91 8b
That's 8 bytes for 5 visible characters — "H", "i", "!", and the
space are 1 byte each, and the emoji alone takes the remaining 4
bytes. Converting either result back through Binary → Text or
Hex → Text returns Hi! 👋 exactly, with the emoji
intact.
Frequently asked questions
Why does one character sometimes turn into multiple bytes?
This tool encodes text as UTF-8, the byte encoding the modern web runs on. Plain ASCII characters (a–z, 0–9, basic punctuation) are 1 byte each, but most other Unicode characters take more: accented letters and many symbols are 2 bytes, most CJK (Chinese/Japanese/Korean) characters are 3 bytes, and characters outside the Basic Multilingual Plane — including most emoji — are 4 bytes. "Hi! 👋" is a good example: H, i, !, and the space are 1 byte each (4 bytes total), but the waving-hand emoji alone takes 4 more bytes — 8 bytes for 5 visible characters.
Is this the same as Base64?
No — different purpose and format. Binary and hex here show you the raw byte values directly (each byte as 8 ones-and-zeros, or as 2 hex digits), which is useful for understanding exactly how text is stored or transmitted at the byte level. Base64 instead re-packs those same bytes into a compact, text-safe alphabet (letters, digits, +, /) meant for carrying data through systems that only handle plain text, like email or data URIs. If you want that compact text-safe format rather than raw byte values, use the base64-encoder-decoder tool instead.
Can I convert really long text?
Yes — there's no artificial length limit. The practical ceiling is your browser's memory, which for text of any normal size (even a full article or a large log excerpt) won't be a concern.
What about plain ASCII text — does it work the same way?
Yes, exactly the same process runs either way. ASCII text just happens to encode as exactly 1 byte per character, so the binary and hex output ends up simpler — no character takes more than 8 bits or 2 hex digits, since every ASCII code point fits well within a single UTF-8 byte.