What is included in this emoji finder
The search index is generated from Unicode’s Emoji 17.0 emoji-test.txt file and pinned CLDR 48.2 English and Simplified Chinese annotations. It contains 3,944 fully-qualified entries: single emoji characters, presentation sequences, keycaps, flags, tag sequences, modifier sequences and recognized zero-width-joiner combinations. The default view hides 2,030 entries containing explicit skin-tone modifiers, leaving 1,914 results that are easier to browse. Enable the checkbox when an exact tone sequence is needed.
“Fully-qualified” is a technical status defined by Unicode. It does not mean every device can draw the entry, nor does the total equal the number on every keyboard. Different counts include or exclude components, tones, minimally-qualified sequences and sequence combinations. The version and count are stated here so this finder remains reproducible instead of silently calling a small hand-written list “all emoji.”
How English, Chinese and code-point search works
Each result combines its CLDR short name, search keywords, Chinese annotation when present, Unicode group and subgroup, version and code-point sequence. Every typed token must appear somewhere in that combined index. Exact glyph, exact name, keyword and code-point matches receive more weight than broad substring matches. The result order falls back to the official Emoji 17.0 ordering.
Search terms stay in the browser. The current query and non-default filters are reflected in the URL so you can bookmark or copy a filtered search. That URL contains the search phrase, so do not enter private text; the box is designed for public names such as “rocket,” “生日,” or “U+1F680.” Search is literal annotation lookup, not sentiment analysis: the same emoji can carry different meanings across communities and conversations.
Why the same emoji looks different across platforms
Unicode assigns the underlying character or sequence and a standardized meaning, while vendors create their own artwork. Color, angle, facial expression, object details and accessibility can differ among Apple, Google, Microsoft, Samsung and individual fonts. Copying from this page therefore copies text—not EasyTool artwork. The destination chooses the glyph.
Support also depends on version. Emoji 17.0 was synchronized with Unicode 17.0 in 2025. A valid new character may appear as an empty box, tofu glyph or monochrome fallback on a system whose font predates it. A newer ZWJ sequence may display as several recognizable emoji instead of one combined image. Test the destination platforms that matter rather than judging support from this browser alone.
Invisible variation selectors and joiners
Some familiar symbols have both text and emoji presentations. U+FE0F, variation selector 16, requests emoji-style presentation for defined sequences; U+FE0E requests text style. U+200D, the zero-width joiner, combines elements in many profession, family, gender and directional sequences. These code points are invisible but significant.
A copied heart may be one code point or a base plus a presentation selector. Two sequences that look similar can have different byte lengths and behavior. Do not trim “invisible” characters from a sequence unless you intend to change it. The details panel exposes every code point plus HTML, JavaScript and CSS forms so source code preserves the selected entry.
Skin tones and combined sequences
Unicode defines five emoji modifiers representing a range of skin tones. They immediately follow a compatible modifier base and can appear inside longer ZWJ sequences. Multi-person emoji can have many explicit tone combinations, which is why tone variants outnumber the default browse set. This tool never generates guessed combinations: it exposes only fully-qualified entries present in the pinned Unicode data.
Names describe the standardized sequence, not a person’s identity. Choose tones thoughtfully and follow the communication norms of the people or product involved. A missing or separated glyph usually indicates font support, not an invalid copy.
Flags are sequences, not guaranteed political statements
Most country flags are pairs of regional-indicator characters. Subdivision flags use longer tag sequences. Unicode defines which sequences are valid, but platforms decide whether to render a flag, letters or another fallback. Product policies and geopolitical context can also affect display. Show a text label when the identity must remain unambiguous.
Using emoji accessibly
Do not use emoji as the only label for navigation, status, safety or payment actions. Screen readers may announce the CLDR name, a platform-specific description, individual sequence parts or nothing useful. In HTML, provide visible text or an appropriate accessible name around meaningful controls. Decorative emoji can be hidden from assistive technology when they repeat adjacent text.
Repeated emoji can create noisy announcements, and a visual joke may not survive a vendor design difference. For professional communication, use emoji as supporting tone rather than the sole carrier of an instruction. The copied glyph is not an image file and does not include alt text; accessibility belongs in the destination markup.
Developer copy formats
- Emoji sequence: best for chat, documents and UTF-8 source files.
- Code points: inspection format such as
U+1F680; not pasted literally to display a glyph. - HTML entities: hexadecimal or decimal character references for HTML source. Modern UTF-8 pages can usually use the emoji directly.
- JavaScript escapes: brace-form Unicode escapes such as
\u{1F680}. Multiple code points remain multiple escapes. - CSS escapes: hexadecimal escapes terminated with spaces. Be careful when the following CSS text begins with a hexadecimal character.
Primary data and specification references
- Unicode Emoji 17.0 test data
- Unicode Emoji 17.0 full list and CLDR names
- Unicode Technical Standard #51: Unicode Emoji
- Unicode CLDR 48 release and Emoji 17 annotations
- CLDR 48 annotation charts
Data and implementation review: 2026-08-02. The committed metadata records source URLs and SHA-256 hashes. Dataset count, qualification, ordering, multilingual search, filters, copy formats, URL state and page integration are covered by deterministic tests. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc.
Frequently asked questions
How many emoji are in this finder?
The pinned Unicode Emoji 17.0 dataset contains 3,944 fully-qualified entries. 1,914 remain when explicit skin-tone sequences are hidden. Counts differ depending on whether components, minimally-qualified sequences and tone combinations are included.
Why does an emoji look different after I paste it?
Unicode defines characters and sequences, not one universal artwork. Apple, Google, Microsoft, Samsung and other vendors draw their own glyphs. Operating-system and font versions also determine whether a newer sequence appears as one image.
Can I search in Chinese?
Yes. The local index includes English and Simplified Chinese short names and keywords from Unicode CLDR 48.2 when available. Some flags, components or specialized sequences may lack a Chinese annotation and fall back to English or code points.
Does clicking an emoji save my history?
No. A successful click copies the emoji and keeps up to 12 recent selections in memory for the current tab. The tool does not upload searches or save history in local storage. Filtered search terms can appear in the URL so a search can be shared.
What are FE0F and ZWJ?
U+FE0F is an emoji presentation selector used by some characters. U+200D is a zero-width joiner used inside many combined sequences. Removing invisible code points can change one emoji into text-style or separate glyphs.