← Back to blog

When a Plain-Text Email Beats Your Designed Template (And How to Test It Properly)

13 October 2026·5 min read
Quick answer: A plain-text email genuinely outperforms a designed HTML template more often than most businesses expect, especially for reminders, follow-ups and anything that should feel like it came from a real person rather than a brand. The only honest way to know which wins for your list is a proper split test — same subject line, same send time, same offer, random 50/50 split, measured on clicks and conversions rather than opens. It's not a universal rule either way. 🤍

Somewhere along the way, "professional" started meaning "has a logo, a header image, and three brand colours," and plenty of businesses now default to a designed template without questioning it. 💖 But we've run this test enough times to know plain-text regularly wins for exactly the emails people assume need the most polish — payment reminders, booking confirmations, re-engagement nudges. It looks like it came from a person, not a campaign, and that changes how it gets read.

What most businesses get wrong

The biggest mistake is assuming more design effort automatically means a better result — it doesn't, and for transactional or relationship-driven emails it can actively work against you by making the message feel like marketing rather than a genuine update. The second mistake is judging any email test on open rate alone. Since Apple's Mail Privacy Protection rolled out in 2021, a huge share of opens are pre-fetched automatically by Apple's servers regardless of whether a human ever looked at the email, which makes open rate an unreliable metric for a meaningful chunk of most lists. Clicks and downstream conversions are a far more honest signal of what actually worked.

The plain-text vs HTML split test method:
  • 1. Pick one send, one goal. Choose an email with a single clear CTA (book now, pay this invoice, read this update) — don't test a newsletter with ten competing links, it muddies the result.
  • 2. Hold everything else constant. Same subject line, same send time, same list segment, same offer — the only variable that changes is format. Changing two things at once means you'll never know which one actually mattered.
  • 3. Split the list randomly, 50/50. Most ESPs have a built-in A/B split feature — use it rather than manually dividing the list, to avoid accidentally biasing the split.
  • 4. Build a genuine plain-text version, not a fake one. Send it as an actual text/plain email, not an HTML email dressed up to look plain — a real plain-text send behaves differently in terms of deliverability and rendering than HTML pretending to be simple.
  • 5. Mirror the content and CTA exactly. Same core message and same link (with identical UTMs) in both versions, so you can cleanly compare click and conversion data without wondering if a wording change caused the difference.
  • 6. Measure clicks and conversions, not opens. Track click-through rate and, ideally, what happened after the click (booked, paid, replied) as your real success metric.
  • 7. Repeat across at least three sends. One send can be a fluke — a consistent pattern across several sends is what you actually act on.
A booking-based business testing appointment reminders: A plain-text reminder that reads like a quick personal note ("Hi [name], just confirming you're in for Thursday at 2pm — reply if you need to reschedule") consistently beat a branded HTML reminder with a logo and a big "confirm" button, likely because it read as genuinely personal rather than automated.
A B2B firm with a long sales cycle testing a follow-up nurture email: A plain-text follow-up that looked like it was typed directly by the account manager outperformed a designed HTML nurture template on reply rate — prospects engaged with it more like an email from a colleague than a drip campaign.
A local service business testing a seasonal promotional offer: This is the scenario where HTML genuinely held its ground — a visual, product-led promotion with a clear discount and imagery performed roughly the same or better designed, which is a useful reminder that plain-text isn't automatically superior for every message type.

Setting up the test properly

Check your ESP's A/B testing feature actually supports a true plain-text send rather than just stripping styling from the HTML version — some platforms fake it, and the rendering difference matters. Keep personalisation tokens (first name, appointment detail) consistent across both versions so that's not an accidental variable either. If your list is small, run the same test across three or four separate sends over a few weeks rather than relying on one thin-sample send. Don't skip checking inbox placement if your ESP reports it — plain-text and HTML sometimes land differently, which can itself explain part of the performance gap.

💡 Write the plain-text version like it's from a real person, not a "do not reply" blast. Sign it with an actual name, keep the sentence structure conversational, and make sure the reply-to address genuinely goes somewhere monitored — half of plain-text's advantage comes from it actually being replyable.

Mistakes to avoid

  • Changing the subject line or send time between versions along with the format — isolate one variable at a time.
  • Judging the result on open rate alone, which is skewed by Apple Mail Privacy Protection.
  • Running the test once on a small list and treating the result as conclusive.
  • Faking a "plain-text" email by stripping styling from HTML instead of sending genuine text/plain.
  • Assuming the result from one email type (e.g. reminders) automatically applies to a different type (e.g. promotions).

Frequently asked questions

Does plain-text always win?

No — and this is the honest nuance most "plain-text wins" takes skip. It tends to win for transactional, relationship-driven and reminder-style emails where personal tone matters more than visuals. For genuinely visual, product-led promotions, a well-designed HTML email often still performs as well or better. Test your own list rather than assuming either way.

How big does my list need to be to trust the result?

There's no single magic number, but very small lists (a few dozen recipients) make it hard to distinguish a real pattern from noise. Running the test across several sends and looking for a consistent direction matters more than hitting one specific list size.

Is plain-text better for deliverability?

It can be, since plain-text emails avoid some of the spam-trigger patterns associated with heavy image-to-text ratios and tracking-pixel-laden HTML, but deliverability depends on many other factors too — sender reputation, authentication setup, and list hygiene matter just as much, if not more.

Can I combine both — a simple, minimally designed HTML email?

Yes, and it's a reasonable middle ground many businesses land on — light HTML with minimal styling, no heavy imagery, that still looks largely like a personal note. If you go this route, it's worth testing that version against both true plain-text and your fully designed template to see where it actually sits.


Keep reading 🤍

Share
Written by
Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