How are Chinese characters and emoji encoded to binary?

UTF-8 encodes every Unicode code point as 1 to 4 bytes. ASCII letters ("A" → 01000001) take one byte. Most Chinese characters use three bytes ("李" → 11100110 10011101 10001110). Emoji outside the Basic Multilingual Plane use four bytes ("🎉" → 11110000 10011111 10001110 10001001). This tool uses the browser's built-in TextEncoder, so the output exactly matches what your terminal, web server, or database stores on disk.

Why is "A" 8 bits but "李" 24 bits?

UTF-8 is variable-length by design. Code points 0–127 (the original ASCII range) fit in one byte so English text stays compact. Code points 0x80 and above need 2 to 4 bytes, with continuation bytes that start with 10xxxxxx. "李" is U+674E, which is in the three-byte range (0x0800–0xFFFF), so it takes 24 bits. If you want every character to use exactly 16 bits regardless of language, switch the encoding to UTF-16.

Does the ASCII mode support extended ASCII (128–255)?

No. This tool uses strict 7-bit ASCII and throws an error the moment your text contains anything above U+007F. The reason is that "extended ASCII" isn't one thing — Windows-1252, ISO-8859-1, MacRoman and a dozen others all disagree about what byte 0xE9 means. If you have legacy bytes from a known code page, encode them in your language of choice first; for any modern text just use UTF-8.

Can I paste binary back to verify a round-trip?

Yes — flip to "Binary → Text" mode (or click Swap, which sends the current output straight into the input and switches modes). The decoder tolerates spaces, newlines and 0b prefixes, so you can copy formatted output from anywhere. If a stray non-binary character sneaks in, the error message points to its exact position; if your bit count is off by, say, 3 bits, the error says so.

What's the difference between UTF-8 and UTF-16?

UTF-8 uses 1–4 bytes per character and is byte-compatible with ASCII, which is why it's now the default for web pages, JSON, source files and Linux file systems (around 98% of the web in 2025). UTF-16 uses 2 bytes for every Basic Multilingual Plane character and 4 bytes (surrogate pair) for the rest; it's used internally by Java, JavaScript strings, and Windows APIs. Choose UTF-8 unless you have a specific reason to match a UTF-16 protocol.

Teaching how UTF-8 turns one emoji into four bytes

A CS instructor demos character encoding to a class of 30. Type "Hi 🎉", switch to 8-bit grouping, and the 🎉 visibly expands to four bytes while "H" and "i" stay one byte each. Students see why a 5-character string can weigh 7 bytes, then flip to ASCII mode and watch the same emoji throw an error at byte 128.

Verifying a round-trip before trusting a homemade decoder

You wrote a binary parser in Python and it mangles accented names. Paste "José" here as UTF-8, copy the 40-bit output, then hit Swap to decode it back. If this tool round-trips it cleanly but your code drops the "é", the bug is in your byte handling, not the data. Costs 10 seconds and rules out half the suspects.

Reading a binary string a colleague pasted in Slack

Someone drops "01001000 01101001" in a thread with no context. Paste it into Binary to Text mode, which ignores the spaces, and you get "Hi" back instantly. No need to count bits by hand or open a Python REPL. If they forgot a digit, the error tells you the count is off by 1 and where.

Building a retro 8-bit puzzle for an escape room

A game designer encodes a 12-character clue into binary for a printed prop. Using 8-bit grouping with spaces, "OPEN THE BOX" becomes a clean grid of 12 byte-blocks that fits one card. Players decode it back with any binary chart, and you confirm the answer here before sending the card to print.

Text to Binary — UTF-8, ASCII & UTF-16

Text to binary (and back) — UTF-8 aware, 8/16/32 bit grouping, emoji safe.

Runs locally
Category Encoding & Crypto
Best for Checking small payloads, tokens, hashes, and encoded values quickly.

Encoding:

Group by:

Separator:

Input

Output

Output appears here.

What this tool does

Convert text to binary and binary back to text, right in your browser. Pick UTF-8 (the modern default, handles Chinese / Japanese / emoji), strict ASCII (errors on bytes above 127, useful for teaching), or UTF-16 big-endian (2 bytes per BMP code unit). Group output in 8, 16, or 32-bit chunks, with space or 0b prefix separators — or no grouping at all for a raw bit stream. The decoder ignores whitespace and 0b prefixes, reports the exact position of any non-binary character, and tells you precisely how many bits your input is off by when it's not byte-aligned. Round-trips emoji and Han characters losslessly. No uploads, no tracking, no signup.

