Get Started

Email Preheader Text: What It Is and How to Write It

Published

The most overlooked line in your email

Open your inbox and look at any unread message. You see the sender, the subject line, and — next to or below it — a short snippet of text. That snippet is the preheader (also called preview text), and it’s one of the highest-impact pieces of copy in your entire email. It sits right at the decision point where a reader chooses to open or ignore, and most senders never write it on purpose.

When you don’t set a preheader, the client grabs whatever text comes first in your email — often “View in browser,” an address block, or the opening of your header. That wasted snippet is a missed opportunity on every send.

What the preheader actually is

Technically, the preheader is just the first readable text the client finds in the email body. The inbox pulls a snippet of it to show alongside the subject line as a preview. There’s no dedicated “preheader field” in HTML — you control it by controlling what the first text in the email is.

That leads to the standard technique: place a short line of preheader copy at the very top of the email’s HTML, then visually hide it so it doesn’t appear in the rendered email but is still picked up for the inbox preview. It’s a small piece of markup, but it’s the difference between a deliberate preview and a random one.

Why it matters so much

The subject line and preheader work as a pair. Together they’re your entire pitch in the inbox:

  • The subject line grabs attention.
  • The preheader adds the context or hook the subject didn’t have room for.

A strong subject with a wasted preheader (“View this email in your browser…”) throws away half your inbox real estate. A strong subject and preheader working together give the reader two reasons to open. On mobile, where the preview can be even more prominent, this matters more, not less.

How to write a good preheader

Treat the preheader as an extension of the subject line, not a repeat of it:

  1. Don’t duplicate the subject. If the subject says “Your order shipped,” the preheader shouldn’t. Add information: “Track it here — arriving Thursday.”
  2. Front-load the value. Inbox previews are short and get truncated, and the visible length varies by client and device. Put the most compelling words first.
  3. Keep it concise. Aim for roughly 40–100 characters. Clients show different amounts, but a tight preheader reads well everywhere and controls exactly what appears.
  4. Create curiosity or urgency without being clickbait. “Only a few spots left” or “Here’s what’s inside” earns the open honestly.
  5. Match the email’s content. The preheader sets an expectation; the email should deliver on it. A mismatch trains readers to distrust you.
  6. Watch the fallback. If your preheader is short, the client may pad the preview with whatever text follows it in the email. Either make the preheader long enough to fill the preview, or add hidden spacer characters so stray header text doesn’t leak into the snippet.

Common preheader mistakes

  • Leaving it blank, so “View in browser” or an unsubscribe link becomes your preview.
  • Repeating the subject line word for word, wasting the extra space.
  • Writing it too long, so the important part gets truncated before it’s seen.
  • Forgetting to hide it, so the preheader appears as a stray line of text at the top of the rendered email.
  • Ignoring the fallback text, so the preview reads “Sale ends Friday Hi there, we wanted to…” — your line plus whatever came next.

How to handle the preheader in Temway

Because Temway is a visual builder, you control the preheader through the content and structure of your email rather than by hand-editing HTML. The practical pattern is the same as everywhere else: make sure the first meaningful text in the email is your intended preview line, and keep the pre-header housekeeping links (“view in browser”) from being the first thing the client sees.

Build your email with blocks, preview it across Desktop and Mobile, then send a test copy to your own inbox — where you can see the actual subject-plus-preheader preview exactly as a reader would, and adjust the opening copy until the snippet reads the way you want. When it’s right, export the HTML or push it to your ESP, where you’ll pair it with your subject line at send time.

Preheaders are also worth standardizing across a template library: a reusable layout that already puts a clean preview line first means every email built from it starts with the inbox preview under control.

Where to go next