Back to Blog
Developers

Slack Emoji Shortcodes to Unicode: Tested Converter

Slack names its emoji the way the emoji-datasource project does, and rich_text blocks already carry the Unicode code points. We checked both on 18 November 2026 and wrote a 25-line converter for text fields and reactions.

Slack Green Team
November 18, 2026
November 18, 2026
3 min read
Share:
slack
slack api
emoji
developers

To turn a Slack emoji shortcode such as :+1::skin-tone-3: into Unicode, look the name up in the emoji-datasource table (short_names to unified), add the skin tone modifier if there is one, and turn each hex code point into a character. For messages you often need no table at all: the rich_text blocks of a message already carry a unicode field such as 1f44d-1f3fc. The text field and reaction names carry only the shortcode. We checked this on 18 November 2026 in a test workspace, and a code read of the Slack web client showed its own emoji table uses the same names as emoji-datasource for 1,972 of its 1,980 entries.

The test message

We typed one line of shortcodes into the Slack web app. The composer turned the standard ones into emoji as soon as they were entered and left three as text: :simple_smile: and :shipit:, which Slack draws as images, and a name that does not exist.

The Slack composer with Launch day followed by rocket, thumbs up with a medium-light skin tone, thumbs up, the Japanese flag, a family, a red heart and a smile, then the plain text :simple_smile: :shipit: :sg-nonexistent:

After we sent it, we added four reactions through reactions.add: thumbsup::skin-tone-5, flag-jp, shipit and white_check_mark.

The sent Slack message with its emoji and four reactions: thumbs up with a dark skin tone, the Japanese flag, the squirrel emoji and a check mark

What the API returned

conversations.history gave the message back in two forms. The text field had changed some names:

Launch day :rocket: :+1::skin-tone-3: :+1: :jp: :man-woman-girl-boy: :heart: :smile: :simple_smile: :shipit: :sg-nonexistent:

We typed :thumbsup::skin-tone-3: and :flag-jp:, and the text field says :+1::skin-tone-3: and :jp:. Slack stores the main name of an emoji, not the alias you typed. The rich_text block kept the typed name and added the code points:

[
 {
  "type": "emoji",
  "name": "thumbsup",
  "unicode": "1f44d-1f3fc",
  "skin_tone": 3
 },
 {
  "type": "emoji",
  "name": "+1",
  "unicode": "1f44d"
 },
 {
  "type": "emoji",
  "name": "flag-jp",
  "unicode": "1f1ef-1f1f5"
 },
 {
  "type": "emoji",
  "name": "man-woman-girl-boy",
  "unicode": "1f468-200d-1f469-200d-1f467-200d-1f466"
 }
]

