How to Write a Plain Text Email That Actually Feels Personal

Here’s how to write a plain text email that actually works: write it like a note to one person. Keep it to a single idea, use short lines with plenty of whitespace, write in first person with contractions, include one or two honestly described links, and sign it like a human being. Most importantly, don’t pretend a mass send is a personal note — plain text is a design choice, not a disguise. That last part is where most marketers go wrong, and it’s exactly where we’re going to spend real time today.

Okay, let’s be honest for a second. You’ve probably received one of those emails — subject line “quick question,” no formatting, signed by a founder you’ve never met — and felt that little flicker of wait, did someone actually write this to me? followed immediately by …no. No, they did not. That flicker is the whole game. Plain text done well earns trust. Plain text done as a costume burns it. I’m going to teach you the honest version, because it’s also the version that keeps working after the gimmick wears off.

What does “plain text email” actually mean? (There are two answers)

Before we get into how to write a plain text email, we need to untangle something, because the term gets used two different ways and the difference genuinely matters.

1. True plain text: no HTML at all

A true plain text email contains nothing but text. No fonts, no colors, no images, no buttons, no tracked links dressed up as buttons — just characters. It’s the format email started with, and it still renders reliably in essentially every email client ever made. The trade-off: you lose all structure beyond line breaks. No headings, no bold, no clickable link text (URLs appear as raw URLs), and typically no standard open tracking, since that relies on an embedded image.

2. Plain-style HTML: the one most marketers actually mean

A plain-style email is technically an HTML email that’s designed to look like a simple personal note. Black text, default-ish font, no header banner, no multi-column layout, maybe one plainly styled link. You keep the practical benefits of HTML — clickable links, basic analytics, a properly formatted unsubscribe footer — while shedding the “this is a campaign” visual signals.

When someone says “plain text emails perform great for us,” they almost always mean plain-style HTML. That’s not a dirty secret; it’s a sensible middle path. In this guide I’ll teach you both, tell you honestly when each applies, and use “plain email” as shorthand for the whole family. Just know which one you’re sending, because the technical trade-offs are different.

Why do plain text emails work so well?

Think about your own inbox. The emails you actually read tend to fall into two buckets: beautifully designed emails from brands you already love, and notes from actual people. Plain emails borrow the clothing of the second bucket, and that does a few real things:

• They read like a person, not a campaign. A plain email has the texture of 1:1 correspondence. It feels like something you’d reply to, which is exactly why it suits emails where a reply is the goal.
• Fewer rendering risks. A heavily designed email can break in dark mode, clip in Gmail, or mangle on an old Outlook build. A plain email has almost nothing to break. What you write is what they see.
• They force clarity. With no design to lean on, the writing has to carry everything. That constraint usually produces tighter, more honest copy. You can’t hide a weak offer behind a pretty button.
• They suit certain senders naturally. Founder updates, B2B outreach from a real account manager, community notes, personal-brand newsletters — contexts where the sender genuinely is a person — feel more congruent in plain form than wrapped in a template.

Notice what’s not on that list: any claim that plain text automatically gets opened more, lands in the inbox more, or converts better. Sometimes it does for some audiences. Sometimes a designed email flattens it. We’ll cover how to find out for your list, because borrowed benchmarks are how people end up confidently wrong.

Where’s the line between “personal-feeling” and fake-personal?

Here’s the part nobody tells you, and it’s the heart of this whole article: plain style is a design choice, not a disguise.

There’s a version of the plain text playbook that treats the format as camouflage. You’ve seen it: the cold email with a fake forwarding chain, the “re:” on a conversation that never happened, the “hey, quick question” subject from a stranger, the mass send written to imply the founder personally typed your name at 11pm. That’s not warmth — it’s cosplay. And the problem isn’t just that it’s a little gross. It’s that it doesn’t survive contact with reality:

• The reader figures it out. Usually within seconds. And the moment they realize the “personal note” was a performance, you haven’t just lost the sale — you’ve taught them your emails lie. Every future send inherits that suspicion.
• It’s the spam playbook. Faked personalization, disguised bulk sends, and hidden commercial intent are precisely the patterns spam filters and regulators have spent decades learning to catch. Imitating spammers to seem human is a strange strategy when you think about it out loud.
• It poisons the format for everyone, including you. Readers who’ve been burned by fake-personal emails start distrusting genuinely personal ones.

