Binary to Text Converter
Translate binary code (sequences of 0s and 1s) into plain English text. Works by grouping binary digits into 8-bit bytes and converting each byte to its corresponding ASCII or Unicode character. Essential for decoding binary data from computers, networks, or digital communications.
How to Use This Converter
Two modes cover both directions — binary to text and text to binary. Everything else (encoding, delimiter, bit length) is adjustable below the toggle.
1. Pick the direction
Use the top toggle to switch between Binary → Text (decode) and Text → Binary (encode). The input and output labels swap accordingly.
2. Paste your input
Type or paste into the left textarea, or click Paste to read from the clipboard. The output updates in real time as you type.
3. Choose the encoding
8-bit ASCII is the default — each character is one byte. 7-bit ASCII is the older standard. 16-bit Unicode handles characters beyond the ASCII range. UTF-8 handles any modern text including emoji.
4. Set the byte delimiter
Space-separated bytes (01001000 01101001) are the most common format. Newline-separated works for multi-line dumps. Comma-separated matches CSV-style data. "None" concatenates everything into one long binary string.
5. Copy or download
Use Copy output to put the result on the clipboard, or Download to save it as a .txt file. Copy input copies the raw input for reuse elsewhere.
6. Load a sample
The pill buttons below the status row load common test strings like "Hello", "Hi", and "Hello, World!" — useful for verifying the tool works as expected.
What This Tool Offers
Built around the fundamental binary ↔ text relationship, with the flexibility to handle the encodings and formats you actually encounter.
Bidirectional conversion
Decode binary to text or encode text to binary — one tool, both directions, with a single click to swap.
Four encodings
8-bit ASCII, 7-bit ASCII, 16-bit Unicode, and UTF-8. UTF-8 handles every character in the Unicode standard, including emoji and non-Latin scripts.
Flexible delimiters
Space, newline, comma, or no delimiter at all — decode whatever format your source uses without manual cleanup.
Live conversion
Output updates as you type. No "convert" button — the result is always in sync with the input.
Input validation
Malformed input (non-binary characters, wrong-length bytes) is flagged with a clear status message instead of silently producing garbage.
Copy and download
Copy the result to your clipboard or save it as a .txt file. Both work on all modern browsers.
What Does Binary-to-Text Conversion Do?
Computers store and transmit everything as binary — sequences of 0s and 1s. To a human, a stream like 01001000 01101001 is meaningless, but to a computer it is the two characters "Hi". Binary-to-text conversion bridges those two worlds: it reads the binary as a series of fixed-length chunks (typically 8 bits each), interprets each chunk as a number, and looks that number up in a character encoding table like ASCII or Unicode. The result is text a person can read and use.
The Conversion Formula
At the most basic level, the process is a three-step recipe:
2. Parse each chunk as a base-2 number → get its decimal value.
3. Look up that decimal value in the character table → get the character.
For example, the 8-bit chunk 01001000 is the decimal number 72, which in ASCII is the capital letter H. 01101001 is decimal 105, which is lowercase i. So the sequence 01001000 01101001 decodes to Hi.
To go the other direction (text to binary):
2. Convert that number to binary (base 2).
3. Pad it with leading zeros to the chosen bit length (8, 7, or 16).
4. Join the chunks with the chosen delimiter.
Character Encodings at a Glance
| Encoding | Bits per char | Range | Characters covered | Typical use |
|---|---|---|---|---|
| 7-bit ASCII | 7 | 0 – 127 | English letters, digits, common punctuation, control codes | Legacy systems, old protocols |
| 8-bit ASCII | 8 | 0 – 255 | 7-bit ASCII plus extended Latin-1 characters (é, ü, ñ …) | Common default, still widely used |
| 16-bit Unicode (UTF-16) | 16 | 0 – 65,535 (BMP) | Almost all modern scripts: Latin, Greek, Cyrillic, Arabic, CJK, most emoji | Windows internals, Java, C# |
| UTF-8 | 8 – 32 (variable) | 0 – 1,114,111 | Every character in the Unicode standard, including all emoji | Web, files, modern protocols |
Common Binary-to-Text Examples
01001000 → 72 → H01101001 → 105 → i01001000 01101001 → "Hi"
→ 01001000 01100101 01101100 01101100 01101111
01010110 01101111 01110010 01111010 01100101 01110000→ V o r z e p → "Vorzep"
00110011 00110001 00110001 → 3 1 1→ "311" (the number, as text)
Why 8 Bits per Character?
The byte — 8 bits — is the fundamental unit of modern computing. Early telegraph and teletype systems used 5 or 7 bits per character, which was enough for uppercase English letters and a handful of punctuation marks. As computing spread to lowercase letters, extended characters, and non-English scripts, 7 bits stopped being enough. The industry settled on 8 bits as the standard in the 1970s, and it has stuck: every byte-addressable machine since then has used 8-bit bytes, and every modern character encoding builds on top of them.
UTF-8, which dominates the modern web, is a clever extension of this design. It uses 8-bit bytes but encodes characters in 1, 2, 3, or 4 bytes depending on the code point. The first 128 code points (plain ASCII) are stored as-is in one byte, so UTF-8 is backwards-compatible with ASCII. Everything else takes more bytes — Greek and Cyrillic letters take 2 bytes, most CJK characters take 3, and rare scripts and emoji take 4. This makes UTF-8 both efficient for Latin text and capable of representing every character in the Unicode standard.
Frequently Asked Questions
Three common reasons. First, the byte length is wrong — if the binary was produced with 7-bit or 16-bit encoding, it will decode to garbage when treated as 8-bit. Second, the binary represents compressed, encrypted, or image data rather than plain text, in which case the "characters" you get back are meaningless bytes. Third, the binary is for a non-ASCII encoding you have not selected. Try switching the encoding to 7-bit, 16-bit, or UTF-8 and see if the output improves.
Yes — switch the encoding to UTF-8. UTF-8 covers every character in the Unicode standard, including emoji, Chinese, Japanese, Korean, Arabic, Hebrew, and Devanagari. When decoding, the tool sends the byte stream through the browser's built-in UTF-8 decoder, which correctly handles multi-byte sequences. Note that emoji are usually 4 bytes long in UTF-8, so they will not fit in a single 8-bit byte — that is a limitation of the encoding, not the tool.
Spaces between bytes are conventional and make the binary readable at a glance — you can see where each byte starts and ends. But they are not required. If your binary has no delimiters, select "None" and the tool will split it into fixed-length chunks by counting bits. If it uses newlines (one byte per line, common in dumps), select "Newline". If it uses commas (CSV exports), select "Comma". The tool handles all four formats transparently.
Both are ways to represent the same underlying data using different bases. Binary uses base 2 (two symbols: 0 and 1) and is how computers physically store data. Hexadecimal uses base 16 (sixteen symbols: 0–9 and A–F) and is how humans usually write it, because each hex digit represents exactly 4 bits — so a byte is two hex digits, which is much more compact than eight binary digits. One hex byte like 48 equals 01001000 in binary equals 72 in decimal equals the letter H in ASCII.
Yes — select "16-bit Unicode" and each character is expected as a 16-bit chunk. This handles the Basic Multilingual Plane (BMP), which covers almost all characters you are likely to encounter. However, characters outside the BMP (including most emoji) require surrogate pairs — two 16-bit code units — and pure 16-bit decoding of those requires proper UTF-16 handling. If you suspect your binary contains characters outside the BMP, use UTF-8 mode instead: it is more robust and handles all code points uniformly.
No. This converter runs entirely in your browser. The input you type is processed by JavaScript on your device and never sent to a server. You can safely use it to convert sensitive data — binary dumps, credentials, proprietary text — without any privacy concern. Even the "Copy link" button only copies the current page URL, not your data.
Variables
| Symbol | Quantity | Unit |
|---|---|---|
| binary | Binary Input | bits |
| text | Decoded Text | characters |
What it means
Binary is the fundamental language of computers. Each character you type is stored as a sequence of 0s and 1s. This converter performs the reverse operation: it takes binary strings and reconstructs the original characters so you can read them.
Worked example
Example 1 – Converting "Hello"
Basic Example| Parameter | Value |
|---|---|
| Binary Input | 01001000 01100101 01101100 01101100 01101111 |
| Encoding | ASCII (8-bit) |
| Characters | 5 |
Example 2 – Decoding "Hi!"
ASCII Example| Parameter | Value |
|---|---|
| Binary Input | 01001000 01101001 00100001 |
| Encoding | ASCII (8-bit) |
| Total Bytes | 3 |
Example 3 – Continuous Binary String
Real-World| Parameter | Value |
|---|---|
| Binary Input | 0101011101101111011100100110110001100100 |
| Grouped Bytes | 01010111 01101111 01110010 01101100 01100100 |
| Encoding | ASCII (8-bit) |
Common mistakes
- Forgetting to group binary digits into 8‑bit chunks.
- Using non‑standard binary separators (spaces, commas).
- Assuming all binary input is ASCII; Unicode may require more bits.
- Mixing up endianness when bytes are stored in reverse order.
Applications
- Decode binary data from files or network streams.
- Translate machine code to human‑readable text.
- Debug binary messages or protocols.
- Learn how binary encoding works in computing.
Related calculators · Data Encoding & Conversion
Recently updated formulas
Suggest an improvement
Found a mistake? Have a better example? Let us know.
You may send up to 3 suggestions per 24 hours.