Binary Code Translator

Translate text to binary code and binary sequences back to readable text with ASCII/UTF-8 encoding support.

Tested tool guide Tested browser tools Checked August 15, 2026

What Binary Code Translator does, with a checked example

This tool converts characters to their binary form and back. Encoding mode takes each character, maps it to its ASCII or UTF-8 byte value, and writes that value as an 8-bit string of 0s and 1s, with a space between bytes. Decoding mode reverses this: it reads 8-bit groups, converts each to a byte value, and reassembles the bytes as text. The most common surprise is byte count on non-ASCII input - an accented letter or emoji is not one 8-bit group under UTF-8, it is two to four, because those code points don't fit in a single byte.

Worked example

A concrete input and expected output from the current implementation.

Input

Hi

Expected output

01001000 01101001

H is ASCII/UTF-8 byte 72 (01001000) and i is byte 105 (01101001); each character maps to one 8-bit group separated by a space.

How the result is produced

Text to binary

Each input character is converted to its Unicode code point, then encoded as one or more bytes (1 byte for ASCII characters, up to 4 for UTF-8 characters outside the ASCII range). Every byte's numeric value (0-255) is written as an 8-digit base-2 string with leading zeros preserved, and the groups are joined with single spaces.

Binary to text

The input is split on whitespace into 8-character chunks; each chunk is parsed as a base-2 integer to recover a byte value (0-255). The resulting byte sequence is then decoded as UTF-8 text. Chunks that aren't exactly 8 digits of 0s and 1s, or that don't form a valid UTF-8 byte sequence, produce an error or garbled output rather than a silent guess.

Good uses

decoding a binary string handed out in a CTF challenge or puzzle hunt
converting a word or short message into binary for a computer science exercise
checking how many bytes UTF-8 uses to represent a specific accented letter, symbol, or emoji

Limits and checks

characters outside plain ASCII (accents, CJK text, emoji) expand to 2-4 bytes each under UTF-8, so the output has more 8-bit groups than there are visible characters
decoding requires each group to be exactly 8 binary digits with no stray characters; binary copied from a source that wraps lines or drops leading zeros will not decode cleanly
a byte sequence that is valid binary but not valid UTF-8 (for example, a stray continuation byte with no lead byte) will fail to decode into text even though the binary itself is well-formed

Common questions

Why did one emoji turn into 32 binary digits instead of 8?

Most emoji sit outside the Basic Latin range and require 4 bytes under UTF-8 encoding, not 1. Four bytes means four 8-digit groups, 32 digits total. This is expected UTF-8 behavior, not a tool error - switching to an ASCII-only assumption would simply fail on that character.

Can I paste binary without spaces between bytes?

The decoder expects 8-digit groups to know where one byte ends and the next begins; a single unbroken run of digits is ambiguous unless the tool documents an assumption of fixed 8-bit chunking. If your source has no separators, re-insert a space every 8 digits before decoding.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.