Skip to main content
UTF-8 Decoder & Encoder Online - Unicode & Byte Sequence Converter
Unicode Decoder • UTF-8 Encoder Decoder

UTF-8 Decoder & Encoder Online

Free online utf 8 encoder decoder, unicode decoder, and utf8 string converter. Easily decode utf8, utf 8 decode byte sequences, inspect utf 8 character codes, and convert to utf8 with full byte-level inspection.

Byte Output Format:
Input String / Text 12 chars
Encoded Output / UTF-8 Bytes 18 bytes
Character Breakdown & UTF-8 Byte Structure
Char Unicode Code Point Name / Range Byte Length UTF-8 Hex Bytes Binary Bits

Developer Guide: UTF-8 Encoding Types & Unicode Decoding

Welcome to the ultimate utf 8 encoder decoder and unicode decoder online. In modern computing, text encoding utf 8 is the undisputed universal standard for exchanging textual information across operating systems, databases, networks, and web pages. Whether you are dealing with raw packet bytes, debugging database collation errors (such as utf8mb4 vs utf8), or need to decode utf 8 byte sequences back into a readable utf 8 string, this utf 8 converter provides crystal-clear transparency down to the individual binary bit.

How UTF-8 Variable-Length Encoding Works

Unlike fixed-width encodings (like UTF-32, which always consumes 4 bytes per character, or UTF-16, which uses 2 or 4 bytes), character encoding utf 8 uses a clever variable-width design from 1 to 4 bytes:

  • 1 Byte (ASCII Compatibility): Code points U+0000 to U+007F (standard English letters, numbers, and basic punctuation). The high bit is always 0xxxxxxx.
  • 2 Bytes (Latin, Greek, Cyrillic, Hebrew, Arabic): Code points U+0080 to U+07FF. Binary format: 110xxxxx 10xxxxxx.
  • 3 Bytes (Asian CJK Scripts, Math Symbols, Currency): Code points U+0800 to U+FFFF. Binary format: 1110xxxx 10xxxxxx 10xxxxxx.
  • 4 Bytes (Emojis, Historic Scripts, Rare Hieroglyphs): Code points U+10000 to U+10FFFF. Binary format: 11110xxx 10xxxxxx 10xxxxxx 10xxxxxx.

UTF-8 vs ASCII: How to Convert UTF-8 to ASCII

While every valid ASCII string is automatically a valid UTF-8 string, converting from utf8 to ascii requires decomposing accented characters (diacritics) into their base Latin equivalents. For example, our utf8 to ascii converter normalizes characters like é to e, ü to u, and ñ to n, while safely stripping non-representable symbols for legacy serial printers or strict ASCII systems.

UTF-8 Bit Distribution Matrix

Unicode Range Byte 1 Byte 2 Byte 3 Byte 4
U+0000 – U+007F 0xxxxxxx — — —
U+0080 – U+07FF 110xxxxx 10xxxxxx — —
U+0800 – U+FFFF 1110xxxx 10xxxxxx 10xxxxxx —
U+10000 – U+10FFFF 11110xxx 10xxxxxx 10xxxxxx 10xxxxxx

Frequently Asked Questions (FAQ)

What causes the "Mojibake" gibberish text like "é"?
Mojibake occurs when text encoded in UTF-8 is erroneously decoded using a single-byte legacy encoding like Windows-1252 or ISO-8859-1. For instance, the UTF-8 two-byte sequence for é (0xC3 0xA9) gets interpreted by Windows-1252 as two separate characters: Ã (0xC3) and © (0xA9). Using our utf 8 decode tool allows you to reconstruct the original UTF-8 string.
What is MySQL's utf8 vs utf8mb4 distinction?
In MySQL, the historical charset named utf8 only supports up to 3 bytes per character, meaning it cannot store 4-byte modern emojis (like 🚀 or 😊) and will crash or truncate text. MySQL's utf8mb4 charset supports the complete 4-byte UTF-8 standard.
What is a Byte Order Mark (BOM) in UTF-8?
A UTF-8 BOM is the three-byte sequence EF BB BF placed at the start of a text file. While useful in Windows Notepad to detect UTF-8, the Unicode Consortium recommends omitting the BOM for UTF-8 files because byte order does not vary in single-byte streaming.
Copied to clipboard!