How to Create Email Templates That Convert

Email templates that convert share five traits: a single clear CTA, a hero section that answers "why should I read this", one-column mobile-first layouts, preheader text that extends the subject line, and a scannable F-pattern body that respects how people actually read inboxes. Everything else (gradients, animations, clever copy) is optional.

Most of the templates I've audited fail on the basics. Litmus found that 41.9% of emails are now opened on mobile devices, and Apple Mail alone accounts for more than half of all opens when privacy pixels fire (Litmus 2024 State of Email Engagement). If your template breaks at 320px wide, you've already lost almost half your audience before they read a word.

Table of contents

What makes an email template convert?

A template converts when it moves a specific reader toward one specific action, quickly, on the device they're holding. That's it. Pretty design helps; pretty design without a clear next step is a PDF. Campaign Monitor's 2024 benchmarks put the average click-through rate at roughly 2.3% across industries (Campaign Monitor Email Benchmarks), and the templates beating that figure almost always do less, not more.

The hard part is restraint. When a founder sends me a template to review, I can usually predict the CTR within half a point by counting the buttons. Two buttons above the fold? Expect average performance. One button, one promise, one clear reason to click? That's where the lift lives. The email-templates that compound over time treat every extra element as a tax on the primary action.

One honest downside worth naming upfront: great templates take longer to build than bad ones. A "good enough" single-column layout with a hero and a CTA might take 30 minutes; a genuinely optimized, accessibility-checked, cross-client-tested template is a half-day of work. Most teams under-invest here and wonder why their sends underperform.

What are the essential elements of a high-converting template?

Every template that converts has the same six elements in roughly the same order: preheader, hero, body, single primary CTA, supporting content, and a footer that builds trust. Miss any one of these and you're pushing readers uphill. Below is the shape I use as a starting point for almost every campaign.

Section	Purpose	Typical length	Conversion role
Preheader	Extends the subject line in the inbox preview	40–90 characters	Gets the open
Hero	Answers "why should I care?" in one glance	1 line + 1 image	Earns the scroll
Body copy	Makes the promise credible with 1–2 proofs	80–160 words	Builds intent
Primary CTA	One button; above and below the fold if long	2–4 words	Captures the click
Supporting block	Secondary link, FAQ, or testimonial (optional)	1 short row	Recovers fence-sitters
Footer	Unsubscribe, physical address, brand contact	2–3 lines	Signals legitimacy

Preheader text is half the open decision

Preheader text is the 40–90 character snippet that Gmail, Apple Mail, and Outlook show next to the subject line. Skip it and the client grabs the first line of HTML (often "View in browser"), which is a wasted slot. Good preheader text reads like a second subject line; it teases, it clarifies, it sets a hook. I run preheaders through Mailneo's email preheader previewer before every send so I can see what actually shows up in each client.

The hero isn't a decoration

Most hero images I see are stock photos with a headline stamped on top. That's a billboard, not a hero. A converting hero answers one question in under two seconds: what's in this for me? A single line of text on a solid background beats a 400kb image most of the time, especially on slow mobile connections.

One CTA, stated plainly

If you've written "Learn More" on a button in the last six months, I'm going to gently suggest you stop. A call-to-action should tell the reader exactly what happens next: "Claim your free seat", "Read the 4-minute guide", "Start my 14-day trial". Specific verbs outperform vague ones; Really Good Emails' public gallery is full of examples if you want a weekend of pattern study (Really Good Emails).

How should you structure an email for readability?

Structure it for scanning, not reading. Nielsen Norman Group has shown for decades that people read screens in an F-pattern (eyes move left to right across the top, then down the left edge, pausing on bolded text, headings, and the first few words of paragraphs) (Nielsen Norman Group: F-Pattern Reading). Emails aren't different; inbox readers are, if anything, less patient than web readers because they didn't seek you out.

Single column, always

I've stopped building multi-column email layouts entirely. Every two-column design I shipped between 2022 and 2024 underperformed its single-column version in A/B tests. Multi-column only works if both columns get equal attention, which on mobile they never do (mobile collapses them to a stack anyway, so the second column becomes a confused afterthought). One column also makes responsive design mostly free; there's nothing to rearrange.

Short paragraphs, clear hierarchy

