Email subject lines and preheaders: length, examples, testing

A good email subject line says what is inside and why it matters to this reader, in the first few words, without promising anything the email does not deliver. The preheader (preview text) is the second line next to or under the subject in the inbox: use it to add the detail the subject had no room for, never to repeat it. Keep both short enough that the point survives truncation on a phone, test them by clicks rather than opens, and write the subject honestly, because a deceptive subject line is illegal under CAN-SPAM and against Gmail's sender rules.
Subject: header; the preheader is the first text of the body, usually hidden, that inbox apps show as a preview. No standard fixes how many characters are visible: it depends on the app, the screen and the font, so put the key words first and measure your own audience with a "ruler" test send. Spam filters score patterns such as all-caps subjects, but no single word gets you blocked; complaints and authentication matter far more. A/B test one variable at a time, pick the winner by clicks or conversions, and expect to need thousands of recipients per variant to detect small differences.What are the subject line and the preheader, and how much of them shows?
The subject line is the Subject: header of the message; the preheader is a short piece of text at the very top of the email body that inbox apps display as a preview after the subject. Together with the sender name they are all a reader sees before deciding whether to open, ignore or delete.
An unstructured header field defined in RFC 5322 (section 3.6.5). It is shown in the message list, in notifications, in the window title of an opened message and in search results.
Not a header at all. Inbox apps take the first readable text of the body and show it next to or under the subject. If you do not write it on purpose, the app shows whatever comes first: "View in browser", an image's alt text, or "Hi Anna,".
Where each one appears depends on the app and the layout. In a typical desktop webmail list view, sender, subject and preview share one row, so a long subject pushes the preview out. On phones, most apps give the sender, the subject and one or two lines of preview their own rows. Notifications on a lock screen usually show the sender and the subject and sometimes part of the preview.
How many characters are visible?
There is no primary source that fixes a number, and the published "ideal lengths" disagree because they measure different apps on different screens. Three things decide the cut-off: the width of the screen or column, the font (an "m" is much wider than an "i"), and the app's settings, such as density or the reading pane. The RFC 5322 limits are about protocol lines, not display: a header line SHOULD be no more than 78 characters and MUST NOT exceed 998, and longer subjects are simply folded onto continuation lines.
So measure it yourself, on the apps your subscribers actually use (your provider's statistics or your own audience survey tell you which). Send yourself a test with a "ruler" subject in which every block of five characters ends with its own position:
# ruler.py – prints a subject and a preheader in which each 5-character block ends with its position
def ruler(n):
return "".join(str(i).rjust(5, "-") for i in range(5, n + 1, 5))
print(ruler(100)) # ----5---10---15---20 ... --100
Open the inbox on each phone and desktop app you care about, and note the last number you can read in the subject and in the preview. Because digits and dashes are narrower than average text, treat the result as an upper bound, then send your real subject and check it again. Whatever the numbers turn out to be, the rule that follows is the same: the first three or four words must carry the meaning, and anything after them is a bonus.
How do you write a subject line people open?
Write the subject as a specific, honest promise of what the email gives the reader, with the most important word first, and use the preheader to add the second piece of information. Clarity beats cleverness: in a crowded inbox a reader decides in a glance, and a vague or cute subject gives them nothing to decide on.
- Name the benefit or the news
"New: export to CSV" tells the reader something. "Exciting news inside!" does not.
- Front-load the key words
Put the noun that matters first: "Webinar tomorrow at 18:00: email automation" survives truncation; "Don't forget to join us tomorrow for our webinar" loses the topic.
- Be specific
Numbers, dates, names of products and concrete outcomes are easier to judge than adjectives.
- Match the email
The first screen of the email should deliver what the subject promised. A mismatch costs clicks this time and opens next time.
- Write the pair together
Subject and preheader are read as one sentence. Split the message between them instead of repeating it.
- Keep your voice consistent
A recognisable sender name and a consistent tone do more over months than any single clever line.
Before and after: examples by email type
| Email type | Before | After (subject) | After (preheader) |
|---|---|---|---|
| Newsletter | Newsletter #48 | 3 ways to cut your SPF lookups | Plus a new DMARC report viewer and a reader question about bounces |
| Promotion | HUGE SALE!!! Don't miss out!!! | 20% off annual plans until Friday | The discount applies automatically at checkout, no code needed |
| Product announcement | Big news from us | New: schedule campaigns by the subscriber's time zone | Turn it on per campaign; everything else stays the same |
| Event reminder | Reminder | Starts in 1 hour: email automation webinar | Your link is inside; the recording goes out tomorrow |
| Re-engagement | We miss you! | Do you still want our weekly tips? | One click keeps you on the list; otherwise we will stop writing |
| Transactional | Notification | Your invoice for October is ready | Amount due: 97 USD, payable by 15 November |
As of November 2026. Examples written for this article.
Personalisation: names, segments and grammatical gender
Personalising with the first name can help, but only when the data is there and correct: a subject that reads "Hi , your report is ready" or uses someone's email alias as a name is worse than none. Relevance (sending the right email to the right segment) usually matters more than a merge tag.
- Write the subject so it reads well without the name. "Anna, your report is ready" breaks if the name is empty; "Your report is ready" never does. Many tools, NetSendo included, replace an empty field with an empty string, so plan the fallback in the wording or send to a segment that has the field filled in.
- Personalise with something that matters: the product they bought, the city of the event, the plan they are on.
- Languages with grammatical gender (Polish, German, Spanish and many others) need different word forms for men and women ("Dear" is Drogi/Droga in Polish, Lieber/Liebe in German). Use your tool's gender syntax only when you store gender reliably; otherwise choose neutral wording.
Can you use emojis and special characters in a subject line?
Yes. Email headers were designed for ASCII, so any emoji or accented letter is transported in an encoded form defined by RFC 2047, and modern apps decode it correctly. Problems come from broken encoding in home-made mailers and from how the symbol looks or sounds, not from the emoji as such.
Here is what Python's standard library produces for a subject with an emoji and an accented name (run on 19 November 2026):
from email.message import EmailMessage
from email import policy
m = EmailMessage(policy=policy.SMTP)
m["Subject"] = "🎁 Your 20% code expires tonight, Zoë"
print(m["Subject"].encode()) # header as it travels:
# Subject: =?utf-8?q?=F0=9F=8E=81_Your_20=25_code_expires_tonight=2C_Zo=C3=AB?=
That =?utf-8?q?…?= block is an "encoded-word": charset, encoding (q for quoted-printable or b for Base64), then the text. The rules that matter when you build headers yourself:
- An encoded-word may not be longer than 75 characters; longer subjects are split into several encoded-words on folded lines (RFC 2047, section 2).
- Each encoded-word MUST represent a whole number of characters: a multi-byte character (an emoji takes 4 bytes in UTF-8, a Polish "ż" takes 2) may not be split between two encoded-words (section 5). Splitting by bytes is the classic bug behind subjects that arrive as
�or as raw=?utf-8?…text. - Raw UTF-8 in headers is allowed only when both servers negotiate the SMTPUTF8 extension (RFC 6532). Your sending library or platform should handle this; do not paste unencoded UTF-8 into a hand-written header.
Spam filters notice badly encoded headers too: SpamAssassin's SUBJECT_NEEDS_ENCODING and SUBJ_ILLEGAL_CHARS rules fire on raw 8-bit characters in the subject (default scores).
✅ Advantages
- An emoji can stand out in a list of plain-text subjects.
- It can replace a word ("🎟️ Your ticket") and save space.
❌ Considerations
- Screen readers read the emoji's name aloud, which can make a subject long and odd.
- The same emoji looks different on each platform and may show as an empty box on old systems.
- If every sender uses them, they stop standing out.
A practical rule: at most one emoji, never as the only carrier of meaning, and test the subject in the apps your readers use.
Do spam trigger words exist, and what does the law say?
Lists of "spam trigger words" are mostly a myth: modern filters decide on sender reputation, authentication and how recipients react, not on a single word. Content rules do exist, but each adds a small score, while a deceptive subject line is a legal problem and a complaint generator in its own right.
What content filters actually check
SpamAssassin is a useful example because its rules are public. It scores a subject that is all capitals (SUBJ_ALL_CAPS, 0.5 points) and a subject that starts with a dollar amount (SUBJ_DOLLARS, 0.1 points), according to its default score file. The default threshold for calling a message spam is 5.0 points (required_score). One shouty subject alone will not get you blocked; it nudges the score up along with everything else. Gmail, Outlook and Yahoo run their own, non-public systems that rely heavily on user feedback.
That feedback is the real "trigger". Google's sender guidelines ask all senders to keep the spam rate reported in Postmaster Tools below 0.3%, and recommend staying below 0.1%. A misleading subject gets opened, disappoints, and gets reported. More on reputation and authentication in our guide to email deliverability for self-hosted senders.
Deceptive subject lines are illegal
- United States: the FTC's CAN-SPAM compliance guide says: "Don't use deceptive subject lines" and requires that the subject line accurately reflects the content of the message. Each separate email in violation can cost up to $53,088.
- Gmail: the sender guidelines require headers and subject to represent the sender and content accurately, and say not to start subjects with "Re:" or "Fwd:" unless the message is a real reply or forward.
- EU: marketing email needs consent under the ePrivacy rules and GDPR, and misleading commercial practices are banned by consumer-protection law; a fake "Re:" or a false deadline in the subject falls into that territory.
This is not legal advice.
⚠️ Avoid: fake "Re:" and "Fwd:" prefixes, fake shipping or invoice notices, invented deadlines ("Last chance" when it is not), all-caps subjects and runs of exclamation marks. Each one trades a short-term open for complaints.
How do you set a hidden preheader in HTML?
Put a hidden element with the preview text as the first thing inside <body>, styled so that it does not show in the opened email but is still read by the inbox list. Most email platforms have a preheader field that does exactly this; write the HTML yourself only when you build templates by hand.
<body>
<!-- Preheader: shown in the inbox preview, hidden in the opened email -->
<div style="display:none; max-height:0; max-width:0; overflow:hidden; opacity:0;
font-size:1px; line-height:1px; color:transparent; mso-hide:all;">
20% off annual plans until Friday. The discount applies at checkout.
͏‌ ͏‌ ͏‌ ͏‌
</div>
<!-- visible email starts here -->
The repeated invisible characters at the end are the "spacer" trick: they fill the rest of the preview so that the app does not pull in the next visible text ("View in browser", the logo's alt text). Each style covers a different client: display:none for most, mso-hide:all for Outlook on Windows, the zero sizes and transparent colour as fallbacks for apps that drop display:none.
Pitfalls
- Too short a preheader leaks body text. Without spacers, a 40-character preheader is followed in the preview by whatever comes next in the HTML.
- Spacers cost bytes. Hundreds of entities add up; Gmail clips messages above about 102 KB of HTML. See how to stay under Gmail's clipping limit. A few dozen repetitions are enough.
- Do not hide important content only there. Hidden text is not read by screen readers in the opened email, so anything the reader needs (a code, a date) must also be in the visible body.
- Keep it truthful. Stuffing hidden text with keywords or with text that contradicts the email is a known spam pattern and the same deception problem as a misleading subject.
- Editors and templates may strip it. Some visual editors remove empty or hidden elements on save. Check the source of the sent message, not the editor preview.
- The plain-text part has no hidden preheader. Start the text version with a meaningful first sentence too.
How do you A/B test subject lines when opens are unreliable?
Test one change at a time on randomly split groups that are large enough, and pick the winner by clicks or conversions, not by opens. Since Apple Mail Privacy Protection preloads images, an "open" is often recorded by a proxy rather than a person, so open rates are inflated and biased toward Apple Mail users (see what open rates still tell you after Apple MPP).
- Write a hypothesis
"A specific number in the subject gets more clicks than a question", not "let's see which one wins".
- Change one variable
Subject only, or preheader only, or sender name only. If you change two, you will not know which one worked.
- Size the test before you send
Use the table below. If your list cannot reach the size, test a bigger difference or repeat the same comparison over several sends.
- Choose the metric up front
Click rate (unique clickers per delivered email) or conversion rate. Use the open rate only as a secondary signal.
- Wait long enough
Clicks arrive later than opens. A test that picks a winner after one hour mostly measures who reads email at that hour.
- Write down the result
Keep a simple log of tests and outcomes. Single wins are noisy; patterns over ten tests are useful.
How many recipients do you need per variant?
| Metric | Baseline rate (%) | Rate you want to detect (%) | Relative lift (%) | Recipients per variant |
|---|---|---|---|---|
| Click rate | 2.0 | 3.0 | 50 | 3,826 |
| Click rate | 2.0 | 2.5 | 25 | 13,809 |
| Click rate | 3.0 | 3.6 | 20 | 13,914 |
| Click rate | 5.0 | 6.0 | 20 | 8,158 |
| Open rate | 20.0 | 22.0 | 10 | 6,510 |
As of November 2026. Calculated for this article with the standard two-proportion formula, two-sided test, significance 5%, power 80%.
You can reproduce the numbers in a few lines:
import math
from statistics import NormalDist
def per_variant(p1, p2, alpha=0.05, power=0.80):
z = NormalDist().inv_cdf
pb = (p1 + p2) / 2
a = z(1 - alpha / 2) * math.sqrt(2 * pb * (1 - pb))
b = z(power) * math.sqrt(p1 * (1 - p1) + p2 * (1 - p2))
return math.ceil((a + b) ** 2 / (p2 - p1) ** 2)
print(per_variant(0.02, 0.03)) # 3826
The lesson for small lists: with 2,000 subscribers you cannot reliably tell a 2.0% click rate from 2.5%. Test bold differences (a question against a number, a benefit against a deadline), or treat a test as a hint and confirm it over several sends.
What should come below the subject line?
The email has to keep the subject's promise in its first screen: one goal, one main call to action, and a plain-text version that says the same thing. A strong subject on a confusing email trains readers to ignore the next one.
📋 Checklist
- One goal per email: register, read, buy or reply, not all four.
- The first sentence continues the subject and preheader, not "Hi, hope you are well".
- One main call to action, as a clear button or link text ("Book your seat", not "Click here"); repeat it lower down if the email is long.
- Short paragraphs and subheadings that work for skimming on a phone.
- Images with alt text, and the message still makes sense with images blocked.
- A
text/plainpart next to the HTML, readable on its own. - A visible unsubscribe link plus one-click unsubscribe headers for marketing mail.
- A test send to yourself, checked on a phone and a desktop app.
If you are still building your audience, start with how to build an email list from scratch; for a sequence of emails that leads to a sale, see how to build an email sales funnel.
How do subject lines and preheaders work in NetSendo?
In NetSendo the subject and the preheader are separate fields of every message, and the preheader is inserted into the sent HTML as a hidden block right after <body>. Checked against the first campaign guide and the source code of version 2.12.0:
- Fields: type the Message Subject and, optionally, the Preheader when you create a message. At send time NetSendo removes any hidden preheader block already in the template and inserts the field's text as a
display:none; max-height:0; overflow:hiddenblock, without spacer characters, so keep the first visible line of your template meaningful. - Personalisation:
[[fname]]inserts the first name in the subject, preheader and body; custom fields work the same way. An empty field becomes an empty string, so write subjects that read well without it. - Grammatical gender:
{{male form|female form}}, for example{{Drogi|Droga}}, picks the form from the subscriber's gender. When gender is not set, NetSendo tries to detect it from the first name (tuned for Polish names) and falls back to the first, masculine form.[[!fname]]gives the Polish vocative of the first name. - Test sends: the Test button sends a copy with
[TEST]in front of the subject, with variables filled from a subscriber or sample data. - A/B tests (GOLD): the A/B Test tab tests the subject, the content, the sender, the send time or the whole message, and each variant can carry its own preheader. The default winning metric is open rate, with a 20% test sample, a 4-hour test window and a 95% confidence threshold; switch the metric to click rate or conversion rate for the reasons above, and lengthen the window if your list clicks slowly.
- Plain text: every email carries a
text/plainpart, either the message's own plain-text version or one generated from the HTML.
NetSendo runs on your own server; install it with the quick start guide, and see plans for what SILVER and GOLD include.
🎯 Expert tips
The first subject you write is usually the generic one. Write five, delete the vaguest three, and test the remaining two.
Subject plus preheader should sound like one sentence a person would say. If it sounds like an ad, rewrite it.
Type your topic into your inbox search. The subjects of other senders show you what readers see next to yours, and how to be different.
If every email is "last chance", none of them is. Readers learn, and so do complaint buttons.
After a test send, open "Show original" or the message source and check the Subject: header and the first lines of the body. Encoding bugs and leaking preview text are visible there at once.
Frequently asked questions
How long should an email subject line be?
No standard fixes a visible length: it depends on the app, screen width and font. Put the key words in the first three or four words and measure truncation on your audience's apps with a test send.
What is a preheader in an email?
The preheader is the preview text that inbox apps show next to or under the subject line. It is taken from the first text in the email body, usually a hidden block placed right after the body tag.
Should the preheader repeat the subject line?
No. Subject and preheader are read together, so use the preheader to add a second piece of information, such as a deadline, a detail or what the reader will find inside.
Do spam trigger words in subject lines send emails to spam?
Not on their own. Filters such as SpamAssassin give small scores to patterns like all-caps subjects, but sender reputation, authentication and spam complaints decide far more.
Can I use emojis in email subject lines?
Yes. Emojis are encoded under RFC 2047 and display in modern apps, but screen readers read their names aloud and they look different per platform, so use at most one and never as the only carrier of meaning.
How do I A/B test subject lines if open rates are unreliable?
Change one variable, split recipients randomly, and choose the winner by click rate or conversion rate. Calculate the sample size first: detecting a click rate rise from 2% to 3% needs about 3,826 recipients per variant.
Sources
- RFC 2047: MIME message header extensions for non-ASCII text
- RFC 5322: Internet Message Format
- RFC 6532: Internationalized email headers
- FTC: CAN-SPAM Act, a compliance guide for business
- Google Workspace: Email sender guidelines
- Apache SpamAssassin: default rule scores (50_scores.cf)
- Apache SpamAssassin: Mail::SpamAssassin::Conf (required_score)
- Digitale-Dienste-Gesetz (DDG), § 6
Write, test and send from your own server
NetSendo gives every message a subject, a preheader, personalisation and A/B tests, and keeps your list on infrastructure you control.




