Email Preheaders in 2026: How to Write Preview Text That Boosts Open Rates (With Examples)

Complete 2026 guide to email preheaders: what they are, why they lift open rates 5 to 30 percent, optimal length by client (Gmail, Apple Mail, Outlook, Yahoo), technical HTML implementation, 12 good-vs-bad examples, and 10 rules for preview text that converts.
Alaa
By Alaa
SMTPedia documents email infrastructure end to end: SMTP standards from the RFC archive, delivera...
13 min read Updated Aug 11, 2026 49 views

The preheader is the second-most-read line of your email. It sits right below or beside the subject line in every modern inbox, previewing what the message is about before the reader opens it. On mobile, where 65 to 75 percent of email is now read, the preheader is often the last line of copy that decides whether the message gets opened or swiped to trash.

And yet most senders still leave it empty, letting the inbox auto-generate a preview from the first line of the message (usually “View this email in your browser” or “Trouble reading? Click here”). This guide covers what preheaders actually are, how they render across every major client in 2026, the length limits that matter, the technical HTML for writing them correctly, and the patterns that consistently lift open rates.

2026 quick answer: A preheader (also called preview text or Johnson Box) is the short text shown next to or below the subject line in the inbox preview. Write between 40 and 90 characters, complement the subject rather than repeat it, and implement it with hidden HTML inside the message body so it renders reliably across Gmail, Apple Mail, Outlook, and Yahoo. A well-written preheader lifts open rates by 5 to 30 percent depending on the segment.

What Is an Email Preheader

A preheader is the short line of text an inbox displays as a preview of the message, positioned right after or below the subject line. In Gmail on desktop, it appears in grey text after the subject on the same line. On mobile, it appears as a second line under the subject. In Apple Mail on iOS, it appears as two lines below the sender name. Every modern inbox pulls preheader text from the first readable content in the message body.

If you do not set a preheader intentionally, the inbox pulls whatever appears first in your HTML. That is usually:

  • A “View in browser” link (“View this email in your browser”)
  • A fallback text (“Trouble seeing this message? Click here to view online”)
  • The first paragraph of the message, which may or may not sell the open

Intentional preheaders replace this with copy that actively supports the subject line and closes the open-decision loop.

Why Preheaders Matter for Open Rates

Open rates are decided in the inbox preview. The subject line gets 60 to 70 percent of the weight, the preheader gets the rest. Together they are the entire pitch. Skipping the preheader means running your campaign with 30 percent of your pre-open real estate blank.

A/B tests across industries consistently show 5 to 15 percent open rate lift when a well-written preheader is added to campaigns previously running with default fallbacks, and 20 to 30 percent lift when replacing a bad auto-generated preheader (like “Trouble viewing?”) with intentional copy.

Mobile is the reason. On desktop the subject line dominates because it is prominently displayed. On mobile, subject and preheader appear at nearly equal weight in the inbox list view. Since 65 to 75 percent of email is opened on mobile in 2026, the preheader is close to as important as the subject.

Optimal Preheader Length by Client

Different inboxes truncate preheaders at different lengths. Writing to the shortest common cutoff means your key message survives everywhere. Writing longer means the tail is only seen in generous clients (Outlook desktop, for example, shows the most).

ClientDisplayed charactersNotes
Gmail (mobile, iOS/Android)40-50 charactersSecond line under subject, cuts hard
Gmail (desktop)75-100 charactersSame line after subject, in grey
Apple Mail (iOS)90-140 charactersTwo lines below sender name, most generous mobile client
Apple Mail (macOS)110-140 charactersPreview pane shows more
Outlook (mobile)55-70 charactersOne line below subject
Outlook (desktop, list view)100-140 charactersLong preview in reading pane
Yahoo Mail (mobile)40-50 charactersSimilar to Gmail mobile
Yahoo Mail (desktop)90-110 charactersSame line after subject
The safe target: Put your key message in the first 40 characters. Extend to 90 characters total for the tail. Everything beyond 100 characters risks being truncated in most mobile clients.

Preheader vs Subject Line: How They Work Together

The subject and preheader are one pitch split into two lines. Treating them as two independent copy elements is the single most common mistake. The three patterns that work are:

1. Continuation. The preheader completes the subject like a second act. Subject: “3 pricing changes we studied this week.” Preheader: “Notion’s stealth tier, Vercel’s math, and Figma seat compression.” The preheader delivers on the promise before the click.
2. Reinforcement. The preheader adds urgency, context, or a specific detail that pushes the open. Subject: “20% off through Sunday.” Preheader: “Ends Sunday 11:59 PM PT. Code applied automatically at checkout.” Concrete details raise perceived legitimacy and close the loop.
3. Curiosity plus payoff. The subject opens a loop, the preheader hints at the payoff without giving it away. Subject: “We changed a lot since you last checked in.” Preheader: “New editor, faster sync, and a lower plan. Worth another look?” This works especially well for re-engagement.
What does not work: repetition. If the subject is “20% off through Sunday” and the preheader is “Get 20% off through Sunday,” you have wasted the second line. The reader learns nothing new. Every preheader should add information the subject does not.

