Updated · 6 min read
Emojis in subject lines: when they help, when they hurt
Add one emoji to a subject line and opens typically tick up 2–8%. Add three and the number goes the other way. It's not a linear relationship, and once audience, category and client rendering enter the room it stops being a universal rule at all. Here's what the data actually says and the two mistakes that keep showing up.

By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
Picture the inbox first — that's where the answer lives
Open your phone and glance at your Promotions tab — the bucket Gmail and Apple Mail use to corral marketing email. Scan ten subjects. Maybe one has a small shopping cart, two have flames stacked up like a pyre, the rest are plain text. Your eye lands somewhere first, lingers somewhere second, skips the rest. That fraction-of-a-second sorting is the entire game emojis are playing. Everything below is just the rules of that game.
The headline number you've probably seen quoted: a single well-placed emoji in a subject line lifts open rate 2–8%. That figure shows up consistently across the large-scale studies from Mailchimp, Experian, and Litmus through the 2020s. Two or more emojis often show no lift, sometimes a decline. The reason is novelty — back in 2014, any emoji stood out because the inbox was a wall of text; as usage saturated, the effect got smaller and a lot more context-dependent.
The emoji that works is the one doing semantic work, not decorative work. A single icon representing the content lifts opens. A string of icons dressing up the copy doesn't.
Audience matters more than most guides admit. Consumer-retail lists respond to emojis. B2B and professional-services lists — think enterprise SaaS buyers, legal-tech, finance ops — mostly don't, and sometimes actively respond worse. A subject line that lifts a lifestyle brand can drop opens for a legal-tech product without either team doing anything wrong. Test for your list, not for the internet's list.
Worth dispatching one common worry up front: the emoji isn't tanking your deliverability — your ability to actually land in the inbox rather than spam. Mailbox filters don't penalise the character itself. What they penalise is the shape of the whole subject — emojis combined with all-caps and promotional keywords starts looking like a pattern. The glyph is fine. The composition around it matters more.
When one emoji actually earns its place
Four situations where a single emoji is doing real work. If your subject doesn't fit one of them, the default is no emoji.
As a visual anchor for meaning. Pair the icon to the content: cart for an abandoned cart, lock for a security email, rocket for a launch. The emoji does work the text would have to do anyway — your reader's eye lands on the glyph and the subject's purpose arrives half a second earlier. That half-second is the entire point.
To break a wall of text. In a Promotions tab where every subject is text, one emoji is a visual anchor. In an inbox where every competitor is already doing the same, yours becomes part of the noise. The surrounding environment is the point — the glyph is only as useful as what it's next to.
On a real deadline. Time-sensitive subjects can use a small clock or flame to convey urgency without writing "URGENT" in caps and tripping filters in the process. Sparingly used, it's the cleanest urgency signal available.
When it matches brand voice. Brands that already use emojis in social and in-app can use them in subject lines without dissonance. Anyone otherwise formal adding a party popper to a CFO email reads as if a different team took over the keyboard.
Where emojis quietly cost you opens
Stack three or more in one subject line and you read as spammy, which usually drops opens. There are rare exceptions for genuine novelty moments — the "Happy Friday" send built around a visual punchline — but the default is one, and the default usually wins.
Mismatched emojis are worse than no emoji at all. A flame on a mundane newsletter is dissonant, and users who click through and find nothing urgent quietly learn to discount your future signals. That's a long-term cost for a short-term open.
Transactional emails — receipts, password resets, shipping confirmations, the legally-required ones — should stay clean. A receipt with a party popper in the subject reads as unprofessional and undermines the document it precedes. The transactional anatomy guide covers the full reason, but the short version: these emails are legal artefacts, not campaigns, and the subject should reflect that.
For professional B2B lists, the default is skip. CFOs reading pitches from enterprise SaaS vendors don't want a flame on the subject line; it reads as unserious. Know the audience. When in doubt, the safer rule is no emoji.
The same emoji can render four different ways
Here's the bit that catches teams who skip QA. Every email client renders emojis using its own font set: Apple has its own, Google uses Noto, Microsoft uses Segoe. For the common glyphs — cart, lock, clock, rocket, party popper — all three render recognisably. Anything newer than Unicode 11 (the standard that underpins emoji support, version 11 shipped in 2018) risks rendering as a blank box on older Outlook installs, especially Windows desktop.
,
Within a single client, mobile and desktop are consistent enough — Gmail mobile and Gmail web look the same. Cross-client is where rendering breaks: Apple Mail iOS vs Outlook desktop is the biggest gap, and it's the one worth specifically checking.
One more thing the emoji is doing: getting read aloud. Screen readers — the assistive tech that voices emails for blind and low-vision users — speak the Unicode description: "shopping cart", "rocket". Usually fine, because the description reinforces the meaning. It becomes awkward only when emojis are used decoratively; a row of sparkles is announced as "sparkles sparkles sparkles". One more argument for semantic over ornamental use.
Position on the line is doing more than you think
Position changes effectiveness more than most teams notice. Start of subject is maximum attention but maximum spam-adjacent — use it for genuine high-impact subjects, not routine sends. End of subject is more subtle and, on most programs, slightly better performing; the text carries the weight and the emoji adds a quiet visual note.
The middle is almost always awkward. It works only when the emoji is replacing a word — "Your 🛒 is waiting" lands because the glyph is a noun. "Save 30% 🎉 on summer items" reads as cluttered because the glyph is just sitting there, smiling.
Should you A/B test emoji vs no-emoji — split your audience, send two versions, see which wins? Yes, do it. Keep the rest of the subject line identical, size the test to detect a small effect (the lift is usually 2–8%, so the sample needs to be big enough to spot it), and re-test occasionally because saturation shifts. A winner in 2022 isn't necessarily a winner in 2026. The A/B testing guide has the sample-size maths.
The decision rule, end of story
,
There is no universal best emoji — whatever matches the content. Commerce gets a cart, security gets a lock, urgency gets a clock. A decorative sparkle bolted onto a subject that doesn't need it tends to underperform the icon that's actually carrying meaning.
The classic spam-pattern emojis are still classic spam-pattern emojis. Stacked fire glyphs, repeated money bags, a row of party poppers — one of each is fine; the repetition-as-emphasis move is a 2014 signal that still lands as amateur in 2026.
treats emoji as a specific tool with a specific job. Most subject lines shouldn't contain one. A thoughtful minority should. The point is to know which is which before sending, not after.
Read to the end
Scroll to the bottom of the guide — we'll tick it on your reading path automatically.
Frequently asked questions
- Do emojis help email open rates?
- Sometimes, and less than operators hope. Peer-reviewed studies and industry data suggest ±5-10% open-rate variance from well-chosen single emojis on B2C audiences. B2B audiences often react negatively. The lift is real but small, and highly audience-dependent. The winning pattern: one emoji that adds meaning (a small truck on a shipping notification), not decoration.
- How many emojis should I use in a subject line?
- Zero or one. Two is pushing it. Three or more consistently underperforms — reads as marketing-template filler and triggers spam filters in some clients. If the subject line needs multiple emojis to work, the copy isn't strong enough. Rewrite the text first, add emoji as accent second.
- Do emojis affect deliverability or trigger spam?
- Modest signal, context-dependent. Gmail's spam filter doesn't penalise emojis alone; the algorithmic penalty comes from emoji combined with other spam signals (excessive punctuation, all-caps, urgency language). A single emoji on otherwise-clean copy doesn't hurt. Three emojis plus all-caps plus exclamation marks is textbook spam pattern.
- Which emojis work best in marketing emails?
- The ones carrying semantic meaning for the content. A truck on shipping notifications, a check mark on confirmations, a package on delivery updates. Emojis that land as decoration (a random sparkle on a promotional send) rarely add measurable lift and often erode B2B trust. Test per audience rather than adopting a universal rule.
- Do emojis render the same across all email clients?
- No. Emoji rendering varies by client: Apple Mail uses Apple's set, Gmail uses Google's Noto Color, Outlook sometimes falls back to text placeholder (:smile: becomes literal text, not an emoji). The same emoji can look completely different between Apple Mail iOS and Gmail Android. Always test in at least 3-4 client/device combos before sending — an emoji that looked perfect in your Apple Mail test may render as a tofu square in Outlook.
This guide is backed by an Orbit skill
Related guides
Browse allPreheader text: the second subject line most programs ignore
The preheader is the snippet shown next to the subject line in the inbox preview. Treat it like a second subject line and you double your hook. Treat it like an afterthought and it says 'View this email in your browser'. Here's how to write preheaders that actually earn the open.
Subject line anatomy: the four parts every line that performs shares
Most subject-line advice is decoration tips — emoji, length, numbers. The lines that actually get opened share a structural pattern. Four parts in a specific order, the three distortions that ruin it, and the four rules that keep A/B tests honest.
Personalisation that doesn't feel creepy
There's a line between personalisation that earns trust and personalisation that breaks it. It's not where most people think it is — it's about how you signal what you know, not what you know. Here's the line, how programs cross it without noticing, and the patterns that keep you on the right side.
Brand voice in lifecycle: how to sound like you, not the generic SaaS CRM voice
Lifecycle emails — the automated sequences that go out on signup, after a purchase, when a cart is abandoned — drift toward a polished, generic SaaS voice because it's the default in every template library. Here's how to actually write in your brand's voice across an entire program.
The email copywriting pyramid: write for the 5-second reader first
Most recipients give an email five seconds before they engage or delete. The email has to land its point at that depth and still reward a longer read. The inverted pyramid — conclusion first, detail after — is how.
Push notification copy that actually gets tapped
Push is the highest-interrupt channel in the stack. A bad push burns goodwill in under a second; a good one feels like a useful nudge from a friend. This is the copy discipline — specific words, specific structures, specific anti-patterns that reliably get a user to turn your notifications off for good.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 63 lifecycle methodologies, 91 MCP tools, native Braze integration. Free for everyone.