## Why the Format of an Email Still Matters Most teams pick an email format once, usually when they choose a template, and never think about it again.
The newsletter goes out as designed HTML, the password reset goes out as whatever the developer wrote, and nobody checks what a recipient actually sees when images are blocked, when dark mode is on, or when the message is opened in a client that ignores half of the styling. That is a missed opportunity.
The format you send affects how your message renders, how accessible it is, how big it is, how it looks to filters, and how easy it is to read on a small screen. It also affects something many senders forget entirely: whether there is a plain-text version of the message at all.
This guide explains the real difference between plain-text and HTML email, why most bulk mail should be sent as a multipart message that contains both, when a plain-looking email beats a designed one, and how to build and test both versions so they hold up across clients. It closes with a pre-send checklist and a short FAQ.
## Plain Text, HTML, and Multipart: What Each One Actually Is Before comparing them, it helps to be precise, because the terms are often used loosely. ### Plain-text email A plain-text email is just characters. There is no markup, no fonts, no colors, no images, and no layout beyond line breaks. Links appear as full URLs.
Every email client can display it, and it looks essentially the same everywhere: a block of text in the client's default font. ### HTML email An HTML email is a web document built for mail clients. It can contain headings, colors, buttons, images, tables for layout, and links hidden behind readable anchor text. It is also where open tracking usually lives, because the tracking pixel is a tiny image inside the HTML.
The catch is that email clients support only a limited and inconsistent subset of HTML and CSS, so a design that looks perfect in one client can break in another. ### Multipart (MIME) email A multipart email is the format most professional senders should use. Using the MIME standard, a single message carries two versions of the same content: a `text/plain` part and a `text/html` part, wrapped in a `multipart/alternative` container.
The recipient's client picks the version it prefers and can display, which in practice is usually the HTML part, with the plain-text part available as a fallback. So the choice is rarely "plain text or HTML." For most bulk and automated mail, the real choice is between an HTML-only message and a well-built multipart message, and between a heavily designed HTML message and a plain-looking one.
## Why You Should Almost Always Include a Plain-Text Part Sending HTML without a matching text part works most of the time, which is why many senders do it. But a good plain-text part costs very little and helps in several ways.
### Fallback for clients and settings that need it Some recipients read mail in clients or modes that show text only: certain terminal and accessibility setups, some smartwatches and notification previews, and users who have chosen to view messages as plain text. Without a text part, those readers see either nothing useful or a messy conversion of your HTML.
### Previews and notifications Inbox previews, lock-screen notifications, and wearables often draw from the text of the message. A clean text part gives those surfaces readable content instead of stray template fragments, alt text, or tracking parameters. ### A more complete, conventional message Legitimate commercial mail is commonly sent as multipart. A message with a sensible text part that matches the HTML looks like what it is: a well-built email from a real sender.
Filters weigh many signals, and no single formatting choice will put you in the inbox or the spam folder on its own. Still, there is no benefit to looking unusual, and an HTML-only message with an empty or mismatched text part is a small, avoidable oddity. ### It forces you to check the message makes sense without design Writing the text part is a useful editorial test.
If the message only works because of a hero image and a big button, the text version exposes that immediately. If the text version reads clearly, the email's core message is sound. ## What Makes a Good Plain-Text Part Many platforms can generate a text part automatically from the HTML.
Auto-generated text is better than nothing, but it often produces long runs of repeated links, leftover alt text, table fragments, and URLs packed with tracking parameters. Treat the text part as real content, not a by-product. - **Match the HTML message.** The text part should say the same thing as the HTML version: same offer, same key details, same call to action.
A text part that is empty, generic, or about something else is worse than an honest copy. - **Lead with the point.** Put the main message and the primary action near the top. Text readers cannot scan visual hierarchy, so order does the work that design does in HTML. - **Write links as readable URLs.** Put the main link on its own line.
Where possible, use short, clean URLs on your own domain instead of long strings of tracking parameters. - **Use simple structure.** Short paragraphs, blank lines between sections, and a few clear labels in capital letters or with dashes are enough. Avoid ASCII art and decorative separators that break on narrow screens.
- **Keep the footer.** The text part needs the same legally and practically important elements as the HTML: who the email is from, why the recipient is getting it, a working unsubscribe link, and any required postal or company details. - **Check line breaks.** Very long lines may be wrapped unpredictably, and hard-wrapped lines can look broken on mobile. Test how your text part displays in a few real clients.
## Where HTML Email Earns Its Place None of this is an argument against HTML. Designed email exists for good reasons. ### Hierarchy and scannability Headings, spacing, and buttons let readers find what matters in seconds. For newsletters, product announcements, and multi-item promotions, that structure is genuinely useful. ### Clear calls to action A well-made button is easier to see and tap than a bare URL, especially on mobile.
HTML lets you put a clear action in a predictable place. ### Brand recognition Consistent colors, a logo, and a familiar layout help recipients recognize mail from you. Recognition supports trust, and trust supports engagement. ### Measurement Most email open tracking depends on HTML, because it uses a small image loaded when the message is displayed. Click tracking works with any format, but in HTML the tracked link can sit behind readable anchor text.
Be aware that open data is noisy: privacy features and security scanners can load images without a human opening the message, and image blocking can hide real opens. Use opens as a directional signal and lean on clicks and conversions for decisions. ## When Plain-Looking Email Wins There is a middle ground that many teams underuse: an HTML email that looks like plain text.
It has minimal styling, no hero image, a simple signature, and perhaps one or two links. It still carries a tracking pixel and a proper multipart structure, but to the reader it looks like a message from a person rather than a brochure. Plain-looking email tends to suit: - **Personal-style messages.** Founder notes, account manager check-ins, and follow-ups after a demo or purchase feel more natural without heavy design.
- **Transactional and service mail.** Receipts, password resets, security alerts, and shipping updates need clarity and speed above all. Simple layouts render reliably and load quickly. - **Re-engagement and win-back emails.** A short, direct message asking whether someone still wants to hear from you can stand out precisely because it does not look like another promotion. - **B2B outreach and replies.** Messages that invite a reply usually work better when they resemble normal correspondence.
Designed HTML tends to suit newsletters, catalogs, event announcements, and seasonal campaigns where showing several items or a strong visual identity is part of the point. The right answer often differs by stream. Many senders use designed templates for marketing and plain-looking templates for transactional and relationship mail, and they test the difference instead of assuming.
## Building HTML Email That Survives Real Clients If you send HTML, the goal is not a design that looks perfect in your editor. It is a design that degrades gracefully in every client your audience uses. ### Design for limited and inconsistent support Email clients do not render HTML the way modern browsers do.
Some ignore certain CSS properties, some strip styles placed in the document head, and some desktop clients use rendering engines with very limited layout support. This is why many email templates still use tables for layout and inline styles. Use a tested template or framework rather than hand-building c
Related Articles
One-click unsubscribe is now part of deliverability. Learn how the List-Unsubscribe and List-Unsubscribe-Post headers work, what RFC 8058 and Gmail and Yahoo require, and how to
Timezone defaults leave opens on the table. Use predictive send-time models, holdouts, and guardrails to reach subscribers when they engage.
Accessible emails reach more readers and survive image blocking, dark mode, and small screens. Learn how to write alt text, meet WCAG contrast ratios, structure headings and layout
A practical 2026 checklist for SPF, DKIM, and DMARC—inventory senders, align domains, and tighten policy without breaking mail.
Spot SMS and email delivery drops in minutes with adaptive baselines, smart alert tiers, and automatic safeguards that protect your reputation.
ISP throttling defers bulk email without bouncing it. Learn the signals, pacing tactics, and monitoring that keep large sends on time.
Shared or dedicated sending IP? Compare reputation, volume, warm-up, and control, and learn when a dedicated IP helps bulk email and when it hurts.
Email cadence shapes engagement, complaints, and inbox placement. Learn how to spot fatigue, test frequency per subscriber, segment cadence by engagement, and cap total email
Explore SESender
SESender brings audience preparation, contact validation, sender and provider controls, scheduling, delivery tracking, and campaign reporting into one workspace. Review the current product and pricing information before deciding whether the platform fits your messaging workflow.
Explore the platform or review pricing.