# Plain Text vs HTML Email: Which to Send When

> Plain text vs HTML email: decision rules for choosing a format, how multipart emails work, the deliverability myths, and how to write each format well.

Canonical: https://www.cresca.xyz/blog/plain-text-vs-html-email
Author: Lalit Kumar Jangid
Published: 2026-09-01
Last updated: 2026-10-26

"Should we send plain text or HTML?" The plain text vs HTML email debate sounds like a design question, but it is really a question about relationship. A plain note feels like it came from a person. A designed email feels like it came from a brand. Both are legitimate, and the right choice depends on what you are sending and to whom. This post gives you a short set of decision rules, explains how the two formats coexist inside a single message, and shows how to write each one well.

## What the two terms actually mean

**Plain text** is just characters: no fonts, colours, images or buttons. Links appear as raw URLs. What the reader sees depends entirely on their mail app's default styling.

**HTML email** uses markup to control layout and appearance: headings, brand colours, images, buttons, multiple sections. It can also be very minimal; an HTML email with one font and no images can look almost identical to plain text.

That last point matters. The real spectrum is not "plain vs fancy" but "how much visual design does this message need?"

## Can you send plain text and HTML in the same email?

Yes, and most marketing emails already do. They are sent as a multipart/alternative message containing a plain-text version and an HTML version of the same content, and the receiving app picks the one it can display best. That makes the plain-text part real content that some readers, accessibility tools and filtering systems will see.

Most marketing emails are sent as a `multipart/alternative` message containing a plain-text version and an HTML version of the same content. The receiving app picks the one it can display best. The rules for this come from [RFC 2046](https://www.rfc-editor.org/rfc/rfc2046), which says the parts should be placed in increasing order of preference, with the best choice being the last part the recipient's system supports. That is why plain text conventionally comes first and HTML last.

In practice this means your plain-text part is not optional decoration. It is what some readers, some accessibility tools and some filtering systems will actually look at. If it says "This email requires HTML to view," you have wasted it.

## Plain text vs HTML email: when should you use each?

Use plain text, or very light HTML, when a message should read like a note from one person, such as a founder's update or a B2B sales follow-up. Use HTML when the reader must see something, like a product launch with photos, or when headings and spacing make a newsletter with several stories easier to scan.

Use these as defaults, then adjust based on what your own results tell you.

| Situation | Lean toward | Reason |
| --- | --- | --- |
| A founder's update or personal note to customers | Plain text, or very light HTML | Should read like a letter from one person |
| Product launch with photos | HTML | The product is the message; people need to see it |
| Weekly newsletter with several stories | HTML | Headings and spacing make it scannable |
| Re-engagement email to quiet subscribers | Plain text | A different look can stand out from your usual campaigns |
| B2B sales follow-up sequence | Plain text | Matches how individual business emails look |
| Event invitation with date, venue and RSVP | Light HTML | A clear button and structured details help |

Two questions settle most borderline cases:

1. **Would a person write this by hand?** If yes, plain text fits. Nobody hand-writes a seasonal catalogue.
2. **Is there something the reader must see?** A product shot, a chart, a before-and-after. If yes, you need HTML.

## Myths worth dropping

### Does plain text get better deliverability than HTML?

Not by default. Filtering decisions rest heavily on sender reputation, authentication and how recipients react to your mail. Google's sender guidelines ask that HTML messages follow HTML standards and not hide content, but they do not tell senders to avoid HTML. A well-built HTML email from a trusted sender is fine; a sloppy one is not.

Filtering decisions rest heavily on sender reputation, authentication and how recipients react to your mail. Google's [email sender guidelines](https://support.google.com/a/answer/81126) focus on things like SPF, DKIM, low spam rates and correct message formatting; they ask that HTML messages follow HTML standards and that you not use HTML and CSS to hide content. They do not tell senders to avoid HTML. A well-built HTML email from a trusted sender is fine. A sloppy one with hidden text or broken markup is a different story.

### "HTML always looks more professional"

Heavy design can make a small business feel like a faceless retailer. For relationship-driven brands, a clean, mostly-text email often feels more trustworthy.

### "Plain text means no tracking, so we can't measure it"

Measurement of outcomes happens on your website and in your store. A raw URL with UTM parameters in a plain-text email reports traffic just as well as a button does. It is merely less pretty, which brings us to the next section.

## Writing a good plain-text email

- **Keep lines short and paragraphs shorter.** You have no layout to guide the eye, so whitespace does that job.
- **Put links on their own line.** Long URLs in the middle of a sentence are hard to read and easy to break when wrapped. Consider a short, readable path on your own domain.
- **Use simple text structure.** Dashes for lists, capitals sparingly for section labels, blank lines between sections.
- **Sign it.** A name at the bottom is what makes plain text feel personal.

An example of a short plain-text product note:

```
Hi Sam,

Quick one: the refill packs you asked about are back in stock.

- Same blend as before
- Now in a compostable pouch
- Ships within 2 days

Order here:
https://example.com/refills

If you'd rather not get product updates, you can
unsubscribe at the bottom of this email.

Asha
Founder, Example Tea Co.
```

## Writing a good HTML email

- **Make it work with images off.** Put important information in live text, not inside an image. Add meaningful `alt` text to images.
- **Use real structure.** Headings, paragraphs and lists help screen readers and make the email easier to skim.
- **Keep the code lean.** Fewer nested tables, fewer unused styles. Lean code is easier to debug across clients.
- **Do not hide text.** Tiny white-on-white keywords and invisible blocks are exactly what Google's guidelines warn against.
- **Write the plain-text part on purpose.** Review the auto-generated version if your tool creates one, and fix anything that reads oddly, such as image alt text sitting mid-sentence.

A useful technique for brands that want the warmth of plain text with a bit of polish: build an HTML email that is a single column of text with your logo at the top, normal paragraph styling and one clear button. It reads like a letter but keeps a tappable call to action.

## How to decide for your own list

Instead of reading other people's plain text vs HTML email tests, compare outcomes on your own list over a few sends. Alternate formats for similar types of message, measure what matters in your store or analytics (orders, replies, signups), and watch your complaint and unsubscribe counts. Keep the content as similar as possible so you are comparing format, not offers. With small lists, look for a consistent direction over several sends rather than reading too much into one result.

In Cresca, the [AI template generator](https://www.cresca.xyz/ai-template-generator) can draft a designed campaign from a prompt, and you can strip it back in the visual editor to a single text column if the message calls for a lighter touch. Either way, campaign reports show deliveries, bounces, complaints and unsubscribes, so you can see whether a format change upset anyone.

## Quick recap

- Send HTML and plain text together, and treat both parts as real content.
- Choose plain or light formatting when the message is personal; choose richer HTML when readers need to see something.
- Deliverability depends far more on reputation and clean code than on format alone.
- Judge by outcomes you record yourself, not by opens.
