Skip to content
Part of: How-to format
How-To

How to Bold Email Subject Lines (Unicode That Renders)

There is no native way to bold an email subject line in Gmail, Outlook, Apple Mail or anywhere else — the subject is a plain-text header field by the email standard itself, so no client offers a bold button. The only workaround is to paste pre-styled Unicode characters (mathematical bold letters) that already look bold. They render in major modern inboxes but can show as empty 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 before rolling out.

Shreyas Bagal·Jun 24, 2026·8 min

There is no native way to bold an email subject line in Gmail, Outlook, Apple Mail or anywhere else — the subject is a plain-text header field by the email standard itself, so no client offers a bold button. The only workaround is to paste pre-styled Unicode characters (mathematical bold letters) that already look bold. They render in major modern inboxes but can show as empty 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 before rolling out.

Key takeaways

  • No email client can bold a subject line natively — the subject is a plain-text header field by the email standard, so Gmail, Outlook and Apple Mail all lack a formatting button. Markdown asterisks or HTML <b> tags do nothing; they'd just show as literal characters.
  • The only workaround is pasting pre-styled Unicode characters (the Mathematical Bold alphabet). They already look bold, so they survive as literal characters in a plain-text subject and display in the inbox list.
  • Rendering is real but not universal: styled subjects show correctly in modern Gmail, Apple Mail and New Outlook, but can appear as empty boxes (□) in some older or locked-down clients that lack the glyph — older desktop Outlook builds have known issues displaying modern Unicode content.
  • There are real downsides — unusual Unicode in a subject can look spammy to filters and is sometimes flagged as a deliverability risk, inbox search for the plain word won't match the styled text, and screen readers handle these letters inconsistently (some read each one by its Unicode name, others map them back to plain letters).
  • Use it sparingly: at most one styled element per subject, keep the literal message readable, keep handles and links plain, and A/B test a small segment to confirm both rendering and open-rate impact before a full send.
How to Bold Email Subject Lines (Unicode That Renders)
On this page

How-to guide

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.

Why there's no "bold" button for a subject line

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:

  1. Open BoldlyType's free bold text generator and type the word or phrase you want bolded.
  2. Copy the styled output (for example, 𝗦𝗮𝗹𝗲).
  3. 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.

Ready to put this into practice?

Open a formatter

Sources

Spotted an error? Email hello@boldlytype.com — we update guides quarterly and welcome corrections.

Frequently asked questions

Latest questions readers ask us about this topic.

How do I bold an email subject line?

There's no bold button for a subject line in any email client, because the subject is a plain-text header field defined by the email standard — Gmail, Outlook and Apple Mail all lack one. The only way to make a subject look bold is to paste characters that are already bold: the Unicode Mathematical Bold alphabet. You type your subject into a tool like BoldlyType's bold text generator, copy the styled output (for example 𝗦𝗮𝗹𝗲), and paste it into the subject field of your email or sending platform. The boldness is baked into each character, so it survives the plain-text header and shows in the inbox list. Your sending platform handles the technical encoding automatically — you just paste. Use it on one word at most, and test before a big send.

Does the Unicode bold subject line trick actually work in all email clients?

It works in major modern clients but not everywhere. Because Unicode bold letters are real characters rather than formatting instructions, they paste into the subject and render in inboxes like Gmail, Apple Mail and New Outlook. But older or locked-down clients can show an empty box (tofu, □) for a character they can't map, and older desktop Outlook builds in particular have documented trouble displaying modern Unicode content. Uncommon or ornate glyphs are the riskiest. So treat 'renders' as true for most modern recipients but never guaranteed for all of them. Always send yourself a test across the clients your audience actually uses before relying on it for a campaign, and keep a readable fallback in mind.

Why does my Unicode subject line show as boxes or question marks?

Those empty boxes are called tofu (□). They appear when the recipient's email client, device or font doesn't have a glyph for the specific Unicode character you used, so it can't draw the letter and shows a placeholder instead. It's most common in older or legacy clients, locked-down corporate environments, and with ornate styles like script. Common sans-serif Unicode bold is the most widely supported, while decorative sets break most often. There's nothing you can fix in the character itself — it's a support gap on the receiving end. The safe move is to test across the clients your audience uses, prefer the plainest bold style, and never put load-bearing words only in styled characters. See our guide on why fancy text shows as boxes for the full explanation.

Is using Unicode in subject lines free and safe?

