Binary to Text Converter

Convert binary strings to readable text and encode text to binary representation with configurable bit length.

Tested tool guide Tested browser tools Checked August 16, 2026

What Binary to Text Converter does, with a checked example

Paste a string of ones and zeros and the words it encodes appear as text; type plain text and it comes back as spaced groups of bits. Each group is a number written in binary, and the converter trades each number for the character with that code. The setting users misjudge is bit length: 8 bits per character covers ordinary ASCII text, but 7-bit and 16-bit groupings exist too, and a snippet that decodes cleanly at one width can read as nonsense at another. Check the width before blaming the output.

Worked example

A concrete input and expected output from the current implementation.

Input

01001000 01100101 01101100 01101100 01101111

Expected output

Hello

Each 8-bit group is a binary number: 01001000 is 64 + 8 = 72, the code for 'H', and 01100101 is 101, the code for 'e'. Decoded at the 8-bit width the five groups spell 'Hello'. Encoding 'Hello' the other way produces exactly the same five groups.

How the result is produced

How decoding works

Input is split into groups of digits, one per character, and each group is read as an unsigned binary integer: 01100101 is 101 in decimal. That number is looked up as a character code, so 101 means lowercase 'e'. The bit-length setting fixes the width of each group: 8 bits covers codes 0 to 255, 7 bits only 0 to 127. Leftover digits after the last whole group are the usual sign that the width does not match how the binary was produced.

How encoding writes bits

Going the other way, each character's numeric code is written in base 2 and padded with leading zeros so every group has exactly the chosen width. Lowercase 'a' is 97, which is 1100001 in 7 bits and 01100001 in 8 bits; both decode back to 'a', but the strings differ. Characters whose code exceeds the width's range cannot fit: 'é' (U+00E9) needs 8 bits, and a code point like U+1F600 needs a 4-byte UTF-8 sequence or a UTF-16 surrogate pair.

Good uses

Decode a binary string from a puzzle, forum post, or chat message - the '01001000 01100101 01101100 01101100 01101111' pattern - without working it out bit by bit.
Encode a short phrase into binary for an escape room, scavenger hunt, or handmade card where someone else is meant to decode it by hand.
Verify the output of a decoder or encoder you are writing, or read what a binary fragment from a file or log actually says before acting on it.

Limits and checks

Width mismatch reads as garbage: text encoded at 16 bits decoded at 8 comes out doubled or broken, and 7-bit groups decoded at 8 only survive because ASCII letters are all under 128. Match the width to the source that produced the binary.
8 bits represents only codes 0 to 255. Accented letters, emoji, and CJK characters have larger codes, so they decode as mojibake or missing characters at 8 bits; encode them at 16 bits or as UTF-8 bytes instead.
Delimiters decide the result: '01001000 01100101' is two 8-bit groups, while '0100100001100101' is only decodable because its length is a multiple of 8. Inconsistent spacing, or a total length that does not divide evenly by the width, makes identical digits parse differently or fail.

Common questions

Why does my binary decode to gibberish instead of my message?

Almost always a bit-width mismatch: the binary was produced at one width and you decoded at another, so each group lands on the wrong character, or the groups never aligned in the first place. Encode a word you know at each width and compare to find the matching setting, and make sure spaces separate whole groups.

Can I paste binary with no spaces at all?

Only if the run of digits is a multiple of the bit length. At 8 bits, 0100100001100101 splits into 01001000 and 01100101, which decode as 'He'. When the length does not divide evenly, leftover bits have no character behind them, so the conversion fails or drops a character. Consistent spacing between groups avoids the ambiguity.

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.