The reactions came back with main names too: +1::skin-tone-5, jp, squirrel (we added shipit, an alias of the workspace's squirrel emoji) and white_check_mark. No reaction carries a unicode field.

Where the emoji isWhat you getNeed a table?
rich_text block of a messagename, unicode hex, skin_toneNo
text field of a message:+1::skin-tone-3:, main nameYes
reactions on a message+1::skin-tone-5, main nameYes
Custom emoji in emoji.listAn image URL or alias:<name>No Unicode exists

Never appear "away" on Slack again

Cloud-based. No downloads. Works 24/7 even when your laptop is off.

Where Slack's names come from

The Slack web client ships its own emoji table in its client-boot script. We downloaded the scripts the page loaded and found entries like this one:

"thumbsup": {"name": "thumbsup", "unicode": "1f44d", "aliasOf": "+1",
  "skinVariations": {"3": {"name": "thumbsup::skin-tone-3", "unicode": "1f44d-1f3fc"}, ...}}

The table holds 1,980 names. We compared each one with emoji-datasource 16.0.0, the open emoji data set by Cal Henderson (iamcal): 1,972 names map to the same code points. The other 8 (landslide, ballet_dancer, trombone, treasure_chest, hairy_creature, orca, distorted_face and fight_cloud) are newer emoji that version 16.0.0 does not list yet. So emoji-datasource is a safe table for Slack shortcodes, with a small gap for the newest emoji.

The converter

import json, re, urllib.request

URL = "https://unpkg.com/emoji-datasource@16.0.0/emoji.json"
data = json.load(urllib.request.urlopen(URL, timeout=30))
by_name, skins = {}, {}
for e in data:
    for name in e["short_names"]:
        by_name[name] = e["unified"]
        skins[name] = {v["unified"].split("-")[1]: v["unified"]
                       for v in (e.get("skin_variations") or {}).values()
                       if "-" in v["unified"]}
TONES = {2: "1F3FB", 3: "1F3FC", 4: "1F3FD", 5: "1F3FE", 6: "1F3FF"}

def to_char(unified):
    return "".join(chr(int(cp, 16)) for cp in unified.split("-"))

def shortcodes_to_unicode(text, custom=None):
    def swap(m):
        name, tone = m.group(1), m.group(2)
        if name not in by_name:
            return (custom or {}).get(name, m.group(0))
        if tone:
            return to_char(skins[name].get(TONES[int(tone)], by_name[name]))
        return to_char(by_name[name])
    return re.sub(r":([a-z0-9_+'-]+):(?::skin-tone-([2-6]):)?", swap, text)

Pass custom a dict if you want custom emoji replaced by something, such as an image tag. Without it, unknown names stay as they are.

Output

We ran the converter on the text field, on each reaction and, for comparison, on the code points in the blocks:

text field : Launch day :rocket: :+1::skin-tone-3: :+1: :jp: :man-woman-girl-boy: :heart: :smile: :simple_smile: :shipit: :sg-nonexistent:
converted  : Launch day πŸš€ πŸ‘πŸΌ πŸ‘ πŸ‡―πŸ‡΅ πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘¦ ❀️ πŸ˜„ :simple_smile: :shipit: :sg-nonexistent:
reaction   : +1::skin-tone-5        πŸ‘πŸΎ
reaction   : jp                     πŸ‡―πŸ‡΅
reaction   : squirrel               :squirrel:
reaction   : white_check_mark       βœ…
blocks     : Launch day πŸš€ πŸ‘πŸΌ πŸ‘ πŸ‡―πŸ‡΅ πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘¦ ❀️ πŸ˜„ :simple_smile: :shipit: :sg-nonexistent:

The text field and the blocks gave the same line. :simple_smile: stayed text in both: emoji-datasource has no such name, and Slack's emoji.list returns it as an image on a.slack-edge.com, not as a Unicode emoji. :shipit: and :squirrel: stayed text too, because they are image emoji in the workspace. The skin tone reaction became πŸ‘πŸΎ (U+1F44D U+1F3FE).

Two details to keep in mind:

  • Skin tones run from 2 to 6 and map to U+1F3FB to U+1F3FF. Slack's table lists no tone 1.
  • Some emoji end in U+FE0F, the variation selector. The heart is 2764-fe0f in both Slack and emoji-datasource; keep it, because it asks for the color emoji form.

For the names themselves, our Slack emoji codes list has the common ones, and the Slack emoji API covers emoji.list and custom emoji. Reactions have their own calls, covered in the reactions API page.

Always Active

Stop Jiggling Your Mouse.

Join hundreds of remote workers who never worry about their Slack status. Set it up once, stay green forever.

Related Articles

Developers

Slack App Configuration Token: Generate, Rotate and Revoke

An app configuration token lets a script create Slack apps from manifests. We generated one, rotated it five times and tested it again 28 hours later.

Slack Green Team
Developers

Slack App Collaborators: Add, Remove and Transfer Ownership

Collaborators are the people who can edit a Slack app. We added and removed one on 20 November 2026 as a regular member of a test workspace, recorded who can be added and what Slack asks you to do after a removal, and wrote down the hand-over path Slack documents.

Slack Green Team
Developers

Slack Bolt Middleware: Global and Listener, Tested

Global middleware runs for every request and listener middleware for one listener. We ran both in Bolt for Python and Bolt for JavaScript on 20 November 2026 and logged what Slack did when next() was skipped: Python answered 404 and Slack sent the event again.

Slack Green Team