Plain Text vs HTML Emails (When to Use Each)

Updated
13 min read
Table of Contents
  1. What Is the Difference Between Plain Text and HTML Email?
  2. What Counts as a Plain Text Email?
  3. Why Every HTML Email Should Carry a Plain Text Version
  4. Plain Text vs HTML Email Performance (What the Data Shows)
  5. Does HTML Hurt Email Deliverability?
  6. How Do Tracking, Images and Accessibility Differ?
  7. When to Use Plain Text vs HTML Email
  8. How to Send a Plain Text Email in Klaviyo
  9. How to Test Plain Text vs HTML on Your Own List
  10. FAQ
  11. Final Thoughts

The difference in plain text vs HTML email comes down to code: an HTML email is built like a little web page with images, buttons and colors, while a plain text email is just words, shown in whatever font the reader's inbox picks.

Most senders end up using both, and that's fine. By the end you'll know what each format is good at, what the testing data says, and which of your emails should get which.

Key Takeaways

  • An HTML email uses code for layout, images and buttons. A plain text email has no code, so it looks the same everywhere.
  • Every HTML email should carry a plain-text version. Klaviyo and Mailchimp both create one for you automatically.
  • In HubSpot's A/B tests, plainer emails got more clicks, even though most people said they prefer HTML.
  • True plain text can't track opens, because open tracking needs an image. Clicks still track.
  • Use HTML when the reader needs to see something, and plain text when the email should read like a person wrote it.
  • Test both formats on your own list and judge the result on clicks, not opens.

What Is the Difference Between Plain Text and HTML Email?

An HTML email is coded like a web page, so it can show images, buttons, brand colors and columns. A plain text email has no code at all, and the reader's email app decides the font, size and color.

Plain text is actually email's default setting. The MIME standard, RFC 2045, says a message with no content type is treated as "text/plain; charset=us-ascii" (email's factory setting is basically a typewriter).

Microsoft's Outlook guide notes that plain text can't show bold, colors or pictures in the body, but it's the one format every email app supports. Here's how the two compare:

FeaturePlain Text EmailHTML Email
What it looks likeA note from a personA designed page
Images and buttonsNoneYes
LinksFull web addresses onlyLinked words and buttons
Open trackingNot possibleYes, through a hidden image
Best forPersonal notes, apologies, founder emailsPromotions, newsletters, product launches
Plain Text Email Code None Images No Open tracking No Looks like A personal note HTML Email Code HTML and CSS Images Yes Open tracking Yes Looks like A web pageMost senders need both formats.Plain text vs HTML email at a glance.

If you go the HTML route, my guide to email design best practices covers layout, fonts and buttons.

What Counts as a Plain Text Email?

A true plain text email has no HTML at all, but most "plain text" marketing emails are really simple HTML dressed up as a personal note. That middle ground matters, because it's what most of the data is about.

In practice, plain text vs HTML email is a spectrum with 3 stops:

  1. True Plain Text: Characters only. No linked words, no images, no tracking pixel.
  2. Hybrid or Text-Only: Simple HTML that looks like a regular email, with a few linked words and maybe a signature image.
  3. Designed HTML: A full template with a header, product images, buttons and columns.

Klaviyo's text-only editor sits in the middle. Klaviyo's text-only email guide says these emails can contain limited formatting and images, but stay much simpler than drag-and-drop HTML emails.

HubSpot's well-known test sits there too. The "plain-text" emails in HubSpot's plain text vs HTML study still had hyperlinks and tracking pixels, so they could measure opens and clicks (even the plain text champions cheated a little).

Why Every HTML Email Should Carry a Plain Text Version

Every HTML email should go out with a plain-text version packed inside it, and the reader's email app picks which one to show. This setup is called multipart MIME, and it means you rarely have to choose one format over the other.

The rule comes from RFC 2046, the MIME standard. The plain text part goes first, the HTML part goes last, and the reader's app shows the last version it can handle. Mailchimp's HTML email guide puts it simply: the format sends both versions and the email program decides what to display.

