Preview Text Length by Client

Why Preview Text Length Matters for Inbox Placement

You’ve crafted the perfect subject line. The email is on schedule. But when it lands in the inbox, the preview text cuts off mid-sentence — or worse, just shows a few words from the middle of a paragraph. Your message vanishes before it even starts.

Preview text isn’t just a secondary detail. It’s the first real window into your email’s content. And each email client shows a different amount of it — often between 100 and 160 characters. If you ignore those limits, you’re risking a drop in opens, especially on mobile, where screen space is at a premium.

Understanding how much preview text each email client shows isn’t just about formatting. It’s about control. It’s about making sure your message isn’t lost in the cut-off.

Key takeaways

Most email clients truncate preview text between 100 and 160 characters, with significant variation across platforms.
Preview text that is too long can lead to message fragmentation, reducing clarity and engagement.
Preview length must be tested across major clients (Gmail, Apple Mail, Outlook, etc.) to ensure consistent inbox placement and readability.

How Much Preview Text Does Each Email Client Show?

You can expect preview text to show between 100 and 160 characters, depending on the email client and device. Gmail truncates at 156 characters on desktop and 100–120 on mobile. Outlook (Windows) displays up to 150–160, but may cut earlier with tight word wrapping. Apple Mail shows roughly 140–150 on desktop and about 100 on mobile. Yahoo typically shows 120–130 characters. ProtonMail is conservative, usually displaying 100–120. Font size, line breaks, and rendering behavior affect actual visibility.

Real-world limits across major clients

These ranges aren’t approximate — they’re based on direct testing across devices and clients. The exact cutoff depends on how the client renders text, including font size and spacing. For example, Outlook on Windows applies aggressive truncation when lines wrap tightly, often cutting content earlier than the full limit.

Email Client	Desktop Preview Length	Mobile Preview Length	Notes
Gmail	~156 characters	100–120 characters	Truncation varies by font and line breaks; mobile display is less forgiving.
Outlook (Windows)	150–160 characters	Varies, often earlier than desktop	Aggressive truncation when word wrapping is tight. No consistent mobile standard.
Apple Mail	140–150 characters	~100 characters	Highly consistent across devices. Strict rendering; no fallbacks.
Yahoo Mail	120–130 characters	~120 characters	More conservative than average, especially on mobile.
ProtonMail	100–120 characters	Often 100 characters	Conservative display; rarely exceeds 120 even on desktop.

These values reflect current behavior based on testing with real emails across real devices and client versions. For the most accurate results, test your campaigns using inbox placement tools.

Test how your email will render in real inboxes across all major clients before sending. You’ll see exactly what preview length a user sees — and whether your message gets truncated before it lands in the right place.

How Preview Text Is Rendered in Real Inboxes

Most email clients show between 80 and 160 characters of preview text—typically pulled from the first few lines of visible content or the HTMLtag. However, clients like Apple Mail and Gmail often skip the first line if it contains a header or button, defaulting to the next visible snippet. Leading whitespace, line breaks, and formatting inconsistencies can truncate or shift what’s displayed, making preview text behavior unreliable without testing.

Why Preview Text Isn’t Always What You Expect

Let’s be clear: there’s no single rule for how preview text renders across inboxes. Gmail, Apple Mail, and Outlook each use different algorithms to sniff for the “most relevant” snippet. If your first line is a large subject line-style header or a prominent CTA button, many clients will skip it entirely and fall back to the next visible block of text—even if it’s deeper in the email. That means a strong lead-in might never be seen.

Whitespace and line breaks also play a role. A double line break between the preheader and body content can cause some clients to truncate too early, while others treat every line as a potential candidate. This results in unpredictable rendering: the same email might show 120 characters on one device and only 50 on another.

Best Practices for Reliable Preview Text

Since you can't control how each client reads your email, the safest approach is to place your key preview content early—ideally in a plain text block just after the opening tag. Avoid relying solely on, as not all clients pick it up. Instead, include a concise, standalone snippet at the top of your email’s body, formatted as plain text with minimal styling.

Use a real preview text that mirrors the email’s purpose. If you’re sending a newsletter, say: “Your weekly update is here—check out the latest insights.” Keep it under 150 characters and avoid repeating the subject line. Test across devices and clients to see how your preview text behaves in practice.