The honest alternative is simple: be a human-sounding brand, not a brand pretending the campaign isn’t a campaign. A plain email can absolutely say “I’m sending this to everyone on the list, and I still mean every word.” Readers don’t resent mass email. They resent being treated as too dumb to recognize one.

Compliance isn’t optional just because the email looks casual

One more bright line, and I need you to hold it firmly: commercial email law doesn’t care how minimal your design is. If it’s a marketing send, the usual requirements — a working unsubscribe mechanism, your identification details, truthful headers and subject lines — still fully apply. Deliberately omitting the footer so the email “looks more personal” isn’t a clever growth tactic; it’s non-compliance, and most reputable email platforms will enforce the footer anyway. A short, plainly formatted footer under a signature reads perfectly fine in a personal-style email. Keep it there, keep it visible (no white-on-white text games), and move on with a clean conscience. Requirements vary by country and change over time, so verify the current rules for the regions you send to.

Do plain text emails get better deliverability?

Time for a myth-check, because this claim is everywhere: “plain text emails skip the promotions tab and land straight in the inbox.”

Not quite. There is no magic inbox pass. Mailbox providers decide placement using a whole constellation of signals — your sender reputation, your authentication setup, how often recipients open, reply to, delete, or report your mail, your list hygiene, your sending patterns. Message format is one input among many, and a minor one compared to engagement and list quality. A plain email sent to a stale, scraped list will perform like what it is. A designed email sent to people who genuinely want it will be fine.

What’s honestly true:

• Plain emails tend to invite replies, and replies are a strong positive engagement signal. So the format can help deliverability indirectly — by earning behavior that providers interpret as “people want this mail.” That’s the real mechanism, and it only works if the email is actually worth replying to.
• Multipart is standard practice. Most email service providers send your message as a “multipart” email containing both an HTML part and a plain text part, and most generate the plain part automatically. It’s worth checking — and often hand-editing — that plain text version, because some subscribers and some clients will see it, and auto-generated versions can be ugly. How this works varies by platform, so verify your current ESP’s handling rather than assuming.
• Simpler emails have less to go wrong technically. Fewer images, fewer links, and no heavy code mean fewer of the mechanical issues that occasionally trip filters. That’s a modest hygiene benefit, not a golden ticket.

So: send plain emails because they fit the message and your readers respond to them — not because someone on the internet promised you an inbox cheat code.

How do you actually write a plain text email? The craft, step by step

Alright, the fun part. Here’s how to write a plain text email that feels effortless to read — which, like all “effortless” writing, takes a bit of deliberate effort.

Step 1: Pick one idea. Just one.

A designed newsletter can carry three stories and a product block because the layout separates them. A plain email can’t — it’s one column of text, and every extra ask dilutes it. Before you write a word, finish this sentence: “When they finish this email, I want them to ______.” Reply? Click one link? Just feel glad they’re subscribed? One email, one answer.

Step 2: Write the way you talk

The register for plain email is conversational: contractions, first person, second person, short sentences. Read it aloud; anywhere you stumble or cringe, rewrite. A good test is to imagine the most skeptical person on your list reading it. If a sentence would make them roll their eyes — “I was just thinking about you!” to twelve thousand people — cut it. Warm and direct beats intimate and false, every single time.

Step 3: Build rhythm with short lines and whitespace

You gave up visual design, but you didn’t give up visual structure. In plain email, your formatting toolkit is line length and empty space:

• Keep paragraphs to one to three sentences. A giant text block in a plain email is a wall; nobody climbs walls on their phone.
• Use blank lines generously. They’re your section breaks, your pauses, your emphasis.
• Let a key sentence stand alone on its own line. Isolation is the plain-email equivalent of bold type.
• For true plain text, keep lines reasonably short and skip fancy characters that may not render everywhere; simple dashes and asterisks are the traditional stand-ins for bullets and emphasis.

Step 4: Handle links honestly and sparingly

Links are where plain emails most often give themselves away. A “personal note” with nine tracked links reads exactly like what it is. My rules:

• One link is ideal; two is the ceiling for most plain sends (your compliance footer links don’t count).
• Describe the destination honestly. “Here’s the full teardown of my content calendar” beats “click here,” and vastly beats link text that misrepresents where it goes.
• In true plain text, the raw URL shows. Use a clean, short, trustworthy-looking URL — a readable page on your own domain, not an endless tracking string.
• A wall of links reads spammy to both humans and filters. If you need many links, that’s a designed digest, not a plain note. Use the right format instead of forcing this one.

