The Preheader Is Half Your Subject Line, and Most Cold Emails Waste It
Open the inbox on any phone or desktop client and every subject line is followed by a short strip of preview text — the preheader. Most senders never write it deliberately, so the inbox fills it automatically with whatever text comes first in the email: often «Hi Maria,» or, worse, an unsubscribe link and a legal footer pulled from the bottom of the template. That's a wasted second sentence of persuasion in a cold email, where every signal competing for a decision-maker's attention matters.
- The preheader is inbox real estate the recipient sees before opening — leaving it to default text wastes it.
- Its job is to extend or complete the subject line's idea, not repeat it or introduce something unrelated.
- Preheader length that displays varies by client, so front-load the important words in the first 40-70 characters.
- A default preheader pulling in «Hi [Name]» or unsubscribe text is a common, easily fixed cold email mistake.
- Test preheader and subject line as a pair, not separately — they're read together, not in isolation.
What the preheader actually is and why it matters here
The preheader — sometimes called preview text or Johnson box — is the snippet of text most email clients display next to or beneath the subject line in the inbox list view, before the message is opened. It's typically pulled from the first line of visible content in the email unless a sender specifically overrides it, and it's visible on essentially every major client: Gmail, Outlook, Apple Mail, and their mobile equivalents all show some version of it.
For cold outreach specifically, the preheader matters more than it does for a newsletter, because a cold email is competing for a decision to open at all, from a recipient who doesn't recognize the sender and has no standing reason to click. The subject line alone carries most of that decision, but the preheader is genuinely a second data point read in the same glance, and it either reinforces the subject line's promise or undercuts it.
Left unset, most email tools default the preheader to whatever text appears first in the body — frequently a greeting line («Hi Maria,») that adds nothing, or in poorly built templates, a fragment of a legal disclaimer or unsubscribe link pulled from the footer. Both outcomes waste a visible, readable slot in the inbox that could otherwise be doing real persuasive work.
What a good preheader does that a good subject line alone can't
A subject line has to be short and often has to be a little intriguing or incomplete to earn the open — that's the nature of the format. The preheader's job is different: it can complete the thought, add a specific detail the subject line didn't have room for, or answer the implicit «why should I care» that a short subject line raises without resolving.
Think of the pair as one sentence split across two visible fragments, not two separate attempts at the same message. A subject line reading «Quick question about your renewal cycle» paired with a preheader that repeats a version of the same idea («A question about renewals») wastes the second slot; paired with a preheader that adds the specific detail — «Noticed your contract terms shortened significantly last cycle» — the two together do more work than either alone.
This pairing effect is where most of the preheader's real lift comes from in cold outreach. It's rarely the preheader alone that decides an open; it's the combined read of subject plus preview snippet in the fraction of a second a recipient's eye passes over the inbox row.
Writing preheaders that extend the hook, not restate it
Start by treating the preheader as a continuation, and draft it after the subject line is close to final, not before — writing it first tends to produce something generic because there's no subject line context to extend yet. Read the two together out loud as if scanning an inbox; if the preheader could apply to any cold email regardless of subject line, it needs another pass.
Specificity does the same work here that it does everywhere else in cold outreach: a preheader referencing a concrete detail about the recipient's company, role, or situation reads as evidence the email is genuinely addressed to them, not just personalized with a mail-merge field. «Saw the note about your Q3 expansion into the Midwest» works harder than «A question for you» in a preheader slot, even though both are short.
Avoid restating the sender's name or company if that's already visible elsewhere in the inbox row — most clients show the From name adjacent to the subject and preheader, so repeating it in the preview text is wasted space that could instead extend the actual hook.
Subject: quick question about your fleet renewal — Preheader: noticed the contract length shortened by a third last cycle, wondering if that's a trend worth flagging.
Length, defaults, and the technical details that trip people up
Displayed preheader length varies significantly by client and device — mobile clients typically show fewer characters than desktop, and different providers cut off at different points, roughly in the 40 to 100 character range depending on the client. The practical rule: front-load the specific, important part of the preheader in the first 40-70 characters, since anything beyond that is a bonus on some clients and invisible on others.
Most email platforms and ESPs offer a dedicated preheader field separate from the body — use it, and set it deliberately for every send rather than relying on the default. If your sending tool doesn't offer a dedicated field, a common workaround is a short line of intentional preview text placed at the very top of the email body, followed by a hidden or minimally styled spacer to push any unwanted default content (like a header image or a repeated greeting) out of the visible preview window.
Double-check the rendered result across at least Gmail and Outlook before sending any meaningful volume — a preheader that looks intentional in one client can render oddly or get cut off mid-word in another if the underlying HTML structure wasn't built with this in mind.
- Set the preheader deliberately for every send — never leave it to the client's default extraction
- Front-load specific, relevant content in the first 40-70 characters
- Read subject and preheader together, not as two independent attempts at the same hook
- Preview render in at least Gmail and Outlook before a full send
- Avoid repeating the From name or company if it's already visible elsewhere in the inbox row
Testing preheaders without over-engineering the process
Test the subject-preheader pair as a single unit rather than isolating the preheader as its own variable — because the two are read together in practice, testing them independently produces results that don't reflect how a recipient actually experiences the message. Run a genuine A/B test with two full subject-plus-preheader combinations against comparable segments of your list, not a single-variable swap.
Open rate is the direct metric to watch, but treat a preheader change with the same skepticism as any other single-lever open-rate optimization: it can move opens without moving replies, especially if the preheader over-promises relative to what the email itself delivers. A stronger open rate that doesn't translate into a comparable reply-rate lift suggests the preheader created curiosity the email body didn't satisfy.
Once a pattern that works for your ICP is established — for instance, preheaders that state a specific number or detail consistently outperforming vague curiosity hooks — apply that pattern as a default across campaigns rather than re-testing from scratch every time, and revisit only if performance drifts.
FAQ
What's the difference between a preheader and a subject line?
The subject line is the primary headline shown in bold in the inbox; the preheader is the shorter preview snippet shown alongside or beneath it, usually in lighter text. They're read together in a single glance, so they should be written to complement each other rather than duplicate the same idea.
How long should a preheader be?
Aim to front-load the important content within the first 40-70 characters, since display length varies by client and device — mobile clients typically show less than desktop. Anything after that range may be cut off depending on where the recipient reads it.
What happens if I don't set a preheader manually?
Most email clients default to pulling the first visible line of body text, which is often a greeting like «Hi Maria,» or, in poorly structured templates, part of an unsubscribe link or legal footer. Either outcome wastes visible inbox space that could otherwise reinforce the subject line.
Does the preheader affect deliverability, not just open rate?
Not directly in most cases — its main effect is on the recipient's decision to open, not on spam filtering. That said, a preheader accidentally pulling in unsubscribe or legal boilerplate text can look unpolished and, in aggregate across a campaign, contribute to a lower-quality impression that indirectly affects engagement signals filters use.
Should the preheader be personalized per recipient like the email body?
Where practical, yes — a preheader referencing something specific to the recipient's company or role performs better than a generic line reused across the whole send. If full personalization at that level isn't feasible, a well-written generic preheader that genuinely extends the subject line is still far better than the client's default extraction.
Want to apply this to your outreach?
We will map it to your segment and product — before any work starts.
Talk to us