Mobile-First Email Design
Design the phone version first, then add width for desktop. The main message, the button and the unsubscribe link all survive on the smallest screen that opens your email.
If you want one tool to support a mobile-first template workflow, Make is the best starting point in this group. Its free plan includes 1,000 credits a month, and its Core plan is $9 a month when billed annually, or $10.59 a month billed monthly, for 10,000 credits. Make does not design your email. Its job here is the repetitive part of quality control: sending a test copy to a review group, collecting the checks and keeping a log of what was fixed. The design decisions stay with your editors, and this page explains those decisions in order.
Start With the Narrowest Version
Mobile-first means you draw the narrow version before the wide one. You decide what a reader sees in the first screen, in what order the blocks arrive and which single action they can take with a thumb. Desktop then gets extra columns, sidebars and imagery if the content needs them. The result is a template whose core is intentional, not a shrunken desktop layout that someone patched with media queries at the last minute.
The practical test is simple. Build the template at a width of about 375 to 400 pixels, print or export a screenshot, and read it top to bottom without any other layout in front of you. If the sentence that carries the offer is buried under two logo rows and a navigation bar, the template is failing before any client has rendered it.
Single Column as the Default
A single column is the most dependable structure for mobile readers because it has no side-by-side elements to reflow. Heading, short intro, one hero image, one main paragraph block and one button read in a fixed order on every screen. You still lose some of the visual variety that multi-column newsletters offer, but you gain predictable stacking, which matters most in clients that ignore responsive CSS.
Use multiple columns only where they carry information that would be lost if stacked. A product grid of four items is a reasonable example, provided each item still makes sense alone when the grid collapses to one column. A decorative sidebar of links is not. When in doubt, move the second column to the bottom of the message as a plain list.
Tap Targets and Buttons
Buttons are the element most often sized for a mouse and then shipped to a thumb. A useful minimum is a tap target of about 44 by 44 CSS pixels, which is a common guideline in mobile interface design. Make the whole button the link, not just its text, so the tappable area does not shrink to the width of the label. Full-width buttons work well on a single-column template because they remove the question of where the thumb should land.
Keep text links away from the most important actions. A text link such as “read more here” is easy to miss and easy to mis-tap when it sits beside another link. Spacing between tappable elements matters as much as their size: give each button or link a clear gap above and below, so a reader scrolling quickly does not hit the wrong one. Place the unsubscribe link and the preferences link in the footer, separated from the primary action.
Type Sizes That Hold Up
Body text under about 14 pixels forces readers to pinch and zoom, and many will simply stop. For most templates a body size between 16 and 18 pixels is comfortable on a phone, with headlines large enough to separate sections at a glance. Line height between about 1.4 and 1.5 keeps paragraphs readable without making the message feel padded.
Avoid stacking several font sizes within one short block. Two sizes, one for headings and one for body, plus a slightly smaller size for legal text in the footer, is enough for nearly every template. Fonts also need fallbacks. Most clients do not load custom web fonts reliably, so specify a system font stack after the preferred family and test that the layout still holds when the fallback is used.
Fold Position and the Primary Action
The “fold” on a phone is the point where the first screen of the message ends. Anything below it requires a scroll, and many readers decide whether to scroll based on what they see above it. Put the primary button in the first screenful, after a headline and one or two short sentences. The exact pixel height of that screen varies by device and by client chrome, so measure it in screenshots from the clients your audience uses rather than trusting a fixed number.
If the offer needs more explanation than fits above the fold, repeat the button lower down. A second button after the supporting detail gives a reader who scrolled a second chance to act without forcing the first screen to carry every argument. Avoid placing three different calls to action in a row; one clear action with a single repeat reads better than three competing ones.
Images, Blocked Images and Alt Text
Many clients block images by default until the reader chooses to load them. An email built mostly from a single hero image therefore arrives as a blank canvas for some readers. Build the message so the headline and the first sentence carry the point in plain text, and treat the image as support. Every image should have descriptive alt text, and any text that matters should live in real text, not inside a picture.
Keep images responsive. A fixed-width image wider than the phone screen forces horizontal scrolling or causes the client to shrink it unpredictably. Set images to a maximum width of 100 percent and keep their proportions simple. Text inside an image is the most fragile element of a mobile template: it becomes unreadable when the image scales down and it disappears when images are blocked. Use it sparingly, and never for the only copy of an offer.
Media Queries as Progressive Enhancement
Media queries let a template stack columns, enlarge buttons or change spacing on narrow screens in the clients that support them. They are useful, but they are not reliable everywhere. Outlook desktop has historically handled them poorly, and some webmail and mobile apps ignore them altogether. The safe approach is to design a base layout that is already readable without any media query, then add queries that refine it for clients that honor them.
Test both states. Look at the template with queries applied and with them stripped, which is roughly what a reader sees when a client removes the stylesheet. If the unstyled version hides the button, stacks the footer above the offer or relies on a column that never collapses, the base layout needs more work before any query is added.
Dark Mode on Phones
Dark mode changes contrast in ways that light-mode previews do not reveal. Clients invert or adjust backgrounds differently, and some leave pale text on a white image box. Avoid pure white backgrounds with thin, light gray text, because both can fade badly under inversion. Give logos and product photos a background that works in either mode, or use transparent PNGs with a solid edge. Check the compiled email in dark mode on a real phone, since preview tools do not always reproduce the client’s logic.
Comparing Mobile-First and Desktop-First Approaches
Some teams still start in a desktop editor because it is familiar. The table below summarizes where the two approaches differ in practice. Neither is wrong for every program, but the choice determines which failure you are most likely to see first.
| Design element | Mobile-first baseline | Desktop-first baseline | Most likely failure |
|---|---|---|---|
| Layout | One column, blocks in reading order | Two or three columns with side elements | Jumbled order when columns collapse |
| Body text | About 16 to 18 pixels | Often smaller, tuned for a wide canvas | Readers zoom or stop reading |
| Primary button | Full width, in the first screenful | Compact, placed beside other buttons | Button missed or mis-tapped |
| Images | Supporting, with alt text and plain-text message | Hero image carries the message | Blank message when images are blocked |
| Preview text | Short, written for a narrow inbox row | Often a longer sentence written for wide webmail | Preview text cut off mid-thought |
Tools That Support the Testing Loop
Template design is mostly a matter of judgment, but the testing loop around it is repetitive and easy to skip. Each template should be sent to real phones, checked against a short list and compared with the previous version after it goes live. The tools below are the ones covered by published pricing information. None of them is an email designer, so read each entry for what it can do in support of the workflow and what it cannot do.
| Tool | Best for | Entry price | Key limitation |
|---|---|---|---|
| Make | Automating test sends, review requests and logs | Free plan; Core from $9 a month billed annually | Free plan allows only 2 active scenarios |
| Heap | Seeing what mobile visitors do on landing pages after a click | Free plan up to 10k monthly sessions | Measures your website, not how the email renders |
| Segment (Twilio Segment) | Moving customer data between tools to build mobile audiences | Pricing on request; free trial mentioned for Connections | Setup is substantial and it is not a template tool |
| Clari | Revenue forecasting for sales teams | Pricing on request | Not designed for email template work |
Make
Make is a visual automation builder. Its strength for this topic is the no-code workflow layer: you can connect a form, a shared spreadsheet and a messaging app, then route a copy of each new template to reviewers and record their checks. The builder offers routers and filters and connects to more than 3,000 apps, which covers the usual tools a small editorial team already uses. Make also provides a free plan with 1,000 credits a month and no time limit.
Where it falls short is limits. On the free plan you can run two active scenarios, each scenario can run at most every 15 minutes, executions stop after five minutes, and execution logs are kept for seven days. That is enough to prove a process. It is not enough for a busy team that wants a check on every send. Each module action in a scenario uses one credit, so a review loop with many steps consumes allowance faster than it looks on paper. Paid plans are priced by monthly credit allowance. The cards show prices for 10,000 credits a month; larger allowances are chosen on a slider with different totals.
Pricing is on the Make pricing page.
Heap
Heap is an analytics product. For a mobile-first template program, its value is downstream of the inbox: when a reader taps through to a landing page, Heap can show how the session behaves on a phone, where people stop and which pages they reach. The free plan covers up to 10,000 monthly sessions with six months of data history and includes core analytics charts and SSO. Paid tiers add more users, longer history, CSV exports and report alerts, but Heap does not publish their prices.
Heap does not show you how an email looked in a client. Its evidence begins after the click, so pair it with your own screenshot checks. The free session cap also matters for larger lists, since a campaign that drives heavy traffic can reach the limit quickly. Check the Heap pricing page for the current plan details.
Segment (Twilio Segment)
Segment is a customer data infrastructure product. Its Connections product collects first-party data and sends it to other destinations, and it also offers Reverse ETL and Functions. This matters for mobile email when your segments depend on device or behavioral data that sits in several systems. A team that wants to send a shorter, mobile-optimized version to subscribers who mostly open on phones may need that data in one place.
The cost of that capability is setup time and an unpublished price. Segment’s pricing page lists plan names and add-ons, including audiences and profile enrichment, but it does not publish numbers. The page mentions a free trial for Connections without giving a length. If your team does not already move customer data between tools, Segment is a heavy choice for a template question. See the Segment pricing page for the plan list.
Clari
Clari is a revenue platform used for forecasting and pipeline visibility. It has no public free plan and its pricing is custom. It is included here only to be clear about fit: it does not help design or test email templates, and an email team evaluating tools for this job should look elsewhere. The Clari pricing page describes its offering.
What the Tools Cost
The table below lists only the prices that appear on the vendors’ pages. Where a vendor does not publish a figure, the table says so. Annual totals are simple multiplication of the monthly rate shown, so you can check them yourself.
| Tool and plan | Monthly price | Billed annually (per month) | Yearly cost at that rate |
|---|---|---|---|
| Make Free | $0 | Not applicable | $0; 1,000 credits a month |
| Make Core (10k credits) | $10.59 | $9 | 12 × $9 = $108 a year, or 12 × $10.59 = $127.08 monthly billing |
| Make Pro (10k credits) | $18.82 | $16 | 12 × $16 = $192 a year, or 12 × $18.82 = $225.84 monthly billing |
| Make Teams (10k credits) | $34.12 | $29 | 12 × $29 = $348 a year, or 12 × $34.12 = $409.44 monthly billing |
| Make Enterprise | Pricing on request | Pricing on request | Pricing on request |
| Heap Free | $0 | Not applicable | $0; up to 10k monthly sessions |
| Heap Growth, Pro, Premier | Pricing on request | Pricing on request | Pricing on request |
| Segment Connections and CDP plans | Pricing on request | Pricing on request | Pricing on request |
| Clari | Pricing on request | Pricing on request | Pricing on request |
The Make figures are for 10,000 credits a month. If you need a larger allowance, check the slider on the vendor page, because the price changes with the credit count and the table above does not cover those points.
Which Tool Fits Which Job
Most teams need one tool for the loop and nothing more. The decision table below turns the comparison into a short set of choices. Read the last column before committing, because it names the limit that is most likely to bite.
| If you need | Pick | Because | Watch out for |
|---|---|---|---|
| To automate test sends and reviewer checks without code | Make | Visual builder with a free plan to start | Two active scenarios and a 15-minute interval on the free plan |
| To see how mobile visitors behave after the email click | Heap | Session analytics with a free plan up to 10k sessions | It starts after the click and does not show the inbox render |
| To combine customer data from several systems into mobile audiences | Segment | Connections and Reverse ETL for moving data between tools | Substantial setup and no published prices |
| To forecast sales pipeline | Clari | Built for revenue teams, not for email design | Not a template tool, and no public price |
| To design the template itself | Your existing editor | None of the tools above is an email designer | Keep the single-column baseline regardless of editor |
A Setup Checklist for the Mobile Loop
A repeatable process beats a one-off review. The checklist below sets up the loop once and keeps it running for every template you ship. Each step has a clear owner and a finish line, so it is obvious when the loop is working.
| Step | Owner | Done when |
|---|---|---|
| Write the single-column baseline with 16-pixel body text and full-width primary button | Template designer | Screenshot at phone width reads top to bottom with the offer visible |
| Check tap targets, spacing and the unsubscribe link position | Template designer | Each button is a full tappable block with a clear gap around it |
| Remove or repair the stripped-CSS version and the blocked-image version | Developer or editor | The core message and button survive with images off and media queries removed |
| Send test copies to real phones in the mail apps your audience uses | Reviewer group | Each reviewer returns a short checklist for their device |
| Automate the reminder and log the results in one place | Operations, with Make or a similar workflow tool | Every test send has a recorded outcome and an owner for each fix |
| Compare mobile clicks against the previous version after the send | Campaign owner | Click results are recorded in the same log as the test checks |
Dark Mode and Narrow Screens Together
Many mobile readers open email in low light, in bed or on a commute. That is when a dark-mode rendering is most likely, so dark mode belongs in the mobile review rather than a separate specialist check. Confirm that the headline still has enough contrast after inversion, that the button stands out in both modes and that logos do not disappear against a dark background. Narrow screens and dark mode also interact: a button that looks fine in light mode can lose its edge on a dark background if it has no border or shadow.
Hide-on-Mobile Modules
Some teams hide a large banner or a wide table on phones. That can be sensible for decoration, but hiding content risks a reader losing information that the message needs. Prefer a restructured version: a smaller image, a shorter table or a single-column list that carries the same facts. Reserve hiding for content that adds nothing on a narrow screen, and check that the rest of the message still makes sense without it.
Frequently Asked Questions
Is Make a good choice for designing email templates?
Not on its own. Make is an automation tool, so it helps with the workflow around a template: sending test copies, collecting reviewer checks and logging results. The design itself still happens in your email editor. The free plan is useful for testing the process before you pay for more credits.
What does Make cost for a small team?
The free plan is $0 and includes 1,000 credits a month. The Core plan for 10,000 credits is $9 a month billed annually or $10.59 a month billed monthly, which comes to $108 a year on the annual rate. Check the pricing page for allowances above 10,000 credits, since those are set on a slider.
Can Heap show me how an email rendered in a phone’s mail app?
No. Heap measures what visitors do on your website after they click, such as sessions and page behavior. It cannot show the inbox render. Use screenshots from real devices for the rendering check and Heap for the landing-page results.
Do I need a mobile-first template if most of my list is desktop?
It depends on your readers. If your data shows that most opens happen on desktop, a desktop-leaning layout can be reasonable. Even then, keep the mobile version readable, because audience habits can shift over the life of a program and a broken narrow layout is costly when they do.
How many test devices do I need?
Start with the two or three mail apps your readers use most, on both an iPhone and an Android phone if your list is mixed. Add Outlook mobile if a meaningful part of your audience uses it. Adding devices gives less value than testing each one carefully in portrait and landscape.
Should preview text be written for mobile too?
Yes. Preview text appears in many mobile inbox rows, usually after the subject line, and it is often cut short. Write it as a complete short sentence that reinforces the subject line rather than repeating it, and keep the important words near the start.
Which related guides should I read next?
Read the email template design guide for the wider structure of a template, responsive email templates for the code side of stacking, and dark mode email templates for contrast and image handling. The template library shows finished layouts you can adapt.