Newsletter subject line length: the ideal character count

Ask ten email tools what the right newsletter subject line length is and nine of them answer the same way: 30 to 50 characters. None of them say where that range came from, or which inbox it was measured in. The honest answer is messier. There is no single ideal character count, because the number that decides whether your reader sees the whole line is not how long you wrote it, it is where their mail app stops rendering it.

That distinction sounds pedantic until you watch the same subject line behave differently in two inboxes side by side. A 55-character line reads complete in Outlook on a laptop and gets chopped after "..." on an iPhone. Same words, same send, two different messages depending on who opened it. So the question is not how long a subject line should be. It is how much of it survives the reader's screen.

The short answer, and why one number misleads

The 30-to-50 rule is not wrong so much as beside the point. It describes an average across clients that no individual reader experiences. Your list is not the average. If most of your opens come from the Gmail app, your usable space is well under 50 characters. If you run a B2B newsletter that people read in Outlook at a desk, you have room to spare.

We think the round-number advice is worse than useless now, because it trains writers to trim toward a target instead of writing toward a screen. A 28-character subject line that says nothing is weaker than a 61-character one whose first six words land the hook. Length is a constraint to design around, not a score to hit.

Where each mail client cuts the line off

Truncation is client-specific and, on mobile, orientation-specific. These are the points where the list view stops showing your subject line and starts showing the ellipsis. They shift a little with font settings and device width, so treat them as working budgets, not laws.

Where it opens	Visible characters	Notes
iPhone Mail, portrait	~41	Widens to ~62 in landscape
Gmail app (iOS / Android)	~38-47	Varies with device width and font size
Yahoo Mail, mobile	~46	Preheader eats the next line
Outlook desktop	~60	Plus a separate preview line
Gmail web (desktop)	~70	Then the preheader continues inline
Apple Mail (Mac, list)	~90+	Wraps to a second line rather than cutting

Two things jump out of that table. The tightest budget is the one most of your readers are on, because phone opens dominate most consumer lists. And the spread is huge: the difference between the iPhone number and the Apple-Mail-on-Mac number is more than double. No single length can be right for both ends of that range at once. What you can do is write so the line works at the tight end and rewards readers at the wide end.

What our subject-line data shows about real length

When we pull the subject lines out of the newsletters landing in our Newsletrix tracking inboxes, the shape of the data is consistent. Most lines cluster in the 30s and 40s of characters, with a long thin tail running past 60 and a smaller bump of very short teaser lines under 20. The median sits in the low 40s. So the industry has quietly settled on writing to roughly the iPhone budget, whether or not anyone did the math.

The more useful finding is what happens when we line length up against open rate. The curve is close to flat across a wide middle band. Push into the extremes and it sags: subject lines under about 15 characters underperform because they rarely carry enough to earn a tap, and lines that run long enough to get chopped mid-word lose the reader at the cut. Between those poles, length barely predicts anything. The subject lines that beat their sender's own average are not shorter on average, they are front-loaded. Their first few words do the selling.

This matches what the seven factors that decide if a subject line works already told us: length is one input among several, and on its own it is a weak one. It only starts to matter when it interacts with the cut-off point.

Character count is the wrong unit

Here is the reframe that changed how we audit subject lines. Stop counting total characters. Count the characters before the cut. Your real budget is the first 40 or so, because that is what the phone shows, and the phone is where the open happens. Everything after character 41 is a bonus that desktop and Apple Mail readers get, and mobile readers never see.

So front-load. Put the specific promise, the number, the name, the verb, in the opening words. "New teardown: how Morning Brew writes its cold open" survives the cut because the payload is up front. "A few thoughts on something we noticed this week about cold opens" dies at the ellipsis with nothing said. Same length range, opposite outcome.

The preheader is your safety valve for the overflow. If the full thought needs 70 characters, write the first 40 as the hook and let the preview text finish the sentence and add the detail. Done well, the phone reader gets a complete line plus a preview that extends it, and the desktop reader gets the whole thing inline. Our preheader strategy guide covers how to write the two as one unit instead of letting your ESP dump the first line of body copy into the preview slot.