Good vs Bad Preheader Examples

Twelve real subject-plus-preheader pairs, side by side.

Subject: Your weekly digest
Preheader: View this email in your browser

Subject: Your weekly digest, 5 minute read
Preheader: AI in finance, the new EU rules, and 3 charts on payroll growth

Subject: Special offer inside
Preheader: Trouble seeing? Click here to view online

Subject: 25% off the annual plan through Friday
Preheader: Applies to new and renewing members, code auto-applied

Subject: Cart reminder
Preheader: You forgot your items!!

Subject: You left the Elm chair in your bag
Preheader: 12 remaining from this run, we hold items for 48 hours

Subject: Newsletter #47
Preheader: Read the latest from our team

Subject: How Ramp cut trial-to-paid time in half
Preheader: Plus Notion’s onboarding rebuild and Vercel’s activation email teardown

Subject: Welcome to our platform
Preheader: We are excited to have you on board!

Subject: Getting started with Linear (3 things first)
Preheader: Create a project, invite one teammate, connect Slack. About 20 minutes.

Subject: Product update
Preheader: See what is new

Subject: Faster sync, better mobile, and the pricing you asked for
Preheader: Sync 3x faster, iOS redesign, and Starter plan at $12/month

Technical Implementation: How to Add a Preheader

The preheader is not a header field like Subject or From. It is content inside the message body that inboxes read as preview. Add it as hidden text at the very top of the HTML body, before your visible content.

The standard hidden preheader pattern

Hidden preheader HTML
<body> <div style=”display:none;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;max-width:0px;opacity:0;overflow:hidden;” aria-hidden=”true”> Ends Sunday 11:59 PM PT. Code applied automatically at checkout. </div> <!– rest of your email starts here –> </body>

The CSS combination hides the div visually while keeping the text readable to inbox scanners. Every major client (Gmail, Apple Mail, Outlook, Yahoo) reads this as the preheader.

The trailing whitespace trick

Some clients (older Outlook, corporate mail systems) also append visible content from your message body to the preheader if the hidden div is too short. To prevent “View in browser” or other footer content from leaking into the preview after your intentional preheader, append zero-width joiner characters (invisible) to fill remaining preview space.

Preheader with trailing whitespace
<div style=”display:none;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;max-width:0px;opacity:0;overflow:hidden;” aria-hidden=”true”> Ends Sunday 11:59 PM PT. Code applied automatically at checkout. &zwnj;&nbsp;&zwnj;&nbsp;&zwnj;&nbsp;&zwnj;&nbsp;&zwnj;&nbsp;&zwnj;&nbsp;&zwnj;&nbsp;&zwnj;&nbsp;&zwnj;&nbsp;&zwnj;&nbsp; </div>

Repeat the zero-width joiner (&zwnj;) and non-breaking space (&nbsp;) pattern 10 to 15 times to fill roughly 100 characters of preview space. This forces the inbox to stop pulling preview from further down.

Setting preheaders in ESPs

Every serious ESP (Mailchimp, HubSpot, Klaviyo, Braze, SendGrid Marketing, ActiveCampaign, Beehiiv, Substack, Kit) has a dedicated preheader field in the campaign editor. Use it, and the ESP handles the hidden HTML for you. Manual HTML is only needed if you send from a custom system or your ESP has no field.

Testing Preheaders Before Send

Preheaders render differently across inboxes. Testing before send is the only way to know how your target audience sees it.

Litmus or Email on Acid

Paid tools that render your message across 90+ inbox environments (Gmail, Outlook 2010-2024, Apple Mail iOS/macOS, Yahoo, corporate clients). Shows exact subject and preheader display per client. Essential for bulk senders.

Send a test to yourself across accounts

Free method: send the actual campaign to Gmail, Outlook.com, Yahoo, and iCloud accounts you own. Check each inbox on mobile and desktop. Screenshot the preview. This catches obvious problems that renderers miss.

Preheader length simulator

Tools like PutsMail and free previews in Mailchimp/HubSpot show approximate mobile and desktop truncation before you send. Useful for iterating on length.

Dark mode check