Headlines, subheads, and body copy should have an obvious size difference. I aim for a 28–32px H1, 20–22px H2, and 16px body, with at least 1.5 line height. Bolding one or two phrases per section guides the F-pattern; bolding twelve things in a section gives the reader nothing to anchor on. [MY EXPERIENCE: template change that lifted click rates with specific numbers]

Text-first, image-second

Images break. Images get blocked. Images load slowly on transit Wi-Fi. A template that's legible with every image stripped out is a template that works everywhere. Design for the worst case first; enhance upward.

How do you design for mobile?

Design mobile-first because mobile's already the majority of your opens. Litmus's 2024 research puts mobile at 41.9% of opens and webmail (much of it on mobile browsers) at another large slice; once you account for Apple Mail on iPhone, more than 60% of real reads happen on a phone screen (Litmus 2024 State of Email Engagement). Email on Acid's mobile rendering research adds the detail that even within "mobile" there's huge variance between Gmail Android, iOS Mail, and Outlook mobile (Email on Acid mobile rendering guide).

A few rules I don't break anymore:

• Body container max-width: 600px; it degrades gracefully to any phone
• Minimum 44x44px tap targets for buttons (matches Apple's HIG and keeps thumbs happy)
• Font size 16px minimum in body copy; iOS zooms anything smaller
• Line length between 50–75 characters per line on desktop; shorter on mobile
• No background images in layouts that break without them (Outlook ignores many)

MJML handles most of this automatically, which is why I default to it. MJML compiles a sane, human-readable markup language down to the table-based HTML that email clients actually render (MJML documentation). If you're writing hand-crafted html-email and hand-rolling media queries, you're doing 3x the work for the same output. The MJML to HTML converter will turn a 40-line MJML file into the 400-line HTML file Outlook needs, and you can paste the result straight into any ESP.

Once the template is built, preview it across clients. Mailneo's responsive email tester runs a single template against a dozen viewport widths in one pass, which is the fastest way to catch the "looks great on my MacBook, breaks on a Pixel 7a" bug.

How do you test an email template before sending?

Test it three ways: render testing, content testing, and a seed send. Skip any one and you'll ship bugs. I lost a client 8% of a campaign's revenue once because a dark-mode color swap turned black text on a dark grey button into invisible text on a dark grey button. It rendered fine on every Litmus preview I ran; I just hadn't flipped dark mode on the iPhone simulator. Lesson learned, expensively.

Render testing

Run every template through Litmus or Email on Acid before the first real send. Both services spin up real clients (Outlook 2016, Gmail iOS, Apple Mail, Thunderbird) and screenshot what they actually render. A template that looks perfect in Chrome can and will break in Outlook 2007 on a corporate customer's locked-down laptop.

Content testing

Read it aloud. Honest advice; takes 90 seconds. If a sentence sounds like a pitch deck, rewrite it. If the CTA doesn't finish the thought started in the hero, rewrite it. If you can't find the unsubscribe link in 5 seconds, the footer's too clever.

Seed send

Send to a small internal list (or to yourself across 3–4 inbox providers) before you push to the full audience. Look at:

• Does the subject line render without truncation in the preview pane?
• Does the preheader appear (and not "View in browser")?
• Do images load without being blocked by default?
• Does the CTA button render as a button, not a blue underlined link?
• Does dark mode invert any colors in an unintended way?

[ORIGINAL DATA: CTR delta for Mailneo templates vs custom-built on the platform]

[SCREENSHOT: Mailneo template editor or a responsive-render preview]

What are the accessibility fundamentals for email templates?

Accessibility isn't a nice-to-have; it's both an ethical requirement and a deliverability signal. Screen-reader users, low-vision users, and users with cognitive differences all get served by the same fundamentals that tend to improve conversion for everyone else. WebAIM's guidance on email accessibility is the clearest starting point I've found (WebAIM accessibility guidance).

Four things to verify on every template:

• Alt text on every image that carries meaning; alt="" on purely decorative images
• Semantic heading structure (one H1, then H2/H3 in order, no skipping levels)
• Color contrast of at least 4.5:1 for body copy against its background
• Logical reading order when CSS is stripped (because screen readers often strip CSS)

Mailneo's email accessibility checker flags all four automatically; it's the single fastest pre-send check I run. Icons and small illustrations can also become a contrast trap if you pick the wrong palette, so the email icon pack ships with a tested-contrast set I use by default.

What are the common template mistakes that tank conversion?

The same seven mistakes show up in almost every underperforming template I review. None of them are exotic; most are boring fixes that take an afternoon.

1. Multiple competing CTAs. Pick one. Put secondary links in the footer.
2. Image-only hero (or worse, image-only email). Gmail clips image-heavy emails as promotions; Outlook blocks images by default.
3. Copy that opens with company news instead of reader value. Nobody cares what your team did last quarter; they care what's in this email for them.
4. Subject/preheader mismatch. If your subject promises a discount and the preheader talks about a webinar, both feel dishonest. (See also the companion guide on email subject lines for pairing heuristics.)
5. Over-personalization. "Hey {{first_name|friend}}" that renders as "Hey friend" signals broken merge fields. Subtle email personalization (referencing plan tier, last action, or segment) outperforms shallow name-drops every time.
6. Walls of text. Anything longer than three short paragraphs without a subhead is a wall. Break it up.
7. Footer-less templates. Missing physical address = CAN-SPAM violation in the US; missing unsubscribe = GDPR violation in the EU.

One more, specific to teams using AI: don't let AI-generated copy ship without a human edit. I've written about the practical workflow in the how to use AI email writing guide, but the short version is that AI drafts are starting points, not finished work. An AI template you didn't read carefully will sound like an AI template, and readers notice.

Key takeaways

• A converting template has one CTA, a hero that answers "why should I read this", and a single-column mobile-first layout; everything else is a tax on the primary action.
• Mobile is 60%+ of real opens once Apple Mail is factored in (Litmus 2024), so any design decision that breaks below 375px costs you roughly half your audience.
• Preheader text is the second half of the open decision; good preheaders read like a second subject line and should be previewed before every send.
• Accessibility fundamentals (alt text, semantic headings, 4.5:1 contrast) are the same fundamentals that lift conversion for sighted users on slow connections.
• The average email click-through rate sits near 2.3% across industries (Campaign Monitor, 2024); templates beating that number are almost always doing less, not more.

Frequently asked questions

How long should a converting email template be?

Long enough to make the promise credible and short enough that the reader hits the CTA before scrolling away. In practice, that's roughly 80–160 words of body copy for most transactional or promotional sends; newsletters can run longer if they're formatted as clear sections with subheads. If you're over 300 words, break it into a digest layout with multiple short summaries, each linking out.

Should I use an ESP's drag-and-drop builder or hand-coded HTML?

Start with MJML or a drag-and-drop builder that outputs clean HTML (Mailneo's does; many competitors' don't). Hand-coded HTML is only worth it if you have a designer who knows the Outlook 2016 table-layout quirks cold. MJML gives you 90% of the control for 30% of the effort, and it exports straight to the HTML email clients need.

How many A/B tests should I run on a template before calling it a winner?

At minimum, get to statistical significance at 95% confidence, which typically means 1,000+ opens per variant for CTR tests. Small lists won't reach that on a single send; aggregate three or four sends of the same template to hit sample size. Declaring a winner at 200 opens is how templates end up "optimized" on noise.

Do emojis in preheaders help or hurt conversion?

It depends on your audience and your brand voice. Consumer audiences often see a modest open-rate lift from a well-chosen emoji in the preheader (not the subject line); B2B audiences tend to ignore or penalize them. Test on your own list before assuming either way; "best practice" advice on emoji usage changes every 18 months.

What's the minimum image size I should design for in the hero?

Design the hero image for 1200x600px at 2x retina, then compress to under 200kb. Smaller hero images load faster on cellular connections; compressed JPEGs beat uncompressed PNGs almost every time for photographic content. For iconography or flat illustrations, SVG is ideal but not all clients render it, so export a PNG fallback.

Related resources

• MJML to HTML converter: turn MJML into Outlook-safe HTML
• Responsive email tester: preview templates across viewport sizes
• Email accessibility checker: flag alt text, contrast, and heading issues
• Email preheader previewer: see what each inbox client actually shows
• Email icon pack: tested-contrast icons for email templates
• Guide to email subject lines: pair the subject line with your preheader
• How to use AI email writing: ship AI drafts without the AI tells
• Email personalization: go deeper than merge-tag name drops