Newsletter sender name best practices

Every inbox decision starts with the From name. Subject line and preheader matter, but the recipient's eye lands on the sender first, and a name they trust gets opened with a subject line that would otherwise be ignored. Most newsletter sender name best practices guides recycle "use a real human name" and stop there. We parse the From header on every newsletter in the corpus we monitor across 12 ESPs, and the data is more interesting than the conventional wisdom. The pattern that wins for a B2B SaaS list is a loss for an ecommerce list. The pattern that wins on desktop gets cut off on mobile. The ESP your competitor uses changes what they can put in the field at all.

What the From name is (and how it differs from the From address)

The From name is the display label, defined in RFC 5322 as the display-name component of the From header. The From address is the addr-spec, the mailbox itself. A raw From header looks like From: "Patrick from Stripe" <[email protected]>. The quoted string is the name. The angle-bracketed part is the address.

Almost no email client shows the address once a name is present. Gmail web, Gmail mobile, Apple Mail, and Outlook all collapse the From header to just the name in the inbox list. The recipient does not see the mailbox unless they tap to expand it. The From name carries the open decision and the From address mostly does not.

The address still matters for deliverability. Gmail builds engagement reputation against the address plus the sending domain, and a mismatched name (one that does not appear in the recipient's address book or past correspondence) can lower the open-rate ceiling before the recipient even sees it. The visible field is the name. The invisible field is doing work behind it.

Character limits that actually render

The character limit to plan to is 22, not 50 or 78. The RFC allows long display-names, the ESP will accept anything you type, and Outlook desktop will render the whole thing. None of that is the binding constraint. The binding constraint is the smallest mobile inbox view your subscribers use.

Gmail iOS truncates the From name at around 22 characters in the inbox list. Gmail Android sits close to 25. Gmail web shows 25 to 30 depending on window width. Apple Mail iOS gives you around 30. Outlook desktop tolerates 40 and rarely truncates. The first 18 characters are the safe zone where nothing important gets cut on any major client.

This is why the "Brand Newsletter" pattern almost always backfires. "Stripe Newsletter" reads as 17 characters on a brand short enough to absorb the suffix, but "ActiveCampaign Newsletter" reads as 25 and gets cut on Gmail iOS. The truncated string looks broken. We see this on roughly one in four newsletters we audit where the brand name is longer than seven characters.

The pragmatic rule: write the name out, count the characters, then preview it on the device a quarter of your subscribers read on. If your audience skews B2B and reads on desktop Outlook, the safe zone is wider. For mobile Gmail, 22 is the cap.

The five From-name patterns we see across the corpus

Almost every newsletter we analyze falls into one of five patterns. They are not equally common and not equally good.

Brand only. "Stripe". "Klaviyo". "Linear". Clean, recognizable, fits the character budget on every client. Strong for ecommerce and transactional-heavy lifecycle sends where the brand is the consistent anchor across many message types. Weak for editorial newsletters where personality is part of the product.

Person at Brand. "Patrick at Stripe". Reads like a Twitter bio. We see it most on B2B SaaS lists where the company wants a face on the send but the marketing team is uneasy about removing the brand. It is a compromise and it reads as a compromise.

Person from Brand. "Patrick from Stripe". The same idea phrased as a casual self-introduction. Reads warmer than "at" and tests better in our audit pass. The B2B SaaS lists that switched from "at" to "from" in the last 18 months almost all kept the change.

First name only. "Patrick". The dominant pattern on creator newsletters and solo Substacks. Works because the subscriber signed up specifically for this person. Fails for any brand with more than one author because the recipient cannot tell who wrote which issue.

Brand plus descriptor. "Stripe Updates". "Stripe Newsletter". "Stripe Weekly". The most common mistake in our audit data. Adds 6 to 11 characters that will get truncated on mobile and signals "promotional list" to Gmail's tab classifier. We have not seen a single A/B test where the suffix outperformed plain brand.

Which pattern wins by newsletter type

The pattern that wins for one type of list is wrong for another. The defensible position we will say out loud: there is no universal best practice and any guide that tells you to "always use a human name" has not looked at enough ecommerce lists.

B2B SaaS: Person from Brand. The buyer wants to know who is talking and which company is talking, and "from" reads as a person introducing themselves rather than a corporate signoff. We see open rates 8 to 14% higher on the Person-from-Brand pattern compared to the same list using plain brand, on the same subject line.

Creator and solo: First name only. The subscriber chose the person. Adding the publication name dilutes the relationship that drove the signup. If the publication is its own brand (a Substack with a name distinct from the author), use the brand only after the author has been writing for at least six months and reader recognition has built up.

Ecommerce: Brand only. Recipients shop the brand, not the founder. The exception is a founder-led brand where the personality is part of the product (Glossier in its early years, Patagonia for activism sends), but even then most operators rotate between brand-only for promotional sends and founder-name for editorial.

Media and publication: Brand plus a tightly-scoped section, when it fits the character budget. "Bloomberg Pursuits" is 16 characters and tells the reader which vertical the email belongs to. "Bloomberg Pursuits Weekly Newsletter" is 36 and gets butchered on Gmail iOS. Short descriptor is fine. Long descriptor is the suffix trap.

The tradeoff every operator weighs is trust against recognizability. A human name reads warmer and lifts opens. A brand name is what subscribers type into inbox search three weeks later when they want your last send. Pick the one that matches how the audience remembers you. For how this fits the wider inbox decision, see the seven subject-line factors that drive opens and our preheader strategy guide. Pre-test the headline paired with your From name in the subject line tester.

ESP defaults that quietly sabotage your From name

Three ESP behaviours show up often enough in our detection work to call out by name. They are not bugs. They are defaults the operator forgot to override.

Mailchimp injects "via Mailchimp" into Gmail's display in some cases when the sending domain is not authenticated with DMARC alignment. The recipient sees "Stripe via mailchimpapp.net" and the warm-name effect collapses. The fix is to set up DKIM and DMARC on the sending domain so Gmail trusts the From name as-is. We covered the mechanics in our SPF, DKIM, and DMARC guide.

SendGrid sub-user defaults pull the From name from the sub-user's account display name unless the sender explicitly sets the field per send. Lists that share a SendGrid parent account across teams often end up with the wrong From name because no one overrode the sub-user default. We see this on roughly one in eight SendGrid-detected newsletters in our audit pass.

HubSpot persona tokens (the "first name + brand" macro the platform offers) generate strings that often overflow on mobile because the rendered length depends on the sender persona configured, and the marketing user setting up the send rarely sees the rendered length on a phone. The result is a perfectly composed From name on desktop and a truncated mess on iPhone.

Detection is straightforward. Drop a competitor's send through any cross-list analytics tool and you can see the rendered From header before the inbox sees it. Cross-newsletter benchmarking tools exist for exactly this. The detection step is the easy part. The hard part is convincing the marketing team to override the platform default on every send.

From-name changes and the deliverability cost

Changing the From name is not free. Gmail and Outlook keep engagement reputation against the combination of From address plus From name. Change the name, even on the same domain, and you reset part of the signal that drives inbox placement. Expect 2 to 4 weeks of softer open rates while the new name accumulates positive interactions.

The change is worth making when the current name is broken (truncating on mobile, mismatched to brand, defaulted by the ESP) or when the audience has outgrown the pattern. It is not worth making for cosmetic reasons or to test "warmer phrasing" if the current name works.

The right time to change is after a strong send and before a quiet period. The wrong time is during a promotional push. We learned this the hard way: we changed our own sender name mid-quarter once and watched the next three sends underperform by 9 to 11% before reputation caught up. See how spam filters score senders and how to land in the Gmail Primary tab for more on the mechanics.

To test your own From name in 60 seconds, send a draft to a Gmail address, an Apple Mail address, and an Outlook address you own. Look at each inbox list view on the device a real subscriber would use. If the name renders fully on all three, you are inside the safe zone. If it truncates on Gmail iOS, you have a problem your dashboard will not flag. The reverse-engineer competitor newsletters walkthrough has the wider sender-setup checklist.

Frequently asked questions

What should I put in the From name of a newsletter?

For most newsletters, the highest-performing format is Person from Brand (for example, "Patrick from Stripe"). It pairs a human name (which lifts opens in Gmail Primary) with a brand reference (which prevents the "who is this?" problem). Pure first-name works for solo creators where the audience already knows you. Pure brand works for ecommerce and transactional-heavy lifecycle programs. Avoid appending "Newsletter" or "Updates" as a suffix, it adds characters that almost always get truncated and signals promotional intent to Gmail.

How long can a newsletter From name be?

Aim for 18 to 22 characters to render fully on mobile. Gmail iOS truncates around 22 characters and Apple Mail iOS around 30. Gmail web shows roughly 25. Outlook desktop tolerates 40-plus. The address-book entry on a recipient's phone is the worst case, so we plan to the Gmail iOS limit and treat anything that renders fully on Outlook as a bonus.

Should I use my name or my company name?

Use your name (or a named person at your company) for B2B SaaS, creator newsletters, and any list where personality is part of the product. Use the brand name for ecommerce, transactional-heavy lifecycle programs, and lists with high subscriber turnover where the brand is the only consistent anchor. The tradeoff is trust versus recognizability: a human name reads warmer but a brand name is what most subscribers type into inbox search three weeks later.

Does changing the From name hurt deliverability?

Yes, temporarily. Gmail and Outlook keep engagement reputation against the combination of From address plus From name. Changing the From name resets part of that signal and you should expect open-rate softness for two to four weeks while the new name accumulates positive interactions. Schedule the change after a strong send and avoid changing it during a promotional push.

What is the difference between From name and From address?

The From name (RFC 5322 display-name) is the human-readable label, like "Patrick from Stripe". The From address (addr-spec) is the actual mailbox, like [email protected]. Most email clients show only the name once it is set, so subscribers rarely see the address. Both fields contribute to deliverability reputation, but recipients judge whether to open based on the name.

Related reading