ASCII Converter: Text to Codes and Back Again

Long before emoji, and long before the many writing systems that modern computers support, there was ASCII: a table of 128 characters, each assigned a number from 0 to 127. Uppercase letters, lowercase letters, digits, punctuation and a set of control characters all had a fixed place in that table, and for decades it was the shared language of computers exchanging text. ASCII still matters today, not because it covers every character in the world, but because it sits inside larger systems. The first 128 code points of Unicode are exactly the ASCII characters, and countless file formats, protocols and programming tools still think in ASCII. The ASCII Converter converts text to ASCII decimal, hex and binary codes, and converts codes back to text, so you can see that mapping directly instead of taking it on trust.

The three code formats are simply three ways of writing the same number. Decimal is the base-10 system we use every day. Hexadecimal is base 16, written with the digits 0 to 9 followed by the letters A to F, and it is popular in programming because each hex digit corresponds exactly to four binary digits. Binary is base 2, written with only 0 and 1, and it is how the computer itself stores the value. Converting between them is arithmetic, not magic, and once you have done a few by hand, the table stops looking mysterious.

How the tool works

You type text, and the tool shows the code for each character in decimal, hexadecimal and binary. You can also go the other way: paste codes and get the text back. Everything happens in your browser, with no upload and no account. That round trip is the most useful feature, because it lets you verify your understanding. If you convert "Hi" to codes and then convert those codes back, you should get "Hi" again. If you do not, something in the middle step is wrong, and you have found the error before it reached a program or a file.

One detail worth stating plainly is the difference between a character and a byte in modern text. ASCII covers 128 characters, but most text today is Unicode, and characters beyond ASCII take more than one byte in common encodings. A converter built around ASCII handles the ASCII range faithfully; it is not a general Unicode inspector, and characters outside the table need a tool that understands their encoding. Knowing that boundary keeps you from drawing wrong conclusions when an accented letter or an emoji does not behave like a plain letter.

A worked example

Take the word "Hi". The letter H has decimal code 72, which is 48 in hexadecimal and 1001000 in binary. The letter i has decimal code 105, which is 69 in hexadecimal and 1101001 in binary. So "Hi" becomes the decimal pair 72 105, the hex pair 48 69, and the binary pair 1001000 1101001. Converting those codes back gives "Hi" again, which confirms the round trip. You can check the hex by hand: 0x48 means 4 times 16 plus 8, which is 64 plus 8, which is 72. Similarly, 0x69 means 6 times 16 plus 9, which is 96 plus 9, which is 105. The binary values check the same way if you add up the place values: 1001000 is 64 plus 8, which is 72, and 1101001 is 64 plus 32 plus 8 plus 1, which is 105.

A single-letter example is even cleaner. The capital letter A has decimal code 65, hex code 41 and binary code 1000001. That one row of the table explains a pattern worth remembering: uppercase letters run from A at 65 to Z at 90, lowercase letters run from a at 97 to z at 122, and the gap between a capital and its lowercase partner is always 32. Digits run from 0 at 48 to 9 at 57. Once you know A is 65, you can work out that D is 68 without looking anything up, and once you know the gap is 32, you can work out that a is 97. These small patterns are what make the table feel learnable rather than arbitrary.

Common mistakes

The most common mistake is confusing the digit characters with the numbers they represent. The character "5" is not the number 5; it is the character with decimal code 53. That distinction matters whenever you parse text into numbers in a program, because code that treats a digit character as its numeric value will be wrong by a fixed amount. A second mistake is mixing up hex and decimal when reading documentation. A code written as 41 could be decimal 41, which is the character ")"; or it could be hex 0x41, which is the letter A. The context, and the 0x prefix where it is used, is the only thing that tells you which one is meant, so always check.

A third mistake is assuming every character you meet is ASCII. A curly quote, an accented vowel or an emoji will not appear in the ASCII table, and forcing it into an ASCII-only process will either replace it, drop it or produce an error. A fourth mistake is reading binary codes without minding the leading zeros. Binary 1000001 and 01000001 represent the same value, but in fixed-width contexts, such as a byte with eight bits, the leading zero matters for alignment, and dropping it can shift everything that follows. When in doubt, write codes in a fixed width and keep the spacing consistent.

Honest limitations

An ASCII converter answers one question: what is the code for this character, or what character does this code represent? It does not explain character encodings in general, it does not decode UTF-8 byte sequences into Unicode characters, and it does not repair text that was decoded with the wrong encoding. If you paste text that contains characters outside the ASCII range, expect the tool's ASCII-centred view to be incomplete for those characters rather than authoritative. It is a learning and checking tool for the classic table, and it is at its best when used for exactly that.

Closing

ASCII is small enough to learn and old enough to be everywhere, which makes it a good place to build intuition about how computers store text. Convert "Hi", check the arithmetic by hand, and convert the codes back. When you can predict that A is 65 and that its lowercase partner is 32 higher, the table is yours. For neighbouring jobs, the Number Base Converter generalises the base arithmetic and Base64 Studio covers a text encoding you will meet constantly, while How to Use Regular Expressions Safely shows how character-level thinking helps with pattern matching too.