How to convert ASCII text and codes
- Choose one of the three text-to-code directions or one of the three code-to-text directions.
- For text input, enter only 7-bit ASCII characters. For code input, separate tokens with whitespace, commas, or semicolons.
- Select Convert. Review the output and the visible character/value list before copying.
- Editing input or direction clears the old result. Clear removes input, errors, and output while keeping the selected direction.
The 7-bit ASCII boundary
This page uses values 0 through 127 only. Each text character becomes one ASCII value. Binary output is padded to seven bits, hexadecimal output to two digits, and decimal output has no required leading width. Decoding accepts leading zeroes; binary may use 0b and hexadecimal may use 0x prefixes.
Values 0–31 and 127 are control characters rather than ordinary printable glyphs. The detail line names them, including NUL, HT, LF, CR, and DEL. A decoded LF is a real line-feed character in the copied result. SPACE is also labeled so a blank result is not mistaken for missing output.
Exact conversion examples
Text “A” is binary 1000001, decimal 65, and hexadecimal 41. Text “A” followed by LF is hexadecimal “41 0A”.
Binary “01000001 0001010”, decimal “065, 010”, and hexadecimal “0x41; 0A” all decode to A followed by a line feed. Leading zeroes do not change the value.
Input validation and limits
- Text containing é, 한글, emoji, or any code point above 127 is rejected. This avoids silently treating UTF-8 bytes, UTF-16 units, or Unicode code points as ASCII.
- Every code token is validated in its selected base and must decode to 0–127. Negative values, fractions, empty separators, binary digit 2, hexadecimal G, and values 128 or above are not accepted.
- This tool does not provide Base64, URL encoding, UTF-8 byte conversion, character-set detection, files, checksums, or Unicode-wide code-point conversion.
ASCII converter FAQ
Why is binary seven bits instead of eight?
ASCII is a 7-bit standard. An eighth zero bit is common in byte displays, but the exact ASCII value needs seven bits.
Can I enter 0x and 0b prefixes?
Yes for hexadecimal and binary decoding respectively. Output omits prefixes to keep token lists compact.
How are tabs and newlines shown?
The output contains the actual control character while the details label it as HT or LF with its decimal value.
Why is non-ASCII text rejected?
Unicode text requires an encoding such as UTF-8; choosing one implicitly would turn this into a different tool.