# Subject Line and Preheader Previewer

> Preview an email subject line and preheader across directional Gmail, Apple Mail, and Outlook layouts, then evaluate how the pair works as a system.

- **Category:** Writing
- **Updated:** July 2026
- **Canonical page:** [https://emailbump.com/tools/subject-line-previewer](https://emailbump.com/tools/subject-line-previewer)
- **Interactive tool:** [Open the previewer](https://emailbump.com/tools/subject-line-previewer)

## What the tool does

The previewer combines a From name, subject line, and intentional preheader into directional desktop, mobile, and notification views. It estimates likely truncation for Gmail, Apple Mail, and Outlook layouts; compares the subject and preview text for repetition; and scores the pair across clarity, front-loading, pairing, honesty, and resilience.

All analysis runs in the browser. Draft sender names, subjects, and preview text are not submitted to Email Bump or an external service.

## Important preview limitation

There is no universal character count that guarantees a complete subject-line display. Available width changes with the mailbox client, device, app version, sender-name length, font size, accessibility settings, notification configuration, and interface state. The visualizations and cutoff estimates are directional. The final check is a real send through the actual sending path to representative inboxes.

## The inbox is a small system

Each visible element has a different job:

1. **From name — who:** establishes a recognizable sender identity.
2. **Subject — what:** states the main topic, event, value, or required action.
3. **Preheader — more:** qualifies the subject or adds evidence, scope, timing, or the next useful detail.

Repeating the same sentence in the sender, subject, and preview wastes limited space. A strong pair makes each line contribute new information while remaining coherent when one part is clipped.

## The five score dimensions

### Clarity

Does the subject state a concrete topic, event, outcome, resource, or action? Vague openings such as “Important update,” “Quick question,” or “You won't believe this” make the recipient work to discover why the message matters.

### Front-loading

Does the useful distinction appear early enough to survive compact views? Put the event, outcome, date, resource, or consequence first. Treat later words as supporting context.

### Pairing

Does the preheader extend the subject rather than repeat it? The checker compares meaningful words and flags heavy overlap or exact duplication.

### Honesty

Does the line avoid fake `Re:` or `Fwd:` prefixes, manufactured urgency, all-caps shouting, and decorative punctuation? Real urgency should name the actual deadline, event, or consequence.

### Resilience

Will the meaning survive clipping, varied emoji rendering, or missing personalization data? Every merge field needs a deliberate fallback. The words should carry the complete meaning even if a decorative symbol does not render as intended.

The total is a communication-quality score, not a spam-filter or deliverability prediction.

## No simplistic “spam word” prediction

No single word reliably determines inbox placement. Mailbox providers evaluate many authentication, reputation, traffic, content, and recipient-behavior signals. Words such as “free” should be used accurately because they shape expectations, not because a prohibited-word list can predict filtering.

## Strong subject and preheader pairs

| Use | Subject | Preheader |
| --- | --- | --- |
| Campaign plan | `Your July campaign plan` | `Three sends, two audience segments, and the goal for each.` |
| Product update | `The welcome flow is live` | `Here’s what changed after the first 500 subscribers.` |
| Transactional | `Order #1842 shipped` | `Expected Thursday—track the package or update delivery instructions.` |
| Billing action | `Action needed: payment failed` | `Update the card for your Northstar workspace by Friday.` |

The preheader adds useful context instead of restating the subject word for word.

## Transactional subject lines

Transactional messages arrive because something happened. Lead with the expected event, useful status, or required action. Keep secrets, full recovery links, temporary passwords, and sensitive account details out of subjects and notification previews.

Examples:

- `Reset your password for Northstar`
- `Order #1842 shipped — arriving Thursday`
- `Invoice #392 is ready — due August 12`
- `Action needed: payment failed for Northstar`
- `New sign-in to Northstar from Chrome`

Urgency is appropriate when it is real and specific. Routine receipts should remain calm and factual.

## Personalization

Personalization should add useful context rather than merely attract attention. A plan, product, workspace, order, event, or progress milestone can be more informative than a first name. Test missing values, unusual lengths, stale data, and special characters. If an incorrect field would feel invasive or confusing, leave it out of the subject.

## Frequently asked questions

### What is the ideal subject-line length?

There is no universal ideal. Put the useful distinction early and test real devices and clients. A concise line can still truncate when paired with a long sender name or large accessibility font.

### Should the preheader repeat the subject?

Usually not. Use preview text for evidence, scope, timing, qualification, or the next useful detail. Set it intentionally so a mailbox does not pull navigation, image alt text, browser-view links, or unsubscribe copy from the beginning of the email.

### Are emojis safe in subjects?

A relevant emoji can work for an appropriate brand and audience, but rendering and interpretation vary. Keep the text understandable without it, avoid decorative strings, and test accessibility and real inboxes.

### Is the highest open rate always the winning subject?

No. Opens are an imperfect signal and curiosity can attract the wrong attention. Evaluate qualified clicks, replies, conversion, complaints, unsubscribes, and the message's actual customer or product outcome.

## Related guidance

- [A simple framework for better subject lines](https://emailbump.com/blog/write-better-subject-lines.md)
- [24 transactional email subject lines](https://emailbump.com/blog/transactional-email-subject-lines.md)
- [Email subject line definition](https://emailbump.com/glossary/subject-line.md)
- [Sender name definition](https://emailbump.com/glossary/sender-name.md)