newsletter · Oct 21, 2026
What is the optimal length for an email newsletter?
How long should an email newsletter be? Practical word ranges by format, Gmail's 102 KB clipping limit, subject and preview lengths, and seven tools compared.
There is no single best length. The right size is whatever your readers can finish in the slot they've set aside for you, and that changes with the format. As a working rule (my own editorial rule of thumb, not a measured benchmark), a link digest or curation issue tends to work at 300 to 800 words, a single-idea essay at 800 to 2,000, and a long read can stretch to a few thousand if your readers signed up for exactly that. The one hard technical ceiling comes from Gmail: email tools consistently report that Gmail clips a message once its HTML passes about 102 KB, which Buttondown's own tests put somewhere between roughly 7,000 and 17,000 words depending on how much formatting and linking the issue carries.
A disclosure before we start. I work on VeloCMS, and it's one of the seven tools I look at near the end. It isn't listed first, it isn't the best fit for most people reading this, and it gets the same scrutiny as the rest, weaknesses included.
Last verified: 2026-10-21.
How long should a weekly newsletter be?
Nobody can hand you a universal number, and I'd be wary of anyone who tries. What you can do is turn words into minutes. Marc Brysbaert's meta-analysis of reading rate, covering 190 studies and 18,573 participants, estimates that adults silently read English non-fiction at an average of 238 words per minute, with most adults falling between 175 and 300 (Brysbaert, accessed 2026-10-21). Divide by 238 and the arithmetic is friendly: 500 words is about two minutes, 1,000 words about four, 2,000 about eight and a half, 3,000 about twelve and a half.
Those are lab numbers for people who are actually reading, and an inbox is a noisier place. I haven't found a trustworthy public benchmark for how long people spend on a newsletter issue, so I'm not going to quote one. What I'd do instead is pick the slot. If your issue lands on Thursday morning and your readers have a coffee's worth of attention, four to eight minutes (so 1,000 to 2,000 words) is a sensible target. If it lands daily, shorten it, because the same reader can't give you eight minutes every morning. If it lands monthly, they've been waiting, and you can go longer.
You'll find advice that says an email should be 50 to 125 words. Campaign Monitor's guide to email length does say that, but it's talking about marketing emails, it admits "these ideal lengths aren't unbreakable rules," and I couldn't find a source for that range in the piece itself (the only statistic nearby, attributed to The Atlantic, reads "50 to 25 words" and looks like a typo) (Campaign Monitor, dated February 2020, accessed 2026-10-21). A promotional blast and a newsletter people chose to read are different animals. I wouldn't apply the first rule to the second.
How do digest, essay and curation newsletters differ in length?
Format sets the range more than any rule does.
A digest is several short items stacked together, each running 50 to 150 words. Eight items lands around 400 to 1,000 words. The danger isn't the word count, it's the links. Every URL is HTML, and Buttondown's advice is to stay "under 15,000 words, or 5,000 if you have a lot of links" (Buttondown, accessed 2026-10-21). A link-heavy digest can reach the size limit well before a plain essay of the same length.
A curation issue adds your commentary to the links: a sentence or three on why each one matters. Keep it to a handful of picks. Ten links with real opinions is already a long read, and the reader who wanted "the best thing you read this week" gets a reading list instead.
An essay is one idea developed properly. Somewhere between 800 and 2,000 words is a comfortable range for one developed idea, though that's editorial taste, not a measurement. If the idea needs 400 words, send 400. Padding to look substantial is the fastest way to teach people to skim you.
A long read (3,000 words and up, a research write-up, a case study) is a legitimate format, and the only one where the technical limits below start to matter. For these, plan the web version first and treat the email as the delivery route.
Does Gmail cut off long emails?
Yes, and many new writers never hear about it. When a message is too big, Gmail shows it cut short with a "[Message clipped] View entire message" link, and the rest sits behind a click.
First, a caveat about the source. I searched for Google documentation of the limit and found none, and Tedium's 2020 history of the 102 KB limit also points to no Google document (Tedium, accessed 2026-10-21). What exists is consistent reporting from the tools that send email: Mailchimp's help article says Gmail clips emails over "a message size larger than 102KB" (Mailchimp, accessed 2026-10-21), MailerLite says Gmail may clip "if your email content is larger than 102 KB" (MailerLite, accessed 2026-10-21), and beehiiv's help article gives the same figure and advises staying under 100 KB (beehiiv, updated 2026-06-23, accessed 2026-10-21). Read 102 KB as an industry-observed figure, not a Google promise.
The size is HTML, not words and not pictures. Per beehiiv, only the code of your email counts: image file sizes don't, though the HTML needed to display images does, and each HTML character is roughly one to two bytes. That's why the same word count can clip or not clip depending on formatting. Buttondown tested it and reports that Gmail's cutoff "tends to work out to around 17,000 words of plain text, or as low as 7,000 words when there's a reasonable amount of formatting" (the same post's summary line says about 15,000 and 5,000, so even their own numbers wobble). Either way, an ordinary 2,000-word essay is nowhere near it.
So why care? Because of what gets hidden. MailerLite notes that its tracking pixel sits at the bottom of the email, and Mailchimp says clipping also clips the code that tracks opens, so a clipped email can under-report opens. (beehiiv says the opposite about itself: its open-tracking pixel sits at the top, so clipping doesn't affect its open rates.) beehiiv adds that readers who open the full message aren't tracked as clicks and that Gmail strips style tags from the clipped portion, which can change how the email looks. And the footer holds your unsubscribe link: Buttondown's warning is that "if your footer gets clipped, subscribers will mark you as spam."
How do you check? Mailchimp's method is manual: send a test to an address you control, view the source, save it to a document and read the file size. Some tools do it for you, as the comparison below shows. Fixes are mostly boring: paste text without carrying formatting along (Mailchimp's Clear Styles tool, beehiiv's "Paste and Match Style," MailerLite's Simple editor), cut images and URLs you don't need, or move the long version to the web and link to it. Kit's deliverability guide agrees on the target: "Be sure your message size is less than 100KB" (Kit, updated July 24, 2024, accessed 2026-10-21).
One more honest note. Vendor pages mention lower thresholds for other mail apps, but I didn't find a reputable, current figure for any client besides Gmail, so I'm not quoting one.
How long should subject lines and preview text be?
Mailchimp's guidance is the clearest I found from a vendor: "We recommend you use no more than 9 words and 60 characters," and "for many recipients, especially those reading your emails on mobile devices, shorter is often better" (Mailchimp, no date shown, accessed 2026-10-21). Neither Google nor Apple publishes a fixed truncation point that I could find, so treat any exact "your subject is cut at 41 characters on phone X" claim as a snapshot at best. Put the part that matters in the first few words, and the cut-off stops being your problem.
Preview text is the second half of the same line. Email on Acid says "many devices display an average of only 35-50 characters" of it, while desktop and webmail clients can show around 50 to 100 (Email on Acid, published April 2019, so dated, accessed 2026-10-21). It also warns about two traps: with no preheader, the inbox "can pull in random pieces of the email," and a very short one can be padded with filler such as "view in your browser." Kit lets you write up to 150 characters of preview text, and Kit notes that email clients will often show a snippet from the start of the email when there's no preview text (Kit, accessed 2026-10-21).
A related detail for tools that email a post as-is: Ghost's help page says it "will use the post title as the subject line" of your newsletter, which you can change from the preview area (Ghost, accessed 2026-10-21). A long headline written for search can make a clumsy subject, so check what your tool defaults to.
Should you send the full text or a teaser with a link?
This is the real length decision for anything past 2,000 words, and neither answer is wrong.
Full text keeps readers in the inbox, where they're already reading. It also carries the size risk above, and it means the email is the only place the writing lives unless you publish it on the web as well. A teaser (an excerpt and a link) keeps the email light and sends the reader to a page you control. It costs you the reader who won't click.
Two vendors recommend the teaser route for long pieces. beehiiv's article suggests publishing the full version on the web and linking to it from the email, and Mailchimp offers a Read More link that "limits the amount of content visible in your recipient's inbox" while, it says, keeping opens tracked (Mailchimp, accessed 2026-10-21). Mailchimp is upfront about a downside: links made up entirely of merge tags, which is what its Read More links are, can't be tracked in click reports.
Paid newsletters have a variation. Substack's features page lists a "free preview for paid posts (control how much non-subscribers see)" and says you can gate content behind a paywall "at any point in a post" (Substack, accessed 2026-10-21). The excerpt becomes a sales pitch for the rest.
There's also a deliverability angle. Buttondown ran its own tests and found that "length does seem to impact deliverability, at least in extreme cases," and that very long emails with heavy design can be a red flag to spam filters. That's one vendor's testing, not an industry study, and "extreme" is doing real work in that sentence. It's a reason to avoid the 10,000-word email, not to fear a 1,500-word one.
How do the major newsletter tools handle long emails?
Seven tools, each checked against its own pages on 2026-10-21, listed alphabetically (not a ranking). I'm comparing how they deal with long issues, not prices, so check each pricing page for the current numbers. Where a page didn't say something, I say so, and "I didn't find it" means exactly that, not "it doesn't exist."
At a glance:
- beehiiv: editor warning as you approach Gmail's limit; recommends a longer web version you link to yourself.
- Buttondown: warning plus a Gmail clipping estimate in the email preview; hosted archives in the base price.
- Ghost: publish-and-email or email-only; no size warning on the pages I read.
- Mailchimp: documented manual size check; Read More links built on archive merge tags.
- MailerLite: dedicated clipping help article; no size meter described on the pages I read.
- Substack: editor shows a "Your post may be truncated" message; free previews on paid posts.
- VeloCMS: post emails are an excerpt plus links by design; no size meter in the campaign composer.
beehiiv
beehiiv is the most direct of the seven about this problem. Its help article says that when your email size approaches the threshold, a warning appears at the top of the post editor, and clicking it shows the current weight (updated 2026-06-23). It also told readers back in 2021 that it had built tools to "monitor and identify newsletters that may be susceptible to clipping and warn you prior to sending" (beehiiv product blog, October 8, 2021). The same help article is candid about a few things: weight can affect spam filtering, readers of clipped mail aren't tracked as clicks, and link shorteners and branded URLs, which it says can break links and are generally incompatible with beehiiv. Its homepage lists "no-code website hosting," but the clipping article doesn't describe an automatic web version of each email, only that you can publish a longer one and link to it (beehiiv, accessed 2026-10-21).
Buttondown
Buttondown has published the most detailed testing I found, including its own word-count experiments (February 2026) and a note that it "shows you a warning when you're approaching the 102kb limit." Its changelog adds "a Gmail clipping estimate to the email preview" on October 8, 2026, and, on September 21, 2026, an improvement to the warning firing "on emails that weren't quite long enough to worry about" (Buttondown changelog, accessed 2026-10-21). That second entry is a useful reminder that these warnings are estimates. Its pricing page lists "Hosted newsletter archives" and a "Rich text or markdown editor" in the base price, while archives on a custom domain are an add-on (Buttondown pricing, accessed 2026-10-21). It's the right choice if you like a small independent tool and care about plain text and markdown, though the add-on model means long-form publishing with a branded archive costs more than the headline price.
Ghost
Ghost treats the web post and the email as the same piece of writing. Its help page lists the options "Publish and email," "Publish only" and "Email only," says the newsletter template is a "clean, optimized HTML email template," and lets you send a test to yourself before the real send. Email cards let you add content that is "only visible in emails" (Ghost changelog, April 2020). What I didn't find is any official page about email size, Gmail clipping or a size warning, so with Ghost you'd rely on your own test sends. Community threads on the Ghost forum from 2021 and 2024 show users working around the lack of a built-in "send an excerpt instead of the full post" option by hand (Ghost forum); no staff reply appeared in that thread, so treat it as community experience, not an official position.
Mailchimp
Mailchimp has long-standing help material on clipping, but the process it describes is mostly manual. The help article says to send a test, view source, save it and check the file size, or to use its Inbox Preview. If you can't cut content, it points you to a Read More link, which takes some setup (per Mailchimp's separate Read More help page): you put teaser text in a block, link "Read More" to the *|ARCHIVE|* merge tag and wrap the remainder in *|IF:ARCHIVE_PAGE|* conditional tags. That's powerful and a bit fiddly for a beginner. The page shows no revision date, only a 2001 to 2026 copyright range, so I can't tell you how recently the advice was reviewed.
MailerLite
MailerLite's clipping article is short and practical: keep the email under 102 KB, minimize your code (saving that step for last), and paste through its Simple editor to avoid extra formatting. It's open about the tracking pixel being at the bottom of the email. A second help page notes the HTML editor has a 1 MB upload limit and that emails "exceeding certain sizes are more likely to be flagged by Internet Service Providers" (MailerLite, last edited March 5, 2024). I didn't find a size meter in the editor described on either page, so assume you'll check with a test send.
Substack
Substack's help center blocked my automated fetch (HTTP 403), so I can't quote its article. Its title is verifiable from search listings, though: "Why does it say 'Your post may be truncated' in the post editor?" (Substack support), which tells you the editor warns about truncation. A search summary of that article describes an estimate of the email version's size with a milder warning near the limit and a stronger one past it, and says the post still displays fully on the web, but I couldn't read the page myself, so open it for the exact threshold and what the warning measures. What I could read on the features page is that every post can be sent as an email, email send can be toggled per post, and paid posts can show a free preview. The paywall-anywhere control makes Substack the most natural fit for the "excerpt first, rest for subscribers" pattern.
VeloCMS
VeloCMS is a blog CMS with a newsletter attached, so its default for long posts is the teaser route. When a published post is sent to subscribers, the email carries the post title, the post's excerpt (or, if you haven't set one, the first 500 characters of the post's markdown), a link to read the full piece, and a "view in browser" link, both pointing at the post on your own site. The subject line is the post title. Posts restricted to members get a teaser to non-entitled subscribers instead of the body. The practical tip is to write a real excerpt, because the 500-character fallback is a raw cut. The web page is your archive, since the post lives on the blog.
The honest limits are on the custom campaign side. The campaign editor is block-based (headings, paragraphs, buttons, images, dividers and a rich-text block), has a preheader field capped at 200 characters with an on-screen hint to aim for 85 to 100, and can send a test to yourself. I searched the newsletter code and found no size meter or Gmail clipping warning, and the campaign send path adds an unsubscribe footer and the one-click unsubscribe headers but no automatic "view in browser" link. Merge tags cover first name, email, tier, the unsubscribe URL and custom fields, with no tag for a web-version link, so you'd paste a link to the post by hand. It's a young product with a smaller ecosystem than Ghost, Mailchimp or Substack and it isn't a dedicated email platform with deep automation. Pro is $9 a month with up to 5,000 subscribers; every plan starts with a 14-day trial (card required unless you have a cardless trial code), first charge on day 15, and there is no free plan (VeloCMS pricing, accessed 2026-10-21).
How do you test the right length for your own list?
Start with the cheap, mechanical check: send yourself a real test and measure it, using Mailchimp's view-source method or your tool's size warning. If an issue is within sight of 100 KB, fix that before you ask any question about taste.
Then look at signals that survive. Apple's documentation says Mail Privacy Protection "prevents senders from seeing if you've opened the email they sent you" (Apple, accessed 2026-10-21), and as you've seen, a clipped email can hide the open pixel from Gmail readers too, depending on where your tool puts it. So open rate is a weak yardstick for length. Replies, clicks, forwards and unsubscribes are better, because each needs a person.
A simple experiment looks like this:
- Pick two lengths for the same kind of issue, say about 800 words and about 1,800.
- Alternate them across your normal schedule so topic and timing average out.
- Log replies, clicks on the main link and unsubscribes for each issue.
- Compare after a handful of issues of each. I won't name a "statistically significant" number, because with a small list there isn't one, and anyone who gives you a sample size without knowing your list is guessing.
Then ask. One line at the bottom of an issue ("too long, too short or about right?") gets you more than a dashboard. Readers who bother to reply are exactly the ones who'd tell you their reading slot.
Who is each option best for?
- beehiiv: writers who want a clipping warning built into the editor and are happy to publish long versions on the web.
- Buttondown: people who want an independent, markdown-friendly tool with a clipping estimate and hosted archives.
- Ghost: publishers whose posts live on the web first and go out by email second, with membership as the business.
- Mailchimp: teams that already use it and don't mind a manual size check and merge-tag Read More links.
- MailerLite: small lists that want a plain email builder and will test sizes by hand.
- Substack: paid-newsletter writers who want free previews and a paywall inside the post.
- VeloCMS: someone who wants posts, newsletter and membership under one login, publishes essays on their own site and emails an excerpt with a link.
When is VeloCMS the wrong choice?
If you want long-form text delivered whole into the inbox with a built-in size meter, beehiiv or Buttondown give you that and VeloCMS doesn't. If your newsletter already lives on a different site and you only need an email tool, moving a whole site for the sake of an excerpt feature is a big job; a standalone newsletter tool fits better. If you need heavy automation, A/B testing or a large integration catalogue, the tools above go deeper. And if you want a free plan, there isn't one.
FAQ
Is there an official Gmail word limit? Not that I could find. Google doesn't document it on pages I could locate, but Mailchimp, MailerLite, beehiiv and Buttondown all report clipping around 102 KB of HTML (Mailchimp).
Do images count toward the 102 KB? The image files don't, but the HTML that displays them does, according to beehiiv's help article (beehiiv).
How many words is 102 KB? It depends on formatting and links. Buttondown's tests found roughly 17,000 words of plain text or as few as 7,000 with a reasonable amount of formatting (Buttondown).
How long should preview text be? Email on Acid says many devices show only 35 to 50 characters, so put the key point first; Kit allows up to 150 characters in the field (Email on Acid, Kit).
Should a long newsletter be split into two issues? Often yes. If one idea needs 4,000 words, a two-part series or a web version with an email teaser is easier on readers and on Gmail. That's my judgment; beehiiv and Mailchimp both suggest linking to a longer web version.
Is shorter always better? No. Campaign Monitor's own caveat is that some marketing emails "should be length by design" (Campaign Monitor). Length that carries the promise is fine; length that postpones it isn't.
Sources (all accessed 2026-10-21)
Brysbaert, "How many words do we read per minute?" (author manuscript) · Campaign Monitor, email length · Tedium, Gmail 102 KB history · Mailchimp, Gmail is clipping my email · Mailchimp, Read More link · Mailchimp, subject lines · MailerLite, Gmail clipping · MailerLite, HTML editor limits · beehiiv, email weight and Gmail clipping · beehiiv product blog · beehiiv · Buttondown, email length and deliverability · Buttondown changelog · Buttondown pricing · Ghost, delivering emails · Ghost changelog, email cards · Ghost forum thread · Kit, email deliverability · Kit, preview text · Email on Acid, preheader length · Substack features · Substack support, post may be truncated · Apple, Mail Privacy Protection · VeloCMS pricing