Technical

Responsive Email Templates: Copyable Code, Use Cases and the Tools to Test Them

For most teams the best single pick for this job is Email on Acid. Its Basic plan starts at $99 a month for 1,000 email previews across 100+ clients and devices, and the preview step is where responsive problems show up before a send. The templates below are plain HTML you can build and send without a paid design tool.

What "responsive" means in an email template

A responsive email is one whose layout reflows to fit the reader's screen. The idea is the same as on the web, but the rendering is not. Email clients run their own engines, strip some CSS, rewrite others and ignore whatever they do not support. A template that looks right in a browser window can still break in a mail app, so responsive email is built on habits rather than on a single trick.

Three habits do most of the work. First, default to a single column, because it reads correctly with no help from CSS. Second, use a fluid container with a maximum width of about 600 pixels, so the email is full width on a phone and capped on a desktop. Third, treat media queries as an enhancement. They give you control on phones where they are supported, but the base layout has to work without them, because some webmail clients do not apply them consistently. Gmail's web interface has been one of the inconsistent cases, so check how the template behaves in each client you care about rather than assuming.

Every template in this guide follows those habits. The code is written with tables for layout, inline styles for the things that matter most and a short media query block for mobile refinements. That structure is older and plainer than modern web code, but it is the structure that mail clients have historically rendered most predictably.

The tools in this guide and what each one does

Three tools come up in the rest of this guide, and they do different jobs. Email on Acid checks how a finished template renders. Make connects a trigger, such as a form submission or an order, to the template and to whatever app sends it. Close is a sales CRM that includes bulk email in its higher tiers, which matters if your templates are for outreach. Mixing them up is the most common buying mistake, so the table below lists what each one is for and the entry price printed on its pricing page.

Tool Best for Entry price (as listed) Key limitation
Email on Acid Checking how a template renders across clients before you send it Basic at $99 per month, 1,000 email previews per month, API access included It previews and tests templates. It does not send email and has no free plan
Make Triggering a template from a form, store or CRM event without writing code Free plan with 1,000 credits per month. Core at $10.59 per month, or $9 per month billed annually, for 10k credits Each module action uses a credit. The free plan allows 2 active scenarios
Close Sales teams sending templated follow-ups from a pipeline Free 14-day trial, no credit card required. Growth at $109 per user per month, or $99 billed annually, includes bulk email Priced per user. Bulk email is not included in the Solo or Essentials tiers

Copyable base template: a single-column skeleton