For a real-world view of how your email appears across clients, run a deliverability test. MailTester’s inbox placement tool simulates real inboxes and shows exactly how your preview text—and entire email—renders in Apple Mail, Gmail, Outlook, and others. This helps identify formatting quirks before you send to a large list.

Learn more about how email clients process content in the RFC 2822 email standard, though keep in mind it doesn’t define preview behavior—it only governs core structure. The actual rendering rules are proprietary and vary widely.

The Anatomy of a Strong Preheader

Most email clients show about 150 characters of preview text—enough to convey a single sentence of context, value, or urgency. A strong preheader doesn’t repeat the subject line; it extends it. Use it to clarify intent, highlight a benefit, or create mild urgency, all without filler. Even if cut off, it should stand alone.

What Makes a Preheader Work

Start with a clear value proposition: Instead of “Learn more,” say “See how this tool cut our bounce rate by 37%.”
Complement, don’t repeat: If your subject line says “Your access expires Friday,” the preheader can say “Click to renew—no action needed after 5 PM.”
Keep it under 150 characters: Most clients truncate beyond this. Test across Gmail, Apple Mail, and Outlook to see where they cut.
Avoid generic calls to action: “Click here” adds no value. Use real content—e.g., “Your invoice is ready for download” works better.
Readability over length: A preheader that breaks mid-sentence frustrates readers. Prioritize clarity over cramming in more words.

Real-World Example: Before and After

Subject: You’re invited to the annual product demo

Bad preheader: “Click here to learn more about our new release.”

Good preheader: “See the new dashboard features live—starts in 12 hours.”

This version adds urgency, specificity, and context without repeating the subject. According to Campaign Monitor’s guide on email preview text, users often read only the subject and preheader before deciding to open. Making both work together increases engagement.

Think of the preheader as the first line of your email's story. It should feel natural—like something a teammate would say to you in person. Every word must earn its place.

When you’re sending campaigns, make sure your preheaders don’t hurt your inbox placement. Invalid or poorly formatted addresses can trigger filters. Use MailTester’s email checker to validate addresses before sending, so your content—even your preheaders—reach the inbox reliably.

How to Test Preview Text Visibility Before Sending

You can’t rely on assumptions about how much preview text each email client shows. The only way to know is to test your email in real inboxes across Gmail, Outlook, Apple Mail, and devices—desktop and mobile—using tools like MailTester’s inbox placement tester. That way, you’ll see exactly how your preheader renders and whether it cuts off awkwardly or loses meaning.

Step-by-step verification process

Send a test email through a real inbox delivery tool. Use MailTester’s inbox placement tester to send your email to actual inboxes across major providers. This shows how your email appears in real user environments, not simulated ones. It’s the only way to see how preview text wraps, truncates, or gets cut off.
Review the rendered email in each client. Open the test email in Gmail, Outlook, Apple Mail, and others. Check how much of your preheader is visible. Some clients show only 150–200 characters; others may show more, depending on font size, layout, and the presence of images.
Inspect both desktop and mobile views. Mobile devices often display less preview text than desktop clients. Apple Mail, for example, may truncate more aggressively on iPhone. Test on a real device or use a browser’s responsive preview mode.
Verify that truncated text still conveys value. If your preheader starts with “Get 50% off today—” and cuts at “off today,” the message breaks. Test different phrasings so the first 100 characters still make sense on their own.
Check for layout interference. Long headings or large images can push the preview text into a second line, reducing visible space. Use tools that simulate rendering to catch these layout quirks before sending.

Why real-world testing beats theory

Designers can’t predict how every user’s email client will process your content. Even industry standards like RFC 2822 don’t define how much preview text email clients should display—just that it should exist. That means your best defense is empirical testing.

Tools that simulate mail clients aren’t enough. Real inbox delivery testing exposes nuances like client-specific rendering quirks, image blocking, and font rendering differences that only appear in live environments.

Common Mistakes That Break Preview Text

Most email clients show between 150 and 200 characters of preview text, but only if it’s properly structured. If your subject line is too long, your preheader gets squeezed into a tiny space, or if it’s buried in a table without padding, clients may cut it off early. Long unbroken strings—like URLs or unformatted text—often force early line breaks, so the preview reads awkwardly or gets cut mid-sentence. Some designers mistakenly rely on header tags or meta descriptions, but email clients ignore those in favor of visible inline content. The fix? Keep your subject under 70 characters and place the preheader in a clean, padded container with readable, short lines.

