Unicode Inspector & Developer Toolkit
Free ยท Runs in your browserPaste any character or string and see exactly how a computer stores it: UTF-8 / UTF-16 / UTF-32 bytes, HTML entities, CSS and JavaScript escapes, URL encoding, the four Unicode normalization forms and a full character map with scripts.
Cheat sheet
| Character | Unicode | UTF-8 | HTML | CSS |
|---|---|---|---|---|
| รฉ | U+00E9 | C3 A9 | é or é | \00E9 |
| โฌ | U+20AC | E2 82 AC | € or € | \20AC |
| ู | U+0645 | D9 85 | م | \000645 |
| ฮฉ | U+03A9 | CE A9 | Ω or Ω | \0003A9 |
| ใ | U+3053 | E3 81 93 | こ | \003053 |
What are the Unicode normalization forms?
NFC โ Canonical Composed
รฉ stays รฉ. Used by macOS and most web systems. Recommended for most databases.
NFD โ Canonical Decomposed
รฉ becomes e + combining accent. Used by Linux and some search indexes.
NFKC โ Compatible Composed
Converts โ โ 1, ๏ฌ โ fi, full-width ๏ผก โ A. Best for search normalization.
NFKD โ Compatible Decomposed
Fully decomposes everything. Common before stripping diacritics.
๐ก Normalization ensures the same text always has the same bytes. Without it, cafรฉ (NFC) and café (NFD) are technically different strings โ a classic source of bugs and duplicate database rows.