The skeleton below is the starting point for most of the templates in this guide. It uses a 600-pixel container that becomes full width on small screens, a headline and body block, a button built from a table cell so it stays clickable in clients that ignore button styling, and a footer with an unsubscribe link. Replace the placeholder text, the link targets and the colours, and keep the structure.

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="x-apple-disable-message-reformatting">
<title>Your subject line</title>
<style>
  body { margin: 0; padding: 0; background: #f4f4f5; }
  img { border: 0; display: block; max-width: 100%; height: auto; }
  a { color: #1d4ed8; }
  .btn { display: inline-block; padding: 14px 24px; font-family: Arial, Helvetica, sans-serif; font-size: 16px; color: #ffffff; text-decoration: none; border-radius: 6px; }
  @media screen and (max-width: 600px) {
    .container { width: 100% !important; }
    .px { padding-left: 16px !important; padding-right: 16px !important; }
    .h1 { font-size: 22px !important; line-height: 1.3 !important; }
  }
</style>
</head>
<body>
<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#f4f4f5">
  <tr>
    <td align="center">
      <table role="presentation" class="container" width="600" cellpadding="0" cellspacing="0" border="0" style="width:100%; max-width:600px;" bgcolor="#ffffff">
        <tr>
          <td class="px" style="padding:32px 32px 8px 32px; font-family:Arial,Helvetica,sans-serif; font-size:16px; line-height:1.5; color:#374151;">
            <p class="h1" style="margin:0 0 16px 0; font-size:24px; color:#111827;">Headline that states the benefit</p>
            <p style="margin:0 0 16px 0;">One short paragraph. Keep it to two or three sentences so it reads well on a phone.</p>
          </td>
        </tr>
        <tr>
          <td class="px" align="center" style="padding:8px 32px 32px 32px;">
            <table role="presentation" cellpadding="0" cellspacing="0" border="0">
              <tr>
                <td bgcolor="#1d4ed8" style="border-radius:6px;">
                  <a class="btn" href="https://example.com/offer">Button text</a>
                </td>
              </tr>
            </table>
          </td>
        </tr>
        <tr>
          <td class="px" style="padding:16px 32px; font-family:Arial,Helvetica,sans-serif; font-size:12px; line-height:1.4; color:#6b7280;">
            You are receiving this because you subscribed. <a href="https://example.com/unsubscribe">Unsubscribe</a>
          </td>
        </tr>
      </table>
    </td>
  </tr>
</table>
</body>
</html>

A few details in the skeleton matter more than they look. The container has a width attribute of 600 as well as a max-width style, because some clients read the attribute and others read the style. The button sits inside a cell with a background colour, so the button shape survives even where the CSS class does not. Font sizes stay at 16 pixels for body copy and 12 pixels for the footer, which is the smallest size that still reads comfortably without zooming. The media query only adjusts padding and the headline, so the layout works even when the query is ignored.

Outlook for Windows renders email with a word-processor engine and ignores max-width. In that client the container will usually fall back to its width attribute of 600, which is the intended result. Check it there specifically, because it is the client most likely to show a layout you did not expect.

Two-column blocks that stack on phones

Multi-column layouts are where most responsive email breaks. A product grid or a pair of feature blocks reads well on a desktop, but on a phone two narrow columns become unreadable. The snippet below keeps two columns on a wide screen and stacks them on a narrow one. It uses the same table structure as the skeleton and changes only the cell display on small screens.

<style>
  @media screen and (max-width: 600px) {
    .col { display: block !important; width: 100% !important; padding: 0 0 16px 0 !important; }
  }
</style>
<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0">
  <tr>
    <td class="col" width="50%" valign="top" style="padding:0 8px 16px 0;">
      <img src="https://example.com/images/item-a.jpg" width="280" height="200" alt="Item A, short description">
      <p style="margin:8px 0 0 0;">Item A name, price</p>
    </td>
    <td class="col" width="50%" valign="top" style="padding:0 0 16px 8px;">
      <img src="https://example.com/images/item-b.jpg" width="280" height="200" alt="Item B, short description">
      <p style="margin:8px 0 0 0;">Item B name, price</p>
    </td>
  </tr>
</table>

Three rules keep this block working. Give every image a width and height so the placeholder holds its space while the image loads. Write descriptive alt text, because a reader on a phone with images off should still understand what each item is. Order the cells so the first one in the markup is the one you want at the top of the stacked view, since that is the order a stacked reader will see.

Templates by use case

The right responsive pattern depends on what the email is for. A newsletter, a receipt and a promotion have different jobs, and each one needs a different emphasis. The notes below describe the decisions that matter for each, along with the parts of the skeleton you would change.

Newsletter

A newsletter is usually a long single column with a headline, a short intro, two or three article blocks and a footer. Keep the single column for the whole email. Use one primary button per article rather than a row of links, because a row of small links is the most common cause of mis-taps. Put the most important article first, since many readers will see only the top of the email before deciding whether to scroll. If you include a table of contents, make each entry a full-width line with generous spacing so the tap target is large enough.

Transactional receipt or order update

A receipt is a table of items, totals and a few links. The responsive problem is the table. On a desktop it can have four columns: item, quantity, unit price and total. On a phone four columns will squeeze the item name into a narrow strip. Stack each item as its own block, with the name on one line and the quantity and total on the next, and keep the total row in a full-width block at the bottom. Make the order number and the support link readable without zooming, because those are the parts a customer needs when something is wrong.

Promotional offer

Promotions are where designers are most tempted to add a hero image with text laid over it, a countdown, a coupon code box and three product grids. On a phone that stack becomes long and slow. Keep one offer, one headline and one button. If the offer depends on an image for its message, put the message in live text above the image as well, because many clients block images by default and a reader who sees only an empty box will not click. Test the coupon code block separately, since a code that wraps onto two lines is a common cause of failed redemptions.

Sales follow-up from a CRM

Sales follow-ups are shorter than newsletters and usually have a personal tone. The template should look like a message from a person rather than a brand banner, so drop the header image and keep a plain text layout with one signature block. Close's bulk email on its Growth tier and above is designed for this kind of templated outreach, and the same single-column rule applies. Keep the signature short enough that it does not push the call to action below the first screen on a phone.

Email on Acid: checking the render before you send

Email on Acid is the tool in this guide built around the question "how does this look in each client?" It previews a template across more than 100 clients and devices, which is the part a designer cannot reproduce by resizing a browser window. For a team that changes templates often, that check catches a large share of the problems that would otherwise reach subscribers.

What it does well for this audience

The Basic plan covers 1,000 previews per month and includes API access, which lets you run previews from a build step rather than by hand. The Premium plan adds accessibility tests and HTML analysis, which are useful for catching missing alt text, low-contrast text and code that a client is likely to strip. If your templates go through a review step, the preview gives reviewers a shared, visual reference that a screenshot in a chat thread does not.

Where it falls short

Email on Acid does not send email, and it does not build templates for you. You still need a sending tool, a template in HTML and someone who knows how to fix what the preview shows. It also has no free plan, so the first purchase is a monthly commitment from $99. If you only change templates a few times a year, the per-preview cost is hard to justify, and a set of test sends to accounts you control will cover most of the risk.

Price and pricing page

Basic is $99 per month for 1,000 email previews per month. Premium is $199 per month for 2,000 previews per month. Both are monthly subscriptions as listed. The full plan details are on the vendor's pricing page at emailonacid.com/pricing.

Make: connecting templates to the events that trigger them

Make is an automation builder. It does not design the email, but it decides when an email should be built and sent. A typical setup takes a form submission or an order event, pulls the customer's details, fills the template's variables and passes the result to the app that sends the message. For teams without developers, that visual flow is the practical way to make a template respond to real events.

What it does well for this audience

Make's free plan includes 1,000 credits per month with no time limit, and it has a visual builder with a large library of connectors. That makes it a reasonable place to prototype a receipt or welcome flow before committing to a paid tier. Each module action in a scenario uses one credit, so you can estimate usage by counting the steps in the flow. Core adds unlimited active scenarios and scheduling down to the minute. Pro adds priority execution, custom variables and full-text search of the execution log, which helps when a template sends the wrong variable and you need to find the run that did it.

Where it falls short

The free plan is limited in ways that matter for email. It allows only 2 active scenarios, scenarios can run at most every 15 minutes, each run is capped at 5 minutes and the execution log is kept for 7 days. A welcome flow that must fire within seconds of a sign-up will not work on the free plan. Credit use also grows with every extra step, so a template that loops through a long list of items can use credits faster than expected. Make is the connective layer, so the quality of the email still depends on the template and the sending app.

Price and pricing page

The free plan costs nothing and includes 1,000 credits per month. Core is $10.59 per month, or $9 per month billed annually, for a 10k credit allowance. Pro is $18.82 per month, or $16 per month billed annually. Teams is $34.12 per month, or $29 per month billed annually. These card prices are for 10k credits per month. Higher allowances are set on a slider on the vendor's pricing page at make.com/en/pricing, and Enterprise is priced on request.

Close: templated outreach from a CRM

Close is a sales CRM with calling, SMS and email built in. Its relevance to this guide is the bulk email feature, which lets a sales team send a templated message to a segment of contacts from the pipeline. If your templates are for outreach rather than newsletters, Close keeps the template, the contact record and the follow-up in one place.

What it does well for this audience

Close keeps the sales context next to the message. A rep can see the last call, the open deal and the previous emails before sending a follow-up, which matters when templates are personal. Automated workflows, custom activities and the power dialer appear from Growth upward, so a team that wants templated email tied to call activity has a single tool to manage. The AI credit allowance is listed per user on each tier, so the usage is predictable for a small team.

Where it falls short

Close has no ongoing free plan. The trial is 14 days and needs no credit card, but after it ends the cost is per user. Bulk email is not in the Solo or Essentials tiers, so a team that only wants a template sender will pay for Growth to get it. Calling and SMS usage is passed through at cost, which can add to the monthly bill. A team that only needs a newsletter sender should look at a dedicated email platform instead, because Close is priced for sales work.

Price and pricing page

Solo is $19 per user per month, or $9 per user per month billed annually. Essentials is $49 per user per month, or $35 billed annually. Growth is $109 per user per month, or $99 billed annually, and it is the first tier with bulk email. Scale is $149 per user per month, or $139 billed annually. Full details are on the vendor's pricing page at close.com/pricing.

What each option costs at realistic workloads

Because the tools are priced differently, a single "price" comparison is misleading. The table below uses the listed prices for a few realistic workloads. Where a tier is billed per user, the total multiplies the per-user price. Where a plan is billed monthly only, the table says so instead of inventing an annual figure.

Workload Plan Price as listed Billing
Solo designer checking up to 1,000 renders a month Email on Acid Basic $99 per month, which is $1,188 for 12 months Monthly subscription as listed
Team checking up to 2,000 renders a month Email on Acid Premium $199 per month, which is $2,388 for 12 months Monthly subscription as listed
Triggered emails with fewer than 1,000 actions a month Make Free $0, with 1,000 credits per month No payment
Triggered emails with up to 10k actions a month Make Core $10.59 per month monthly, or $9 per month billed annually, for 10k credits Monthly or annual
Sales team of 3 sending bulk templated email Close Growth $327 per month monthly (3 × $109), or $297 per month billed annually (3 × $99), which is $3,564 a year Per user, monthly or annual

Two of these rows show why the per-user figure needs care. A sales team of three on Essentials would pay $147 a month monthly or $105 a month billed annually, but that tier does not include bulk email, so it is not a substitute for Growth in this use case. Make's price rises with credit volume, so the realistic cost of an automation is the number of actions per run multiplied by the number of runs, not the card price on the page.

Decision table: which tool for which job

The decision table matches the most common situations to the tool that fits them, along with the reason. Most teams need one of these jobs more than the others, and the reason column explains why a second tool may still be necessary.

If you need Pick Because
Confidence that a template renders in many clients before a send Email on Acid Basic It previews across 100+ clients and devices, with API access on this plan
Accessibility and HTML checks on a template library Email on Acid Premium Accessibility tests and HTML analysis are included on this plan only
A receipt or welcome email triggered by a form or order, without writing code Make Its visual builder connects triggers to templates and sending apps
A few automations at low volume and no budget Make Free 1,000 credits per month with no time limit, within the 2 active scenario cap
Sales reps sending templated bulk email from a pipeline Close Growth Bulk email and automated workflows sit beside the contact and deal records
Templates with no subscription at all Plain HTML from the skeleton above No tool cost. You still need a sending app and a set of test sends to accounts you control

Setup checklist for an existing template

Most teams are not starting from nothing. They have an existing template that was designed desktop-first and needs to be made responsive. The checklist below turns that job into steps you can complete in order. Each step ends with a check you can verify, so the template is not "done" until the check passes.

Step What to change Done when
1. Export the current HTML Copy the full source from your sending tool, including any inline styles You have one file with no references to external stylesheets
2. Replace fixed widths Set the main container to a 600-pixel width attribute with a max-width style and a width of 100% The container is full width on a narrow screen and capped on a wide one
3. Flatten the columns Convert multi-column blocks to the stacking pattern shown above Each column stacks in a single column on a phone with the intended order
4. Fix images Add width, height and alt text to every image, and set max-width to 100% The template reads correctly with images turned off
5. Rebuild buttons Replace image buttons with a table cell that has a background colour and a link inside The button is still clickable and readable when CSS is stripped
6. Check the footer Keep a visible unsubscribe link and a sender address The footer is present on the mobile and desktop views
7. Preview and send test copies Run a preview and send test messages to accounts you control Every client you care about shows the layout you intended

A quality-control workflow for responsive templates

Once the template is built, the remaining work is checking it. Start with the clients that cause most of the trouble: the Gmail web app, the Gmail and iOS Mail apps on a phone, Outlook for Windows, and Samsung's mail app on an Android device. Send a test copy to an account in each one, then open it on a phone held in portrait and then in landscape. Repeat the check with images turned off, because the reader who sees only alt text is the one most likely to miss a call to action.

Dark mode needs its own pass. Many clients invert colours automatically, so a dark text colour set on a light background may become unreadable or disappear. Keep the text colours high-contrast against both the background and its inverted version, and avoid placing text over images without a solid colour behind it. If a preview tool shows a client you do not use, check it anyway, because your readers may use it.

Finally, make a checklist that the next person can follow. The QA table below is a short version that you can paste into a team wiki. It covers the content, the rendering and the governance questions that tend to get skipped.

Check What to verify
Content One purpose, a clear order of headline, body and button, and alt text that makes sense without the image
Rendering Phone and desktop views, portrait and landscape, images on and off, and dark mode in the clients your readers use
Links and footer Every link goes to the intended page, and the unsubscribe link works
Ownership A named owner for the template, a record of the last approved version and a date for the next review

Common responsive mistakes

Most responsive email problems fall into a short list, and each one has a clear fix. The first is a button made of a small image. A reader cannot tap a tiny target accurately, and the image is blank when images are off. Rebuild it as a table cell with a link. Apple's interface guidelines use 44 by 44 points as a common minimum tap target, so give buttons generous padding rather than shrinking them to fit a line.

The second is horizontal scrolling. It usually comes from a fixed-width image, a table with no width limit or a long URL in body text. Set images to max-width 100%, and break long links into shorter display text. The third is text that is too small. Body copy below 14 or 16 pixels forces a reader to zoom, and disclaimers at 11 or 12 pixels are the practical floor for small print. The fourth is crowded navigation, with several links in one line and no room between them. Give each tappable item its own line.

The last mistake is treating the desktop preview as the final check. A layout that looks right on a laptop can still stack in the wrong order on a phone, lose its button in one client and hide the offer behind an image in another. The checklist and the test sends above exist to catch exactly those cases.

How to choose

Start with the job, not the tool. If the problem is that templates look wrong in some clients, buy a preview tool or run test sends before you buy anything else. Email on Acid is the pick for that job because it covers more than 100 clients and devices from its entry plan, and the cost is a monthly subscription rather than a one-time purchase. If you change templates only a few times a year, a set of test accounts and a disciplined checklist may be enough, and the $99 a month is better spent elsewhere.

If the problem is that emails go out late or not at all after a customer action, you need an automation layer. Make's free plan is a practical place to build and test a flow, provided your volume and the 15-minute run limit suit the trigger. Move to a paid tier when the flow needs to run more often, when you need several active scenarios or when the execution log has to be kept longer than 7 days.

If the problem is that a sales team needs templated follow-ups tied to their pipeline, the choice is between a CRM with bulk email and a separate sender. Close's Growth tier is priced per user, so the cost scales with headcount. For a team of three, that is $297 a month billed annually, or $3,564 a year. If the same team only sends newsletters, a dedicated email platform is usually the better fit, and Close is worth the cost only when the sales workflow around the email is the real need.

Whatever you choose, keep the template in plain HTML that you own. A template that lives only inside one vendor's editor is harder to move, harder to review and harder to fix when a client changes its behaviour. The skeleton and the stacking block in this guide are short enough to store in version control, and that single habit makes every later choice easier.

Responsive email template FAQ

What width should a responsive email be?

A main container of about 600 pixels is the common choice. Set it with a width attribute of 600 and a max-width style of 600 pixels with a width of 100%. The email then fills a phone screen and stops at 600 pixels on a desktop. Avoid fixed widths larger than that, because they cause horizontal scrolling on narrow screens.

Do media queries work in every email client?

No. Some clients apply them and others ignore them, and the behaviour changes over time. Build the base layout so it works without media queries, then add a short query block for mobile refinements such as padding and headline size. Check the result in the clients your readers use.

Should I use single-column or multi-column layouts?

Use a single column by default. Add a second column only where it adds real value, such as a product pair, and make sure it stacks on a phone using the pattern in this guide. A single column is easier to get right and easier to read on a small screen.

What is the smallest font size I should use on mobile?

Keep body copy at 16 pixels where you can, and do not go below 14 pixels for main text. Small print such as a legal footer can be 12 pixels. Anything smaller forces readers to zoom, which is the main reason people stop reading on a phone.

Why does Outlook for Windows look different?

Outlook for Windows uses a word-processor rendering engine and does not support max-width. It usually falls back to the width attribute, which is why the skeleton sets both. Always check the template in Outlook for Windows, because it is the client most likely to show an unexpected layout.

Do I need Email on Acid, or is testing by hand enough?

For a template you change rarely, sending test copies to accounts you control covers the most common clients. A preview tool becomes worth paying for when you change templates often, need coverage beyond the clients you can access, or want accessibility and HTML checks as part of the review. Email on Acid's Basic plan starts at $99 per month for 1,000 previews.

Can Make send the email itself?

Make triggers the workflow and passes data to the app that sends the message. Whether it can send directly depends on the sending app you connect. The template still has to be built in HTML and checked in the clients your readers use, because Make does not change how the email renders.

Is Close the right choice for newsletters?

Usually not. Close is a sales CRM, and its bulk email is designed for templated outreach from a pipeline. For a newsletter with a large audience and a publishing schedule, a dedicated email platform is usually a better match. Close makes sense when the email is part of a sales workflow that already runs in the CRM.