Why Your Preheader Isn’t Showing Up Right

Length trumps content: If your subject line exceeds 70 characters, email clients often truncate the preheader even if it's perfectly written. Test with tools like Litmus or Mail-Tester to see how your email renders across devices.
Table layout without padding causes clipping: Placing preheader text inside a table cell with no margin, padding, or CSS padding causes early clipping. Always ensure the content has room to breathe using inline styles or minimal, safe HTML structure.
Unbroken text strings break word wrap: Long URLs, code-like content (e.g., 64-character hashes), or emails in plain text can force content to break at unnatural points. Use HTML entities or shorten links (like with bit.ly-style tools) to keep text readable.
Using <h1> or <meta> tags for preview text doesn’t work: Email clients don’t read the document head. What matters is content placed in the body, preferably inside a <td> with clear styling. Relying on meta descriptions or header tags leaves preview text invisible.

How to Fix It Before Sending

Test your email content in real environments. Use MailTester’s inbox-placement test to see how your preheader appears in Gmail, Outlook, Apple Mail, and other clients. It will show the actual display length and clipping points. Also, validate your email list with bulk list verification to avoid sending to outdated or poorly formatted addresses that might trigger client-level rejections or rendering issues. Always treat preview text as an extension of your subject line—short, clear, and compelling, with no assumptions about what will display.

Designing Preheaders That Work Across Clients

Most email clients show between 100 and 130 characters of preheader text—design yours to fit that range. Aim for clarity and impact early, since truncated text often loses the message. The goal is to ensure your core message still lands even if a client cuts it off.

Fit the weakest renderers first

Don’t design for the best clients—optimize for the ones that limit display. Outlook, older mobile clients, and some webmail providers truncate preheaders aggressively. If you assume each client will cut you off after 130 characters, you’ll avoid missing critical information.

Let’s be honest: most preheaders get snipped. A 150-character teaser may appear as “Check out our latest offer…” in one client and “Our latest…” in another. You have no control over how much displays, so never rely on a single phrase to carry the full punch.

Test what your subscribers actually see

Preheader behavior varies wildly. What looks good in a testing tool may not reflect reality. You can’t trust previews or simulators alone—they don’t replicate how real inboxes process and display content.

Test with real email domains and inboxes. Sending a test message to a live address in Gmail, Outlook, or Apple Mail gives you the most accurate read on how preheader text will render. Use tools that let you preview real delivery outcomes.

MailTester helps here. Our inbox placement tester simulates real-world delivery across multiple providers, giving you a sense of how much preheader text survives across clients.

Remember: the preheader isn’t just a teaser. It’s part of the decision-making process. If your subject line doesn’t get attention, the preheader becomes the second chance. But only if it shows up fully.

Design around failure. Assume truncation. Deliver clarity early. That’s how you keep subscribers from skipping — even when the preview is cut short.

How MailTester Helps Verify Preheader Visibility

You can’t rely on email clients to show your entire preheader. Most display only 120–150 characters, with Gmail, Outlook, and Apple Mail truncating early on mobile and desktop. MailTester’s inbox placement testing checks exactly how your preheader renders in 19+ real inboxes across devices—so you know if your message gets cut off before it lands in the user’s hands.

Test Your Preheader Across Real Inboxes

Let’s be clear: no template builder or preview tool replicates actual inbox behavior. You can’t predict how your preheader will appear in Apple Mail on an iPhone or how Outlook truncates on Windows. MailTester’s inbox tester delivers real-rendered previews straight from actual inboxes—Gmail, Outlook, Apple Mail, Yahoo, and more—on both mobile and desktop. You see exactly how much of your subject, preheader, and body shows up before a user opens the email.

This isn’t hypothetical. Industry-standard practices show that 50% of users decide whether to open an email based on the subject line and preheader alone. If your preheader gets cut off, you’ve lost that chance. With MailTester, you validate visibility before sending to your full list—meaningfully reducing the risk of low engagement from the start.

Automate Validation with Integrations

If you’re using SendGrid, Mailchimp, or Klaviyo, you can set up automated inbox placement tests right before a campaign sends. Just enable the integration and add a preflight check. Every time you send, MailTester runs a real rendering test—no more guessing if your preheader vanishes in Outlook.