Tool details

Input: Text + Numbers; The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output: Live result + Copy + Download; The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy: Browser-side processing; The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share: No account required; Open the page and use it; whether results survive refresh depends on the tool.
Performance budget: Initial JS <= 14 KB; No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit: Encoding & Crypto · Developer; Category and role tags drive related tools, internal links, and quick fit checks.

How to use

1. Input

Paste or drop your content into the tool panel.
2. Process

Click the button. All processing is local in your browser.
3. Copy / Download

Copy the result or download to disk in one click.

How Text to Binary Converter fits into your work

Use it for quick browser-side encoding, decoding, hashing, token checks, and share-safe transformations.

Encoding jobs

Checking small payloads, tokens, hashes, and encoded values quickly.
Preparing values for APIs, URLs, docs, or support tickets.
Avoiding account-based tools when the input might be sensitive.

Encoding checks

Do not paste live secrets unless you are comfortable with local browser handling.
Confirm whether the operation is reversible before sharing the result.
For hashes, compare the exact algorithm and casing expected by the receiver.

Good next steps

These links move the current task into a more complete workflow.

Real-world use cases

Teaching how UTF-8 turns one emoji into four bytes
A CS instructor demos character encoding to a class of 30. Type "Hi 🎉", switch to 8-bit grouping, and the 🎉 visibly expands to four bytes while "H" and "i" stay one byte each. Students see why a 5-character string can weigh 7 bytes, then flip to ASCII mode and watch the same emoji throw an error at byte 128.
Verifying a round-trip before trusting a homemade decoder
You wrote a binary parser in Python and it mangles accented names. Paste "José" here as UTF-8, copy the 40-bit output, then hit Swap to decode it back. If this tool round-trips it cleanly but your code drops the "é", the bug is in your byte handling, not the data. Costs 10 seconds and rules out half the suspects.
Reading a binary string a colleague pasted in Slack
Someone drops "01001000 01101001" in a thread with no context. Paste it into Binary to Text mode, which ignores the spaces, and you get "Hi" back instantly. No need to count bits by hand or open a Python REPL. If they forgot a digit, the error tells you the count is off by 1 and where.
Building a retro 8-bit puzzle for an escape room
A game designer encodes a 12-character clue into binary for a printed prop. Using 8-bit grouping with spaces, "OPEN THE BOX" becomes a clean grid of 12 byte-blocks that fits one card. Players decode it back with any binary chart, and you confirm the answer here before sending the card to print.

Common pitfalls

Pasting binary with stray letters and blaming the tool. The decoder ignores spaces and 0b prefixes but a typo'd "0l001000" (lowercase L) fails; read the error, which names the exact position.
Expecting ASCII mode to handle "café" or "李". Strict 7-bit ASCII errors on anything above U+007F by design; switch to UTF-8 for any non-English text.
Assuming "李" should be 16 bits because it is "one character". UTF-8 gives it 24 bits (three bytes); pick UTF-16 only if you truly need a fixed 2-byte width.

Privacy

Every conversion runs entirely in your browser via the built-in TextEncoder and TextDecoder. Your text and binary never leave the page, never hit a server, and are not logged. Your input is not written to the URL either, so pasting a password or private message here leaves no trace in history or shareable links. Close the tab and it is gone.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Browse all tools for this role

Text to Binary — UTF-8, ASCII & UTF-16

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How Text to Binary Converter fits into your work

Encoding jobs

Encoding checks

Good next steps

Real-world use cases

Teaching how UTF-8 turns one emoji into four bytes

Verifying a round-trip before trusting a homemade decoder

Reading a binary string a colleague pasted in Slack

Building a retro 8-bit puzzle for an escape room

Common pitfalls

Privacy

FAQ

Morse Code Translator

ROT13 Encoder & Decoder

ASCII Table Reference

Base64 Encoder & Decoder

URL Encoder / Decoder

MD5 / SHA Hash Generator

Base64 Image Converter

QR Code Generator

HTML Entities Encoder

AES Text Encryptor

Affine Cipher Encoder & Decoder

Atbash Cipher