Why Developers Need an Emoji Reference
Emoji show up in commit messages, documentation, READMEs, API responses, Slack messages, and marketing copy. But the platform emoji picker doesn't tell you the shortcode (for Markdown), the Unicode codepoint (for encoding), or the HTML entity (for web). A developer's emoji reference gives you all three: the character itself, its standard name, its shortcode, and its technical identifiers.
Emoji Formats
- Raw emoji: 😀 — paste directly into text. Works in most modern contexts but may render differently across platforms.
- Shortcode:
:smile:— used in Markdown, Slack, GitHub, Discord, and Notion. Platform-agnostic; rendered by the platform's emoji set. - Unicode codepoint:
U+1F600— the definitive identifier. Use for encoding work and technical documentation. - HTML entity:
😀(decimal) or😀(hex) — for embedding in HTML.
Emoji vs. Emoticon
Emoticons are text-based: :) ¯\_(ツ)_/¯. Emoji are actual Unicode characters: 😀 🤷. Emoticons render consistently everywhere (they're just ASCII art). Emoji render differently per platform (Apple's 😀 looks different from Google's). In technical documentation and code comments, emoticons are safer — they never break encoding assumptions.
Search Every Emoji Now
Use ToolsVito's Emoji Reference to search every Unicode emoji by name or keyword. Click to copy with its shortcode, codepoint, and HTML entity. All searchable in your browser.