Newsletter format: the complete guide
Every newsletter has a format, whether its writer chose one or not. Some chose it deliberately: one essay, every Sunday, always the same shape. Others drifted into it, adding a section here and a sponsor block there until each issue looked a little different from the last. Readers notice the difference long before they could explain it.
This guide covers the decisions behind a good format, from the type of newsletter to the technical limits that decide whether it arrives intact.
What "format" actually means
A newsletter format is the repeatable shape of each issue: what kind of content it carries, in what order, at what length and with what layout. A good format makes the newsletter recognisable at a glance, easier to write every week and easier for readers to scan, and it stays the same from issue to issue.
Format is not the same as design. Design is how an issue looks: colours, fonts, spacing. Format is the structure underneath: an opening note, then three stories, then links, then a sign-off. You can redesign a newsletter without changing its format, and you can keep a design while the format slowly falls apart.
A clear format does three jobs at once. It tells readers what to expect, so they know whether to read now or later. It makes the writer's week easier, because there is a slot to fill rather than a blank page. And it makes the newsletter recognisable in a crowded inbox, which matters more than any single subject line.
The main types of newsletter
Most newsletters fit one of six types: the personal letter, the long-form essay, the links roundup, the fixed-section digest, the single story, and the multi-section magazine. Each suits a different kind of writer, frequency and reader, and mixing them is the most common reason a format feels unclear.
The personal letter. One person writing to readers, with little or no design. It reads like an email from a friend, and providers tend to treat it like one. Best for writers whose voice is the product. See the Plain Letter template.
The long-form essay. One substantial piece per issue, with a heading structure and room for quotes. Best for analysis and opinion. The format lives or dies on line length and type size. See Long-form Essay.
The links roundup. A set of links, each with a line or two on why it matters. The value is the selection and the comment, not the links themselves. See Links Roundup.
The fixed-section digest. The same sections every issue, filled with the week's material: news, numbers, what is coming. Best for local, industry and company newsletters, because readers learn where to look. See Weekly Digest.
The single story. One story, often led by one image, with a link to read more. Good for publications that want each issue to feel like an event. See Single Story with Image.
The magazine. Several sections with a clear hierarchy, for newsletters that carry a lot. It is the hardest to keep readable on a phone and the easiest to bloat. See Magazine Multi-section.
Pick one as the base. You can add a small recurring element from another, such as a short links section at the end of an essay, but the base should be obvious.
Structure: the parts of an issue
Most effective newsletters share the same skeleton: a header that identifies the publication, an opening line that sets up the issue, the main content, one clear call to action, a sign-off, and a footer with the unsubscribe link. Keeping that skeleton fixed lets readers find their way around every issue.
Whatever the type, an issue usually needs:
- A header that says whose newsletter this is. A name in text is enough. A logo image is optional and, if used, should have alt text so it still works when images are off.
- An opening. One or two sentences that tell readers what this issue is about and why it is worth their time.
- The main content, in the shape your type dictates.
- One call to action. Reply, read the full piece, register, buy. One. Several competing buttons usually means none of them gets clicked.
- A sign-off. A name, especially for personal newsletters. It reminds readers there is a person behind it.
- A footer with why the reader is receiving this, a visible unsubscribe link, and a postal address where the law requires one.
Length and frequency
There is no ideal newsletter length. Match length to the type and frequency: short notes for frequent sends, longer issues for weekly or monthly ones. What matters more is consistency, because readers learn how much time each issue asks of them, and long HTML has a technical limit in Gmail.
A daily newsletter that takes fifteen minutes to read will not be read daily. A monthly one that takes ninety seconds will feel thin. Length should follow frequency and type, and once chosen, it should stay roughly stable.
Long issues have one hard technical limit. Gmail clips messages whose HTML exceeds 102 KB and hides the rest behind a link, including your footer and unsubscribe link. Length in words rarely gets there on its own. Heavy code does. See Gmail clipped message.
If an issue will run unusually long, say so at the top. Readers forgive length they were warned about.
Layout: one column, around 600 pixels
Most newsletters use a single column between 560 and 640 pixels wide, because it reads well on desktop and shrinks cleanly to a phone. Two-column layouts can work, but they need careful code to stack on small screens, and most reading now happens on phones.
A single column is the default for good reasons. It is easy to read, it scales down to a phone without rearranging anything, and it is the hardest layout to break across email clients. Most templates set a maximum width of around 600 pixels, which keeps lines comfortable on a desktop. More on widths and images in email width, images and alt text.
Two columns work for visual content, such as product grids or paired stories, provided the code makes them stack into one column on a phone. Otherwise readers zoom and scroll sideways, and they stop doing that quickly. See responsive email design.
Subject line and preheader
The subject line and the preheader are the only parts of an issue a reader sees before opening. Treat them as a pair: the subject says what the issue is about, and the preheader adds the reason to open now. Never leave the preheader empty, or the email client fills it with whatever text comes first.
These two lines decide whether the rest of your format ever gets seen. The subject line should say what is inside, in words the reader would use. The preheader, the grey text shown next to or below the subject, should add something the subject did not.
If you do not set a preheader, most clients show the first text in the email, which is often "View in browser" or your logo's alt text. Both waste the space. Guides to each: newsletter subject lines and email preheader.
Typography
Use a font stack that starts with your preferred font and falls back to a system font every client has, such as Arial or Georgia. Set body text at 16 to 18 pixels with generous line height. Many email clients, including Gmail, ignore custom web fonts and show the fallback.
Type does most of the work in a newsletter, because most of a newsletter is text. Two rules carry most of the weight. First, body text should be at least 16 pixels, with a line height around 1.5, so it reads comfortably on a phone. Second, always define a fallback font, because many clients, Gmail among them, will not load a custom web font and will show the next font in your list. See best fonts for email newsletters.
Images
Images make a newsletter feel finished, but every image should be optional. Some clients block images by default, so the issue must still make sense without them. Give every image alt text, set its width in the code, host it on a reliable address, and avoid issues that are a single large image.
Images help, especially a lead image on a single-story issue or product photos in a business newsletter. But design every issue to survive without them. Some email clients block images until the reader allows them, and an issue that relies on an image to carry its message arrives as an empty box.
Practical rules: write alt text for every image, keep important text in real text rather than inside images, and never send an issue that is mostly one big image. That pattern is common in spam and filters treat it with suspicion.
Plain text, and why every issue needs it
Every newsletter should be sent as two versions in one message: the HTML version readers see, and a plain-text version for clients that cannot or will not show HTML. Legitimate mail usually carries both, and a missing plain-text part is one of the small signals that make a message look automated.
Email can carry two versions of the same message, an HTML one and a plain-text one, and the reader's client picks which to show. Most platforms generate the plain-text part automatically, often badly. It is worth checking yours and writing it properly for your template once.
There is also a separate question: should the issue itself look plain? Minimal, letter-style issues often do better than heavily designed ones. The case is made with real numbers in plain text vs HTML emails.
Dark mode
Many readers now see email in dark mode, and email clients handle it in different ways: some respect your dark colours, some invert your design automatically, and some leave it untouched. Test your format in dark mode, avoid text baked into images, and give logos a version that works on dark backgrounds.
A growing share of readers open email with dark mode on. Some clients apply the dark styles you define, others invert colours on their own, and the results can range from elegant to unreadable. Dark mode is covered in responsive email design. Every template in our library is checked in dark mode before it is published.
How to choose and keep a format
- Start from what you will actually write every week, not from a design you admire.
- Pick one base type from the six above.
- Write three issues in it before you send the first. If the third was hard to fill, the format is too ambitious.
- Keep the skeleton fixed for at least a few months. Change content freely, structure rarely.
- When you do change it, tell readers. A line at the top is enough.
If you want a starting point, every template in our library is built on one of these types, weighed against Gmail's limit and tested for inbox placement.
Frequently asked questions
What is the best format for a newsletter?
The one you can keep writing. For most solo writers, a personal letter or a short essay works best. For organisations, a fixed-section digest is easier to fill consistently. The best format is the one that is recognisable from issue to issue.
How long should a newsletter be?
Long enough to deliver what the subject promised, and consistent from one issue to the next. Frequent newsletters should be short. Weekly and monthly ones can run longer, as long as the HTML stays well below Gmail's 102 KB clipping limit.
Should a newsletter use images?
It can, but it must still work without them. Use images where they add information or atmosphere, give each one alt text, and keep the message in real text so the issue makes sense when images are blocked.
Does newsletter format affect deliverability?
Somewhat. Very heavy HTML, image-only issues and missing plain-text versions are small negative signals, and clipped messages hide your unsubscribe link. Format matters less than authentication and list quality, but a lean format removes several avoidable risks.