Step 5: Sign it like a person

End with a human signature: a first name, maybe a role, maybe one line of personality. Skip the giant corporate signature block with four banners and a legal disclaimer in the signature itself — the compliance footer below handles the required details. And if the email invites replies, make sure it’s sent from an address a human actually monitors. “Just hit reply” from a no-reply address is a tiny broken promise, and plain email lives and dies on kept promises.

Step 6: Keep the subject line in the same register

A plain body under a hype-y subject line is a costume change mid-sentence. Write the subject the way you’d title a note to a colleague: specific, lowercase-casual if that fits your voice, zero fake urgency. And no fake “re:” — that’s the fake-personal trap wearing a different hat. The same care applies to your opening line; if you want a deeper dive on first sentences that earn the second one, I’ve written a whole piece on how to write a newsletter intro that pulls people in, and every word of it applies double when there’s no design to help you.

When should you use a plain text email instead of a designed one?

Plain isn’t better. Designed isn’t better. They’re different tools, and the honest answer is “it depends on the job.” Here’s the decision guide I use:

Situation	Best format	Why
You want replies (feedback, questions, booking a call)	Plain / plain-style	A personal-feeling note invites conversation; a glossy template signals “broadcast, don’t respond.”
Founder letters, personal notes, behind-the-scenes updates	Plain / plain-style	The format matches the sender. A human voice in a corporate wrapper feels off.
Text-heavy essays or teaching emails	Plain-style	The writing is the product; design would just be furniture.
Win-back and re-permission emails (“still want to hear from us?”)	Plain / plain-style	These are sincerity moments. A designed campaign asking “do you still like us?” undercuts its own question.
Product showcases, lookbooks, visual announcements	Designed HTML	Images do work words can’t. Don’t describe a product photo when you can show it.
Multi-story newsletters and digests	Designed HTML	Layout separates sections and lets readers scan. Plain text turns a digest into a scroll.
Transactional emails (receipts, confirmations)	Either — prioritize clarity	Structure helps scanning; many great transactional emails are nearly plain anyway.

One more honest trade-off: designed emails make calls-to-action easier to see and tap, and buttons with real contrast can be easier targets for folks with motor or vision challenges. Plain emails put all that weight on link text, which is exactly why Step 4 matters so much.

What about accessibility — is plain text more accessible?

Partly, and the nuance is worth getting right. Plain emails have genuine accessibility advantages: a single column of readable text in a logical order, no layout tables for a screen reader to trip through, no text baked into images, no low-contrast design flourishes. For many readers, that’s a smoother experience than the average designed campaign.

But true plain text loses something important: semantics. There are no real headings for a screen reader to navigate by, no proper list markup, no descriptive link text — just a raw URL read aloud character by character, which is about as fun as it sounds.

The sweet spot for most senders is the middle path: plain-style HTML with honest semantics. Visually it’s a simple personal note; under the hood it has genuine heading tags where needed, real list markup, descriptive linked text, and sufficient color contrast. You get the personal feel and the navigable structure. If you want to go deeper — and I’d love it if you did, because this stuff is both kind and good for results — here’s my full guide on how to make emails accessible.

Worked example: turning a designed promo into an honest plain-style email

Theory is nice; a before-and-after is nicer. Say your designed email was a product-launch promo: hero banner, headline “MEET YOUR NEW CONTENT WORKFLOW,” three feature blocks with icons, two buttons, Instagram footer. Perfectly fine designed email. Here’s the honest plain-style rewrite:

• Subject: we built the thing you kept asking for
• Body:

Hi [first name],

Quick note — this is going out to everyone on the list, but I didn’t want you to hear it from a banner graphic.

For the past few months, the most common request in our inbox has been a way to plan a month of content in one sitting instead of scrambling every Monday. As of today, that exists.

It’s a planning view: you sketch the month, drag things around, and nothing goes out until you say so.

Here’s the walkthrough, including the two things it doesn’t do yet: [link]

If you try it and something feels clunky, just reply — I read these.

— Maya

Notice the moves: it admits it’s a mass send in the first line and is somehow warmer for it. One idea, one link, honestly described — including what the feature doesn’t do, which buys more trust than any superlative. It invites replies and means it. And the compliance footer still sits below the signature, quietly doing its job.

