How do emojis render across different mailbox providers?

You pick the perfect emoji for your subject line, hit send, and half your audience sees a black square. That's not hypothetical. It's one of the most common emoji surprises in email, and it comes down to how mailbox providers and operating systems actually handle emoji rendering.

Here's the short version: emojis are Unicode characters, and rendering depends on the OS and email client, not just the mailbox provider. The mailbox provider passes the character through. What the reader's device does with it is another story.

How the big clients handle emojis

Gmail renders emojis well on both desktop and mobile. It uses Google's Noto emoji font on Android and defers to the OS font stack elsewhere. You'll generally see color emojis in Gmail across devices, though the style of the emoji will match Google's design, not Apple's.

Apple Mail and iOS are the gold standard for emoji rendering. Apple's emoji set is high-quality and renders beautifully in subject lines and body text. Your 🍎 on iPhone will look polished. No surprises here.

Outlook is where things get interesting. Outlook on the web (OWA) handles emojis reasonably well. But the Microsoft 365 desktop app and older Outlook versions (2016 and earlier) use the system font for rendering. On Windows 10 and 11, that means Segoe UI Emoji, which supports color emojis. On older Windows versions or enterprise machines that haven't updated their font libraries, emojis can render as black and white symbols or plain boxes. This is the Outlook problem everyone warns about.

Yahoo Mail renders emojis on its own emoji font and generally does a decent job across modern browsers. The look will differ slightly from Apple or Google's interpretation of the same character, but you won't usually get broken boxes.

Android rendering depends on the version and manufacturer. Stock Android uses Google's Noto emoji font. Samsung devices use their own emoji style, which can look noticeably different. Older Android versions (pre-4.4) have minimal emoji support and will show empty boxes for newer Unicode characters.

The fallback problem

When a client or OS doesn't recognize a Unicode character, it shows a replacement character, usually a box (□) or a question mark inside a box (🮻). This happens most often with newer emojis (added in Unicode 13 or later) on older devices or enterprise email systems that haven't updated in years.

Lotus Notes and other legacy enterprise clients have historically shown emojis as raw Unicode escape sequences or garbled text. If a significant chunk of your list is enterprise B2B with locked-down IT environments, that's worth knowing before you add 🚀 to every subject line.

What actually controls the visual style

Two things decide how your emoji looks. First, the Unicode code point determines which character it is. Second, the OS-level emoji font determines what it looks like. A thumbs-up 👍 on iOS looks like Apple's design. The same character on Android looks like Google's design. Both are correct renderings of the same Unicode character. They just look different.

Still this is why you can't fully control what your subscribers see. You're sending a character, not an image.

What to watch for in B2B and enterprise sending

Enterprise environments often run older versions of Outlook on Windows machines that IT hasn't updated. A financial services company on Windows 7 with Outlook 2013 is going to show your subject line emoji as a box. In those environments, the rest of your subject line still needs to carry the message on its own. If the emoji is decorative, the box is just a minor visual glitch. If the emoji was meant to convey meaning, the reader loses context entirely.

It's also worth noting that whether you should use emojis and how they render are two separate questions. Even if your audience would love them, knowing where they'll break helps you decide how much weight to put on them.

How to check before you send

But the best way to know how your emoji looks is to preview it. Most ESPs have inbox preview tools that show you subject line rendering across major clients. You can also just send yourself a test on an Android phone, an iPhone, and a Windows desktop if you have access to them. That covers the majority of your audience in most cases.

If you want to see how your subject line reads overall before it goes out, try our free subject line tester. It won't simulate every OS, but it'll catch obvious issues fast.