KoltrixEmoji and special characters in email subject lines
Emoji can lift attention or break a subject line. How they are encoded, where they render badly, what screen readers say and how to test before you send.
On this page(8 sections)
A rocket in a subject line, a checkmark in a receipt, a curly apostrophe in a customer's name. Tiny characters, and they behave differently in different inboxes. Sometimes they add a little warmth or clarity. Sometimes they show as an empty box, get read aloud as a string of words, or push the useful part of the subject off the screen.
This guide explains how special characters travel through email, where the trouble spots are, and how to decide when to use them. There is no rule that emoji are good or bad. There is a practical question: does this character help the reader in every place the subject will appear?
How a subject line carries more than plain letters
Email headers were designed for basic ASCII text. To carry anything else, such as an accented letter or an emoji, the sender wraps it in an encoded word. A subject like this:
Subject: =?UTF-8?B?8J+agCBZb3VyIHJlcG9ydCBpcyByZWFkeQ==?=
is a subject line that starts with a rocket and reads "Your report is ready". The UTF-8 says which character set is used, the B says the bytes are base64 encoded, and the rest is the text. A library or an email service creates this for you. You do not write it by hand.
Three consequences matter in practice:
- Length is counted in bytes once encoded. An emoji takes four bytes in UTF-8 and more when encoded. Long subject lines are split into several encoded words, and a badly made one can break in the middle of a character, which produces a garbled result.
- The sender must declare the character set. If your system does not encode the header, some receivers show question marks or odd symbols.
- The address is a different matter. Accents in a subject are normal. Accents or emoji in an email address need a separate, less widely supported extension. See Unicode in email addresses: SMTPUTF8 and IDN.
Where trouble shows up
Rendering
An emoji is a code point, and the picture comes from the font on the reader's device. The same message can look different, or break, depending on the system.
- Different designs. A grinning face on one platform looks friendlier or stranger than on another. Meaning can shift slightly, and a few emoji can look alarming on a device you did not test.
- Missing characters. Newer emoji, or those combined from several code points, such as skin-tone variants or family groups, may appear as a box or as separate symbols on older systems.
- Mixed line height and alignment. In some clients an emoji makes the line taller or shifts the text.
- Old or locked-down clients. Some corporate clients, command-line tools and older versions of software show plain monochrome shapes or nothing at all.
Screen readers
Assistive technology reads emoji by name. A subject line of "🚀 Launch day 🎉🎉🎉" may be spoken as "rocket, Launch day, party popper, party popper, party popper". One or two used sparingly can be fine. A row of them is tiring and can bury the message. This ties into the wider guidance in the accessibility checklist for plain and HTML email.
Space on small screens
Phones show only the first 30 to 45 characters of a subject in the list view, and the number changes by device and orientation. An emoji uses the space of one or two characters. If the only useful words come after a long run of symbols, many people will never see them. Put the meaning first.
Special punctuation and look-alike characters
Not all special characters are emoji.
- Curly quotes and long dashes are fine and render widely. Pasting them from a document is usually safe if the header is properly encoded.
- Characters from other alphabets are fine when the reader's language uses them. A subject in Japanese or Arabic needs the right encoding and a font on the device, and often benefits from testing on a real phone.
- Look-alike letters such as a Cyrillic "а" in place of a Latin "a" can be used to disguise a message. Spam and phishing filters pay attention to this, and so should you if text is ever pulled from user input. See lookalike domain phishing.
- Invisible characters, such as zero-width spaces used to pad a subject or preview text, can look like a trick to filters and make the subject behave oddly in search.
- Reserved characters in merge fields. If you insert a customer's name, it may contain quotes, accents, emoji or very long text. Test with awkward names.
Do emoji hurt deliverability?
There is no reliable evidence that one or two relevant emoji, on their own, send a message to spam. The concern is the pattern around them. Messages that look like bulk promotion tend to trigger caution: all caps, many exclamation marks, repeated symbols, urgent money claims. A subject full of emoji tends to travel with those habits. What decides placement is mostly authentication, sender reputation and what recipients do with your mail, not a single character. Spam filter myths covers this well.
Use common sense: an emoji that adds meaning is fine, and a string of decoration is a risk to readability first and to filtering second.
When emoji help and when they do not
They can help when:
- They carry a clear, shared meaning, such as a checkmark for "done" or a warning sign for something that needs attention.
- The audience is informal and your brand voice already uses them.
- They help one message stand out in a list of similar ones, like a weekly digest.
Think twice when:
- The message is serious. Payment failures, security alerts, legal notices and apologies read poorly with decoration. Support emails people read argues for plain words in moments like these.
- The audience is formal or older. A bank, a hospital or a law firm customer may find them out of place.
- The message is transactional. A receipt or password reset should look dependable. Trust matters more than attention.
- You need the subject to be searchable. Customers searching their mailbox for "invoice" will not find it if you replaced the word with a symbol.
A simple policy
- Words first, symbols second. The subject must make sense if every emoji disappears.
- At most one, near the start or end, never a row. Repeated emoji are tiring for everyone and unhelpful to screen readers.
- Use well-established emoji. Choose ones that have existed for years and render in common fonts. Avoid new releases and complex sequences.
- Do not replace words with symbols. "Your ✅ order" should say "Your order is confirmed".
- No emoji in transactional or sensitive messages, unless your brand deliberately and consistently uses them.
- Keep the first 35 characters meaningful. That is what a phone list shows.
- Strip or normalize user-supplied text that goes into the subject: remove control and zero-width characters, cap the length and check for unusual scripts.
How to test
Do this before you ship a template with special characters, and again when you change it.
- Look at the raw header. Send a test and view the original message. Check that the subject is encoded with the right character set and is not truncated mid-character.
- Open it in several places. At least Gmail and Apple Mail on a phone, Outlook on the desktop and a web client. Look at the list view, not just the opened message.
- Try an older device or an uncommon client if your audience includes one.
- Listen to it. Turn on VoiceOver or TalkBack and hear the subject read aloud.
- Try awkward data. A long name, a name with an apostrophe, an emoji in the name, a name in another script.
- Search for it. Search the test mailbox for the main word of the subject and confirm it appears.
- Automate what you can. A check for header encoding and maximum subject length belongs in your pipeline. See email tests in CI.
Preheaders and sender names
The same care applies next to the subject. The preheader (the preview text) and the sender name can also hold emoji or special characters, and they appear in the same crowded list. An emoji in the sender name is read aloud first and can look like impersonation to filters and to people. Keep the sender name plain and consistent so recipients recognize it.
Key takeaways
- Non-ASCII characters travel as encoded words, and your email library should create them. Check the raw header after a test send.
- Emoji look different on different devices, can show as empty boxes and are read aloud by name, so one is plenty.
- Put the real meaning in the first 35 characters and make the subject understandable without any symbols.
- Avoid decoration in serious or transactional messages, and never replace words people may search for.
- Test in several clients, with a screen reader and with awkward names before you send.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
