Text to Binary
Convert text and byte values in both directions, using ASCII or UTF-8.
Use 8 binary digits per byte, separated by whitespace: 01000001.
Limit: 4,096 bytes; numeric input up to 36,864 characters. ASCII accepts 0–127. Invalid UTF-8 is rejected.
Input is saved in this browser. Up to 500 characters also appear in the URL; shared links include them. Clear removes both.
Related tools
-
Unit converter
Type a value, pick two units and see the result and a table of every unit in the group. -
Roman numeral converter
Convert both ways and understand every symbol. -
URL encoder and decoder
Encode text for URLs or decode percent escapes as you type. -
JSON formatter
Format, minify and check JSON, with the line and column of the first error. -
JWT Decoder
Read token contents and dates. Signatures are not verified.
Convert text into byte values or turn a sequence of bytes back into text. Choose binary, hexadecimal, octal or decimal notation, then select UTF-8 for multilingual text or ASCII for its original seven-bit character set. This is useful when examining an encoded message, preparing a small test fixture or learning how characters become bytes. Each output byte is separated by a space. Conversion happens in your browser, and invalid input produces an error instead of a guessed or partially decoded result.
How to use
- Choose text to bytes or bytes to text, then select the number base and character encoding.
- Type text or paste whitespace-separated bytes; use the example to see the required format.
- Read the result and byte count, then copy the output or clear the saved input.
What it handles
- Binary uses eight digits per byte, hex two and octal three; decimal accepts one to three digits.
- UTF-8 preserves accents, combining marks, emoji, CJK and right-to-left text.
- ASCII accepts only values 0–127; UTF-8 rejects malformed sequences without replacement characters.
- Converts up to 4,096 bytes; numeric input is limited to 36,864 characters including whitespace.
FAQ
Why does one character produce several bytes?
UTF-8 uses one to four bytes per Unicode code point. An accented character may use two bytes, and an emoji often uses four. A visible character made from several code points can use more. ASCII only covers values 0–127, so choose UTF-8 for text outside that range.
How should I separate the input bytes?
Use spaces, tabs or line breaks between bytes. Binary requires eight digits, hexadecimal two, and octal three, including leading zeroes. Decimal accepts one to three digits. Every byte must be between zero and 255. Commas, number prefixes, signs, fractions and joined byte groups are rejected rather than interpreted automatically.
What happens when UTF-8 bytes are invalid?
Conversion stops and clears the output. Overlong encodings, isolated continuation bytes, incomplete sequences and encoded surrogates are rejected. The decoder does not silently insert replacement characters. An actual replacement character encoded correctly as EF BF BD remains valid text, and an initial byte order mark is preserved.
Is my input saved or included in shared links?
Processing stays in the browser. The current input is saved locally within the input limit, and text of up to 500 characters is also placed in the URL with its options. A shared link can therefore reveal that input. Clear removes saved input and its URL value. Larger inputs are not put in the URL.
Updated