Emoticon Character Analyzer

See exactly which Unicode characters an emoticon contains before you paste it into code, HTML, or a profile.

9
Unicode code points
9
UTF-16 code units
No
ASCII only
Stable
under NFC normalization

This text uses Unicode beyond ASCII. Most modern apps support it, but glyph shape, width, and fallback fonts can differ.

Character sequence

PositionCharacterCode pointDecimalUTF-16 units
1¯U+00AF1751
2\U+005C921
3_U+005F951
4(U+0028401
5U+30C4124841
6)U+0029411
7_U+005F951
8/U+002F471
9¯U+00AF1751

Copy-safe formats

plain

¯\_(ツ)_/¯

html

¯\_(ツ)_/¯

javascript

'¯\\_(ツ)_/¯'

unicode

U+00AF U+005C U+005F U+0028 U+30C4 U+0029 U+005F U+002F U+00AF

Why counts disagree

A JavaScript string's length counts UTF-16 code units, not user-perceived characters. Many symbols outside the Basic Multilingual Plane use two units. A visible emoji can also combine multiple code points through variation selectors or joiners. The table exposes that underlying sequence.

Compatibility is not universal

ASCII faces such as :-) have the widest baseline, but spacing can still vary with the font. Kaomoji combine characters from several scripts and symbol blocks, so a missing glyph or different font width can change the face. Test important text in the exact app and font where it will appear.