Email Template Best Practices for 2026: Copyable Templates by Use Case
Structures you can copy for welcome, billing, retail, clinic and nonprofit emails, plus the tools that build and send them.
By the editorial team. Last updated 8 October 2026. Prices are taken from each vendor's pricing page as checked on 7 October 2026.
For most small teams the best starting point is Stripo, because its free plan has no time limit, so you can build and refine a template before you pay anything; its Basic plan is $20 per month when you need more. Pair it with the email platform you already send from. If you have no platform yet and your list is 250 contacts or fewer, Mailchimp's free plan covers that size and sends up to 500 emails a month. The rest of this page gives you copyable template structures by use case and industry, the technical rules that keep them rendering correctly, and a clear comparison of the tools that build and send them.
Start with the job each email does
A template is only as good as the job it does. Before you open a builder, write one sentence for each email type: who receives it, what they should do next, and what happens if they ignore it. "A trial user who signed up but has not created a project should book a setup call within three days" is a usable brief. "A nice welcome email" is not. That single sentence decides the order of blocks, the length of the copy and the one call to action you keep. It also prevents the most common failure in template libraries: a dozen near-identical layouts with different logos and no clear purpose. Group your emails into a small number of families, such as onboarding, billing, reminders, news and transactional notices, and build one master layout per family. Each family then shares header, footer and button styles, and you only change the middle section for each specific email.
Technical rules that still matter
Use table-based layouts for structure
Email clients do not support modern page layout reliably, so most production templates still use nested HTML tables for structure. Mark layout tables with role="presentation" so screen readers do not announce them as data tables. Keep the nesting shallow; deep nesting makes templates fragile and hard to edit.
Inline the CSS that matters
Many clients ignore or strip styles placed in the document head, so put font, colour, spacing and width rules directly on the elements they affect. Build tools such as MJML or Maizzle can do this automatically, which lets you keep readable source while sending inlined markup.
Use a single column about 600 pixels wide
A single column around 600 pixels wide is the convention most templates follow. It reads comfortably on desktop and mobile without horizontal scrolling. Avoid designs that depend on two columns side by side on phones; if you need two columns, stack them below a width breakpoint and check that the stacked order still makes sense.
Build buttons from HTML, not images
Many clients block images until the reader allows them, so a call to action built as an image can disappear entirely. A bulletproof button is a styled table cell with a link inside it. It stays visible and clickable when images are off. Here is a minimal version you can copy:
<table role="presentation" cellspacing="0" cellpadding="0" border="0">
<tr>
<td bgcolor="#1d4ed8" style="border-radius:4px;">
<a href="https://example.com/start" style="display:inline-block;padding:12px 20px;font-family:Arial,Helvetica,sans-serif;color:#ffffff;text-decoration:none;">Start your trial</a>
</td>
</tr>
</table> Use system fonts as fallbacks
Web fonts do not load everywhere. Specify a font stack such as Arial, Helvetica, Georgia or Verdana after any custom font, so the email still looks deliberate when the custom font fails. Set font size and line height explicitly; leaving them to client defaults is a frequent cause of cramped or oversized text.
Write alt text for every meaningful image
Alt text is what a reader sees while images are blocked, and what a screen reader announces. Describe the content or purpose of the image in a few words. Decorative spacer images should carry empty alt text. A logo should be described as the company name, not as "logo".
Keep contrast high enough to read
The Web Content Accessibility Guidelines ask for a contrast ratio of at least 4.5:1 for normal body text (WCAG 2.2, success criterion 1.4.3). Check light grey text on white and white text on coloured buttons in particular, because those combinations fail most often in marketing designs.
Keep the HTML lean
Large messages are more likely to be clipped or to fail in some clients, and heavy markup is slower to edit. Remove duplicate styles, skip unused layout tables and compress images before you upload them. Keep the message light enough that the most important content appears early in the source as well as on screen.
Copyable template structures by use case
Each template below gives you the order of blocks, a subject line pattern, a preview line and the call to action. Replace the bracketed text with your own details. The merge tag syntax depends on your sending platform, so use the form your platform expects, for example {{first_name}} in one system and *|FNAME|* in another.
SaaS: trial ending in three days
- Subject: Your trial of [Product] ends on [date]
- Preview: Keep your projects. Choose a plan in two minutes.
- Opening: Name the one feature the user already used, then say what changes on the end date.
- Middle: A short comparison of the two plans the user can pick, with the price and billing period for each.
- Call to action: "Choose a plan" linking to billing, not to the homepage.
- Footer: A one-line reason they got the email, and a way to reply with questions.
SaaS billing: a payment did not go through
- Subject: We could not process your [Product] payment
- Preview: Update your card to keep access. Takes about a minute.
- Opening: State the plan, the amount and the date of the failed charge in plain words.
- Middle: What happens next and when access would change. Do not threaten; state the date.
- Call to action: One button to the card update page. Do not put a second button for support in the same block.
- Footer: A reply address for billing questions, and a note that the receipt is sent separately.
Billing emails are transactional in tone. Keep them short, avoid promotional imagery and use a plain sender name so the email reads as a notice rather than an advertisement.
Clinic: appointment recall
- Subject: Time for your check-up at [Clinic name]
- Preview: Book online or call the front desk.
- Opening: The date of the patient's last visit and the interval the clinic recommends.
- Middle: Two or three available time slots, or a link to see current availability.
- Call to action: "Book my appointment" to the booking page.
- Footer: Phone number, opening hours and a way to opt out of reminders.
Health-related sends need care with content. Send only the information the patient already has a reason to expect, keep clinical detail out of the body, and check your local rules on patient communication before you use merge fields for treatment names. Use a dedicated sender identity so patients can recognise the clinic.
Restaurant: reservation confirmation
- Subject: Your table at [Restaurant] on [day] at [time]
- Preview: Change or cancel with one tap.
- Opening: Date, time, party size and address.
- Middle: Parking or arrival notes and any policy about late arrivals.
- Call to action: "Change reservation" linking to the management page.
- Footer: Phone number for same-day changes.
Online store: shipping update
- Subject: Your order [number] has shipped
- Preview: Track your parcel and see the delivery window.
- Opening: Carrier name and tracking link above the fold.
- Middle: A list of the items in the parcel, with quantities.
- Call to action: "Track parcel".
- Footer: Returns policy link and customer service contact. Do not add a promotion to a shipping notice.
Nonprofit: donation receipt with impact update
- Subject: Thank you, [first name]. Your gift is received.
- Preview: Your receipt is attached and below.
- Opening: The amount, the date and the designation of the gift.
- Middle: One specific example of what the gift paid for. Describe what happened, not an outcome you cannot show.
- Call to action: A link to a short impact page, not a second donation request.
- Footer: Tax information where it applies, and an address for corrections.
Re-engagement: a quiet list
- Subject: Still want [topic] updates?
- Preview: One click keeps you on the list.
- Opening: Acknowledge the gap in plain words, without guilt language.
- Middle: The two or three types of email the subscriber can expect, so the choice is clear.
- Call to action: "Keep me subscribed" as the primary button, with "Update preferences" as a text link.
- Footer: Unsubscribe link in the standard position.
The tools that build and send these templates
The tools below fall into three groups: visual builders for designers and marketers, code frameworks for developers, and sending platforms that also offer templates and automation. Most teams combine one from the first two groups with one from the third. The table compares the entry point of each tool, using the prices on each vendor's pricing page as of 7 October 2026.
| Tool | Best for | Starting price (plan, billing) | Key limitation |
|---|---|---|---|
| Stripo | Drag-and-drop templates for marketers | Free plan with no time limit; Basic $20 per month | The price shown is monthly; no annual rate is listed on the pricing page |
| Beefree | Teams that reuse content blocks across many designs | Starter free (up to 10 designs, 6 exports a month); Professional $30 per month | Free plan limits exports to 6 a month; 15-day free trial on paid plans |
| Email on Acid | Checking rendering across clients before a send | Basic $99 per month for 1,000 previews | No free plan is listed; it checks design, not your sending |
| MJML | Developers who want responsive markup in a simple syntax | Self-hosted; no subscription listed on the pricing page | Needs a developer and a build step |
| Maizzle | Developers who want a templating framework with inlining | Self-hosted; no subscription listed on the pricing page | Requires a configured project and a team comfortable with the tooling |
| Mailchimp | Small lists that need templates and sending in one place | Free up to 250 contacts and 500 sends a month; Standard from $20 per month at 500 contacts | Price rises by contact tier, so growing lists move up quickly |
| Constant Contact | Small businesses that want a free trial before paying | Lite $12 per month, or $10.20 billed annually | The exact price depends on your contact count, so check the pricing page for your size |
| Make | Triggering template emails from forms, CRMs and other apps | Free with 1,000 credits a month; Core $10.59 per month for 10,000 credits, or $9 billed annually | Free plan allows 2 active scenarios and runs at most every 15 minutes |
Stripo
Stripo suits marketers who need to produce a lot of designs without writing code. Its drag-and-drop editor gives you blocks for headers, buttons, columns and social links, and you can keep your own colours and fonts in one place so new templates start on brand. Its free plan has no time limit, which makes it a sensible place to build the first master layout for each email family.
Where it falls short: the paid plans are priced by tier, and a team that wants to avoid designer time will still need to test each design in the clients its audience uses. The Stripo plugin for other editors has its own pricing, with Plugin Startup at $100 per month and Plugin Business at $550 per month. Check the pricing page at stripo.email/plugin/ before you commit to a plugin tier, because the plugin and the standalone plans are separate products. Basic is $20 per month, Medium $45 per month and Pro $125 per month for the standalone editor.
Beefree
Beefree is a good fit for teams that reuse the same blocks across campaigns, such as a standard footer with legal text and a set of product cards. Professional at $30 per month gives you unlimited project folders and reusable content blocks, and the Business plan at $160 per month adds advanced brand controls, which matters once several people edit the same templates.
Where it falls short: the free Starter plan caps you at 10 designs and 6 exports a month, so a team that publishes often will reach the limit quickly. Plan on the Professional tier if you need unlimited folders. The 15-day free trial lets you test the workflow with real templates before you pay. Pricing is at beefree.io/pricing.
Email on Acid
Email on Acid is a checking tool rather than a builder. It previews a finished template in the clients your audience uses, and its Premium plan adds accessibility tests and HTML analysis. Use it for the last step before a major send, especially for billing or clinic emails where a broken button or clipped text carries real cost.
Where it falls short: there is no free plan on the pricing page, and the Basic plan at $99 per month includes 1,000 previews. Premium at $199 per month doubles that to 2,000 previews and adds the accessibility and HTML tools. It will not write your template or send it for you, so budget for a builder alongside it. See emailonacid.com/pricing for current plan details.
MJML and Maizzle
Both are code frameworks for developers. MJML gives you a simplified markup language that compiles to responsive HTML, and Maizzle is a templating framework that adds inlining and a build pipeline on top of standard HTML and CSS. The advantage is version control: templates live in a repository, change through pull requests, and can be reviewed like any other code. That is valuable for billing and transactional emails that change rarely and must not break.
Where they fall short: both need a developer and a build step, and neither includes a sending platform. Neither lists a subscription on its pricing page, so your cost is the developer time to set up and maintain them. Check mjml.io/pricing and maizzle.com/pricing for the current terms of each.
Mailchimp
Mailchimp combines templates, a contact list and sending in one account, which removes the handover step that trips up small teams. Its free plan covers up to 250 contacts and 500 sends a month, with a maximum of 250 sends per day, so a newsletter for a local business or a small nonprofit can run at no cost. Templates made in the editor can be reused for each campaign.
Where it falls short: the price is tied to contact tiers, and the jumps are steep. At 500 contacts the Standard plan starts at $20 per month, and the 2,501–5,000 contact band is $100 per month. Plan for the band you will be in within a year, not just today's list. Pricing is at mailchimp.com/pricing.
Constant Contact
Constant Contact fits small businesses that want to try the platform before paying. Its free trial needs no credit card, and it bundles email with social media tools on its entry plan. Lite starts at $12 per month billed monthly or $10.20 per month billed annually, Standard at $35 or $29.75, and Premium at $80 or $68 on the same basis.
Where it falls short: the exact price depends on your contact count, so the plan figures above are starting points. If your list is large or changes often, ask for the price at your size before you build templates around a plan. Details are on constantcontact.com/pricing.
Make
Make is not an email platform. It is a workflow builder that connects forms, CRMs, payment tools and other apps. Its value for templates is triggering the right template at the right moment: a new trial sign-up starts the onboarding family, a failed payment starts the billing notice, a reservation starts the confirmation. It has more than 3,000 apps available.
Where it falls short: the free plan allows 2 active scenarios and runs at most every 15 minutes, which is enough to test a flow but not to run a busy store. The Core plan at $10.59 per month for 10,000 credits, or $9 per month billed annually, removes the scenario cap and lets you schedule down to the minute. Each module action uses one credit, so count credits before you add steps. See make.com/en/pricing.
What the monthly cost looks like at real list sizes
Cost depends on how many contacts you store, not how many templates you own. The table shows the sending platforms that publish contact-based prices. Where the pricing page does not give a figure for your size, the table says so instead of estimating.
| Contact list size | Mailchimp (plan and monthly price) | Constant Contact |
|---|---|---|
| 500 contacts | Standard, from $20 per month, up to 6,000 emails a month at this size | Pricing on request for this contact count |
| 5,000 contacts | Contacts 2,501–5,000 band, $100 per month, up to 60,000 emails a month | Pricing on request for this contact count |
| 10,000 contacts | Contacts 5,001–10,000 band, $135 per month, up to 120,000 emails a month | Pricing on request for this contact count |
Two conclusions follow. First, the step from 2,500 to 5,000 contacts on Mailchimp is the largest single jump in these bands, so model it before you grow the list through a paid acquisition campaign. Second, if you run a Make scenario that triggers emails, budget that cost separately: at 10,000 credits a month on the Core plan it is $10.59 per month, and the number of credits you use depends on how many steps each scenario contains.
Which tool to choose
Choose by the constraint that matters most, not by the longest feature list. A solo marketer with no developer needs a visual builder and a sending platform that fits the list size. A development team with a release process needs code, version control and a checking tool. A business whose emails depend on payments or bookings needs a trigger tool as well. The table below turns that reasoning into a short decision list.
| If you need | Pick | Because |
|---|---|---|
| A template this week and no developer | Stripo, starting on the free plan | Drag-and-drop blocks, and the free plan has no time limit |
| Reusable blocks shared by a team | Beefree Professional at $30 per month | Unlimited project folders and reusable content blocks |
| Rendering checks before a major send | Email on Acid, Basic at $99 per month | Previews across the clients your audience uses, with no free plan to rely on |
| Version-controlled templates from developers | MJML or Maizzle | Templates live in a repository and change through review |
| Sending under 500 emails a month to a small list | Mailchimp free plan | Up to 250 contacts and 500 sends a month at no cost |
| Emails triggered by forms, CRM records or payments | Make, Core at $10.59 per month for 10,000 credits, sending from your platform | Connects the events to the right template without manual sends |
| A trial with no card before committing | Constant Contact | Free trial that needs no credit card, then plans from $12 per month |
Setup checklist for a new template family
A template family is a master layout plus the emails that use it. Set one up in this order and you avoid rebuilding headers and footers each time a new email is needed.
| Step | What to do | Done when |
|---|---|---|
| 1. Inventory | List each email, its trigger and the one action it asks for | Every email has a sentence describing its job |
| 2. Master layout | One single-column table layout with header, body slot, button and footer | The layout renders in your two most-used clients |
| 3. Merge tags | Map each field to the syntax your sending platform uses | A sample contact fills every field with no blanks |
| 4. Accessibility | Alt text on meaningful images, contrast checked, link text descriptive | No link reads "click here" and text meets the contrast target |
| 5. Rendering test | Preview in the clients your audience uses, or send to seed addresses | Images load, buttons are visible and clickable with images off |
| 6. Send test | Send to an internal list and click every link | Every link goes to the page the copy promises |
| 7. Owner | Name one person to approve changes and review the family each quarter | The owner's name is in the template notes |
Moving templates between tools
Templates often move when a team changes its sending platform or adds a builder. The safest route keeps the HTML as the source and rebuilds only the parts the new tool handles differently. Export the HTML from the current builder, not a screenshot. Then open it in the target editor and check three things: how it treats your merge tags, whether it keeps your table layout or rewrites it, and whether it keeps the button markup. Many editors convert merge tags to their own syntax, so rename them by hand and test with a sample contact.
Keep a single source of truth for copy. Store subject lines, preview text and button labels in a shared document, so when a template moves you copy the words from one place rather than from an old version. For billing and transactional emails, freeze the old version until the new one has passed the checklist above, because a broken billing email is more costly than a slow migration.
Frequently asked questions
Which template tool should a small team start with?
Start with Stripo on its free plan if you need to design without code, because the free plan has no time limit. Move to its Basic plan at $20 per month when you need more than the free tier covers. If you already send from Mailchimp and have 250 contacts or fewer, its free plan lets you use its editor at no cost.
Do I need a paid sending platform to use these templates?
Not for a small list. Mailchimp's free plan covers up to 250 contacts and 500 sends a month, with a limit of 250 sends per day. Once you exceed that, the Standard plan starts at $20 per month at 500 contacts. Templates made in a separate builder can be exported as HTML and used in any platform that accepts it.
Are bulletproof buttons still necessary?
Yes, for any call to action that matters. A button built as an image disappears when images are blocked, and the reader has no obvious next step. A table-cell button with a text link stays visible and clickable in every case, so use it for billing, booking and purchase emails.
How often should I re-test templates?
Test every template after each edit to its layout or merge tags, and run the full checklist before any major send. Recheck the master layouts once a quarter, because clients change how they render content over time. Assign one owner so the review does not depend on whoever happens to send next.
Why does Constant Contact not show a single price for my list?
Its pricing depends on how many contacts you store, and the pricing page gives plan prices alongside the contact-count rules rather than a fixed figure for every size. The plan prices in this article are the starting figures from the pricing page as checked on 7 October 2026. For an exact figure at your list size, check the pricing page or request a quote.
Can Make send the emails itself?
Make is a workflow builder. It connects your forms, CRM and payment tools and triggers actions in other apps, including your email platform. Use it to decide when a template goes out and which contact it goes to, then let your sending platform deliver the message. Each step in a scenario uses credits, so count those before you design a busy flow.