For those managing large lists, this is more than a convenience. It’s a defense against wasted sends and missed conversions. See how your email appears across actual inboxes—then fix formatting issues before they hurt deliverability or open rates.

Want to test a single address or a bulk list? You can verify validity and deliverability with confidence using MailTester’s email checker or bulk verification. The same engine that checks for spam traps or role accounts also reveals rendering quirks, so your message gets seen.

For deeper insight into how email clients handle content, refer to RFC 6650, which outlines how clients should handle email display, or explore general best practices via Return Path’s research on inbox placement and email engagement. Always trust rendering data from real systems, not guesswork.

Real-World Testing Beats Guesswork

There’s no exact formula for how much preview text each email client shows—each client, device, and UI version cuts off differently. Even tiny changes like a space or punctuation shift can push your preview text into the fold. The only way to know for sure is to test in real inboxes, not simulations.

Why Simulations Fail

Many tools claim to predict inbox behavior using hypothetical models. But real-world testing proves these models miss edge cases—like how Outlook on iOS truncates text at 80 characters, while Gmail might show more if the layout is simpler. Client versions, screen sizes, and even font rendering affect what users see.

Let’s say you have a 95-character preview. One client might show it fully. Another might cut it at 90. Change a comma to a period and suddenly it’s 95 again—only to be cut at 89. These nuances don’t appear in test data; they emerge only in live delivery.

Real Delivery, Real Data

Automated inbox testing with actual deliveries to real accounts is the only reliable method. Tools that simulate inboxes may give a false sense of safety. MailTester’s inbox checks use verified inboxes across major providers—Gmail, Outlook, Yahoo—delivering real emails to actual user accounts, not test environments.

Results reflect how your content appears in real user inboxes. You see exactly what your audience sees, including truncation points, formatting quirks, and layout shifts. This level of fidelity isn’t possible with mockups or API-based estimations.

For teams that care about inbox placement, this means fewer surprises—and more control. You’re not guessing. You’re validating. And that consistency matters when a single line of preview text can determine whether an email is opened or ignored.

You can test your inbox placement with MailTester’s real-world inbox tester: run a live inbox-placement check across multiple clients to see exactly how your preview text renders in practice.

The Bottom Line: Optimize Preheaders for Real Delivery

Preview text isn’t just filler — it’s a primary driver of open rates. A well-crafted preheader can turn a scroll-through into a click. But its visibility depends entirely on how each client truncates it.

Most clients limit preview text to 100–120 characters, especially on mobile. Gmail, Apple Mail, and Outlook vary in how much they show. Never assume the full preheader will be visible. Design for truncation: place key messaging at the start and ensure the message remains clear even when cut off.

Test your preheaders in actual inboxes. Use inbox placement testing with access to real client environments to see exactly how your message appears. Only then can you verify it lands as intended.

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What is the maximum preview text length for Gmail?

Gmail typically shows up to 156 characters on desktop, but truncates to 100–120 on mobile. Use 130 characters as a safe limit.

Does Outlook always show the full preheader?

No — Outlook (Windows) may cut text early due to spacing, font size, or layout rendering. Test with real inboxes.

Can I use emoji in the preview text?

Yes, but avoid relying on emoji as the key message. Some clients render them inconsistently or replace them with placeholders.

How important is preview text for mobile users?

Extremely — mobile inboxes have limited visible space. Preview text must deliver key value within 100–120 characters.

Does a long subject line affect preview text visibility?

Yes — when the subject line is long, clients may prioritize it, reducing space available for preview text.

What happens if my preheader is too long?

It gets cut off. If the most important message is near the end, it may be lost. Design for truncation.

Can I test preview text without sending an email?

Yes. Tools like MailTester allow inbox placement testing without sending to real users. Check how it renders in real inboxes.

Does the preheader affect spam filtering?

Indirectly — if the preheader is misleading or filled with deceptive language, it can harm sender reputation over time.

Should I write the subject line and preheader separately?

Yes — treat them as complementary. The subject line attracts attention; the preheader sustains interest.

Is there a universal preview text length standard?

No. Clients vary widely. Best practice is to design for the shortest common display — around 100–120 characters.

How often should I test my preheader?

Test every time you change a subject line, preheader, or layout. Use inbox placement tools before every major send.

Can spam filters read the preview text?

Not directly, but they analyze content patterns. Avoid repetitive or manipulative phrasing that could signal spam.