Binary Code Translator

Paste ones and zeros to read them as text, or type text to see the binary that encodes it — both directions run in this page, with no upload and no waiting.

How to Use the Binary Code Translator

The binary code translator runs in both directions, so the first decision is which way you are heading: binary to text, or text to binary.

1. Pick a direction. The two tabs at the top of the tool switch between Binary → Text and Text → Binary, and the labels on the input and output boxes change with them.
2. Add your input. Paste from a log line, a memory dump, a chat message, or type straight into the box. On the binary side, spaces, commas, tabs and line breaks are treated as separators, and a 0b prefix in front of each group is stripped before anything is decoded.
3. Choose the encoding. UTF-8 is the default and fits most text. ASCII, UTF-16 and GBK are there for older data and for strict checks.
4. Use the result. The output updates about 150 ms after you stop typing. Copy it, clear the form, or press Swap to push the result through the opposite direction and confirm it survives the round trip.

The Convert button exists for the cases where you want an explicit action: a screen-reader announcement, a screenshot, or a paste you want to inspect before committing. Auto-conversion and the button call the same function, so the output is identical either way — the button simply skips the debounce.

Text to Binary and Back

A binary code translator is only as good as its round trip: whatever you decode should encode back to the same bytes, and whatever you encode should decode back to the same characters.

That symmetry depends on the encoding setting, not on the tool. Encode the word café as UTF-8 and you get seven bytes, because é takes two. Encode it as ASCII and the fourth character is rejected, since é sits at 233 and ASCII stops at 127. The same string in UTF-16 doubles every character to two bytes, which is why UTF-16 output looks twice as long as the text you typed. GBK lands in between: one byte for Latin letters, two for most Chinese characters.

The Swap button makes that symmetry visible. Decode a binary string, press Swap, and the decoded text becomes the input for the encode direction, producing the original bits whenever the encoding matches. When it doesn't match, the difference is informative rather than broken: a string encoded as UTF-16 and decoded as UTF-8 comes back with a null character between every letter, which tells you the source was almost certainly a Windows tool.

Invalid input is reported, never silently dropped. If a character other than 0 or 1 appears where a bit should be, the status line names its position in your original paste, quotes the character, and shows the surrounding text so you can find it. Text that cannot be represented in the selected encoding gets the same treatment, with the character number and the offending symbol. Nothing is truncated and nothing is guessed.

Binary Code Formats Explained

Binary code arrives in more shapes than most people expect, and a binary code translator that accepts only one of them forces you to reformat by hand before you can do anything useful.

The usual form is eight bits per character with spaces between groups: 01001000 01101001. The spaces carry no data. They exist so a human can count the boundaries without losing their place. Some tools print a 0b prefix, a convention borrowed from Python, C++14 and Rust, where 0b01001000 is a single binary literal. Others print a continuous stream with no separators at all, which is what you get from a memory viewer or a network capture. This page accepts all three and also tolerates commas, tabs and line breaks, because that is what binary looks like when it is pasted out of a spreadsheet.

Hex is the other shorthand you will meet. Four bits map to one hex digit, so a byte becomes two characters: 01001000 is 48, and 01101001 is 69. Hex is shorter and easier to scan in a column, but it hides the bit pattern, which is why tutorials still show binary when the point is to explain how a byte is built.

How a byte becomes a letter

A byte holds a number from 0 to 255. ASCII assigns the first 128 values to letters, digits, punctuation and control codes, so a byte can become a character through a single lookup. Take the word Hello:

01001000  =   72  =  H
01100101  =  101  =  e
01101100  =  108  =  l
01101100  =  108  =  l
01101111  =  111  =  o

Read the first group left to right and the weights are 128, 64, 32, 16, 8, 4, 2, 1. Only the 64 and the 8 are set, so the value is 72, and 72 is H. The same method gives 01101001 = 105 = i, which is why 01001000 01101001 reads as Hi — a two-character check worth running against any decoder you have not used before.

UTF-8 keeps those 128 values identical and uses two to four bytes above them, so an English string encodes to exactly the same bits in both encodings. That compatibility is why UTF-8 took over, and why a UTF-8 decoder is a reasonable default when you have no idea where a binary string came from. Strip away the notation and a binary code translator is a byte splitter plus a lookup table; the rest is deciding which table the bytes were written with.

ASCII and UTF-8 reference table

The table below lists every printable ASCII character with its 8-bit binary, decimal and hex value. UTF-8 leaves the range 0–127 untouched, so these are also the UTF-8 bytes for the same characters.

95 characters

Control characters such as tab (00001001) and line feed (00001010) are left out because they do not render, but they decode normally if they appear in your input.