숏코드 찾기
Find the shortcode built from any emoji's CLDR English name, such as :thumbs_up:, and copy it.
Finder
How to Use
-
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 by name, keyword or character.
-
2
Read the shortcode
Each emoji has one shortcode made from its CLDR English name, such as :thumbs_up: for 👍. Platform aliases such as :+1: on Slack and GitHub are not included, and shortcodes are not standardized, so check the app you paste into.
-
3
Copy the shortcode
Click the copy button next to the shortcode to copy it in :colon-wrapped: format for a message field, Markdown renderer or automation script.
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.