Introduction
Somewhere in every marketing team, someone says it: “We should try plain text. Apparently it gets way better engagement.”
They’re repeating a claim that’s been circulating for years, usually attached to a case study where a plain-text version beat a designed one. And there’s something intuitively right about it. Plain text feels personal. It looks like a message from a human rather than a brand.
But the claim has a problem that almost nobody mentions, and once you know about it, most of the evidence falls apart.
You cannot track opens in a true plain-text email. Open tracking works by loading a tiny invisible image. Plain text can’t contain images. So when a study reports that plain text had a higher open rate, it is reporting a number that could not have been measured — which means whatever was tested wasn’t really plain text at all.
This guide clears that up. What the two formats actually are, what the evidence does and doesn’t show, which one to use for each type of email you send, and why the real answer is usually “both at once.”
Quick Answers
Does plain text get better engagement than HTML?
Not inherently. Plain text often wins for one-to-one and onboarding emails where a personal tone matters, while HTML wins where images and layout help the reader. The format matters far less than relevance and timing.
Can you track opens in a plain-text email?
No. Open tracking requires an invisible image, and plain text can’t contain images. Any study comparing open rates between the two formats is not measuring true plain text.
Is plain text better for deliverability?
Not by itself. What matters is your sender reputation, authentication and engagement, not your format. A poorly built HTML email can cause problems, but a well-built one doesn’t.
What’s the best approach?
Send both. Nearly every email platform sends an HTML version with a plain-text alternative attached, and each recipient’s app picks whichever it can display.
So why do plain-text tests sometimes win?
Usually because they’re testing tone, not format. A short, personal message beats a polished promotional one in certain contexts — and that would be true even if both were HTML.
What Each Format Actually Is
Plain text is exactly what it sounds like: letters, numbers and line breaks. No fonts, no colours, no images, no buttons, no layout. Links appear as full URLs the recipient can click. It’s what you’d get if you typed in Notepad and hit send.
HTML email uses code to control how the message looks: typefaces, colours, images, columns, buttons, spacing. Almost every marketing email you receive is HTML.
And then there’s the one that confuses everything:
Plain-text-styled HTML. This is an HTML email designed to look plain. Black text, a simple system font, no images, no header banner, links in blue, left-aligned, no containing box. It looks like a personal email but it’s HTML underneath.
This third category is what most “plain text” marketing emails actually are. It matters because it has all the tracking and formatting capability of HTML while borrowing the intimacy of plain text. When a case study says plain text outperformed HTML, it’s usually this.
Why the “Plain Text Wins” Studies Don’t Hold Up
Four problems run through most of the evidence.
1. The open-tracking problem. As above, true plain text can’t be tracked for opens. If a test reports open rates for both formats, one of two things is true: the “plain text” version was really styled HTML, or the open figure was estimated from clicks. Either way it isn’t the comparison it claims to be.
2. They’re testing tone, not format. The typical plain-text test sends a short, personal, first-person message against a designed promotional campaign with a banner and a product grid. Of course they perform differently. But the difference is the writing and the intent, not the markup. Write the same short personal message in simple HTML and you’d likely see the same result.
3. Open rates aren’t reliable anyway. Privacy features now load images automatically in many mail apps, which registers opens that no human caused. Any comparison built on open rate is standing on soft ground. The metrics glossary explains what each figure does and doesn’t tell you.
4. Novelty effect. When your list is used to receiving designed emails, a plain one stands out. That advantage fades once plain becomes your norm. A single test captures the novelty; it doesn’t capture what happens by email number eight.
None of this means plain text is worthless. It means the question “which format gets better engagement?” is the wrong question. The right one is: what is this specific email trying to do, and which format serves that better?
What Each Format Is Genuinely Good At
Where plain text (or plain-looking) wins
It feels like a person wrote it. For anything that should read as one-to-one — a founder’s note, a check-in, a follow-up from a salesperson — a design frame actively undermines the message.
It renders identically everywhere. No broken layouts, no images failing to load, no dark mode surprises, no rendering quirks between mail apps. What you send is what they see.
It loads instantly and is tiny, which matters on a slow mobile connection.
It’s accessible by default. Screen readers handle it cleanly, because there’s no layout to interpret.
It invites replies. Something about a designed email signals “do not reply.” A plain one signals the opposite — and replies are both useful feedback and a positive signal to mailbox providers.
Where HTML wins
When the product is visual. If you sell clothing, furniture or food, showing the thing is the entire job. A URL is not a substitute for a photograph.
When structure aids comprehension. Multiple stories, a comparison, an order summary, a set of steps — these are far easier to scan with headings, spacing and visual hierarchy.
When you need a clear, single action. A button is more clickable than a bare link, and it’s more obvious on a phone.
When you need to measure properly. Clicks are trackable in both formats, but HTML gives you a cleaner picture, including which element in a message drove the action. That feeds into your campaign reports and makes A/B testing more useful.
When brand consistency matters. For a well-known brand, an unbranded email can read as suspicious rather than personal.
The Deliverability Myth
The second thing people say about plain text is that it “lands in the inbox better.” This is mostly folklore.
Mailbox providers don’t decide placement based on whether your email contains markup. They decide based on your sending reputation, your authentication setup, and how recipients react to your mail.
Where the myth comes from is a kernel of truth. Certain things do hurt deliverability, and they happen to be HTML problems:
A single large image with almost no text. Filters can’t read an image, so this pattern looks like something to hide.
Bloated or broken code. Messy markup from some builders can trip filters.
A missing plain-text alternative. Sending HTML alone, with no plain-text version attached, is a small negative signal.
Too many links, especially to unfamiliar domains.
Fix those and your HTML delivers perfectly well. What actually drives inbox placement is authentication — set up properly in domains — plus list quality and engagement. The deliverability guide covers it fully.
The one genuine deliverability point in plain text’s favour: it’s physically impossible to make an image-only plain-text email. The format protects you from one specific mistake. That’s a modest advantage, not a reason to abandon HTML.
The Answer Most People Miss: Send Both
Here’s the part that resolves the debate.
Email supports a format called multipart/alternative. It means a single message carries two versions — the HTML one and a plain-text one — and the recipient’s mail app displays whichever it can handle. The reader never sees two emails. They just see the version that works for them.
Nearly every email platform does this automatically, including NevTan Engage. Which means for most senders, “plain text vs HTML” was never an either/or.
But there’s a catch worth checking. Many platforms auto-generate the plain-text version by stripping the code out of your HTML, and the result is often a mess: stray characters, missing context, raw URLs in odd places, a call to action that no longer makes sense.
Hardly anyone reads the plain-text version, so hardly anyone checks it. Two reasons to check it anyway:
Some readers genuinely receive it — certain corporate mail systems, older devices, smartwatches, screen readers.
Filters read it. A garbled plain-text part is a small negative signal.
Spend ten minutes once: open the plain-text version of your main template, tidy it up, and make sure it reads as a coherent message on its own. You can review and edit this in the template editor and save it with your standard templates so every future send inherits a clean version.
Which Format for Which Email
A practical breakdown.
Email type | Use | Why |
|---|---|---|
Welcome email | Plain-styled | Feels like a greeting, not a pitch |
Onboarding sequence | Plain-styled | Reads as help; encourages replies |
Founder or personal note | True plain text | Any design undermines the point |
Sales follow-up (B2B) | True plain text | Should match how the rep normally emails |
Newsletter | HTML, lightly designed | Multiple stories need structure |
Promotional or sale | HTML | The offer and products need visual weight |
Product launch | HTML | People need to see it |
Cart recovery | HTML | The product image is the whole message |
Order confirmation | HTML | Tables and order detail need structure |
Shipping update | Plain-styled or simple HTML | Short, functional, one link |
Re-engagement | Plain-styled | A quiet, human tone outperforms a loud one |
Review request | Plain-styled | A personal ask gets more responses |
Event invitation | HTML | Date, time, location and a clear action |
Two patterns run through that table.
The more personal the intent, the plainer the format. Anything that should feel like it came from an individual works better without design.
The more visual or structured the content, the more HTML earns its place. Products, data, multiple items, anything with an order summary.
For B2B specifically, plain text has a real structural advantage: it matches what the recipient’s colleagues send them all day. A designed email in a B2B inbox announces itself as marketing. See B2B lead gen and, for product onboarding, SaaS onboarding and retention flows.
How to Write a Plain-Looking Email That Works
If you go plain, commit to it. A half-designed email looks broken rather than personal.
Write like an email, not a campaign. First person, direct address, normal sentences. If it reads like it was written by a committee, the format can’t rescue it.
Keep it short. Plain text with no visual hierarchy is hard to scan, so length hurts more here than in HTML. Short paragraphs, plenty of line breaks.
Use one link, maybe two. Without buttons to guide the eye, multiple links compete and none wins.
Send from a person, not a department. “Priya at [Brand]” beats “[Brand] Marketing Team.” If the email reads as personal, the sender name should too.
Use a real reply-to address and let people reply. A personal-looking email from a no-reply address is a contradiction the reader will notice.
Match the subject line to the tone. A plain, understated subject suits a plain email. All-caps urgency does not. See the subject line testing framework.
Resist adding one image. A single logo at the top undoes the entire effect. Either commit to plain or build it as HTML.
Don’t fake intimacy at scale. A message claiming to be a personal note from the founder, sent to 200,000 people with a tracked link and an unsubscribe footer, reads as a tactic. Personalisation should be real. See personalised emails and customer retention.
How to Test It Properly
If you want to know what works for your audience, test it — but test it in a way that produces a real answer.
Hold the content constant. Same message, same offer, same subject line, same send time. Change only the format. If you also change the copy, you’ve learned nothing about format.
Measure clicks and conversions, not opens. Opens are unreliable generally and unmeasurable in true plain text. Revenue or conversion per recipient is the number that matters. Our guide to email attribution covers how to connect that properly.
Run it more than once. The first plain email outperforms partly because it’s unfamiliar. Run the test three or four times before concluding anything.
Test by segment. Format preference varies a lot between audiences. Your long-term customers and your new signups may respond very differently, which is an argument for testing within segments rather than across your whole list. If segmentation is new, start with customer segmentation 101.
Don’t test it on everything. Some emails obviously need HTML. Testing a plain-text version of your product launch is time you won’t get back.
Common Mistakes
Believing the benchmark without reading the method. Most plain-text case studies compared tone, not format.
Ignoring the auto-generated plain-text version. It’s probably a mess, filters read it, and fixing it takes ten minutes once.
Sending HTML with no plain-text alternative. A small but avoidable negative signal.
Building an image-only email. The single most damaging format mistake, and the real source of the deliverability myth.
Half-committing to plain. One logo and a button turns “personal” into “broken.”
Using a no-reply address on a personal-looking email. It contradicts the whole premise.
Switching your entire programme to plain after one good test. The novelty wears off, and then you’ve lost the ability to show your products.
Treating format as the lever that matters. It isn’t. Relevance, timing and audience matter far more. More on that in the top mistakes businesses make in email marketing.
Quick Checklist
[ ] Every send includes a plain-text alternative alongside the HTML
[ ] The auto-generated plain-text version has been read and tidied up
[ ] No image-only emails anywhere in your programme
[ ] Personal and onboarding emails use a plain or plain-styled format
[ ] Product, promotional and order emails use HTML
[ ] Plain-styled emails send from a person with a real reply-to address
[ ] Format tests hold content constant and measure clicks, not opens
[ ] Authentication set up correctly, since that matters more than format
FAQ
Do plain-text emails get better engagement than HTML emails?
Not because of the format itself. Plain text tends to win for personal, one-to-one style messages like onboarding and sales follow-ups, while HTML wins where images, structure or a clear button help the reader. Most studies claiming plain text wins were really comparing a short personal message against a designed promotional one, which is a difference in tone rather than format.
Can you track open rates in a plain-text email?
No. Open tracking relies on loading a small invisible image, and plain text cannot contain images. This is why any comparison of open rates between plain text and HTML is unreliable — whatever was measured wasn’t true plain text.
Are plain-text emails better for deliverability?
Not inherently. Inbox placement depends on sender reputation, authentication and recipient engagement, not markup. Plain text does prevent one specific mistake, since you can’t accidentally send an image-only email, but a well-built HTML email delivers just as well.
What is a multipart email?
A multipart (specifically multipart/alternative) email carries both an HTML version and a plain-text version in one message. The recipient’s email app displays whichever it can render. Most email platforms do this automatically.
Should I write the plain-text version myself?
It’s worth doing once for your main template. Auto-generated versions are created by stripping out the code and often read poorly. Since filters read that version and some recipients receive it, a tidy one is worth ten minutes of effort.
When should I use true plain text instead of plain-styled HTML?
Use true plain text when the email should genuinely read as a one-to-one message, such as a B2B sales follow-up or a personal note. Use plain-styled HTML when you want that look but still need reliable click tracking and a little formatting control.
Do plain-text emails work for e-commerce?
For some emails, yes — shipping updates, review requests and re-engagement messages all work well plainly. But anything where the product itself is the message, like a launch or cart recovery, needs HTML. The e-commerce email marketing playbook covers which is which.
Does plain text help with Apple Mail Privacy Protection?
Not in a useful way. Privacy protection affects open tracking, and plain text simply removes open tracking altogether. Neither gives you better data; both are reasons to measure clicks and conversions instead.
Is HTML email outdated?
No. HTML remains the right choice for anything visual or structured, which is most commercial email. What has changed is that heavily designed, image-dense templates have fallen out of favour in favour of lighter, simpler layouts. See email design best practices and designing for mobile-first inboxes.
Which format should a beginner start with?
A light HTML template with a clean plain-text alternative. It covers every situation, renders well, and gives you proper measurement. The beginner’s guide to email marketing walks through setting one up.
Build Both Versions in One Place
The real answer to plain text versus HTML isn’t a choice. It’s sending a well-built version of each and letting the format follow the purpose of the email.
With NevTan Engage, every email campaign goes out with both versions attached, and you can edit the plain-text part rather than leaving it to a stripped-out auto-generation. Build a lightly designed template or a plain-styled one in the template editor, start from a ready-made template, or draft one quickly with AI templates — then compare how each performs in campaign results.
See how it works for e-commerce, SaaS and agencies, or compare plans.
Create your free account and send your first campaign in ten minutes.