How do you measure whether plain emails are working?

Knowing how to write a plain text email is half the job; knowing whether it worked for your list is the other half. Since I’ve promised you no fabricated benchmarks, here’s the method instead — which is worth more anyway, because the only numbers that matter are yours.

• Make replies your north star for plain sends. Plain emails exist to feel like correspondence, so measure them like correspondence. Count replies, read them, and tag their sentiment. A plain email that triggers twenty thoughtful replies did its job even if clicks were modest.
• Track clicks on your one honest link — with one link, click-through becomes a clean signal of whether the message landed.
• Treat open rates gently. Open tracking relies on an embedded image, so true plain text usually can’t measure opens at all, and privacy features in modern inboxes have made open data fuzzy everywhere. Directional at best.
• Build your own baselines. Run your normal designed sends and your plain sends for a few cycles, compare replies, clicks, unsubscribes, and spam complaints against your own history, and let that — not a stranger’s case study — decide your mix.
• A/B test the format itself when you can: same content, plain-style versus designed, and watch what your audience actually does. Audiences differ; let yours vote.

And schedule the experiment deliberately rather than vibes-based — plain sends work best as an intentional part of your cadence, not a panic move when a designed email underperforms. If your sending rhythm is currently “whenever we remember,” start with my guide to building an email content calendar; it gives every send, plain or designed, a reason to exist and a place to live.

Your plain-email checklist

Before you hit send on any plain or plain-style email, run this list:

• One idea, one desired action — and I can state it in a sentence.
• Opens honestly: no fake “re:”, no implied one-to-one typing, no pretend forwarding chain.
• Conversational voice: contractions, first person, reads aloud smoothly.
• Short paragraphs (1–3 sentences) with generous whitespace; key line stands alone.
• One or two links max, each describing its destination truthfully.
• Human signature; replies go to a monitored address if replies are invited.
• Unsubscribe link and required sender details present and visible — no hiding.
• Plain text part of the multipart send reviewed (not just auto-generated mush).
• Plain-style HTML version keeps real semantics: genuine headings, lists, linked text, solid contrast.
• Test sent to yourself and read on a phone before it goes to anyone else.

Print it, pin it, make it a ritual. The checklist is boring precisely so your emails don’t have to be.

One small honest aside, since you might be wondering where SocialBlaze fits into all this: we’re an organic social media management platform — scheduling, publishing, analytics, and a unified inbox across your social channels — not an email service provider, so you’ll write and send these emails in your ESP. But email and social are two halves of the same relationship with your audience, and the channel where consistency usually falls apart first is social. That part, we can genuinely take off your plate.

Frequently asked questions

What is the difference between a plain text email and an HTML email?

A true plain text email contains only text — no fonts, colors, images, buttons, or clickable link text. An HTML email can include all of those. In between sits plain-style HTML: technically an HTML email, but designed to look like a simple personal note. Most marketing emails described as “plain text” are actually plain-style HTML, which keeps clickable links and a proper footer.

Do plain text emails avoid spam filters?

No — there’s no format that guarantees inbox placement. Spam filtering and tab placement depend mostly on sender reputation, authentication, list quality, and how recipients engage with your mail. Plain emails can help indirectly because they tend to earn replies, which are a positive engagement signal, but a plain email to a bad list still performs badly.

Do I still need an unsubscribe link in a plain text email?

Yes, always, for any commercial send. Email marketing laws apply based on what the email is, not how minimal it looks, so a working unsubscribe mechanism and your required sender details must stay visible. A short, plainly formatted footer below your signature fits the personal style fine. Check current requirements for the regions you send to, since rules vary.

How long should a plain text email be?

As long as one idea needs and no longer. Most effective plain emails are short — a few brief paragraphs with generous whitespace — because the format mimics a personal note, and personal notes don’t ramble. Teaching-style emails can run longer if the writing stays tight, with one-to-three-sentence paragraphs and a single clear call to action.

Can I track opens and clicks in a plain text email?

In true plain text, opens generally can’t be tracked, since open tracking relies on an embedded image, and links appear as raw URLs. Plain-style HTML emails can track clicks normally and opens approximately, though modern inbox privacy features make open data unreliable everywhere. For plain sends, replies and clicks on your one main link are the more meaningful metrics.