Colon Emoji and Shortcodes on a Mac: The :fire: Syntax

If you have ever typed :fire: in Slack and watched it turn into 🔥, you have used a colon emoji shortcode. It is a small piece of text, a name wrapped in colons, that stands in for an emoji, and it is the fastest way to enter emoji without ever touching a picker. This guide explains what colon emoji and shortcodes actually are, where the :fire: syntax came from, and how to get the same shortcodes working in every app on your Mac with Comoji, not just the handful of apps that support them out of the box.

Short version: a shortcode like :tada: is just the emoji’s name between two colons, and apps that support them swap the code for the emoji as you type. macOS does not do this system-wide on its own, but Comoji adds it everywhere. Read on for what the codes are, which ones are worth memorizing, and how to type them anywhere.

What is a colon emoji shortcode?

A shortcode is the text name of an emoji wrapped in colons: :fire: for 🔥, :tada: for 🎉, :rocket: for 🚀. Instead of opening a grid and hunting for the right glyph, you type the name and the app renders the emoji. The colons are the signal that says “this is an emoji code, not just a word,” which is why fire on its own stays as text but :fire: becomes the flame. Because the codes are plain ASCII, they travel through any keyboard and any text field, and the app on the receiving end decides whether to draw the emoji or leave the code as written.

There are two flavors worth knowing. Some apps expand the code the instant you close the second colon, so :fire: becomes 🔥 in place. Others, and this is the pattern most people mean by “colon emoji,” autocomplete as you type: you enter :fir, a menu of matches appears, and you accept one with Tab or Return before you ever type the closing colon. That second style is faster because you do not have to remember the exact name, you just type a few letters and pick from the list.

Where the :fire: syntax comes from

The colon syntax is not something Apple or Unicode invented. It grew out of developer tools. GitHub popularized a set of named codes called gemoji so people could drop emoji into issues and commit messages with plain text, and the same list of names spread to Slack, Discord, Basecamp, and countless other apps. That shared vocabulary is why :100: means 💯 in Slack and on GitHub alike: they draw from the same underlying names. Comoji ships with that exact gemoji alias set, so the codes you already know from those tools work the same way here.

If your muscle memory comes specifically from a chat app, two companion guides cover the details: the Slack-style emoji shortcuts guide and the Discord emoji shortcuts guide. Both use the same colon syntax described here.

Do colon shortcodes work everywhere on a Mac?

Not by default, and this is the catch that trips people up. Colon shortcodes are an app feature, not a macOS feature, so whether :fire: becomes 🔥 depends entirely on where you are typing:

• Slack, Discord, Notion, and GitHub understand the codes, so :party and :check autocomplete inside them.
• Messages, Mail, Safari, Chrome, Pages, and most native Mac apps do not, so :fire: just sits there as literal text.
• macOS itself has no system-wide colon autocomplete, the built-in route is the Control-Command-Space picker, which is a grid you open rather than a code you type.

So the habit you built in Slack quietly breaks the moment you switch to a text message or an email. You are left either pasting emoji in or opening the system picker and searching, which is slower than the colon code you wanted to type in the first place. For the full list of built-in ways to enter emoji on a Mac, see how to type emoji on a Mac.

How to get colon shortcodes in every app

Comoji is a tiny menu bar app that brings colon autocomplete to every text field on your Mac, so the :fire: syntax stops being a per-app feature and becomes a system-wide typing habit. Type a colon token like :party and a popover shows the best matches; arrow to one and press Tab or Return to insert it.

Under the hood it uses the same gemoji names Slack, Discord, and GitHub use, so the codes carry over unchanged. It ranks by recent use so your most-typed emoji climb to the top of the list, handles skin tones, and works in Messages, Mail, Notes, Safari, Chrome, Notion, and most other apps. Forgot a name? Double-tap the trigger (:: by default) to open a large, searchable browser of the full set right at your cursor. And because everything is processed locally, nothing you type is uploaded.

A few shortcodes worth knowing

You do not need to memorize codes to use colon autocomplete, since typing a few letters and picking from the list is the whole point. But a handful come up so often that they become one-shot muscle memory:

• :fire: 🔥, :100: 💯, and :tada: 🎉 for approval and celebration.
• :eyes: 👀 and :thinking: 🤔 for reactions and “I am looking at this.”
• :rocket: 🚀 and :sparkles: ✨ for shipping and polish.
• :joy: 😂, :heart: ❤️, and :pray: 🙏 for the everyday ones you send most.

With Comoji you can type just :roc and accept 🚀 from the list, so even the longer names take only a few keystrokes. If you currently keep a short list of favorites as Text Replacements, it is worth reading how the two approaches compare in Text Replacements vs. emoji autocomplete, because autocomplete removes the need to define each code by hand.

Set it up in under a minute

Download the DMG, drag Comoji into your Applications folder (do this before granting permissions, macOS ties the grant to the app’s location), and launch it. On first run it walks you through the two permissions any keyboard utility needs, both in System Settings › Privacy & Security: Input Monitoring (to notice your colon tokens) and Accessibility (to read the text field and insert the emoji). It runs on macOS 13 Ventura or later, everything stays local, and password fields are ignored on purpose.

Should you use colon shortcodes?

If you live in Slack, Discord, or Notion, their built-in colon menus are already there and free, so use them. The moment your typing spreads across Messages, Mail, browsers, and native apps, the codes stop working and the friction returns. That is exactly the gap Comoji fills: it takes the :fire: syntax you already know and makes it work in every text field, ranked by what you actually send, with skin tones and a full searchable browser one double-tap away. Same habit, no more per-app boundaries.

Want your colon shortcodes to work everywhere? Download Comoji, grant the two permissions, and your next :fire: is one Tab away in any app.