Last updated:
Email Newsletter Writing Tips - Word Count and Structure
Optimal Word Counts
| Element | Recommended Length | Notes |
|---|---|---|
| Subject Line | 6–10 words (30–50 chars) | Mobile shows ~30 chars |
| Preheader | 8–15 words (40–90 chars) | Supplements the subject line |
| Sender Name | 2–4 words | Brand + person name is ideal |
| Body Copy | 100–400 words | Adjust by purpose |
| CTA Button | 2–5 words | Start with an action verb |
| Footer | 20–50 words | Unsubscribe link + contact info |
Place your most important keywords within the first 30 characters of the subject line. Use Character Counter to verify length before sending.
These figures are practical starting points as of August 2026, not published specifications. Email clients do not document how much of a subject line they display, and no inbox provider publishes a required length for any of these elements. Use the ranges to get a first draft into a sensible shape, then let your own sending history move them.
Why Subject Line Length Matters
Subject line length is not something an inbox rewards or penalizes. It matters for a simpler, more mechanical reason: in a list view each message gets one line, and whatever does not fit is cut off. Two consequences follow from that alone.
- The end of a long subject line may never be read. If the specific detail that would make someone open the email sits at the end, it can be replaced by an ellipsis before it reaches the reader.
- The opening words carry the decision. Readers scan a column of sender names and first phrases, so the part that says what the email is for belongs at the front rather than after a preamble.
Body length works the same way in a different dimension. A long email is not penalized, but every extra screen of scrolling is another chance for the reader to stop before reaching the call to action. That is why placing a CTA mid-email, and not only at the end, matters more as the body grows.
Working Out Your Own Numbers
Recommended send times and lengths are easy to find and hard to trust, because they average across industries, list types, and reader habits that have nothing to do with yours. Your own sending history is the better source, and it takes only a few campaigns to start reading it.
- Compare a mid-body CTA against an end-of-body CTA. Place the same link in both positions with different tracking parameters. If the middle link consistently collects most of the clicks, readers are stopping early and the body is longer than they want.
- Group past campaigns into rough length buckets rather than exact word counts, then compare click rates per bucket. Buckets are enough to show a direction; exact counts mostly add noise.
- Test send time and length separately before looking at them together. Two variables changed at once cannot be attributed to either.
- Watch unsubscribes and spam reports alongside clicks. A version that wins on clicks while raising complaints is not a win.
Plain Text vs. HTML Newsletters: A Comparison
The format you choose affects how you should approach word count and design. Each format has distinct strengths and trade-offs.
| Factor | Plain Text | HTML |
|---|---|---|
| Impression on the reader | Reads like a message from a person | Reads like a published piece |
| Click path | Inline text links only | Text links plus button-style CTAs |
| When the body leans on images | Not applicable; everything is text | Meaning disappears for readers whose client blocks images |
| Recommended Body Length | 50–250 words | 100–400 words |
| Dark Mode Compatibility | No issues | Color inversion requires attention |
| Image Blocking | No impact | Layout breakage risk |
Plain text emails feel like personal messages, making them ideal for B2B outreach and relationship building. HTML emails leverage visuals for e-commerce promotions and brand campaigns. For plain text, keep copy concise; for HTML, balance images and text while allowing for slightly longer content.
Body Copy Structure
- Sale/promotion: 50–150 words (concise, action-focused)
- Content digest: 150–250 words (summaries + links)
- Newsletter column: 250–400 words (substantive reading)
- Drip campaign: 150–300 words (one topic per email)
The first 2–3 lines must hook the reader. Place CTA buttons in both the middle and end of the email.
Subject Line Length in Practice
Roughly 6–10 words (30–50 characters) is a workable starting point: long enough to say what the email is about, short enough to survive truncation in most list views. What you do inside that space matters more than hitting a particular count.
- Front-load the specific part. “Invoices for March are ready” survives truncation. “A quick update about something we have been working on” does not.
- Numbers set expectations. “5 tips for...” tells the reader how much they are committing to, which “Tips for...” does not.
- Do not spend characters on your own name. The sender name is already displayed next to the subject line, so repeating the brand there costs space that could carry information.
- Keep the subject and the body in agreement. A subject line that promises more than the body delivers costs you the next open, not just this one.
Getting Your Email Opened
- Test send day and time against your own list rather than against published averages
- Personalize the sender name
- Leverage the preheader with 40–90 characters of supplementary text
- Personalize content based on reader behavior
- Keep the frequency you promised at signup, and change it openly if you need to
Surprising Facts About Newsletters
- Google does not measure your open rate. Its guidelines for senders state that Google does not track open rates, and that a low open rate does not necessarily reflect how mail is being delivered or classified. Open rate is a number your sending tool produces, not a signal the receiving side acts on.
- Open detection depends on loading an image. An “open” is normally recorded when a small tracking image is fetched, so every reader whose client blocks external images is missing from the count. The metric systematically undercounts exactly the audiences most likely to have images off, corporate inboxes among them.
- The number the receiving side does watch is the spam complaint rate. The Google sender guidelines ask senders to keep reported spam below 0.10% and to avoid ever reaching 0.30%. As of August 2026 that is the published threshold worth monitoring.
Common Mistakes
- Spam trigger words - Overusing "FREE," "ACT NOW," or excessive symbols increases spam folder risk.
- Body too long - The longer the email, the more screens a reader has to get through before the CTA, and the more of them stop first. Keep to one topic and link out for details.
- CTA only at bottom - Readers who abandon mid-email never see it. Place CTAs in multiple locations.
Emoji in Subject Lines: Encoding Pitfalls
Adding emoji to subject lines can help a message stand out in a crowded list, but there are technical pitfalls to be aware of.
- UTF-8 encoding overhead: Emoji consume 4 bytes in UTF-8. Against the subject line byte limit (RFC 5322 specifies 998 octets per line), a single emoji uses more space than a standard ASCII character (1 byte)
- Variation Selector issues: Some emoji include Variation Selectors (U+FE0E / U+FE0F) that toggle between text and emoji presentation. Not all email clients handle these correctly, leading to unexpected rendering
- Legacy client fallback: Older email clients, and corporate mail environments built in-house, may replace emoji with “□” or “?”. For B2B newsletters, consider whether your audience’s email clients support emoji
- Character count discrepancies: Emoji appear as one character visually but may consist of multiple code points internally (e.g., flag emoji use two Regional Indicator symbols). Different counting tools may report different lengths-use Character Counter for accurate measurement
Dark Mode and Image Blocking Fallbacks
Two commonly overlooked challenges in HTML newsletter design are dark mode rendering and image blocking.
Dark mode: Apple Mail (iOS 13+), Gmail app, and Outlook app support dark mode, which automatically inverts background and text colors. This auto-inversion can cause several issues:
- Logo images designed for white backgrounds display with visible white borders
- Light-colored text becomes invisible against the dark background
- Button background colors invert, breaking the intended design
Mitigations include using transparent PNGs for logos, always pairing color with background-color in inline styles, and defining dark-mode-specific styles via @media (prefers-color-scheme: dark) for clients that support it.
Image blocking: Corporate email servers and security software often block external images by default. To ensure your message gets through even without images:
- Add meaningful
alttext to every<img>tag - Duplicate critical information (prices, deadlines) in text, not just images
- Build CTA buttons with HTML + CSS (“bulletproof buttons”) instead of image-based buttons
- Specify
widthandheighton images to prevent layout shifts when images are blocked
Email Client Display Differences: The Technical Background
How much of a subject line a reader actually sees is not published by any of the major email clients, and it is not a fixed number: it changes with the app, the device, the window or screen width, and the reader’s own text size setting. Instead of memorizing per-client character counts, it is more useful to understand the three structural differences that produce the variation.
- Where the preheader sits. Some clients put preheader text on a second line beneath the subject; others put it in gray immediately to the right of the subject, sharing the same line. In the second layout, a long subject line pushes the preheader out of view entirely.
- Desktop widths vary, phone widths effectively do not. On desktop the message list resizes with the window, so the same subject line is cut at different points on different screens. On phones the width is fixed in practice, which makes mobile the tighter constraint to design for.
- Interfaces use proportional fonts. A subject line is measured in pixels, not characters: “illinois” and “WOMBAT” take up very different widths at the same character count. Capitals, wide characters, and full-width characters all reduce how much fits.
Because of this, treat any per-client character count as directional rather than exact. Placing the essential words first is the one mitigation that works regardless of where the cut falls. Use Character Counter to check the length of a subject line before sending.
How Preheader Text Works
The preheader (40–90 characters) is critical because mobile devices display it immediately after the subject line. A two-pronged approach, hooking with the subject and supplementing with the preheader, gives the reader two chances to see why the email is worth opening.
The preheader display logic varies by email client. For HTML emails, clients determine preheader text using the following priority:
- Hidden text placed immediately after the
<body>tag (the most common implementation) - The first visible text content in the HTML body
- The opening text of the plain-text part (for multipart emails)
Without a custom preheader, the email body’s opening text (often “If this email doesn’t display correctly...”) appears automatically, undermining the reader’s motivation to open. The “preheader hack”-inserting invisible zero-width characters (‌ repeated) after the preheader text-prevents unintended body text from bleeding into the preview.
Spam Filters and What Is Actually Published
Advice about spam filters circulates as a set of very specific thresholds: a minimum subject length, a maximum share of symbols, a required text-to-image ratio, a minimum body length, a running score for “trigger words.” None of these appear in the Google guidelines for senders, which set out no character-count or ratio requirements at all (as of August 2026). The one published number concerns complaints: keep the rate at which recipients report your mail as spam below 0.10%, and never let it reach 0.30%.
So word count is not the lever here. What is worth doing is the short list of practices that keep complaints down, which is the measure the receiving side actually applies.
- Make the subject line and the body match. Complaints cluster around mail that turns out to be about something other than what it promised.
- Always include readable text. An email that is a single image, or a bare URL with nothing else, gives neither the reader nor the client anything to go on.
- Do not stack decorative symbols. Rows of exclamation marks and all-caps words read as spam to people, and people are the ones who file the complaints.
- Make unsubscribing obvious. A reader who cannot find the unsubscribe link reports the message instead, and a complaint costs far more than a lost subscriber.
Pro Newsletter Techniques
- The “preheader hack” - Insert invisible zero-width characters (
‌ repeated) after the preheader text in HTML emails. This prevents body text from bleeding into the preheader display, ensuring only your intended preview text appears in email clients. - Segmented sends - Instead of sending the same content to every subscriber, segment by purchase history, browsing behavior, or demographics. How much this gains you depends entirely on the quality of the list: a segment that is genuinely different in what it wants responds differently, and one that is only different on paper does not. Compare against your own bulk sends rather than against improvement figures quoted for someone else's list.
- Send-time optimization - Some sending platforms offer a feature that learns when each subscriber usually opens mail and schedules delivery accordingly. The names and the behavior differ from tool to tool, and none of them can do anything until enough per-subscriber history has accumulated, so treat it as something that starts working after several campaigns rather than on the first one.
Designing Effective A/B Tests
Improving newsletter performance requires data-driven A/B testing, not guesswork. Here are the key principles for designing effective tests.
- Test one variable at a time: Subject line length, CTA label, send time-change only one element per test. Changing multiple variables simultaneously makes it impossible to attribute results to a specific change
- Size the test to the difference you want to detect: There is no universal minimum number of sends. The smaller the gap between two versions, the more sends it takes to tell them apart, and a difference of a percentage point or two will stay invisible on a small list no matter how the test is arranged. On a small list, split it 50:50 and repeat the same comparison across several campaigns instead of trying to settle it in one send
- Synchronize send times: Send both A and B variants at the same date and time. Day-of-week and time-of-day differences would confound your results
- Subject line test examples: “6-word subject vs. 10-word subject,” “subject with number vs. without,” “question format vs. statement format”-always test with a clear hypothesis
- Define success metrics upfront: Decide whether you’re optimizing for open rate, click-through rate, or conversion rate before running the test. A high open rate with low CTR may indicate a gap between subject line promise and body content
Optimizing Word Count by Segment
Different subscriber segments respond to different content lengths. Tailoring word count by audience behavior and attributes maximizes engagement.
| Segment | Recommended Subject Length | Recommended Body Length | Rationale |
|---|---|---|---|
| New subscribers (first 30 days) | 7–10 words | 150–250 words | Need brand introduction; thorough onboarding is effective |
| Active readers (open 2+ per month) | 6–8 words | 75–175 words | Already familiar with brand; prefer concise updates |
| Dormant readers (3+ months inactive) | 4–7 words | 50–125 words | Short, high-impact content for re-engagement |
| Past purchasers | 6–8 words | 100–200 words | Include product recommendations and cross-sell info |
| VIP customers (frequent buyers) | 6–10 words | 150–300 words | Exclusive content and early access create loyalty |
These are practical starting points as of August 2026, not established standards. Nothing about segment behavior is published by inbox providers, and the boundaries between segments (what counts as dormant, how long onboarding lasts) differ by business. Use the table to decide where to start, then let the click and unsubscribe figures for each segment move the ranges.
Reducing Unsubscribe Rates Through Word Count Strategy
Unsubscribes happen when readers decide your newsletter no longer provides value. Word count strategy plays a key role in retention.
- Inverse frequency and length: If you send 3+ emails per week, keep each to 50–150 words. For weekly sends, 200–400 words of substantive content works well. High frequency combined with long copy feels intrusive and drives unsubscribes
- Front-load value in the first 2–3 lines: The opening 15–25 words should clearly communicate the reader’s benefit. Long greetings or preambles signal “not worth reading” and lead to unsubscribes
- Make the unsubscribe link easy to find: Counterintuitively, hiding the unsubscribe link causes readers to mark your email as spam instead. Spam reports damage your sender reputation far more than unsubscribes. Include a clear unsubscribe notice in the footer (20–50 words)
- Offer frequency options: Instead of a binary subscribe/unsubscribe choice, offer options like “reduce to weekly” or “monthly digest only.” Many unsubscribes are not a rejection of the content but of the volume, and a reader whose only available answer is “stop entirely” will give that answer. Providing a smaller answer keeps the relationship for people whose actual complaint was frequency
Conclusion
Start with subject lines of about 6–10 words and body copy of 100–400 words, and put the words that matter in the first 30 characters, since that is the part no client can truncate away. Beyond that, treat the ranges as a starting point rather than a rule: the only published number in this area is the spam complaint threshold, so let your own click and unsubscribe figures decide the rest. Use Character Counter to check your newsletter text.