From a message to bits, and back again
Use this binary code translator to read a sequence of bytes or see how a message becomes binary. Start by choosing the direction: Binary to text reads encoded bytes, while Text to binary turns the characters you type into bytes. Leave UTF-8 selected for ordinary text, including accented letters, other writing systems, and emoji. Choose ASCII when you need to work within its smaller character set.
Paste your input, check the selected byte format, and review the result. For a simple first example, enter Hi in text mode. Its binary representation is 01001000 01101001. Put those two groups into binary-to-text mode and the message becomes Hi again. The example button provides a longer starting point with Hello world! so you can experiment without preparing an input.
Once the result looks right, copy it into your notes, code, or message, or download the output as text. Keep the encoding alongside the result when sharing it: the same bytes are not guaranteed to produce the same characters under every encoding. If you are checking a programming exercise, compare one byte at a time before moving on to a longer message.
A byte is a value, with several ways to write it
A bit is a binary digit, either 0 or 1. A byte contains eight bits and can hold a value from 0 to 255. Binary writes that value using base two. Hexadecimal and decimal are other ways to display the same value; changing the display format does not, by itself, change the underlying data.
For example, the uppercase H in Hi uses the byte 01001000 in ASCII and UTF-8. That is 48 in hexadecimal and 72 in decimal. The lowercase i is 01101001, hexadecimal 69, or decimal 105. The byte inspector lets you compare these representations without having to calculate every place value by hand.
Spaces between displayed binary groups make byte boundaries easier to read. They do not insert spaces into the decoded message. A real space in the message has its own byte, 00100000. This distinction is useful when a result looks joined together: check for the space byte in the data, rather than adding more visual separators between groups.
ASCII and UTF-8 answer different needs
ASCII defines 128 values, from 0 through 127. It is a seven-bit character code, although its values are commonly stored and shown in eight-bit bytes with a leading zero. It covers English letters, digits, punctuation, and controls such as tab and line feed. Strict ASCII cannot represent an accented letter such as é or an emoji.
UTF-8 represents Unicode code points using one to four bytes. Its basic ASCII characters keep the same byte values, so Hello world! produces the same bytes under both settings. Other characters need more space: é occupies two UTF-8 bytes, and 🙂 occupies four. A displayed symbol can also combine multiple code points, so counting visible characters does not reliably tell you the byte count.
Choose the encoding used by the source of your data. UTF-8 is a useful default for modern text, but it cannot repair bytes copied from an unrelated encoding or recover missing data. If decoding fails, first check the input and its origin. Switching encodings at random can hide the actual problem, especially when the original data was never text.
The number 42 is different from the text “42”
Number conversion and text encoding start with different kinds of input. The numeric value forty-two is 101010 in binary and 2A in hexadecimal. No character encoding is involved: you are expressing one integer in another base. Use the number conversion mode when that is your task, including when checking a long integer that must stay exact.
The text 42 contains two characters: the digit 4 followed by the digit 2. Encoding that string as ASCII or UTF-8 gives two bytes, 00110100 00110010. Those byte values are 52 and 50 in decimal. They describe the characters on the screen, not the numeric quantity forty-two.
The same distinction applies to a decimal byte list. In text decoding, 72 105 is a list of two byte values that spells Hi. In number mode, an input represents one integer. Before converting, decide whether you are working with a quantity, a written message, or a sequence of raw bytes. That choice determines which mode gives a meaningful result.
Inspect small examples without uploading your input
Use the converter to check a lesson, prepare a small test fixture, inspect text copied from a byte dump, or understand an unexpected character in an integration. Start with a short sample you can recognize. If Hi works but the full message does not, inspect where the data changes rather than assuming that every eight-bit value must be a printable letter.
Text and file conversion run in your browser. The converter does not send the text you enter or the file you select to a conversion server, and no account is needed. Loading the website still makes normal web requests. Local conversion describes how your input is processed; it does not mean that visiting the page involves no network activity.
File mode reads a selected file's existing bytes and displays them as binary, hex, or decimal. The first release accepts files up to 64 KiB, or 65,536 bytes. This is a small file inspection tool, not a backend API or a file-type converter. Viewing a PDF or image as bits does not extract its text, change its format, or make it suitable for plain-text decoding. Use a format-aware tool for those tasks.