Preserve every byte boundary
Translate UTF-8 text and binary bytes
Enter text or binary within the bounded limit shown by the interface, choose the direction, and copy the complete result. Binary input must resolve to complete octets and valid UTF-8.
Loading the binary translator…
Enable JavaScript to translate and copy values. The UTF-8, byte-boundary, validation, and scope guidance remains readable below.
Characters become bytes first
How text becomes binary with UTF-8
Unicode assigns a code point to each encoded character, but a code point is not automatically one byte. UTF-8 maps every Unicode scalar value to a sequence of one to four bytes. The translator then displays each byte with eight binary digits, preserving leading zeroes so byte boundaries remain visible.
ASCII occupies code points U+0000 through U+007F. UTF-8 represents that range with the same single-byte values, so the letter A is U+0041, byte hexadecimal 41, and binary 01000001. The Korean syllable “한” is U+D55C and becomes three UTF-8 bytes: ED 95 9C, displayed as 11101101 10010101 10011100.
User-perceived characters can contain more than one code point. An accented letter may be precomposed or may use a base letter plus a combining mark; an emoji sequence may include variation selectors, modifiers, or zero-width joiners. The translator encodes the exact string provided and does not normalize it silently.
Binary output is a representation of text bytes, not “the language computers speak” in one universal sense. Machine instructions, compressed streams, images, encrypted values, floating-point layouts, and protocol records all use bits but require their own formats and parsers.
- Character
- An element of text represented by one or more Unicode code points.
- Code point
- A Unicode number such as U+0041 or U+D55C.
- UTF-8 byte
- One octet in the variable-width UTF-8 encoding.
- Binary display
- Eight zero-or-one digits for each UTF-8 byte.
- Scope
- Bounded Unicode text and strict UTF-8 bytes; not arbitrary binary formats.
A digit can be data or notation
Numeric zero and the character “0” are different inputs
A number-base converter treats digits as a notation for a mathematical value. Decimal zero, binary zero, and hexadecimal zero all describe the quantity 0. Minimal binary notation writes that value as 0.
A text translator treats the displayed glyph “0” as a character. Unicode assigns it U+0030, and UTF-8 encodes it as the byte 30 hexadecimal. Writing that byte in binary produces 00110000. The leading bits are not optional padding for a number; they belong to the complete byte representation of the character.
The same distinction applies to text “10.” As a binary integer it represents decimal two. As two text characters, UTF-8 contains bytes 31 30, displayed as 00110001 00110000. Select the tool by the data contract rather than by whether the input happens to contain zeroes and ones.
Use explicit base, sign, and width controls instead of decoding the digits as text bytes.
Open the Binary Converter →Reject ambiguity and data loss
Complete octets and strict UTF-8 decoding
01002A bit may only be zero or one; unsupported syntax stops parsing.0100000Seven bits do not identify a complete UTF-8 byte, so the tool does not invent padding.11100010 10000010The leading byte requires another continuation byte; decoding stops.11000000 10000000Overlong and otherwise malformed encodings are rejected rather than normalized.format-specificA byte sequence may belong to another encoding or binary format; this page does not guess.Translate one owned layer
A reliable binary-to-text workflow
- 1
Confirm the data is text bytes
Use this translator only when the source contract says the bits form UTF-8, not a number, encrypted message, compressed file, or machine instruction.
- 2
Preserve complete octets
Keep eight bits per byte and use only separators accepted by the interface. Do not delete or add bits to make the input decode.
- 3
Treat errors as evidence
An invalid sequence may reveal truncation, the wrong encoding, or arbitrary binary content. Keep the original bits when investigating the source.
Local conversion, explicit limits
Translate copied byte strings without a remote service
Text encoding and binary decoding run in the current browser tab. LiveParse does not send input to a translation endpoint, save a history, identify the content, or try the result as code. The interface displays a bounded limit so conversion and output rendering remain responsive.
Binary notation does not conceal content. Anyone who receives the bits can recover valid UTF-8 text. Remove secrets before copying output to an issue, chat, documentation page, or prompt, and remember that browser extensions and clipboard managers operate outside the page.
For normative behavior, consult the WHATWG UTF-8 encoding definition and the Unicode Standard. The RFC 20 ASCII table documents the 7-bit range that UTF-8 preserves as identical single-byte values.
Find one ASCII-range character's decimal, hexadecimal, octal, and 8-bit binary values without translating a whole message.
Open the ASCII Table →Questions answered
Binary translator FAQ
How does the binary translator convert text?
It encodes the text as UTF-8, then writes every resulting byte as eight binary digits. ASCII-range characters keep their familiar one-byte values, while many other Unicode characters require two, three, or four bytes.
Why is character 0 different from numeric zero?
The numeric value zero is binary 0. The text character 0 is Unicode U+0030, which UTF-8 encodes as byte 30 hexadecimal or 00110000 binary. A numeral converter and a text translator therefore answer different questions.
Must binary text be grouped into eight bits?
UTF-8 is a byte encoding, so decoding begins with complete 8-bit octets. Supported visual separators may be ignored as shown by the interface, but the remaining bit count must form complete bytes; the tool does not pad an incomplete final group.
What happens when binary bytes are invalid UTF-8?
The translation stops with a diagnostic instead of inserting replacement characters. This preserves evidence that the input is truncated, malformed, uses another encoding, or contains arbitrary binary data rather than valid UTF-8 text.
Can a binary translator decrypt a message or open a binary file?
No. It only changes between UTF-8 text and an explicit binary display of those bytes. It does not decrypt ciphertext, decompress data, execute machine code, identify file formats, or recover meaning from arbitrary bytes.
Is binary or text input uploaded?
No. UTF-8 encoding and strict decoding run in the current browser tab without sending the input to a translation service. The bounded input limit shown in the interface protects responsiveness; clipboard tools and extensions remain separate boundaries.