You've written the subject line, checked the offer, and scheduled the campaign. Then, between meetings, you scan a crowded inbox and decide what survives the swipe. In Gmail, Apple Mail, Outlook, and other major clients, the gray line beside or beneath the subject may be the detail that earns the open, or the reason the message disappears.
Email preview text, also called a preheader, is more than leftover body copy. It's the second hook paired with your subject line. The subject creates interest, while the preview text gives the reader a concrete reason to continue. Used well, it can extend an offer, clarify the message, or add enough personality to make a sales email feel human.
What Email Preview Text Actually Does in the Inbox
Email preview text became a standard inbox element as webmail and mobile clients began showing the first lines of an email beside or below its subject. Gmail documents an inbox reading and preview pane, while Microsoft Outlook provides a “Show preview text” option, confirming that snippets are built into major email ecosystems. Google research on mobile email information preview also found that two or three lines offered a useful balance between context and screen space, as described in the Gmail inbox and preview documentation.
For a DTC campaign, treat the subject and preheader as a paired message with separate jobs:
- Extend the offer: If the subject says “Your weekend edit is here,” the preview can add the discount or shipping detail.
- Add specificity: Name the product, deadline, category, or customer benefit that the subject couldn't accommodate.
- Reduce sales friction: A direct promotional subject can feel less aggressive when the preview supplies proof, reassurance, or brand personality.
A weak preheader often reads like “Free shipping on orders over $50+” or “View this email in your browser.” Those lines may be accurate, but they frequently waste the most visible copy after the subject. The reader needs a reason to open, not a utility notice.
Practical rule: Write the subject to create the question, then use the preview text to answer why opening matters.
Testing supports treating this space as a conversion lever. In a MarketingExperiments test, one preheader variant generated a statistically significant 104% relative increase in clicks without a statistically significant change in opens, while another variant produced a statistically significant 12% relative decrease in clicks, according to the MarketingExperiments preheader test. The lesson is straightforward. Preview text can change downstream behavior, and bland or poorly matched copy can hurt.
For broader guidance on pairing both inbox elements, use email open rate improvement strategies as a practical reference. Your preheader isn't metadata to fill in at the last minute. It's a small piece of conversion copy.
How Different Email Clients Show Preview Text
The same preheader can look polished in one inbox and awkward in another. Display depends on the client, device width, subject-line length, font settings, and the surrounding interface. There isn't one universal character limit.
Published guidance places Apple Mail desktop around 140 characters, Gmail in a browser around 97 characters, Gmail mobile around 40 to 50 characters, and Outlook desktop around 35 characters, as summarized by Enchant Agency's email preview text guidance. Litmus recommends keeping preview text under 90 characters, because senders can't reliably control how much each inbox will reveal in its preview text support guide.
| Email Client | Visible Characters, Approx. | Rendering Notes |
|---|---|---|
| Apple Mail desktop | Around 140 | Can show a relatively long snippet, depending on layout and subject length |
| Gmail web | Around 97 | Subject length affects the remaining preview space |
| Gmail mobile | Around 40 to 50 | Tighter space makes early wording especially important |
| Outlook desktop | Around 35 | Often shows a short snippet, so late-stage details may disappear |
| Apple Mail mobile | Around 90 | Mobile width and the subject line determine the visible balance |
Outlook deserves special attention because rendering behavior can diverge from what your email service provider preview suggests. Some Outlook desktop environments pull the first body text rather than honoring a dedicated preheader field, so a Klaviyo or Mailchimp preview can break when the template begins with “View in browser,” navigation, or an accessibility notice. A hidden spacer or carefully structured preheader can prevent that leakage, but you should verify the actual inbox result.
The safest writing rule is to place the essential idea in the first 40 to 50 characters. A practical range for the full message is roughly 40 to 90 useful characters, consistent with Selzy's preview text recommendations. Put the product, benefit, or deadline first, then add supporting context for clients that show more.
If body copy leaks into the inbox or displays badly, use the troubleshooting steps in this guide to clipped email messages. Always test the subject and preheader as one visual unit, not as isolated fields.
Writing Preview Text That Earns the Open
A reliable preheader formula has three parts:
- Payoff or offer: Start with the immediate benefit.
- Concrete detail: Add the product, promotion, deadline, or customer context.
- Voice flourish: Use personality only after the message is clear.
The first part must survive mobile truncation. The third part is optional.
Welcome flow
Subject: Welcome to {{company}}
Preview: Your 15% off code lives here. Use it in the next 7 days.
The subject establishes the relationship. The preheader gives the subscriber a reason to open by identifying the incentive and its timing. It also answers the question a new subscriber is likely to have, namely, where the promised benefit is and how long it remains useful.
Cart abandonment
Subject: You left something behind
Preview: The linen trousers are still in your bag. Free shipping ends Sunday at midnight.
This version adds product specificity and urgency without copying the subject. The shopper already knows something was left behind. They don't yet know which product, what benefit is available, or when the incentive ends.
Win-back
Subject: It's been a minute
Preview: We saved 20% off just to see you back. Expires in 72 hours.
The tone is conversational, but the copy still delivers an offer and a deadline. That combination works better than vague lines such as “We miss you” because the reader can understand the value before opening.
Two anti-patterns appear often in lifecycle programs:
- Word-for-word repetition: Repeating the subject wastes the second hook and can make the send look automated.
- Generic brand language: “Discover something special inside” could belong to almost any store, so it gives the reader little information.
Keep the copy concise. Email subject line best practices for ecommerce support the same operating principle, the preview should add useful detail rather than restate the headline. Aim for roughly 40 to 90 characters, depending on how much room the subject consumes.
What the Testing Data Actually Shows
Preview text testing produces uneven results, which is exactly why teams should test it rather than assume every preheader helps. A structured preheader improved open rate in one experiment, while a specifically crafted version reduced open rate in another. One MarketingExperiments treatment generated a 104% relative click increase, while a different treatment recorded a 12% relative click decrease, with the subject line held constant in the study cited earlier.
Additional benchmark data reported by Stripo found that emails with custom preheader text averaged a 22.3% open rate versus 19.3% without it, and 3.3% click-through versus 2.2% without it, as detailed in Stripo's email preheader analysis. These results show why opens alone aren't enough. A preheader can attract attention without creating useful traffic, or it can improve clicks without producing a visible open-rate change.
| Flow Type | Control Preview | Variant Preview | Sample Size | Click Rate Lift |
|---|---|---|---|---|
| Controlled email test | Existing preheader | Benefit-led preheader | Not provided | 104% relative increase in one treatment |
| Controlled email test | Existing preheader | Alternative preheader | Not provided | 12% relative decrease in another treatment |
| Benchmark comparison | No custom preheader | Custom preheader | Not provided | 1.1-point click-through difference |
The practical takeaway is to judge the preheader by the action it is supposed to support. A welcome email may need clarity about the incentive. A cart email may need product recognition and reassurance. A promotion may need urgency, but urgency without substance can create a bait-and-switch feeling.
Preview text also isn't a deliverability lever. Inbox placement depends on authentication and sender reputation, not the preheader itself. Still, misleading copy can reduce engagement or contribute to complaints after the message is seen, as explained in MailBlaze's guide to preview text.
Teams that need a cleaner way to track email campaign results should connect preheader tests to clicks and conversions, not just opens. For context on interpreting open-rate benchmarks, see typical email marketing open rates.
Setting Up Preview Text in Klaviyo, Mailchimp, and Omnisend
The writing only matters if the platform sends the intended text. Check the field name, confirm the fallback behavior, and send a test to real inboxes.
Klaviyo
Open the email template or campaign editor and locate the Preview Text field in the email template settings. Enter the preheader separately from the subject line, then inspect the rendered inbox preview.
Klaviyo templates can also use hidden preheader code when the first body element would otherwise leak into the inbox. A common implementation uses a zero-width space followed by a styled HTML comment or other spacer content to push unwanted body copy beyond the visible preview. The objective is to keep utility text from replacing your deliberate message, not to create an artificially long sentence.
Mailchimp
In the campaign builder, use the field labeled Preview Text. If you leave it blank, Mailchimp can pull from the template default or from the first available body copy, depending on the template setup. Review the template's default value before sending, especially if it includes navigation or browser-view language.
Omnisend
Configure the field under the campaign step labeled Subject and Preview Text. If the email uses dynamic content, add conditional fallback tags so a missing product name, discount, or customer attribute doesn't leave an incomplete sentence in the inbox.
Klaviyo, Mailchimp, and Omnisend all require the same quality-control habit: preview the actual message after personalization resolves. A field can be correctly populated while the final output still truncates awkwardly or exposes fallback content.
Preview Text Examples for Common Ecommerce Flows
The quickest way to improve a preheader is to compare a redundant version with a complementary one. The examples below use common DTC scenarios across skincare, apparel, and home goods. They're editorial examples, not performance claims.
Welcome email
- Subject: Welcome to Glow Theory
- Weak preview: Welcome to Glow Theory
- Stronger preview: Your routine starts with a welcome gift inside
The stronger line introduces a benefit without repeating the brand name. If the gift has a firm deadline, place that detail early.
Browse abandonment
- Subject: Still thinking about it?
- Weak preview: Still thinking about it?
- Stronger preview: The serum you viewed is back in stock
This version connects the message to the shopper's behavior and gives a reason to return. Don't claim scarcity unless the inventory condition is real.
Cart abandonment
- Subject: Your cart is waiting
- Weak preview: Your cart is waiting
- Stronger preview: Your cotton set is saved and ready when you are
The product reference makes the reminder recognizable in a crowded inbox. A shipping or discount detail can follow if it applies.
The same principle works after purchase, but the emotional job changes:
- Subject: Your order is on its way
- Weak preview: Your order is on its way
- Stronger preview: Track your parcel and see what to expect next
For a win-back email:
- Subject: Ready for a fresh start?
- Weak preview: Ready for a fresh start?
- Stronger preview: A returning-customer offer is waiting inside
For a home-goods launch:
- Subject: The new collection has landed
- Weak preview: The new collection has landed
- Stronger preview: Textured linens and warm neutrals for the new season
A preheader shouldn't force intrigue into every send. In one reminder-style treatment, leaving the preheader empty outperformed both a repeated subject and a crafted alternative. That result aligns with Litmus guidance that shorter or even absent preview text can sometimes help an email stand out. Test the blank version when the subject already carries the complete message.
The visual comparison matters as much as the wording. See how the subject and preheader behave together in the accompanying video.
A Simple A/B Testing Framework for Preview Text
Start with one variable. If the subject, sender name, offer, and preheader all change at once, you won't know what caused the result. For a preheader test, keep the subject line, sender name, creative, audience, timing, and offer fixed.
Use a single audience segment with at least 5,000 contacts, then allow the test to run through the planned decision window of 48 to 72 hours. Those thresholds come from the testing framework specified here, not from a universal rule. Your own send volume and audience behavior may require a different design.
The operating sequence
- Choose the hypothesis. For example, “A product-specific preheader will produce more clicks than a generic benefit line.”
- Create two versions. Keep the subject identical and change only the preview text.
- Measure the primary action. Use click rate as the main decision metric because open tracking is less reliable across privacy-protected inboxes.
- Record the result. Add the audience, send date, exact copy, click rate, conversion outcome, and decision to a shared testing log.
Don't call a winner early because one version has a higher open rate. Look for a meaningful difference in clicks and downstream behavior, then document whether the result supports, rejects, or refines the hypothesis.
| Metric | Threshold | Decision |
|---|---|---|
| Variable control | One changed element | Continue only if subject and campaign conditions remain fixed |
| Audience | At least 5,000 contacts | Use a segment large enough for the planned test |
| Test window | 48 to 72 hours | Review after the decision window, unless a business deadline requires earlier action |
| Primary KPI | Click rate | Choose the version that produces stronger meaningful engagement |
| Documentation | Complete testing log entry | Reuse the insight in future subject and preview pairings |
For a founder-friendly overview of experiment design, this founder's guide to A/B testing offers useful context. The central discipline remains simple: hold the subject fixed when testing the preheader, or attribution becomes guesswork.
The Pre-Send Checklist and When to Skip Preview Text
Before every send, check the actual inbox presentation rather than trusting the editor preview alone.
- Inbox preview: Render the message in Litmus or Email on Acid.
- Mobile rendering: Review iOS Mail and the Gmail app, where truncation can change the second hook.
- Character count: Confirm that the key phrase survives the 90-character practical ceiling recommended by Litmus.
- Subject relationship: Make sure the preheader adds a reason to open instead of repeating the subject.
- Fallback content: Check for “View in browser,” navigation labels, unsubscribe text, and failed personalization.
- Client variation: For a major send, review Gmail, Apple Mail, and Outlook. Their inbox layouts and truncation can expose different problems.
Leaving preview text blank can be the better choice. A transactional shipping confirmation may already state the order update in its subject, leaving no useful work for a second hook. Reminder emails can also benefit from whitespace, keeping attention on the sender name and subject rather than adding another crowded line.
Test the blank version when the subject already carries the event and action. Repeat the subject only when the inbox or client is likely to hide the preheader and repetition preserves clarity. Otherwise, write the missing context or benefit into the preview text, then inspect how the pair appears on mobile.
Save the final version, client screenshots, and result in the testing log so future sends benefit from the same discipline.
Ecommerce Boost helps online retailers plan and optimize lifecycle campaigns across welcome, browse, cart, post-purchase, and win-back flows, with testing and reporting tied to customer actions. Visit Ecommerce Boost to review its email marketing services and explore how stronger subject and preview pairings can support retention and revenue.