Preheader text in white color (#ffffff) can become visible in dark mode if the client inverts the background. Test with dark mode on to catch this. Use color:transparent if you see leakage.

Common Preheader Mistakes

1. Leaving it blank. The most common mistake by far. When empty, the inbox pulls whatever appears first in your HTML, usually “View in browser” or a fallback text. That is your preheader, whether you set it or not.
2. Repeating the subject verbatim. Two identical lines waste half of your inbox real estate and signal a rushed send. Always make the preheader add information the subject does not.
3. Writing 200+ characters. Only the first 40 to 90 characters are seen by most recipients. Beyond that, the tail is invisible except in generous desktop clients. Write for mobile length.
4. Stacking emoji or symbols. Multiple emoji or repeated symbols look manipulative and can trigger spam filters. One tasteful emoji is fine, three or more is a signal.
5. Using ALL CAPS or excessive punctuation. Same rules as subject lines: sentence case, at most one exclamation mark, no ??? or !!!. Preheaders are scored by spam filters just like subject lines.
6. Ignoring dark mode. A white-colored hidden preheader can become visible in dark mode. Use display:none plus color:transparent as belt-and-suspenders. Test with dark mode on.

10 Rules for Writing Preheaders That Convert

1. Never leave it blank. Set the preheader on every campaign. “View in browser” as your preheader is a red flag.
2. Put the key message in the first 40 characters. Mobile clients truncate hard. The first 40 are seen everywhere.
3. Extend to 90 characters for the tail. Adds context for readers in more generous clients without hiding what matters.
4. Add information the subject does not. If it repeats, you have wasted the line.
5. Use sentence case. Same as subject lines. Filters and users trust it more.
6. Add concrete detail. Prices, dates, product names, numbers. Specificity raises perceived legitimacy and click intent.
7. Cap emoji at one, at most. Only if it clarifies (a small green check next to a shipping confirmation, for example). Not decorative.
8. Test on mobile. Send yourself the test, open on your phone, look at the inbox list view before opening. That is what your recipient sees.
9. A/B test length and pattern. On lists over 5,000 subscribers, split-test 40-char continuation vs 90-char reinforcement vs curiosity-plus-payoff. Winner over 4 to 8 campaigns wins the pattern.
10. Implement hidden HTML with trailing whitespace. Prevents fallback content from leaking into the preview when the preheader is short.

Frequently Asked Questions

What if my ESP does not have a preheader field?

Add the hidden HTML manually at the very top of the message body, right after the opening <body> tag. Every major ESP renders it correctly even without a dedicated field.

Do preheaders affect spam scores?

Yes. Preheaders are scanned by spam filters just like subject lines. Trigger words (FREE, ACT NOW, cash), all-caps text, emoji stacks, and excessive punctuation all count against you in the preheader as much as in the subject.

Should I use emoji in preheaders?

One tasteful emoji at most, ideally at the end. Stacking multiple emoji looks promotional and can trigger content filters. Emoji do render inconsistently across older Outlook and some corporate clients, so never rely on them for meaning.

What is the difference between preheader, preview text, and Johnson Box?

All three terms describe the same thing. “Preheader” and “preview text” are the modern names. “Johnson Box” is a legacy direct-mail term (from Frank Johnson, who popularized the boxed teaser at the top of sales letters in the 1950s). Same concept applied to email.

Are preheaders visible when the email is opened?

No. When implemented with hidden HTML (display:none), the preheader is only visible in the inbox preview, not once the message is opened. That is intentional: the preheader sells the open, then disappears so the actual email design can take over.

Can I use personalization tokens in the preheader?

Yes, and it often lifts open rates. “Hey [First name], here is your weekly summary” works well. Test that tokens render (unrendered tokens like {FIRST_NAME} in a preview are the worst possible signal). Some ESPs have separate token syntax for preheader fields.

Do preheaders work in plain-text emails?

No, plain-text messages have no HTML to hide, so no preheader mechanism. The inbox pulls the first line of visible text as the preview. Make the first line of your plain-text version work as the preheader.

What is a good preheader length for cold outreach and B2B?

Shorter than for consumer marketing. 30 to 60 characters. Cold outreach preheaders should feel like a natural continuation of the subject and avoid any promotional register. “Following up on your team’s Q4 plans” reads as human. “Get 50% more meetings booked” reads as a pitch.

Does the preheader affect my Sender Score or deliverability?

Indirectly. Preheaders influence open rates, which influence engagement metrics, which feed into sender reputation over time. High-performing preheaders that lift opens improve reputation. Preheaders written like spam (all caps, urgency, triggers) can push you toward the spam folder.

Do preheaders work in Gmail Promotions tab?

Yes, Gmail Promotions and other category tabs still show preheaders in the preview. The tab affects folder placement, not preview rendering. If anything, a well-written preheader helps a Promotions message stand out from surrounding sends.

Are there character limits enforced by ESPs on the preheader field?

Most ESPs allow up to 150 to 200 characters in the preheader field, well beyond what any client displays. The limit is soft. Write for the display limit (90 to 100 characters), not the field limit.

Updated for the 2026 inbox landscape (mobile-dominant, dark-mode default in many clients). Preheader rendering patterns evolve, revisit annually and always test on mobile before send.


About the Author

Alaa - SMTPedia author

Alaa · LinkedIn

Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.


About SMTPedia

SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.

We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.