Binary to Text Converter
Convert Binary to Text instantly in your browser.
0 characters
0 characters
Everything is converted in your browser. Nothing you paste is uploaded or stored.
Worked example
Each row shows a short sample written as Binary, and the same value converted to Text.
| Binary input | Text output |
|---|---|
| 01001000 01101001 | Hi |
| 01010011 01000111 | SG |
| 01110100 01101111 01101111 01101100 | tool |
In-depth guide
Binary to text: reading 0s and 1s as characters
How binary is split into bytes and decoded as UTF-8, which input formats the converter accepts, why multi-byte characters need all their bytes, and what each error means.
Key figures at a glance
- Group size
- 8 bits per byte
- A run of digits with no spaces must be a multiple of 8 long, then it is cut into bytes.
- Separators
- Space, comma, semicolon, colon, hyphen or underscore
- Groups shorter than 8 digits are accepted when separated, for example 1001000 1101001 reads as Hi.
- Decoding
- Strict UTF-8
- Bytes that are not valid UTF-8 produce an error instead of replacement characters.
- Source: RFC 3629
- Value range
- Each group must be 0 to 255
- A separated group that is longer than 8 digits and above 11111111 is rejected as out of range.
Decoding binary to text step by step
The converter does this on every keystroke.
-
Step 1: Split into bytes
Step 1Separate the digits into groups of 8. Pasted input with spaces or commas is split on them; an unbroken run is cut every 8 digits.
-
Step 2: Convert each byte to a number
Step 2Add the place values 128, 64, 32, 16, 8, 4, 2, 1 wherever there is a 1. 01001000 is 64 + 8 = 72.
-
Step 3: Read the bytes as UTF-8
Step 3A byte starting with 0 is a character by itself. A byte starting with 110, 1110 or 11110 begins a character of 2, 3 or 4 bytes.
-
Step 4: Check the result
Step 4If you get an error or odd characters, the bits are probably cut in the wrong place or are not UTF-8 text.
What the converter accepts
Paste binary with spaces, commas or line breaks between bytes, or as one unbroken string. If the string has no separators and is longer than 8 digits, its length must be a multiple of 8, otherwise the tool reports the length problem rather than guessing. Digits other than 0 and 1 are rejected and the message names the offending group.
Worked examples
| Binary input | Result | Why |
|---|---|---|
| 01001000 01101001 | Hi | 72 and 105 |
| 0100100001101001 | Hi | Unbroken, cut every 8 digits |
| 1001000 1101001 | Hi | 7-bit groups are accepted when separated |
| 11000011 10101001 | é | Two bytes: a 110xxxxx lead byte and a continuation |
| 11100100 10111000 10101101 | 中 | Three bytes for one Chinese character |
| 11111111 | error | 255 is never valid on its own in UTF-8 |
| 101010101 | error | 9 digits, not a multiple of 8 |
Why a multi-byte character needs every byte
In UTF-8, 11000011 alone is only the first half of a character. If you paste just one byte of 中, or cut the string in the middle of a character, the tool cannot show it as text and says so. Keep the bytes of one character together and in order.
Tip: If your binary came from a source that used 16-bit or 32-bit units (UTF-16 or UTF-32), it will not decode as UTF-8 text here. Characters would come out as odd symbols or an error.
Reading by hand
Take 01100001. The set bits are 64, 32 and 1, so the value is 97, which is a in ASCII. Values from 0 to 127 are ASCII; anything from 128 up is part of a multi-byte UTF-8 character.
Where you meet binary text
Teaching, puzzles, geocaching and CTF challenges, and debugging low-level data. Binary text is a readable view of bytes, not a storage format.
Common mistakes
- Wrong grouping. Starting a group one digit late shifts every later byte, giving nonsense or an error.
- Treating 7-bit and 8-bit the same. A leading 0 is part of an 8-bit byte; leaving it out only works when the groups are separated.
- Decoding UTF-16 or an image as text. Not all bytes are text.
- Expecting the result to be translated. The tool decodes characters; it does not change language.
Related tools
- Text to binary — encode text as bits.
- Binary to ASCII — see the decimal values of the bytes.
- Hex to text — decode hexadecimal bytes.
- Octal to text — decode octal bytes.
- Unicode explorer — look up a character.
Frequently asked questions
Is my data sent anywhere?
No. The conversion runs entirely in your browser using JavaScript. Nothing you paste leaves your device, is logged, or is stored.
How should I separate values?
Spaces work, and so do commas, colons and semicolons. For binary, hex and octal you can also paste a single unbroken run of digits — it is split into bytes automatically.
Does it handle emoji and non-English text?
Yes. Text is treated as UTF-8, so accented characters, Chinese, Tamil and emoji all convert correctly. They simply take more than one byte each.
Why did I get an error?
The input contained a character that is not valid for the source format, a value above 255, or a run of digits that does not divide evenly into bytes. The message names the specific token so you can find it.
Sources
- RFC 3629 — UTF-8, a transformation format of ISO 10646 — How bytes map to characters.
- MDN — TextDecoder — Browser UTF-8 decoding.
This guide explains published rules in plain language. It is not financial, legal or official advice — rules change, so confirm with the agency linked above before you commit.