Length by newsletter type

The right budget shifts with who you are writing to. Editorial and media newsletters, the daily and weekly reads people open on a phone over coffee, live and die on the tight mobile budget. Curiosity has to land in the first few words. We see the strongest media subject lines running short and punchy, often well under the 41-character cut, because they are competing with a dozen other newsletters in the same crowded list view.

Ecommerce and promotional sends behave differently. They lean on offer specifics, and a price or percentage carries even when the sentence around it gets chopped. "40% off ends tonight" works truncated because the number is the message. B2B newsletters get the most latitude, because a real share of their opens happen in Outlook and Apple Mail on a desktop, where the line runs long before it cuts. That is where a descriptive, longer subject line earns its length instead of wasting it.

None of this is free. Write short for the phone and you lean harder on the preheader and on your baseline open rate to carry the send; there is less room for nuance. Write long for the desktop and your mobile majority sees a fragment. The tradeoff is real, and it comes down to knowing your open split before you decide, not guessing.

How to test your own subject line length

Do not trust a character counter alone. A counter tells you the length; it does not tell you where the cut lands or whether the payload survives it. Three steps get you a real answer.

First, find your open split. Your ESP reports opens by device or client. If 70% of your opens are mobile, write to the phone budget and stop agonizing over the desktop view. Second, preview the line where it renders, not in your editor. Send a seed to your own iPhone and to a desktop client, and look at the list view, not the open. That list view is the only place truncation shows. If you want a full client matrix without seeding by hand, a rendering suite covers it, and we compare that approach in our Litmus alternative breakdown. Third, read only the visible part out loud. If the first 40 characters make sense on their own, you are safe. If they trail into a setup with no payoff, rewrite the front.

When you do test length, test it against something, not in a vacuum. Pair a short front-loaded line against a longer descriptive one and let the open rate decide, the way we lay out in the subject line A/B testing guide. And remember that emoji and personalization tokens spend from the same budget. An emoji at the front costs one to two characters of prime space, and a "Hi {FirstName}" opener can burn a third of your visible line before you say anything. We dug into whether that trade pays off in do emojis increase open rates.

The takeaway is not a number. It is a habit: write the first 40 characters as if they are the whole subject line, because for most of your readers they are.

Frequently asked questions

What is the ideal newsletter subject line length?

There is no single ideal length, because each mail app truncates at a different point. The safe rule is to put whatever matters most in the first 40 characters, since that is roughly what iPhone Mail and the Gmail app show in portrait, and let anything beyond that be a bonus for desktop readers. Aiming for one magic number optimizes for an average inbox that does not exist.

How many characters before a subject line gets cut off on mobile?

On iPhone Mail in portrait the list view shows around 41 characters before it cuts off. The Gmail app is tighter and varies with screen width, roughly 38 to 47 characters. Yahoo Mail on mobile sits near 46. Rotate the phone to landscape and all of these widen, but most people read upright.

Does subject line length affect open rates?

Length itself is a weak predictor. When we line up subject-line length against open rate across the newsletters we track, the curve is close to flat through a wide middle band and only sags at the extremes, very short lines with no information and very long lines that get chopped mid-word. What moves opens is whether the visible part of the line carries the value, not the total character count.

Should I count spaces and emojis in the length?

Yes. Every visible glyph, spaces included, takes up room in the truncation budget. An emoji usually renders about as wide as one to two characters and sits at the front where it costs you prime space. If you open with an emoji, count it as part of the first 40 characters, not a free extra.

What length works best on iPhone Mail?

Write for the roughly 41 characters iPhone Mail shows in portrait. That does not mean your subject line must be 41 characters or shorter. It means the first 41 characters should read as a complete thought, so the line still works when the rest is hidden. Apple Mail on a Mac shows far more, so a longer line rewards those readers without punishing phone readers.

Related reading