Text to ASCII/Unicode Code Converter

Convert text to a list of decimal character codes and back — covers the full Unicode range, not just 7-bit ASCII.

1,067 views

How It Works

Every character you type is walked one at a time and converted to its Unicode code point — the same numbering system whose first 128 values, 0 through 127, are the original ASCII table. Within that range, codes 32-126 make up the printable block: letters, digits, punctuation and the space character. Codes 0-31 are control characters, a historical layer left over from teleprinters and typewriters that used specific codes to move the print head or paper rather than print a glyph — code 13 (carriage return) sent the head back to the start of the line, and code 10 (line feed) advanced the paper by one line, a split that is why plain-text files on different operating systems still disagree about how a line ending is stored.

Example: typing "Hi!" produces the code list 72, 105, 33 — capital H is 72, lowercase i is 105, and the exclamation mark is 33, all inside the printable 32-126 range. Pasting that list back into the decoder rebuilds "Hi!" exactly, character for character.

Where this tool goes beyond a textbook ASCII table is codes 128 and above. That upper range, informally called "extended ASCII," was never standardized: different vendors and regions built different 256-value code pages, assigning different glyphs to the same byte. A byte that meant "ğ" on one Turkish code page could mean an entirely different character, or nothing printable at all, on another system's code page. That inconsistency is precisely the problem UTF-8 and full Unicode code points were built to solve: instead of one byte per character with a code-page-dependent meaning, every character gets a stable numeric identity that means the same thing everywhere. That is why this converter encodes each character as a full Unicode code point rather than truncating to a single byte, so Turkish letters like ğ, ş, ı, ö, ü, ç and emoji all convert reliably.

What to Know

  • Printable range: codes 32-126 always correspond to a visible character on any system; anything else needs context (a font, a code page, or full Unicode) to interpret correctly.
  • Control codes have no glyph: decoding a value from 0-31 (or 127, DEL) back to text will not show a printable character — that is expected, not an error, since these codes were never meant to be displayed.
  • Beyond byte 255: Unicode code points go far past the old 256-value ceiling — emoji, for instance, live in the hundred-thousands — and this tool handles the full range, not just one byte's worth.
  • Lossless round-trip: encoding then decoding always returns your original text exactly, since each code point maps to one character with nothing approximated or compressed.
  • Runs entirely in your browser: no text is sent anywhere, so it is safe to convert sensitive strings, tokens or passwords for debugging.

Frequently Asked Questions

Is this really ASCII, or something more?

True 7-bit ASCII only covers codes 0-127 (English letters, digits, basic punctuation). This tool uses the same idea but extends it to the full range of Unicode code points, so Turkish letters (ç, ğ, ş, ı), accented letters and emoji convert correctly instead of breaking or falling back to a question mark.

What separator does the code list use?

Commas, by default with a space after each — but the decoder also accepts codes separated by plain spaces or line breaks, so pasting a list copied from another tool usually works without reformatting.

What is the difference between code 10 and code 13?

Both are historical line-ending control characters: code 10 is "line feed" (move down one line), and code 13 is "carriage return" (move to the start of the line). Unix uses LF alone, classic Mac used CR alone, and Windows uses both together (CRLF) — a split that traces directly back to physical teletype hardware.

Why do codes above 127 look different in other tools?

Because that range was never standardized. Each vendor's "extended ASCII" code page assigned its own glyphs to bytes 128-255, so the same byte value can decode to different characters on different systems. This tool sidesteps that entirely by working in full Unicode rather than a fixed 256-value table.

Can this handle emoji and other multi-byte characters?

Yes — emoji and many other symbols live at code points far beyond 255, and this tool converts each one to its full decimal Unicode value (some emoji, like flags, are actually built from two code points, which the list will show as two separate numbers).

Comments

No comments yet — be the first to write one!

Similar Tools