Text to ASCII Codes Converter
Each character becomes its Unicode code point in four bases.
72 105 33
110 151 41
48 69 21
01001000 01101001 00100001
The text to ASCII codes converter shows each character as its Unicode code point in four bases at once (decimal, octal, hexadecimal and binary) and converts the numbers back to text. The name says ASCII, but it handles the whole of Unicode, not just the 128 characters ASCII defines.
How it works
Every character has a code point, a number identifying it in the Unicode standard. ASCII occupies the first 128 of these, which is why the two are used interchangeably for plain English text and why the distinction matters as soon as accents or emoji appear.
- Decimal is the familiar form: A is 65, a is 97, space is 32.
- Hexadecimal is what Unicode itself uses, U+0041 for A, and is padded to two digits here.
- Binary is padded to eight digits, which is one byte, matching how ASCII is stored.
- Octal is a legacy notation still seen in Unix escape sequences.
Characters above U+FFFF, most emoji, have code points beyond 65,535, so their binary form is longer than eight digits. Splitting on a fixed byte boundary would corrupt them, which is why the tool works in code points rather than bytes.
Examples
A short string in four bases
Text
Hi!
Result
Decimal 72 105 33 · Octal 110 151 41 · Hex 48 69 21 · Binary 01001000 01101001 00100001
H is 72, i is 105, ! is 33. The uppercase and lowercase forms of a letter differ by exactly 32, which is why case conversion is a single bit flip in ASCII.
Decoding back
Codes
72 105 33
Base
Decimal
Result
Hi!
Codes separated by spaces or commas convert straight back. The round trip is exact for any input.
A character beyond ASCII
Text
é
Result
Decimal 233 · Hex E9
Outside the 0–127 ASCII range but well within a single code point. Emoji go further still. 😀 is decimal 128512.
Frequently asked questions
Is this ASCII or Unicode?
Unicode code points, which happen to match ASCII for the first 128 characters. The tool is named for what people search, but it handles accented letters, CJK characters and emoji correctly rather than failing at 127.
Why are the binary values eight digits?
Because one byte is eight bits, and ASCII characters fit in one byte. Characters above 255 need more, so their binary form is longer. The padding is a convention for readability, not a limit.
Why do uppercase and lowercase codes differ by exactly 32?
Because ASCII was designed that way. A is 65 and a is 97; the difference is bit 6, so changing case is a single bit operation. That is why early case-conversion code used bitwise arithmetic rather than lookup tables.
What happens with emoji?
They convert correctly, because the tool iterates code points rather than UTF-16 units. An emoji like 😀 is code point 128512, which would be split into two meaningless halves by anything working on raw string indices.