TL;DR No email client can bold a subject line — the subject is a plain-text header field by the email standard itself, so Gmail, Outlook and Apple Mail have no formatting button. The only way to make a subject look bold is to paste pre-styled Unicode characters (the Mathematical Bold alphabet) that already look bold. They render in major modern inboxes but can show as boxes (□) in some older or locked-down clients, may look unusual to spam filters, and are read inconsistently by screen readers. Use one styled element at most, keep the literal words readable, and A/B test a small segment first.
Here's the answer up front, because it surprises people: you cannot bold an email subject line natively in any email client. There's no toggle in Gmail, no button in Outlook, no menu item in Apple Mail. And this isn't a feature someone forgot to build — it's baked into how email works. The subject is part of the message header, and by the email specification header fields are plain text. There is no bold, italic, color or font control for a subject line anywhere, in any mainstream client.
So when you see a "bold" subject line standing out in your own inbox, it isn't formatting. It's a different trick entirely: characters that are already bold. This post explains why native formatting is impossible here, shows you the one workaround that actually renders, gives you copy-paste examples, and is honest about where it breaks — because in email, a broken subject line can cost you the open or hurt how the message reads.
In most "how to format text on X" guides, the question is which field takes native formatting and which needs a workaround. For email subject lines, that breakdown is unusually simple: nothing native exists.
The subject line is a header field, like From: and Date:. The email standard (RFC 5322) treats header fields as plain text. There is no styling layer for headers — no place for "make this bold" to live. That's why:
- No client offers a button. Gmail (web and app), Outlook (desktop and web), Apple Mail, Yahoo — none of them have a way to bold, italicize or color a subject. This comes up constantly in mail-client help forums, and the only workaround anyone offers is Unicode characters.
- Markdown doesn't work. Typing
**Sale** in the subject won't bold anything. There's no renderer reading the header, so recipients just see the literal asterisks: **Sale**.
- HTML doesn't work either.
<b>Sale</b> in a subject shows the literal tags or gets stripped. HTML formatting works in the email body — the subject has no such layer.
This is the opposite of the email body, where you have a full formatting toolbar. The body is rich; the subject is raw text. So if you want a subject that looks styled, you have exactly one option.
The only workaround: paste pre-styled Unicode characters
The fix is the same one that lets people put "bold" text in an Instagram bio or a LinkedIn post that have no formatting either: use characters that are already styled.
Unicode — the universal character standard — includes a block called Mathematical Alphanumeric Symbols. It contains entire alphabets that already look bold, italic, script and more: a bold A through Z, bold a through z, and bold digits, each as its own distinct character. Because the boldness is part of the character itself (not a formatting instruction), these letters survive in a plain-text subject and display in the inbox list. Nothing has to be "rendered" — the character is bold.
Here's the same word in a few Unicode styles you can copy straight from this page:
- Bold: 𝗦𝗮𝗹𝗲
- Italic: 𝘚𝘢𝘭𝘦
- Bold serif: 𝐒𝐚𝐥𝐞
- Small caps: sᴀʟᴇ
Paste any of those into a subject field and it stays styled. A few realistic examples:
𝗙𝗶𝗻𝗮𝗹 𝗵𝗼𝘂𝗿𝘀: 40% off ends tonight
Your 𝗶𝗻𝘃𝗼𝗶𝗰𝗲 is ready
𝗪𝗲𝗹𝗰𝗼𝗺𝗲 — here's your first step
Notice in each one, only a word or two is styled. That's deliberate, and we'll get to why in the deliverability section.
You don't need to do any technical encoding. Behind the scenes, non-ASCII characters in a subject are transported using a standard MIME "encoded-word" mechanism (the =?UTF-8?B?…?= form, defined in RFC 2047). Your sending platform or mail client handles all of that automatically. You just paste the styled characters; the recipient's client decodes them back and displays them. Don't over-think the plumbing — copy, paste, send.
How to make a bold subject in seconds
The mechanics are generate → copy → paste:
- Open BoldlyType's free bold text generator and type the word or phrase you want bolded.
- Copy the styled output (for example, 𝗦𝗮𝗹𝗲).
- Paste it into the subject line of your email — or into the subject field of your email-marketing platform (Mailchimp, Klaviyo, HubSpot and the like all accept pasted Unicode).
That's it. The same styled text works whether you're sending a one-off personal email or a campaign to a list. There's no plugin, no setting, and nothing to configure on your end.
Where it renders — and where it breaks
Here's the honest part. "It renders" is true for most modern recipients, but it is not guaranteed for everyone, and you should treat the failure cases as real.
Where it generally works: modern Gmail (web and app), Apple Mail on current iOS and macOS, and New Outlook all display the Mathematical Bold letters correctly, because the fonts they ship with cover that Unicode range.
Where it can fail: older or locked-down clients can show an empty box — called tofu (□) — wherever the recipient's font has no glyph for the character. Older desktop Outlook builds on Windows in particular have documented trouble displaying modern Unicode content, and tightly controlled corporate mail setups sometimes strip or mangle unusual characters. Ornate styles (script, gothic) break more often than plain sans-serif bold, because fewer fonts include them.
There's nothing you can fix in the character itself — tofu is a support gap on the receiving end, not a mistake in your subject. The practical rules that follow from that:
- Never put a load-bearing word only in styled characters. If "𝗙𝗿𝗲𝗲" boxes out, the recipient should still understand the subject from the rest of the line.
- Prefer the plainest bold style (sans-serif Mathematical Bold) over decorative sets — it has the widest font coverage.
- Send yourself a test across the clients your audience actually uses before any real send. This is the single most reliable check, and it takes two minutes.
If you want the full mechanics of why characters box out, see our guide on why fancy text shows as boxes.
The deliverability catch
Beyond rendering, there's a separate risk worth naming plainly: unusual Unicode in a subject can look spammy to filters. This is widely repeated in email-marketing guidance as a reason to be cautious, and it's plausible — spam filters do weigh unusual character patterns — but it's a risk to test for, not a proven, fixed penalty. There is no public study quantifying a deliverability hit specifically from Mathematical Bold subject lines.
So treat it the way you'd treat any subject-line experiment:
- Use it sparingly. One styled element per subject at most. A subject that's entirely styled characters looks far more like spam than a single bolded word.
- Don't use it on every send. Reserving it for the occasional message keeps it from becoming a pattern your recipients' filters learn to distrust.
- Watch your inbox placement, not just opens. If a styled subject quietly lands more of your mail in Promotions or Spam, that hidden cost can outweigh any visual bump.
The accessibility and search catch
Two more downsides that don't show up in your own inbox preview:
Screen readers handle these letters inconsistently. Many readers — and historically VoiceOver — announce each Mathematical Bold letter by its Unicode name ("mathematical bold capital S, mathematical bold small a…") instead of saying the word, which is unintelligible to a listener. Other readers, like newer versions of Android TalkBack, now map these styled ranges back to plain letters and read the word normally. The behavior depends on the reader, its version and the user's verbosity settings, so you can't rely on the word being announced correctly for everyone. If accessibility matters for your audience, this alone is a reason to keep the readable words plain. (See our deeper look at screen readers and fancy text.)
Search won't match it. Because 𝗦𝗮𝗹𝗲 is a different sequence of codepoints than "Sale," a recipient who searches their inbox for the plain word may not find your styled email. The same applies to filters and rules they've set up on the literal text.
Do styled subjects actually lift opens?
It's tempting to assume a bold-looking subject gets more opens. Be careful here: there's no reliable data that Unicode bold letters specifically lift open rates — treat the tactic as untested.
The open-rate figures that circulate online are about emojis and symbols in subject lines (a sun glyph, a heart, an umbrella), not Mathematical Bold letters — and those are a different mechanism, a decorative pictograph versus a styled letter. Even that emoji/symbol research is mixed and dated: an older Experian study found a majority of brands saw a higher open rate when they added a symbol, but the lift varied enormously from one symbol to the next, and the study is years old. None of it measured bold letters.
So don't import emoji open-rate stats as evidence for this tactic. The words of your subject, your sender reputation and your segmentation move opens far more than any character trick. If you want to know whether styled subjects help your list, the only honest answer is to test:
- Run an A/B test on a small slice of your list — styled subject versus a plain control.
- Compare opens and deliverability (inbox vs. spam), not opens alone.
- Only scale the styled version if it genuinely wins, and re-check it over time.
The bottom line
You can't bold an email subject line with any button, because the subject is a plain-text header by the email spec — markdown and HTML do nothing there. The one workaround that survives is pasting pre-styled Unicode Mathematical Bold characters, which already look bold and display in modern inboxes like Gmail, Apple Mail and New Outlook. But they can box out in older or locked-down clients, can look unusual to spam filters, break inbox search for the plain word, and are read inconsistently by screen readers. Use one styled element at most, keep the literal message readable on its own, keep links and handles plain, and A/B test a small segment — for both rendering and deliverability — before you send it to your whole list.