English
العربية
Deutsch
Español
Français
Italiano
Português
Русский
Türkçe
Tiếng Việt
Binary to Text Converter
Decode a stream of bits into readable text, and see why byte order can change the result.
The same eight bytes can spell two different things depending on which end you start reading from. That is not a hypothetical — it is called endianness, and it is a real source of corrupted files and garbled network data.
From a bit stream to letters
A raw stream of binary has to be split into fixed-size chunks before it means anything. For text, that chunk is almost always one byte, 8 bits, decoded against a character table such as ASCII or UTF-8. Get the chunk size wrong — split into 7-bit groups instead of 8, say — and every character after the mistake comes out wrong.
Numbering the bits inside a byte also follows a convention worth knowing: the rightmost bit is called bit 0, not bit 1. This is the same reason array indexes in most programming languages start at 0 rather than 1 — the count reflects an offset from the start, and the first position is zero positions away from itself.
Same bytes, different order
Endianness is about which end of a multi-byte value gets stored first. Big-endian writes the most significant byte first, the way you would naturally write a number left to right. Little-endian writes the least significant byte first — backwards, from a human’s point of view, but it is how most everyday processors, including the x86 chips in most PCs, actually store data.
The number 1, stored as four bytes, is 00 00 00 01 in big-endian and 01 00 00 00 in little-endian — identical bytes, opposite order, two completely different numbers if you decode them assuming the wrong one. Network protocols standardise on big-endian for exactly this reason, so two machines with different native byte orders can still agree on what a value means.
Where this trips people up in practice
- A file format that specifies its byte order in a header, and gets misread by a tool that assumes the wrong default.
- Binary data copied between a big-endian system and a little-endian one without conversion.
- Multi-byte Unicode text, where UTF-16 can be either big-endian or little-endian depending on the byte-order mark at the start of the file.
- Network packets, which use big-endian by convention regardless of the sending or receiving machine’s native order.
- Debugging a hex dump where a value looks plausible but is actually its own bytes reversed.
Binary to text questions
How does a program know where one character ends and the next begins?
For plain ASCII text, every character is exactly one 8-bit byte, so the bit stream is simply split into groups of eight from the start. Multi-byte encodings like UTF-8 use extra marker bits within each byte to signal how many bytes a character spans.
What is endianness in plain terms?
It is the order in which the bytes of a multi-byte value are stored: most significant byte first, called big-endian, or least significant byte first, called little-endian. The individual bits inside each byte are not reordered, only the sequence of whole bytes.
Why does endianness matter for converting binary to text?
Single-byte text like plain ASCII is not affected, since there is only one byte per character to worry about. Multi-byte encodings, such as UTF-16, can be stored in either order, and decoding with the wrong assumption produces the wrong characters entirely.
Why do array indexes and bit numbering start at 0?
Because the number represents an offset from the starting position, not a count of items. The first bit or the first array element is zero positions away from the start, which is why it is labelled 0 rather than 1.
Which byte order do most modern computers use internally?
Little-endian, since the x86 and x86-64 processors common in desktops and laptops use it natively. Network protocols and some file formats still standardise on big-endian, which is why conversion between the two remains relevant.
