E-Shot Media Practical guides to email newsletters

Template

Plain HTML email starter template

A small, commented, single-column HTML email you can copy, with an explanation of every part and why it is there.

Updated 9 min read

Most of the time you will build emails in your email tool’s editor, and that is fine. But it helps to know what a sound HTML email looks like underneath, especially if you are using a self-hosted tool that expects you to paste in your own template, or if your tool’s templates keep breaking in Outlook. This page gives you a small, complete starter you can copy and adapt.

It is deliberately plain: one column, about 600 pixels wide, live text, one image and one button. That shape works in almost every email app because it asks very little of them. Copy the code below, replace the example bakery details with your own, and send yourself a test before you use it with real subscribers.

The template

<!doctype html>
<html lang="en-GB" xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <meta name="color-scheme" content="light dark">
  <meta name="supported-color-schemes" content="light dark">
  <title>Riverside Bakery: October news</title>
  <style>
    /* Clients that support <style> get these extras. Everything
       essential is also inline, below. */
    body { margin: 0; padding: 0; }
    a { color: #1a4fa0; }
    @media (max-width: 620px) {
      .container { width: 100% !important; }
      .px { padding-left: 20px !important; padding-right: 20px !important; }
    }
    @media (prefers-color-scheme: dark) {
      .bg-page { background-color: #111418 !important; }
      .bg-card { background-color: #1c2128 !important; }
      .text    { color: #e8e6e1 !important; }
      .muted   { color: #b5b1a8 !important; }
      a        { color: #8db4ff !important; }
    }
  </style>
</head>
<body style="margin:0; padding:0; background-color:#f4f1ea;">

  <!-- Preheader: shown in the inbox, hidden in the email itself -->
  <div style="display:none; max-height:0; overflow:hidden; mso-hide:all;">
    New autumn loaves, a Saturday baking class, and our Christmas order dates.
  </div>

  <table role="presentation" class="bg-page" width="100%" cellpadding="0" cellspacing="0" border="0" style="background-color:#f4f1ea;">
    <tr>
      <td align="center" style="padding:24px 12px;">

        <table role="presentation" class="container bg-card" width="600" cellpadding="0" cellspacing="0" border="0" style="width:600px; max-width:600px; background-color:#ffffff;">

          <!-- Header: live text, not an image -->
          <tr>
            <td class="px text" style="padding:28px 40px 8px; font-family:Arial, Helvetica, sans-serif; font-size:14px; line-height:20px; color:#555555;">
              Riverside Bakery &middot; October 2026
            </td>
          </tr>

          <!-- Main image -->
          <tr>
            <td style="padding:16px 0 0;">
              <img src="https://www.example.co.uk/email/autumn-loaves.jpg" width="600" alt="Three sourdough loaves on a wooden board" style="display:block; width:100%; max-width:600px; height:auto; border:0;">
            </td>
          </tr>

          <!-- Body copy -->
          <tr>
            <td class="px text" style="padding:28px 40px 8px; font-family:Arial, Helvetica, sans-serif; font-size:16px; line-height:26px; color:#222222;">
              <h1 style="margin:0 0 16px; font-size:26px; line-height:32px; font-weight:bold;">Autumn loaves are back</h1>
              <p style="margin:0 0 16px;">Hi {{first_name|there}},</p>
              <p style="margin:0 0 16px;">Our spelt and walnut loaf returns this Friday, and we have four places left on Saturday&rsquo;s beginners&rsquo; bread class.</p>
            </td>
          </tr>

          <!-- Button: a padded link inside a table cell -->
          <tr>
            <td class="px" style="padding:8px 40px 32px;">
              <table role="presentation" cellpadding="0" cellspacing="0" border="0">
                <tr>
                  <td style="border-radius:6px; background-color:#1a4fa0;">
                    <a href="https://www.example.co.uk/classes" style="display:inline-block; padding:14px 28px; font-family:Arial, Helvetica, sans-serif; font-size:16px; line-height:20px; font-weight:bold; color:#ffffff; text-decoration:none; border-radius:6px;">Book a class place</a>
                  </td>
                </tr>
              </table>
            </td>
          </tr>

          <!-- Footer -->
          <tr>
            <td class="px muted" style="padding:24px 40px 32px; border-top:1px solid #e5e1d8; font-family:Arial, Helvetica, sans-serif; font-size:13px; line-height:20px; color:#5f5f5f;">
              <p style="margin:0 0 8px;">You are getting this because you signed up to Riverside Bakery news at riverside.example.co.uk.</p>
              <p style="margin:0 0 8px;">Riverside Bakery Ltd, 1 Example Street, Exampletown, EX1 2AB</p>
              <p style="margin:0;"><a href="{{unsubscribe_url}}" style="color:#1a4fa0;">Unsubscribe</a> &middot; <a href="mailto:hello@example.co.uk" style="color:#1a4fa0;">Reply to us</a></p>
            </td>
          </tr>

        </table>

      </td>
    </tr>
  </table>
</body>
</html>

Why it is built this way

Email HTML is not like web HTML. Each email app, from Gmail and Apple Mail to the various versions of Outlook, decides for itself which HTML and CSS it supports, and some versions of Outlook on Windows use a rendering engine based on Microsoft Word. The safe approach is to use simple, old-fashioned techniques that everyone understands, and to treat anything newer as an optional extra.

The head

The charset and viewport meta tags make sure characters such as the pound sign display correctly and that phones show the email at a sensible size. The color-scheme and supported-color-schemes tags tell apps that support them that your email is designed to work in both light and dark mode, which can stop them applying their own heavy-handed colour changes. The lang attribute helps screen readers use the right pronunciation.

The style block

Some apps read a <style> block; some strip it out. So the block here only holds extras: a mobile adjustment that makes the 600px container full width on small screens, and dark-mode colours. Everything the email needs to look right is repeated as inline style attributes on the elements themselves. If your tool inlines CSS automatically, you can write more in the block, but keep the principle that the email must still work if the block disappears.

The hidden preheader

The div just inside the body holds the preheader: the line many inboxes show next to or under your subject line. It is hidden in the email itself but read by inbox previews. Without it, apps grab the first text they find. Write it as a second line to your subject line, not a repeat of it. See subject lines and preheaders for more.

Tables with role="presentation"

Layout tables are still the most reliable way to centre a fixed-width email across apps, particularly in Outlook for Windows. Adding role="presentation" tells screen readers to ignore the table structure, so they do not announce “table, three rows” before every paragraph. The outer table fills the screen with the background colour; the inner one is the 600px card.

Live-text header and body

The bakery name at the top is real text, not a logo image. If images are blocked, which is still common in some workplace email setups, the reader still sees who the email is from. If you want a logo, add it as an image with alt text set to your organisation’s name, and keep the important words in text. Body text is 16px with generous line height, which is comfortable to read on a phone.

The image

The image has a width attribute for Outlook, plus width:100% and height:auto in the inline style so it shrinks on phones. display:block removes the small gap some apps add below images. The alt text describes what the picture shows. Export images at twice the display size (here, 1200px wide) for sharp results on high-resolution screens, and compress them well.

The button

The button is a normal link, given padding and a background so it looks like a button. Because it is live text, it is readable with images off, works with screen readers and can be tapped easily. The background colour is set on the table cell as well as the link because a few apps ignore padding on links; in those apps, the cell colour still shows. Check that your button text has strong contrast with its background in both light and dark mode.

The footer

The footer says why the reader is getting the email, who sent it and where you are, and gives a clear way to unsubscribe. Identifying yourself and offering a simple opt-out in every marketing message are requirements under PECR, not optional extras. Use your real organisation name and a valid contact address. The ICO’s guidance on direct marketing using electronic mail explains the rules.

Dark mode

The prefers-color-scheme: dark rules swap the background and text colours in apps that support them, such as Apple Mail. Other apps handle dark mode their own way: some leave your colours alone, and some invert them automatically, and you cannot fully control the result. The defensive approach is to avoid pure black text on pure white, avoid images of text, and give logos with transparent backgrounds a light outline or a solid background so they do not disappear on dark grey.

Adapting it

To add another section, copy one of the body copy rows (a <tr> and its <td>) and paste it below. Keep to a single column: two-column layouts need extra code to stack on phones and are the most common source of broken emails. Keep the total HTML small, because Gmail clips messages over roughly 100KB and hides the rest behind a “View entire message” link, which can hide your footer and unsubscribe link with it.

Keep fonts to safe system choices such as Arial, Helvetica or Georgia. Web fonts work in some apps and fall back silently in others, so always name a safe fallback. Avoid relying on background images, CSS grid, flexbox or JavaScript, none of which you can count on in email.

Testing before you use it

  1. Paste the template into your tool’s HTML or code editor and replace the merge tags with your tool’s own.
  2. Send a test to yourself and open it in at least Gmail (on the web and on a phone), Apple Mail or the iPhone Mail app, and Outlook if your readers use it at work.
  3. Check it with images turned off, and in dark mode on your phone.
  4. Click every link, including the unsubscribe link, in the received test, not in the editor.
  5. Run through the pre-send checklist before the real send.

When you want to know whether a particular HTML or CSS feature works in a particular app, look it up on Can I email, which tracks support across email clients. For the wider design principles behind this template, read designing emails that render everywhere.