Generating the characters is free and safe — BoldlyType's bold text generator is free, needs no signup, and runs entirely in your browser, so nothing you type is uploaded or stored. The output is plain Unicode text you copy and paste, not a download. 'Safe' for deliverability, though, is a separate question. Unusual Unicode in a subject can look spammy to filters and is sometimes flagged as a deliverability risk by email-marketing guidance, and characters that don't render can hurt how recipients perceive the message. So the tool is safe; the tactic carries some deliverability risk that you should test for. Use one styled element at most, keep the rest of the subject normal, avoid using it on every send, and A/B test a small segment to confirm both inbox placement and open-rate impact before rolling it out widely.

Do Unicode bold subject lines increase open rates?

There's no reliable data that they do — treat it as untested. The open-rate research people cite is about emojis and symbols in subject lines, not Unicode bold letters, and those are a different mechanism. Even that emoji/symbol data is mixed and dated: an older Experian study found a majority of brands saw higher opens with a symbol, but the lift varied wildly by symbol and the study is years old. None of it measured Mathematical Bold letters specifically. The actual words of your subject, your sender reputation and your segment matter far more than decoration, and overusing styled characters can flag you as spam, which cuts opens. So run an A/B test on a small slice of your list, compare opens and deliverability against a plain control, and only scale the styled version if it genuinely wins for your audience.

Can I just use markdown or HTML to bold the subject instead?

No. Markdown like **bold** and HTML tags like <b>bold</b> do nothing in a subject line. The subject is a plain-text header field by the email specification, so there's no renderer to interpret that markup — recipients would simply see the literal asterisks or angle-bracket tags, or the tags would be stripped. This is different from the email body, where HTML formatting works normally. The header has no styling layer at all, which is exactly why the only option is characters that already look bold. That's what Unicode Mathematical Bold letters are: distinct codepoints that display as bold without any formatting instruction. Paste those into the subject and they survive; paste markdown or HTML and you get junk. The body is where real formatting lives; the subject only takes literal characters.

The sub-questions readers ask next — answered, with where to go.

LinkedIn's post box — used for feed posts, comments, your headline and your About section — is plain text with no formatting toolbar and no markdown, so there's no bold button. The workaround the whole creator economy uses is Unicode bold: type your line, convert it to bold Unicode characters (𝗯𝗼𝗹𝗱) in a generator, then paste it back and the emphasis sticks, because the style is baked into the characters themselves. Bold only the hook — the part that shows before the “…see more” cut-off — to earn the click, and keep the rest plain so the post stays skimmable. Two caveats matter: Unicode text isn't read by LinkedIn's search and is announced poorly by screen readers, so never bold the keywords, names or hashtags you want found or read aloud. For true rich text (headings, lists), use LinkedIn's separate 'Write article' editor instead.

Format a LinkedIn post

Instagram's native composer collapses the line breaks you type, which is why captions paste in as one dense block — it's worst when you post from the web or through some schedulers. The reliable fix is to compose the caption with the spacing you want and paste it back with the breaks preserved, rather than relying on invisible-character hacks (blank Unicode characters can break Instagram's search and are read poorly by screen readers). Write the caption with your intended breaks, generate the spaced version, and paste it into the caption field. Put your strongest hook on line one, since that's the part that shows before the 'more' cut-off in the feed. Keep paragraphs short — two or three lines — so the caption stays skimmable on a phone, where almost everyone reads it.

Open the line-break tool

Yes — WhatsApp is the exception among messaging and social apps because it has its own built-in markup that it renders for everyone. Wrap text in *asterisks* for bold, _underscores_ for italic, ~tildes~ for strikethrough, and triple backticks for monospace; the symbols disappear and the styling shows. So you usually don't need Unicode characters on WhatsApp at all. Reach for a Unicode formatter only when you want a style WhatsApp's markdown doesn't cover — small caps or script for a Status, say — or when you're writing one message to post across several apps that don't share WhatsApp's syntax (Instagram, X and Threads strip these symbols and show them literally). For everyday bold and italic inside WhatsApp itself, the native markup is the better and more accessible choice.

Format for WhatsApp

Because that editor is plain text and strips anything it doesn't parse. Markdown (*bold*), HTML tags and rich-text styling only render where the platform explicitly supports them — paste them into Instagram, X/Twitter or a LinkedIn post and you see the raw asterisks, or nothing at all, because those boxes have no formatting engine. Unicode styling works differently: the bold or italic look is baked into each character (a Unicode bold 'A' is its own code point), so it survives any plain-text field and travels with a copy-paste. That's the whole reason Unicode 'fancy text' formatters exist. The trade-off is accessibility — because they aren't ordinary letters, screen readers can mis-read them and in-app search may not match them — so use Unicode for short emphasis, not for body copy or anything that must be searchable.

Generate paste-proof styles

Related in this series

See all in How-to format

Explore the topic cluster

More tools and guides across this topic cluster.

Get the next post.

Craft notes on writing for the internet. One short email, every other week. No spam.

Keep reading