Binary to String Converter: Binary, Hex & Base64 to Text
Convert binary to text, hex to string, and Base64 to text in one tool. Uses UTF-8 encoding so you get readable output for any language. Free, runs in your browser, and supports 7-bit ASCII or 8-bit bytes. Use it to decode binary strings, hexadecimal data, or Base64-encoded text instantly.
What is a binary to string converter?
A binary to string converter (or binary to text converter) turns a sequence of 0s and 1s into human-readable text. Computers store all data as binary; this tool interprets those bits as UTF-8 (or 7-bit ASCII when the bit count fits), so you see the actual characters. You can also go the other way: type or paste text and get the corresponding binary string, hex, or Base64 representation. That makes it useful for debugging, learning encoding, handling API payloads, and quick conversions without writing code.
This converter supports three formats in one place: binary (space- or comma-separated or clumped), hexadecimal (with or without 0x and spaces), and Base64. Choose the format in the toolbar; the same conversion logic runs so you get consistent, accurate results whether you're decoding binary to string, hex to text, or Base64 to plain text.
How to convert binary to text (step by step)
To convert binary to text manually or to understand what the tool does: split your binary into groups of 8 bits (one byte each). Convert each 8-bit group to a decimal number (0–255), then interpret that byte sequence as UTF-8. For example, the binary for "Hi" is 01001000 01101001: 01001000 = 72 (the character H), 01101001 = 105 (the character i). Our tool does this automatically and also accepts 7-bit groups for classic ASCII. Just paste your binary string (with or without spaces) into the left panel and read the decoded text below.
One byte = 8 bits. "Hello" in UTF-8 = 5 bytes = 40 bits of binary.
If you see "Incomplete byte" or "Invalid UTF-8 sequence", check that the total number of bits is a multiple of 8 (or 7 for ASCII) and that the bytes form valid UTF-8. Use Strict UTF-8 to fail on invalid sequences, or Loose to replace bad bytes with a replacement character so you still get a string.
Hex to text and Base64 to text
The same tool decodes hex to text and Base64 to text. Select "Hex" or "Base64" in the toolbar, then paste your hex string (e.g. 48656c6c6f or 48 65 6c 6c 6f) or Base64 string (e.g. SGVsbG8=). Each pair of hex digits is one byte; Base64 is decoded with the standard alphabet. The result is the same UTF-8 text you’d get from the equivalent binary, so hex to string and Base64 decode are just different input formats for the same conversion.
When to use which format? Binary is the raw bit view and is handy for learning or low-level debugging. Hex is compact and common in logs, hashes, and network dumps. Base64 is used in JSON, email, and data URLs when you need to embed binary data as text. This converter handles all three so you don’t need separate hex to text or Base64 decode tools.
ASCII vs UTF-8: what this converter uses
ASCII uses 7 bits per character (values 0–127) and covers basic English letters, digits, and symbols. UTF-8 is backward-compatible with ASCII for that range: the first 128 code points are the same single-byte values. So when people search for a binary to ASCII converter, they usually mean "binary to readable text"; this tool does that and more, because it uses UTF-8. That means you can decode not only ASCII (e.g. 01001000 = H) but also accented characters, emoji, and any Unicode character, each as one to four bytes.
We support both 7-bit and 8-bit binary input. If your binary length is a multiple of 7, we interpret it as 7-bit bytes (ASCII). If it’s a multiple of 8, we use 8-bit bytes (UTF-8). So you can paste legacy 7-bit binary or modern UTF-8 binary and get the correct string every time.
Common use cases: who uses a binary to string converter?
Developers and DevOps use it to inspect payloads, decode hex dumps from logs, or quickly check Base64-encoded tokens or config. Students and educators use it to see how text maps to binary and to verify homework (e.g. "convert Hello to binary"). Security and forensics work with hex and Base64 often; this tool gives instant hex to text or Base64 to text without leaving the browser. API and integration work sometimes involves Base64 or hex-encoded strings; decoding them here is faster than scripting. All conversions run locally—no data is sent to a server—so you can use it on sensitive snippets without privacy concerns.
Why "Invalid character" or "Invalid UTF-8 sequence"?
Invalid character in input means you pasted something other than 0 and 1 in binary mode (or non-hex in hex mode). Strip spaces, commas, and prefixes like 0x if needed; only the relevant digits are used. Incomplete byte means the number of bits isn’t a multiple of 8 (or 7); add or trim bits so each byte is complete. Invalid UTF-8 sequence means the bytes don’t form valid UTF-8 (e.g. a truncated multi-byte character). In Strict mode the tool reports an error; in Loose mode it replaces invalid bytes with the Unicode replacement character so you still see a string. For binary to string conversion that must be exact, fix the source data or use Strict to catch problems.
Binary to String FAQ
? Why must binary length be a multiple of 8?
In UTF-8, each character is represented by one or more bytes, and each byte is exactly 8 bits. Valid binary input is a string of 0s and 1s whose length is a multiple of 8 (or 7 for ASCII). Spaces and commas are ignored; only 0 and 1 are used. If the length isn’t a multiple of 8 or 7, you’ll see "Incomplete byte" until you add or remove bits.
? What encoding does this converter use?
UTF-8. It’s the standard encoding for the web and supports all Unicode characters. ASCII characters (basic English letters and numbers) use one byte each; many other characters use two, three, or four bytes. So you can convert binary to string for any language or symbol, not just ASCII.
? Can I paste binary with spaces?
Yes. Spaces, commas, and line breaks are stripped before conversion. You can paste binary like 01001000 01100101 01101100 01101100 01101111 or clumped like 0100100001100101011011000110110001101111 and get "Hello". Same for hex: optional spaces and 0x are ignored.
? How do I convert hex to text?
Select "Hex" in the toolbar, then paste your hexadecimal string (e.g. 48656c6c6f or 48 65 6c 6c 6f). Each pair of hex digits is one byte; the tool decodes the byte sequence as UTF-8 and shows the text. Hex to string conversion is the same as binary to string—only the input format differs.
? What is the difference between Base64 and binary encoding?
Binary encoding is raw 0s and 1s (8 bits per byte). Base64 encoding represents the same bytes using 64 printable ASCII characters (A–Z, a–z, 0–9, +, /) plus padding. Both represent the same underlying bytes; Base64 is used when you need to embed binary data in JSON, XML, or URLs. This converter decodes both: paste Base64 to get text, or paste binary to get the same text. Base64 to text is just another input format here.
? Is binary to string the same as binary to ASCII?
For basic English text, yes: ASCII is a subset of UTF-8, so converting binary to string with UTF-8 gives the same result as binary to ASCII for characters 0–127. This tool uses UTF-8 so it also handles accented letters, emoji, and every Unicode character. If your binary is 7-bit ASCII only, you can use 7-bit groups and get the same output as a binary to ASCII converter.
? Why does my binary show "Invalid UTF-8 sequence"?
That means the byte sequence doesn’t form valid UTF-8—for example, a multi-byte character is truncated, or a continuation byte appears where a new character should start. Check that your binary is complete (full bytes) and from a UTF-8 source. Use Loose decoding to replace invalid bytes with the replacement character (U+FFFD) and still see a string, or fix the source data and use Strict to ensure valid output.