• Skip to main content
  • Skip to footer

Dyspatch

  • Products
      • Overview
      Features
      • No-code email builder
      • Email collaboration
      • SMS builder
      • AMP for Email
      • Template localization
      • Expert services
      • Partners & integrations
      •  
      Find your fit
      • Tools for email Designers
      • Dyspatch for translators
      • Email production for Marketers
      • Resources for email Developers
      Sendwithus Logo
      • Overview
      • Analytics
      • A/B testing
      • Triggered emails
  • Pricing
  • Case studies
  • Resources
    • Blog
    • Free templates
    • Webinars
    • Ebooks, guides, & reports
  • Company
    • About us
    • Careers
    • Contact us
  • Login
    • Dyspatch
    • Sendwithus
Get a demo

The Myth of Deliverability: Plain Text Email vs. HTML Email

By Matt Harris | January 18, 2022 | Categories: Email Marketing
⏱ 4 minute read

Is there a deliverability risk associated with sending HTML email instead of just plain text email?

We’ve alluded to this debate before, and recently, we wrote a whole blog post on HTML vs. plain text email. TLDR: There are a couple instances when plain text emails win out, but on the whole, we recommend HTML emails — with the stipulation that you should test both.

The reason for that stipulation, however, is more about your subscribers’ preference than email deliverability…

Does plain text email really have 100% deliverability?

There is no email client in the world that cannot open a plain text email. So there’s that. But 100% deliverability is a bit misleading. I can assure you there are plenty of plain text emails in my spam folder right now.

Of course, you’re not sending actual spam emails (you wouldn’t do that, right?), and there are only so many ways you can verify email addresses, so there are really two issues to focus on:

  1. Would my users prefer plain text?
  2. How do I keep my HTML emails from triggering filters?

Do the people want plain text emails?

There are a couple of circumstances where it makes sense to use plain text as an aesthetic decision. Sometimes you want to follow up with a user in a personal way, while still automating the process for timeliness.

Here’s a great example from our friends at Zapier:

Even simple emails like this, though, often contain a bit of HTML — either for formatting links or to load a tracking pixel. But no email filter is going to use the existence of that small amount of code as a reason to flag the email as spam. Derek Halpern wrote a great post on testing what he called “simple vs. fancy” for the mailing list at DIYThemes.

So do you want simple or fancy?

Fancy, obviously — but how do you do fancy, not flagged?

The short version is pretty simple: Write like a human. Ask yourself, “Would this look at home on a Geocities page circa 1997?” And go from there. Scrolling text, word-art, code generated from Microsoft Word — any of these things can get you targeted by an email filter and, frankly, it’s no surprise they do.

Include a plain text email alternative

Most email template builders allow you to generate and include a plain text version of the email. This is considered a crucial factor for accessibility, and thus deliverability (you can read more about the importance of email accessibility here). And in our no-code modular editor, it’s just a couple of clicks away:

Mind the plain text email preview

Most email clients will pull the first text outside of a tag and use it for a preview of the email.

A lot of templates include a dedicated space for this preview text, known as the preheader, and it’s often populated with placeholder copy. If you’re using such a template, I suggest you make it a top priority to replace this text. The chances of captivating any customer’s attention with text that reads, “Insert preview text here”, is slim to none. And again, this can hurt your deliverability.

Don’t overuse images

Gmail made the switch to automatically display images in emails some time ago (this was always an option, it just wasn’t the default). This increased their capacity to display images through their proxies. However, be warned this is not an invitation to turn entire emails into images.

A high image-to-text ratio is the most common cause of false positives in spam filters. Consider using an HTML button from our library of bulletproof email components. They’re more responsive, they look nicer, and they help keep that ratio in check.

Don’t send broken code

This seems like common sense, but you’d be surprised how often it happens. Always — and I mean always — check your code. Within both Dyspatch and Sendwithus, we use Litmus for testing to make sure every email renders properly on all email clients, devices, and settings (like dark mode, for example) before you press send. This ensures every subscriber has a positive experience when reading, and defends against the risk of them reporting you for spam.

Don’t come on too strong

If you didn’t grow up with commercials like the one above, they’re basically TV spam. The bottom line is that there are just some things that are never going to be legitimate…and statements like “Free Money” is certainly one of them. In general, it’s a good idea to avoid the language common to this kind of promotion.

There’s a great entry on HubSpot with a big collection of spammy words to steer clear of. But a good rule of thumb is to avoid making any kind of hyperbolic claim — the kind of phrases you might see on a bus stop bench or tacky billboard could very well put you in the danger zone.

