smileys-emotion (faces, hearts)people-body (hand gestures)animals-nature (animals, plants)food-drink (food, beverages)activities (sports, games, arts)travel-places (transport, buildings)objects (tools, technology)flags (country flags)1F600 (hex without prefix)U+1F600 (Unicode standard)0x1F600 (C-style hex)\\u1F600 (escape sequence)
No emoji found matching your search criteria.
Try:
- Different keywords (e.g.,"happy" instead of"joy")
- Simpler search terms
- Switching search types
- Using the random examples above
ℹ️ About Emoji Unicode Lookup
Emoji Unicode Lookup searches a curated emoji dataset by pasted glyph, Unicode code point, official-style name, keyword, or category. Use it when you need to identify an emoji before placing it in HTML, JSON, documentation, UI tests, accessibility notes, or log output.
Emoji are Unicode pictographic characters and, in many cases, multi-code-point sequences. The core emoji model is defined by Unicode Technical Standard #51, while character names and code point properties are described by the Unicode Character Database.
Useful searches:
- By emoji: paste a glyph such as
😀,🎉, or❤️to inspect it. - By name: search text such as
grinning face,red heart, orparty popper. - By keyword: use practical terms such as
happy,love,food, orcomputer. - By category: filter groups such as
smileys-emotion,animals-nature,objects, orflags. - By Unicode: enter hexadecimal forms such as
1F600,U+1F600,0x1F389, or\u2764.
Results include the emoji, name, category, keywords, decimal code point, hexadecimal U+...
notation, UTF-8 byte sequence, and numeric HTML character references. For example,
😀 is U+1F600, decimal 128512, UTF-8 bytes
0xF0 0x9F 0x98 0x80, HTML decimal 😀, and HTML hex
😀. UTF-8 is specified by
RFC 3629,
and HTML character references are covered by the
HTML Standard.
The lookup is best for quick developer reference and common emoji discovery. The local dataset is aligned with this tool's Unicode 15.0 / Emoji 15.0 metadata, but it is not a complete replacement for the full Unicode emoji data files. Some emoji render as sequences using variation selectors, skin-tone modifiers, regional indicators, or zero-width joiners; display can vary by browser, operating system, and installed fonts. For those sequence emoji, treat the returned primary code point and numeric entity as a starting point and verify the complete sequence when exact interchange matters.
The interactive lookup runs in your browser after the page script loads. Use the API endpoint when you want the same lookup behavior from scripts or test automation.
API Usage Example:
POST /api/tools/conversion/emoji
Content-Type: application/json
{
"query": "1F600",
"search_type": "unicode"
}