Maaz Zindani

Loading the index…

↑↓ move↵ openesc close3993 pages

Free tool · Writing tools

Binary to text

Paste binary, hex or decimal bytes to read them as text, or type text to see its bytes. It reads UTF-8, so accents, symbols and emoji work, and a byte table shows exactly how each character is stored. Nothing you type leaves your device.

  • Free
  • No sign-up
  • Runs in your browser

By Maaz Zindani · Updated

Direction
Your bytes are written in

Spaces, commas and line breaks between groups are fine, and so is no separator at all (8 digits per byte).

Text
Hello World
  • 11 bytes
  • 11 characters
  • ASCII only: 1 byte each
Binary
01001000 01100101 01101100 01101100 01101111 00100000 01010111 01101111 01110010 01101100 01100100
Hex
48 65 6C 6C 6F 20 57 6F 72 6C 64
Decimal
72 101 108 108 111 32 87 111 114 108 100
Byte table
CharacterCode pointUTF-8 bytes (binary)HexDec
HU+0048010010004872
eU+00650110010165101
lU+006C011011006C108
lU+006C011011006C108
oU+006F011011116F111
(space)U+0020001000002032
WU+0057010101115787
oU+006F011011116F111
rU+00720111001072114
lU+006C011011006C108
dU+00640110010064100

How to use the Binary to Text

  1. Choose a Direction: Bytes to text or Text to bytes.
  2. Choose the format your bytes are written in, or want them shown in: Binary, Hex or Decimal.
  3. Paste or type into the box. Spaces, commas and line breaks between groups are fine, and so is no separator.
  4. Read the result and the Byte table, then press Copy. A message tells you what is wrong if the input is not valid.

How do I convert binary to text?

Computers store text as numbers, and each number as a byte of eight binary digits. To read binary as text, cut it into groups of eight, turn each group into a number, and look the number up as a character. "01001000 01101001" is the two numbers 72 105, which are the letters "Hi". Paste the groups with or without spaces: "0100100001101001" gives the same "Hi", because the tool cuts an unbroken run into whole bytes itself. A leading 0b on each group is ignored, and commas and line breaks work as separators.

If you separate the groups with spaces, a group shorter than eight digits is padded with zeros on the left, so 7-bit ASCII such as "1001000 1101001" still reads as "Hi". A longer example: "01001000 01100101 01101100 01101100 01101111" is "Hello".

How does binary represent letters: ASCII or UTF-8?

ASCII uses seven bits and covers English letters, digits and punctuation. UTF-8 is the encoding the web uses for everything else. It stores the ASCII characters in one byte, exactly as ASCII does, and other characters in two, three or four bytes. That is why "é" is two bytes (11000011 10101001), "€" is three (11100010 10000010 10101100) and an emoji is four. This tool uses UTF-8 in both directions, so text with accents and emoji converts correctly and a plain ASCII-only converter would give you garbage.

The same characters as UTF-8 bytes, produced by this tool
TextCode pointBytesBinaryHex
HiU+0048201001000 0110100148 69
éU+00E9211000011 10101001C3 A9
€U+20AC311100010 10000010 10101100E2 82 AC
😀U+1F600411110000 10011111 10011000 10000000F0 9F 98 80

The byte table under the result does this for your own text, one row per character, so you can see which characters use more than one byte. For text that was encoded another way, the Base64 decoder handles Base64, and the URL encoder and decoder handles percent-encoded text such as %C3%A9.

Why do I get strange characters or an error?

Most problems come from the grouping. Binary without spaces needs a multiple of eight digits. Seven digits in one run give: "7 bits do not make whole bytes: a byte is 8 bits. Add 1 or remove 7, or separate the groups with spaces." A digit that does not belong, such as a 2 in binary or a G in hex, is named in the message with the group it appeared in. In decimal, every number must be between 0 and 255.

Valid bytes can still fail as text. UTF-8 has strict rules about which byte may follow which. If a byte starts a character that is cut off or has the wrong follow-up bytes, the tool does not hide it. It shows the replacement mark and says: "Byte 1 (C3) does not start a valid UTF-8 character, so the text shows replacement marks from there. Check the grouping, or the data may not be text." Text that was written in another encoding, such as a legacy Windows code page, or data that is not text at all, usually produces this.

Two more habits help. First, check how many bytes you expect: the chip under the result counts bytes and characters, and if the byte count is larger than the character count, some characters use more than one byte, which is normal for accents, symbols and emoji and a clue that the text is not plain ASCII. Second, when a result looks like noise, look at the byte table: a row whose bytes start with 110, 1110 or 11110 begins a multi-byte character, and the rows after it should start with 10. If they do not, a byte went missing or was typed wrongly, and fixing that one group usually fixes the whole message.

Hex and decimal work the same way as binary. "48 69" in hex and "72 105" in decimal both give "Hi". The three views of your bytes are always shown under the result, so you can convert between the number systems at the same time.

Use it with

Questions

How do I convert binary to text?

Split the binary into groups of eight digits, convert each group to a number, and read each number as a character. "01001000 01101001" is 72 105, which spells "Hi". Or paste it here.

How do I convert text to binary?

Choose Text to bytes and Binary. Each character becomes one or more UTF-8 bytes of eight digits: "Hi" is 01001000 01101001.

What is 01001000 01101001 in text?

It is "Hi".

Does binary represent letters with ASCII or UTF-8?

Both agree for English letters, digits and punctuation, which take one byte. UTF-8 uses two to four bytes for other characters. This tool uses UTF-8.

Why do I get strange characters?

The bytes may be grouped wrongly, may not be UTF-8 text, or may be cut off. The tool flags the first bad byte, for example: "Byte 1 (C3) does not start a valid UTF-8 character, so the text shows replacement marks from there. Check the grouping, or the data may not be text."

Do I need spaces between the groups?

No. Spaces, commas and line breaks all work, and so does a single unbroken run of whole bytes.

How this page was made: the tool's results are computed in your browser by the code on this page; the explanations were drafted with AI help and checked against the tool's own output.