Though it’s true, spam algorithms have moved away from keyword-based filters, it’s still a good idea to avoid “spam words”. After all, you don’t want to leave a bad impression on your subscribers. And you definitely don’t want them to mark your email as spam.

Plain text email deliverability: The bottom line

To sum things up, here are the key points to understand when it comes to email deliverability:

  • While plain text email deliverability is strong, it’s not 100% guaranteed.
  • User experience matters most: Ask yourself what format benefits your audience, and go from there.
  • HTML emails that are well-crafted, properly coded, and put to the test will get delivered — and deliver results for you.

Originally published: September, 2014. Last updated: January, 2022.

Matt Harris, CEO at Dyspatch

A certified email nerd. Passionate about customer experience and how technology can make it better. Founder and CEO of Dyspatch and Sendwithus.

  • Twitter
  • LinkedIn

    Related Posts

  • How to Send Email like Uber
  • 7 AMP for Email Myths, Debunked
  • 5 Ways Fitness Companies Can Benefit From AMP Emails
Tags: Email Deliverability
Share this post:
  • Facebook
  • Pinterest
  • Twitter
  • Linkedin
LET’S CHAT!

Why wait? Take your email marketing to the next level today.

Get a demo

5307 Victoria Drive #899
Vancouver, BC
V5P 3V6

548 Market Street,
San Francisco, California
94104 US

  • Phone 1-877-458-9231
  • Email us@dyspatch.io
    security@dyspatch.io
  • Facebook
  • Twitter
  • Instagram
  • LinkedIn
  • YouTube

Get the latest email strategies, tips, and trends right to your inbox.

About Dyspatch

  • About us
  • Careers
  • Contact us
  • Pricing
  • Press & Media
  • Release Notes

Find your fit

  • Tools for email Designers
  • Dyspatch for translators
  • Email production for Marketers
  • Resources for email Developers

Features

  • Dyspatch overview
  • No-code email builder
  • Email collaboration
  • Email template localization
  • AMP for Email
  • Sample AMP email templates
  • Expert Services
  • Sendwithus Overview
  • Agency Program

Email resources

  • Blog
  • Webinars
  • Ebooks Guides & Reports
  • HTML email templates
  • Knowledge base
  • Figma email builder
  • The Dyspatch Block gallery

Integrations

  • Partners & Integrations directory
  • Email builder for Braze
  • Email builder for Iterable
  • Email builder for Salesforce Marketing Cloud
  • Email builder for Pardot
  • Email builder for SendGrid
  • Email builder for Marketo
  • Email builder for HubSpot
  • Email builder for Oracle Eloqua

Dyspatch respectfully acknowledges the Lekwungen and W̱SÁNEĆ People, whose unceded territories we live and work on. We would also like to express our gratitude to all of the Coast Salish people as we continue to work and live as guests on their lands.

We recognize that acts of colonization created many inequities for First Nations, Inuit, and Métis people. As a company, we acknowledge that we have a responsibility to work towards reconciliation and to remain open to suggestions and consultations, especially with Indigenous communities.

Privacy policy    |    Terms of service    |    Web accessibility    |    Cookie policy    |    Usage    |    Sitemap

Copyright © 2025 Techdrop Labs Inc. All Rights Reserved.


Features & Functionality
Starter Teams Teams+
Universal styling  ✓  ✓  ✓
Drag and drop email builder  ✓  ✓  ✓
Custom code editor  ✓  ✓  ✓
Custom fonts  ✓  ✓  ✓
Device specific elements  ✓  ✓  ✓
Version history  ✓  ✓  ✓
Social media link settings  ✓  ✓  ✓
Commenting  ✓  ✓  ✓
Live previews  ✓  ✓  ✓
Dark mode previews  ✓  ✓  ✓
Litmus testing  ✓  ✓  ✓
Custom merge fields  ✓  ✓  ✓
Image hosting  ✓  ✓  ✓
Brand & legal compliance guardrails  ✓  ✓  ✓
User role permissions  ✓  ✓  ✓
ESP logic  ✓  ✓  ✓
Code Export  ✓  ✓  ✓
AMP Email Support  ✓  ✓  ✓
Approval Workflows  ✓  ✓  ✓
API Access  ✓  ✓  ✓
User Management –  ✓  ✓
Translation (via Smartling) – –  ✓
Export via API – –  ✓
Localizations – –  ✓
Account Manager – –  ✓
Premium Support – –  ✓
SLA – –  ✓
Premium SAML SSO – –  ✓
Custom Themes – –  ✓
Workspaces – –  ✓
Design / AMP Services – –  ✓
Pricing $149/mo $499/mo Custom
Get a demo

Get a quote