Guide to Text Encoding: ASCII, ISO-8859, and UTF-8 Explained

Have you ever opened a web page or CSV file and seen strange characters like é instead of é? This garbled output is known as mojibake (Japanese for "character transformation"), caused by a mismatch in text encoding.

The Evolution of Text Encoding

1. ASCII (1963): 7-bit standard supporting only 128 characters. Perfect for English, but entirely incapable of encoding accented European letters, Asian scripts, or mathematical symbols.
2. Extended ASCII & ISO-8859 (1980s): Utilized the 8th bit to provide 256 characters. However, different regions required different "code pages" (ISO-8859-1 for Western Europe, ISO-8859-5 for Cyrillic, Shift-JIS for Japanese), making international document exchange notoriously fragile.
3. Unicode (1991): The universal breakthrough. Instead of cramming characters into 8 bits, Unicode assigns a universal, immutable Code Point (e.g., U+1F600 for grinning face) to every letter, symbol, and emoji across all languages.
4. UTF-8 (1992): Invented by Ken Thompson and Rob Pike on a placemat in a New Jersey diner. UTF-8 encodes Unicode code points using a variable-length format:
   • Standard English ASCII characters consume just 1 byte.
   • Greek, Arabic, and Hebrew consume 2 bytes.
   • Chinese, Japanese, and Korean characters consume 3 bytes.
   • Emojis and historic scripts consume 4 bytes.

Today, over 98% of all websites worldwide use UTF-8 as their primary encoding standard.

Inspect binary representations and encode strings with our free Binary to Text Converter.