Emoji ↔ shortcode batch converter — :smile: ↔ 😄 (GitHub / Slack / Discord)

The text you convert contains more context than the emoji

Converting :heart: :coffee: in the morning :sunny: is trivial, but the surrounding sentence is the draft of a PR body, an internal Slack announcement, or a blog post. Pasting that text into an online converter transmits the full content to a server. For publicly intended text the exposure is low; for an unannounced feature description in a PR title or an internal memo it is not.

Short converters feel lightweight, which lowers the threshold for pasting carelessly. But a one-line PR title can include an unreleased feature name, a customer codename, or an internal acronym — small character counts do not imply small leakage.

The structural risk of upload-style converters

Online shortcode converters present a simple “paste, click, copy” UI, but server-side they routinely persist the full input text. Terms of service typically reserve broad rights to retain submissions for “usage analytics”, “service improvement”, or “abuse detection”, and the actual retention windows are rarely disclosed at a level a user could audit.

Because these tools are usually thin wrappers on Cloud Functions or edge workers, request bodies also land in the upstream cloud provider’s logs. From the user perspective only the tool vendor is visible, but structurally several operators may see the request payload — a quiet asymmetry between what the user perceives and what is actually recorded.

node-emoji and a bundled dictionary for offline conversion

This tool bundles node-emoji (MIT) and the gemoji-derived 1570+ shortcode dictionary at build time. Shortcode-to-emoji conversion is dictionary lookup plus string replacement; emoji-to-shortcode is the reverse mapping. Both directions run in browser memory — no network request is needed at conversion time.

The unknown-shortcode handling (keep / strip / replace with ?) is also pure JavaScript conditional branching. Open DevTools Network and convert any text: request count does not change after the initial page load. The implementation is on GitHub.

Using it as a pre-paste verification step

Before pasting shortcode-heavy text into a GitHub PR body or a Slack message, running it through this tool catches unknown tokens that would render as literal :my-custom: instead of an emoji. This is especially useful for externally visible PRs — vendor integrations, partner-facing documentation — where a stray unresolved shortcode looks unprofessional. The conversion takes a second in the browser; the check is worth adding to the pre-submit habit.

How shortcode dictionaries diverge across platforms

The :smile: :thumbsup: shortcode style originated with GitHub’s gemoji dictionary; early Slack inherited the same set. Over time each platform added its own entries and aliases, so today the same shortcode can map to different emoji on different platforms, or only exist on one of them. :hugs: maps to 🤗 on Slack but Discord prefers the alias :hugging:; older GitHub PRs may not recognise :hugs: at all.

This tool’s 1570+ dictionary is the GitHub-flavoured gemoji set, which is the most general baseline. When targeting Slack / Discord / Mattermost specifically, treat the converted output as a starting point and verify each shortcode against the target platform’s own list rather than pasting directly. The FAQ summarises the most common cross-platform divergences.

Modifier and ZWJ pitfalls that shortcodes cannot fully express

Simple emoji like :thumbsup: 👍 are stable, but Fitzpatrick-scale skin-tone variants like 👍🏽, family ZWJ (zero-width joiner) sequences like 👨‍👩‍👧‍👦, and profession emoji like 👩‍💻 are composed of multiple Unicode code points joined together. Most cannot be addressed by a single shortcode and rely on extensions like :thumbsup_tone3: that some dictionaries support and others do not.

New emoji from Unicode 15.1 or 16.0 only appear via shortcode after the dictionary file is updated. This tool’s dictionary comes from the MIT-licensed node-emoji library and refreshes on library upgrades. If a recent emoji refuses to convert, copy-pasting the Unicode character directly is the reliable fallback. To confirm a shortcode’s canonical spelling and inspect the underlying codepoints, emoji-info shows the name and per-codepoint breakdown, and markdown-html-convert helps preview how the shortcode-laden message will render once it is converted to HTML.