Content6 min read
Newsletter Formatting: Turning a Blog Post Into an Issue
A blog post and a newsletter issue are the same words in a different container. The reader is what changed, and the reader is in an inbox with a thumb.
Newsletter formatting is mostly not rewriting. A blog post and a newsletter issue are the same words in a different container, and what changed is the reader: the blog reader arrived on purpose and will scroll, while the newsletter reader is in an inbox, on a phone, with a thumb, reading the subheads to decide whether to read anything.
So the work is adding the navigation the post did not need and the email does.
Sections, and where they break
The unit a newsletter reader skips is the section, not the paragraph. That makes the section length the main formatting decision.
- Around 120 words — about thirty-five seconds. The shape for a links-and-notes issue where the
reader is picking rather than reading.
- Around 220 words — about a minute. The default for an essay-shaped issue.
- Around 400 words — nearly two minutes. Works when each section is genuinely one argument, and
fails the moment it is two.
Break at paragraph boundaries and nowhere else. A section that runs slightly long reads better than an argument cut in half, and a paragraph is the smallest unit you actually composed.
If the post already has headings, use those. Your own structure is better information than a word count, and overruling it with arithmetic produces sections that end mid-thought.
FreeMentioned in this article
Newsletter Section SplitterA long post, cut into newsletter sections at the seams it already has.Subheads are the most-read line in the email
In a blog post a subhead is signposting. In an email it is the thing a skimming reader reads instead of the paragraph, and a substantial share of your readers will read nothing else.
That has two consequences.
The first is that a subhead should say something rather than label something. "The temperature problem" labels. "Your kitchen is colder than the recipe assumes" says. The second reads as a complete thought on its own, which is exactly the job.
The second is that generated subheads are dangerous. A placeholder that reads like finished editorial is the one that ships, so if you are drafting them automatically, keep them visibly unfinished — in brackets, in caps, anything that makes an unedited one obvious before send.
The intro is a separate decision
The paragraph above the first subhead is doing a different job from the rest of the issue: it decides whether there is a rest of the issue.
Keep it short and keep it unheaded. A heading above the first paragraph reads as the start of a section, which pushes the "should I read this" moment further down and gives the reader an obvious place to stop.
The subject line is the same problem one level up, and it is the only formatting decision that affects whether any of this is seen at all. Email subject line length and preheader text cover the two lines that arrive before the email does.
The clipping limit nobody mentions until it happens
Gmail truncates a message past roughly 102KB and shows a "View entire message" link — a limit it documents in its bulk sender guidelines.
That sounds generous and is not, because the figure counts HTML rather than words — a template with heavy markup can clip a fairly short issue. When it clips, three things break at once: the end of your email is not read, the tracking pixel frequently sits below the cut, and your open rate quietly becomes a different number.
Practical mitigations, in order of effect:
- Write shorter issues. Around 1,000 words of body copy is comfortable in most templates.
- Use fewer nested layout blocks. Most of the 102KB is usually structure, not prose.
- Move the long thing to the web. A "read the rest" link is not a failure — it is what the
blog post was already for.
A contents block, and when it earns its place
A list of the subheads at the top helps above about five sections and is noise below it. Under five, the contents block is longer than the distance it saves.
Past about eight sections it stops helping too, for a different reason: at that length, people read the contents block instead of the email. If an issue needs a contents block to be navigable, it is usually two issues.
Newsletter formatting that travels badly
Email clients render less than you expect, and the ones that render least are the ones with the most business readers.
- Tables survive, and are painful on a narrow screen. Two columns is the practical maximum.
- Custom fonts frequently do not load. Set a real fallback stack and check what it looks like.
- Emoji render, mostly. A few do not, and the ones that fail are the newer ones —
why an emoji is not showing covers which.
- Wide images are resized by the client, not by you, and often badly.
Text that was copy-pasted from a document is the other reliable source of trouble: curly quotes are fine, but zero-width characters and non-breaking spaces travel invisibly and turn up as boxes. Invisible characters covers finding them.
The same post, three containers
Once a post is sectioned, it is close to being three things — the post, the issue, and a set of social posts drawn from the sections.
That is the actual argument for doing the sectioning deliberately rather than pasting the post into the email and hoping. Content repurposing covers the wider version of this, and the sections are the natural seams.
How long should a newsletter section be?
About a minute of reading — roughly 220 words. A section is the unit a reader skips, so anything past two minutes gets scrolled past whole.
Should a newsletter have subheads?
Yes. In an email the subhead is what a skimming reader reads instead of the paragraph, which makes it the highest-leverage line in the issue.
Why does Gmail cut off my newsletter?
It clips messages past roughly 102KB of HTML. The cut usually takes the tracking pixel with it, so open rates drop at the same time.
How long should a newsletter be?
Around 1,000 words of body copy sits comfortably inside most templates without clipping. Longer issues are better split or moved to the web.
Can I just paste my blog post into the email?
The words, yes. The structure, no — a post written for a reader who chose to be there needs sections and subheads before it works in an inbox.
Paste the post into the newsletter section splitter and it will break it at paragraph boundaries with a placeholder subhead per section.
Put it to work
Tools for the job you just read about
Free to run, most of them without an account.
FreeContent
Newsletter Section Splitter
A long post, cut into newsletter sections at the seams it already has.
Split →
FreeContent
Bio Builder per Platform
One set of facts about you, built to each network’s actual bio limit.
Build →2 runs
FreeContent
Keyword Cluster Splitter
A keyword dump, grouped into the topics that should each be one page.
Split →
FreePreviews
Google SERP Snippet Preview
See your title and description as a Google result — on a desktop and a phone.
Preview →5 runs
FreeUtilities
Social Media URL Cleaner
Strip the tracking off a link — and see what each parameter was telling somebody.
Clean →1 runs
FreeAnalytics & growth
Instagram Money Calculator
What to charge for a post — priced the way a brand actually prices it.
Calculate →
Keep reading
More from the blog
Content4 min read
Preheader Text: The Half of Your Email Preview Nobody Writes
Leave the preheader empty and every inbox fills it from the first text in your email — usually a link nobody clicks. It is the cheapest fix in email marketing.
Content4 min read
Content Repurposing: One Video, a Fortnight of Posts
Content repurposing works when it is planned before the piece is made. Here is a mapping from one long video to a fortnight of posts across platforms.
Content5 min read
What to Put in a Pinned Comment
The pinned comment is the only part of a published video you can still edit. That is what it is for: the things that change, and the thing you got wrong.