أداة البحث عن الرموز المختصرة

ابحث عن الرموز المختصرة لأي رمز تعبيري عبر Slack وDiscord وGitHub ومنصات أخرى. جاهز للنسخ واللصق.

Finder

لم يتم العثور على رموز مختصرة لهذا الرمز التعبيري.

How to Use

  1. 1
    Enter an emoji or keyword

    Type or paste an emoji character directly, or enter a keyword like 'heart' or 'tada' to find matching emoji. The tool searches across shortcode libraries for Slack, Discord, GitHub, and other platforms simultaneously.

  2. 2
    Compare shortcodes across platforms

    Review the shortcode for each platform side by side. Note that shortcodes are not standardized — :slightly_smiling_face: on Slack corresponds to :slightly_smiling: on Discord, and some emoji have shortcodes on one platform but not another.

  3. 3
    Copy the correct shortcode

    Click the copy button next to any platform's shortcode to copy it in the correct :colon-wrapped: format ready for use in that platform's message field, markdown renderer, or automation system.

About

Emoji shortcodes emerged as a practical workaround in the early days of platform-specific emoji support, when keyboard input for emoji was limited and different applications maintained separate glyph libraries before Unicode standardization took hold. Platforms like Campfire, then Slack, GitHub, and Discord developed colon-delimited shortcode systems (`:smile:`, `:tada:`) that let users reference emoji by descriptive name in plain text interfaces. These shortcodes are converted to actual Unicode emoji characters — or sometimes proprietary image files — by the receiving platform's parser.

The relationship between shortcodes and Unicode names is loose and historically contingent. Shortcodes were often assigned based on early Emoji 1.0 drafts, popular Japanese carrier names, or informal community consensus before the Unicode Consortium formalized emoji character names. This explains why shortcodes frequently diverge from official Unicode names: `:poop:` rather than `:pile_of_poo:`, `:+1:` rather than `:thumbs_up:`. Some platforms allow multiple shortcode aliases per emoji to accommodate different user vocabularies.

For developers building integrations with Slack, Discord, GitHub, or similar platforms, shortcode handling requires platform-specific dictionaries since no universal standard exists. Open-source projects like `emoji-mart` and `node-emoji` maintain curated shortcode mappings for multiple platforms, but these require ongoing maintenance as platforms add custom emoji and update their naming conventions. When building cross-platform emoji features, it is safer to work at the Unicode codepoint level for storage and transmission, converting to platform-specific shortcodes only for display contexts where the platform expects shortcode input.

FAQ

Are emoji shortcodes standardized across platforms?
No — emoji shortcodes are entirely platform-specific and not standardized by any official body. Slack, Discord, GitHub, and other platforms each maintain their own shortcode dictionaries, which overlap significantly but differ in naming conventions and coverage. GitHub's emoji set (used in Markdown files and issues) maps closely to the Unicode emoji list but uses underscores and its own naming conventions. Slack's shortcodes tend to use full words, while Discord aligns closely with Twemoji naming. There is no cross-platform standard, so :cat: on GitHub may behave identically to :cat: on Discord but produce different results than :cat: on a platform using a different glyph set.
What is Twemoji and how does it relate to shortcodes?
Twemoji is an open-source emoji graphics library originally created by Twitter (now X) that provides SVG and PNG renderings of Unicode emoji. Many platforms — including Discord, older versions of Slack, and numerous web apps — use Twemoji glyphs to display emoji consistently across operating systems. When a platform uses Twemoji, its shortcodes and glyph names often align with Twemoji's naming conventions. Twemoji is released under the Creative Commons Attribution 4.0 license for its artwork, making it widely used in web applications that need cross-platform emoji consistency without relying on OS-native rendering.
How do I use emoji shortcodes in Markdown?
GitHub Flavored Markdown (GFM) supports emoji shortcodes preceded and followed by colons — for example, :smile: renders as 😄 and :tada: renders as 🎉. This rendering is performed by GitHub's own parser and is not part of the official CommonMark Markdown specification. GitLab, Bitbucket, and other platforms support similar syntax with their own shortcode dictionaries. In static site generators like Jekyll and Hugo, emoji shortcode support is typically a plugin that maps the shortcodes to actual Unicode emoji characters or image files during build time. Standard Markdown parsers without plugins do not render emoji shortcodes.
Why do some emoji have shortcodes that don't match their Unicode name?
Emoji shortcodes were largely established before the Unicode emoji naming conventions were fully standardized, and many platforms created their own naming conventions based on early Emoji 1.0 drafts, Japanese carrier names, or community usage. For example, GitHub's :octocat: shortcode maps to a custom GitHub mascot image that is not a Unicode emoji at all. :+1: and :thumbsup: both map to the same thumbs-up emoji on most platforms. Some shortcodes like :poop: reflect informal community names rather than Unicode names ('pile of poo'). Shortcode dictionaries are also extended by platform communities to include custom emoji beyond the Unicode set.
What is the difference between a shortcode and a Unicode code point?
A Unicode codepoint (like U+1F600) is a globally standardized, permanent identifier defined by the Unicode Consortium for a specific character. It is part of an international standard and has a normative character name in UnicodeData.txt. A shortcode (like :grinning:) is an informal, platform-specific text alias used as a convenient input shorthand in environments where typing the emoji character directly is impractical — such as text-based chat systems before native emoji keyboard support. When a platform parses a shortcode, it converts it to the corresponding Unicode character for storage and transmission. The shortcode is an input mechanism only; all modern systems store and transmit the Unicode character.