Emoji Search

Find the right emoji fast

Emojis are ordinary Unicode characters, each with a code point and a standard name. This tool lets you search a curated set by name, keyword, shortcode or category, then copy the glyph with one click. It also surfaces each emoji’s U+ code point and its :shortcode: alias for chat platforms that prefer text.

How it works

The emoji dataset is bundled into the page, so filtering is instant and fully offline. Your search term is matched against four fields: the official name, the :shortcode:, any tagged keywords, and an exact glyph match. The code point shown under each emoji comes from char.codePointAt(0) converted to hexadecimal with a U+ prefix. Copying calls the browser clipboard API and confirms with a brief “Copied” badge.

Searching by feeling, not just name

Emojis rarely have intuitive official names. The ❤️ fire emoji is officially named “fire”, but you might search for “hot”, “energy”, or “launch”. This tool tags emojis with additional keywords beyond the official Unicode name so searches like these work:

• “happy” → 😀 😄 😁 and related faces
• “error” → ❌ ⚠️ 🚫 and prohibition symbols
• “done” → ✅ ✔️ 👍 and affirmative symbols
• “up” → ⬆️ 📈 🔝 and directional symbols
• “weather” → ☀️ 🌧️ ⛈️ 🌩️ and meteorological symbols
• “code” → 💻 🖥️ ⌨️ and computing symbols

Category filtering narrows results to a specific group — Smileys & Emotion, People & Body, Animals & Nature, Food & Drink, Travel & Places, Activities, Objects, Symbols, or Flags — when you know roughly what kind of emoji you want.

Shortcodes in different platforms

Shortcodes are text aliases wrapped in colons, like :fire: or :thumbsup:. They were popularized by GitHub and Slack and are now supported across most team chat and developer tools. Key differences between platforms:

• GitHub Markdown: uses :emoji_name: syntax in comments, issues, and pull requests. Emojis render in rendered Markdown view.
• Slack: supports the same basic set plus custom emoji added by workspace admins. Type : to trigger the emoji picker or type the shortcode directly.
• Discord: supports a similar shortcode system and adds server-specific custom emoji accessed as :custom_name:.
• GitLab: renders the same shortcode set as GitHub in Markdown.
• Plain text and email: shortcodes do not render — paste the glyph character directly instead.

When you need a shortcode for documentation, use the format shown in this tool’s results. When you need the character for plain text or HTML, use the Copy button to get the glyph.

Code points for developers

The U+ code point displayed under each result is useful when working with emoji at the code level:

• Regex matching: many emoji require matching on code points above U+FFFF, which need the u flag in JavaScript regex: /\u{1F525}/u for 🔥.
• Font and rendering checks: if an emoji is not rendering, comparing the code point against your font’s supported characters identifies missing glyphs.
• Database storage: most modern databases store emoji correctly when the column is UTF-8 (utf8mb4 in MySQL for code points above U+FFFF).
• Input filtering: if you need to strip or allow emoji in user input, working from code point ranges is more reliable than matching character-by-character.

Tips and notes

• In Slack, GitHub and Discord you can type the shortcode such as :rocket: and it expands to the emoji automatically.
• The same emoji can render differently per platform because vendors ship their own artwork for each code point.
• Searching by feeling works: happy, love, done and error all map to keyword tags, not just exact names.
• For the technical code point (for example to use in a regex or font check), read the U+ value shown beneath each result.