How to Convert Text to ASCII Code Online

To convert text to ASCII code online, type or paste your text into an ASCII converter and read off one number per character: capital A is 65, lowercase a is 97, and the digit 0 is 48. Each character becomes its decimal ASCII code, separated by spaces. Try it instantly with our free text to binary converter, which shows the binary form of the same ASCII values, and see the chart below for the full mapping.

Try it now: Text to Binary Converter →

What ASCII Code Actually Is

ASCII, short for American Standard Code for Information Interchange, is the numbering scheme computers agreed on in the 1960s so that different machines could exchange text. Before ASCII, every manufacturer encoded letters differently, and a file written on one machine was gibberish on another. ASCII fixed that by assigning every common character a number from 0 to 127: control characters occupy 0 to 31, printable characters run from 32 (the space) to 126 (the tilde), and 127 is delete. Capital letters sit in one tidy block, A is 65 through Z at 90, lowercase letters sit in another, a is 97 through z at 122, and the digits run 0 at 48 through 9 at 57. That tidy layout is not an accident. It is why converting text to ASCII code feels orderly rather than random, and why programmers still reach for ASCII values when they sort strings, validate input, or debug garbled output. If you work with binary rather than decimal numbers, our guide to converting text to binary by hand shows how the same ASCII numbers become eight-bit patterns.

Try it now: Text to Binary Converter →

The 30-Second Method: Convert Text to ASCII Code Online

The fastest route is a converter, and it takes four steps. First, copy the text you want to convert, whether it is a word, a sentence, or a whole paragraph. Second, paste it into a text-to-code tool. Third, choose decimal ASCII output rather than binary or hexadecimal if the tool offers a choice. Fourth, copy the number list out. The result for the word Hi is 72 105, because H is 72 and i is 105. For Hello the result is 72 101 108 108 111. Spaces count too: a space is 32, so Hello World becomes 72 101 108 108 111 32 87 111 114 108 100. One practical tip: if your converter returns binary instead of decimal, remember that binary 01001000 is just 72 written in base 2, so you already have the ASCII value in a different costume. Our free text to binary converter shows that binary form, and our binary to decimal walkthrough teaches the hand conversion for checking your work.

ASCII Code Chart: Letters A to Z, Digits, and Punctuation

You do not need to memorize the whole table, but knowing its landmarks makes conversion feel instant. The digits 0 to 9 are 48 to 57, so you can find any digit by adding its face value to 48: the digit 7 is 55. Capital letters A to Z are 65 to 90, so M, the thirteenth capital, is 65 plus 12, which is 77. Lowercase letters a to z are 97 to 122, exactly 32 higher than their capitals, which is the single most useful ASCII fact in programming: flipping case is just adding or subtracting 32. Common punctuation has its own landmarks too: exclamation mark 33, comma 44, period 46, question mark 63, at sign 64, and underscore 95. The space, character 32, is the one people forget most often, and forgetting it is the most common reason a converted string fails to decode back to the original text. When you check a long conversion, scan for 32s first: every word boundary in your original text should appear as a 32 in the output.

Text to ASCII Converter: Going the Other Direction

Converting back, from numbers to text, is the same table read in reverse, and it is how you verify that a conversion survived intact. Take the sequence 84 111 111 108 78 101 115 116 and look each number up: 84 is T, 111 is o, 108 is l, 78 is N, 101 is e, 115 is s, 116 is t, which spells ToolNest. The reverse trip matters in practice because ASCII codes travel through systems that mangle letters: email headers, URL parameters, and old databases sometimes store text as numbers, and decoding them by hand is the only way to read the original message. Watch for two traps on the way back. First, numbers above 127 are not ASCII at all; they belong to extended encodings, and treating them as ASCII produces the wrong characters. Second, a missing space code collapses two words into one, which is why decoders that show word boundaries explicitly are worth preferring. If your numbers came from an encoded file rather than plain text, our guide to decoding Base64 strings covers the encoding that wraps binary data as text.

ASCII vs Unicode: Why ASCII Still Matters in a Unicode World

Unicode did not kill ASCII; it absorbed it. The first 128 Unicode code points are identical to ASCII, character for character, which means every valid ASCII text is also valid Unicode text, and every ASCII conversion you do today still decodes correctly in modern software. Unicode extends the table past 127 to cover accented letters, scripts like Arabic and Chinese, and emoji, using encodings such as UTF-8 that store common characters in one byte and rarer ones in up to four. That is why a converter that only knows ASCII will choke on an emoji or an accented letter: those characters simply have no ASCII number. The practical rule is simple. If your text is plain English letters, digits, and standard punctuation, ASCII conversion is exact and universal. If it contains anything beyond that, use a Unicode-aware tool and expect multi-byte values. Programmers still lean on ASCII daily because the 32-gap between upper and lower case, the 48-offset for digits, and the printable range from 32 to 126 are baked into string libraries in every language. For a related encoding question, see our guide to encoding URL special characters, where ASCII punctuation meets percent-encoding.

Common Mistakes When Converting Text to ASCII

Four mistakes account for most bad conversions. First, dropping the space: 72 105 without a 32 between words merges them on decode. Second, confusing similar-looking characters: capital O is 79 while the digit zero is 48, and lowercase l is 108 while the digit one is 49, so a password or serial number converted carelessly decodes to the wrong string. Third, assuming every character has an ASCII code: curly quotes, em dashes, and emoji do not, and a converter that silently substitutes question marks has destroyed information. Fourth, mixing up decimal and hexadecimal output: 41 in hex is 65 in decimal, the letter A, so a converter set to hex mode will hand you numbers that look right but decode wrong. The cure for all four is a round trip: convert your text to codes, convert the codes back, and confirm you get the original text exactly. If the round trip fails, the error is in the settings, not the table.

Where ASCII Codes Show Up in Real Work

ASCII values surface in places you would not expect. Spreadsheet and database functions like CHAR and CODE translate between characters and numbers for sorting and validation. Programmers compare strings by ASCII order, which is why uppercase letters sort before lowercase ones and why sorting Zebra before apple surprises beginners. Network protocols still speak ASCII: HTTP headers, email headers, and URLs are ASCII text, which is why special characters in a web address must be percent-encoded first. Even barcode and QR systems lean on ASCII, since the data they encode starts as ASCII text before it becomes bars or squares. Our minutes to hours converter and centimeters to inches converter handle the numeric side of everyday conversions, while this guide covers the text side. The thread running through all of it is the same: computers store numbers, and ASCII is the agreement that turns those numbers back into readable words.