Emoji version - the release cycle that decides what your phone can show
This article takes about 4 minutes to read.
When Unicode releases a new emoji, it can take 6 months to 2 years before everyone in your group chat sees it. That gap is governed by the emoji version system.Unicode publishes new emoji on a roughly annual schedule, but each platform implements them on its own timeline. Understanding the version system helps you plan content, set expectations, and explain why an emoji "doesn't work" on someone's phone.
Definition
Emoji version is a numbering system used by the Unicode Consortium to label batches of newly added or updated emoji. Emoji versions are published alongside Unicode versions but follow a slightly different numbering and timeline. Each version specifies which codepoints, sequences (ZWJ, modifier, tag), and properties are added or changed.
Unicode version vs. Emoji version
| Aspect | Unicode version | Emoji version |
|---|---|---|
| Scope | All Unicode characters | Emoji-specific data |
| Examples | 15.0, 15.1, 16.0 | 15.0, 15.1, 16.0 |
| Release frequency | Roughly annual (September) | Tracks Unicode releases |
| Defines | Codepoints, properties, scripts | Emoji codepoints, sequences, RGI list |
Emoji versions historically had their own numbering (Emoji 1.0, 2.0, 3.0...) that diverged slightly from Unicode versions. From Unicode 11.0 onward, the two have been numerically aligned (Emoji 11.0 = Unicode 11.0 emoji additions).
Notable releases
- Emoji 1.0 (2015): First standalone emoji version, introduced skin tone modifiers (Fitzpatrick scale)
- Emoji 5.0 (2017): Added gender-neutral emoji and first wave of profession ZWJ sequences
- Emoji 11.0 (2018): Numbering aligned with Unicode
- Emoji 13.0 (2020): Smiling face with tear, transgender flag, ninja
- Emoji 14.0 (2021): Melting face, biting lip, troll
- Emoji 15.0 (2022): Pink heart, donkey, jellyfish
- Emoji 15.1 (2023): Family ZWJ updates, lime, phoenix
- Emoji 16.0 (2024): Shovel, leafless tree, fingerprint, harp
The platform implementation gap
Unicode publishes a version specification, but each vendor (Apple, Google, Samsung, Microsoft, Meta) implements the changes on their own schedule. The typical lag follows roughly this pattern:
- Month 0 (September): Unicode publishes the version
- Months 1-6: Major vendors design the new glyphs
- Months 6-12: First implementations ship in OS updates (often iOS first)
- Months 12-24: Wider rollout to Android, Windows, web platforms
- Months 24+: Older devices that won't get updates remain unable to render the new emoji
The "long tail" of older devices is significant. Devices stuck on older emoji versions may never receive the latest emoji, leading to permanent rendering gaps in cross-platform conversations.
How to check what version a device supports
- iOS: usually matches the iOS major version's emoji table; iOS 17 supports through Emoji 15.0/15.1
- Android: depends on the OEM; Samsung One UI, Pixel, and others have different schedules
- Windows: emoji versions tied to feature updates; Windows 11 typically lags Apple by 6-12 months
- macOS: tracks iOS closely
- Web: depends on the browser's emoji font (often Noto Color Emoji on Linux/Chrome OS)
Emojipedia maintains current cross-platform availability charts for each emoji, which is the most practical way to check support.
Implications for content design
1. Treat new emoji with caution for 12-18 months
Don't rely on emoji from the latest Unicode version in critical content (logos, brand campaigns, important UI elements) until the platform majority supports them. For a public-facing product, that often means waiting through one or two OS update cycles.
2. Older emoji are safer
Emoji from versions 5-10 (released 2017-2020) have near-universal device support today. They're the safest pool for cross-platform messaging where you can't predict the recipient's device.
3. Test with your audience
For specific apps or products, look at your user demographics. Heavy iOS users will see new emoji faster than corporate Android fleets. Plan emoji choices accordingly.
The ZWJ sequence twist
Even when an emoji's base codepoint is widely supported, ZWJ sequences combining it with newer modifiers may fail. For example, gender ZWJ variants of an old emoji can be added in a later version, requiring up-to-date support to render correctly. Version compatibility isn't just about codepoints - it's about the full set of sequences.
Common misconceptions
- ❌ "All devices update together" → ✅ Vendor and device-level update schedules vary widely
- ❌ "If I see it on my phone, everyone sees it" → ✅ Older or different platforms may not have caught up
- ❌ "Emoji versions and Unicode versions are unrelated" → ✅ Aligned since version 11.0