Binary to Text Decoder

A Cyrillic letter takes two bytes in UTF-8, so sixteen digits rather than eight. If the original code was written one byte per letter in CP1251 or KOI8-R, this decoder cannot rebuild it — you will get Latin letters and control marks instead. Check which encoding produced the bytes before you decode them.

The input field expects space-separated bytes, so a continuous run of ones and zeros has to be split into groups of eight first. Any text editor will do, or paste it eight characters at a time. If the total length is not divisible by eight, the fragment was copied incompletely and the tail is still in the source.

There is no fixed cap. Everything is decoded in the tab's memory, so the only ceiling is your device. A paragraph of text — a few thousand bytes — converts instantly. A megabyte of binary may freeze the tab for a second or two, so split very large dumps into chunks.

Yes. Both text areas scroll on a mobile screen and Copy writes to the system clipboard. The one annoyance is that a long binary string wraps across many narrow lines, which makes it easy to lose a space while editing by hand. For long dumps a desktop browser is easier.

No. The output is treated as a text string, so the bytes of an image or an archive become unprintable characters rather than a downloadable file. For binary payloads use a decoder that returns a file, such as the Base64 to File tool in the same section.

Nowhere beyond the tab. A small script on the page does the conversion without contacting any endpoint, and no history is kept. Reload or close the page and both fields are empty again, with nothing recorded on the server side.