So who sees the plain-text part? Klaviyo's plain-text version guide says some inboxes only take plain text, for security or accessibility, and you can't detect which version a recipient views. Some people even choose it, because Outlook lets readers turn on "Read all standard mail in plain text".

You don't have to write it yourself. Klaviyo adds a plain-text version to every drag-and-drop email, and Mailchimp automatically creates one too.

Pro tip: Open the auto-generated version before a big send. Once you edit it in Klaviyo, Klaviyo's guide warns that it stops syncing with your HTML template, so future changes have to be made in 2 places (or click Auto-Generate Plain Text to start over).

For the screen reader side of this, see my email accessibility best practices.

Plain Text vs HTML Email Performance (What the Data Shows)

In HubSpot's testing, the plainer email won on clicks, which is surprising, because people say the opposite when you ask them.

In a 2014 survey quoted in HubSpot's plain text vs HTML study, nearly 2/3 of respondents said they preferred HTML and image-based emails. Then HubSpot ran A/B tests, and the results went the other way:

Across more than half a billion customer emails, HubSpot also found that even a single image reduced the click rate. People say they want the pretty version and then click the plain one (the email version of ordering a salad and eating your friend's fries).

Inbox Connect HubSpot's Plain Text vs HTML Tests 2/3 Prefer HTML Survey respondentswho said they likeHTML emails. 42% More Clicks Plain text vs a GIFversion. 51% Fewer Clicks HTML template withimages vs plain text. 30% More Clicks Simple HTML vs aheavy HTML template. i HubSpot's plain text tests still had links and tracking.From HubSpot's plain text vs HTML email study.

Klaviyo sees the same pattern. Klaviyo's text-only email guide says text-only emails "often see higher click rates than fully designed HTML emails", especially when a real person like the founder signs them.

There's a catch, though. HubSpot itself says ecommerce brands may see different results, because shoppers expect to see the product (you can only describe a sneaker so well).

Does HTML Hurt Email Deliverability?

HTML on its own doesn't send you to spam, but sloppy or sneaky HTML can. Inbox providers care far more about your reputation and engagement than your template.

What Gmail does ask for is clean code. Google's email sender guidelines say to format HTML messages according to HTML standards, keep links visible and easy to understand, and never use HTML or CSS to hide content, because hidden content might get your messages marked as spam.

The format still plays a small part. Klaviyo's plain-text version guide says a plain-text version can help differentiate you from spammers.

The riskiest HTML email is one giant image, because readers with images off see a blank box. Klaviyo's accessibility guide says to avoid image-only emails for exactly that reason (a JPEG of your sale is a postcard nobody can read).

If you're landing in spam, start with my guide to improving email deliverability before you strip out your template.

How Do Tracking, Images and Accessibility Differ?

HTML emails can track opens and plain text emails can't, but both can track clicks.

Opens are counted with a tiny hidden image. Klaviyo's tracking guide explains that it adds an invisible pixel to the email and records an open when it loads, while clicks are tracked through the links. Mailchimp's open tracking guide confirms that open tracking won't work in plain-text emails.

Here's what each format can and can't measure:

What Each Format Can Track HTML email: opens Yes, via pixel HTML email: clicks Yes Plain text email: opens No Plain text email: clicks Yes, full URLs showFrom Klaviyo's and Mailchimp's tracking guides.

Even HTML opens are shaky. Outlook lets readers block external images, which stops the pixel, and Klaviyo's tracking guide notes that Apple Mail Privacy Protection may record opens the subscriber never made. My Apple Mail Privacy Protection guide covers the fallout.

Plain text clicks have a quirk too. With no anchor text to hide behind, Mailchimp's click tracking guide says recipients see the full tracking URL (long, ugly and slightly suspicious looking).

Accessibility can go either way. Klaviyo's text-only guide says text-only emails are easier for screen readers and smart watches, and an HTML email works too with Klaviyo's accessibility basics: alt text, good contrast and no details locked inside pictures.

When to Use Plain Text vs HTML Email

Use HTML when the reader needs to see something, and plain text when the email should feel like one person writing to another. You're choosing per email, not per brand:

Email TypeFormatWhy
Sale or product launchHTMLShoppers need to see the product
Newsletter with several storiesHTMLSections and images help people scan
Order confirmation or receiptLight HTMLClear layout for order details
Founder welcome notePlain text or text-onlyReads like a personal note
Apology or service updatePlain text or text-onlyFeels human, not like a campaign
Cold outreachPlain textShould look like a normal email
Win-back check-inEither, so test itDepends on your list

Klaviyo's text-only guide backs up two of those picks: it suggests text-only for a message in your welcome series and for apology emails. For receipts and password resets, my transactional email best practices cover what to include, and cold email vs marketing email explains why outreach plays by different rules.

Either way, the words do the heavy lifting (no format can save "Just checking in"), so run them past my email copywriting tips.

How to Send a Plain Text Email in Klaviyo

In Klaviyo, you switch a campaign to the text-only editor from the three-dot menu, or choose Text only when you edit a flow email. Here are the steps from Klaviyo's text-only email guide for a campaign:

  1. Go to Campaigns, click Create campaign, choose Single channel and Email.
  2. Choose recipients and tracking settings, then add the subject line.
  3. Open the three-dot menu and select Switch to text only editor.
  4. Write the email, click Preview email, then Save.

For a flow, drag in an Email action, open its three-dot menu, click Edit and select Text only. Klaviyo caps text-only emails at 1.05 MB, according to the same Klaviyo guide, which is plenty for words.

Create campaign Pick recipients Add subject line Switch to text only editor Write and preview Save Creating a text-only campaign in Klaviyo.

Here's a worked example. Say your welcome flow has 3 designed emails. Swap email 2 for a short text-only note from the founder with one link to the bestseller and an invitation to reply. Keep emails 1 and 3 in HTML for the product photos.

Pro tip: Preview it on your phone before it goes live. A giant logo at the top of a text-only email defeats the point.

How to Test Plain Text vs HTML on Your Own List

The only way to know which format your list prefers is to A/B test the same email in both versions and judge it on clicks. Opens won't help, because plain text can't record them, as Mailchimp's open tracking guide points out.

A fair plain text vs HTML email test looks like this:

  1. Pick a Regular Send: Use a weekly newsletter or a flow email so you get several rounds of data.
  2. Keep the Words the Same: Same subject line, copy and links, so only the format changes.
  3. Split the List Evenly: Send each version to a random half of the audience.
  4. Measure Clicks and Revenue: Compare clicks, orders and unsubscribes, and ignore opens.
  5. Repeat Before You Decide: Run it a few times, because one send can be a fluke.

Make the plain version easy to read, too. Mailchimp's plain-text guide admits plain text is harder to read than HTML and suggests dividing lines and line breaks to break it up.

For sample sizes, see my guide to A/B testing in marketing.

FAQ

Is plain text or HTML better for email marketing?

Neither wins every time. HubSpot's study found plainer emails got more clicks, but says ecommerce brands may see different results.

Do plain text emails have better deliverability?

Not on their own. Google's sender guidelines ask for standards-compliant HTML with no hidden content, and Klaviyo says including a plain-text version helps differentiate you from spammers.

Can you track opens in a plain text email?

No. Mailchimp's open tracking guide explains that opens are tracked with a hidden image, which plain text can't contain, so only clicks can be measured.

Why did I receive an email in plain text instead of HTML?

Your email app showed the plain-text part of a multipart email. RFC 2046 has the app show the richest version it supports, and Outlook can be set to read all mail in plain text.

Yes, as full web addresses rather than linked words. Mailchimp's click tracking guide notes that readers of plain-text emails see the full tracking URL.

Should I send a plain text version of every HTML email?

Yes. Mailchimp and Klaviyo both create one automatically, so your main job is checking it reads well.

Final Thoughts

You now know how plain text and HTML emails differ and what each does to tracking, deliverability and clicks. My recommendation: HTML for sales, launches and newsletters, plain text or text-only for founder notes, apologies and outreach, a plain-text version on every HTML send, and every test judged on clicks.

Pick one flow email this week and run it as a text-only version against your current design. If you'd like a second pair of eyes on your formats and inbox placement, book an email audit.

Russ

Ready for better results?

Get expert help with your email marketing strategy.