Mobile-First Email Design Without Losing Desktop
Most email lists now open on phones more than anywhere else. If your program looks anything like the median, somewhere between 55% and 75% of opens happen on a mobile client. That single fact has pushed a lot of teams into “mobile-first” redesigns. The trouble is that the phrase gets used to justify two contradictory things: stripping everything down to a single narrow column, or bolting on a media query and calling it responsive.
Neither approach survives contact with a real list. Your subscribers are spread across Gmail on iOS and Android, Apple Mail, Outlook on Windows and Mac, Yahoo, and a long tail of corporate clients that render email like it’s 2009. A layout that looks perfect in an iPhone preview can collapse into a 600px-wide mess in Outlook, and a “simple” single-column design can waste half the screen on a desktop monitor.
This is a practitioner’s guide to the design decisions that actually matter: fluid layouts that adapt without a media query, tap targets that respect thumbs, stacking behavior you can predict, and a testing routine built around the clients that actually hold your list rather than the ones that look good in a screenshot.
Start with the constraint, not the canvas
The instinct is to design a 600px email and then “make it mobile.” Reverse that. Design for a 320px viewport first, because that’s close to the narrowest screen your list will realistically hit, and the layout you build there has to survive being stretched to 700px on a desktop without looking like a lonely column of text.
A few numbers worth keeping in view. The usable width on a typical phone in portrait is roughly 320–390 CSS pixels. Gmail’s mobile apps strip or ignore a meaningful chunk of CSS, including some media query support in older Android versions, so a design that only works because of a media query is fragile. Outlook on Windows renders with Word’s engine and has no media query support at all in many versions, which means your desktop fallback is what those subscribers see regardless of window size.
That combination pushes you toward fluid, percentage-based layouts as the foundation and media queries as an enhancement, not the other way around. The email should be legible and correctly ordered at 320px with zero CSS beyond what’s inline. Everything else is polish.
Fluid layout is the real mobile-first technique
A fluid email uses percentage widths and max-widths so columns shrink and grow with the viewport. The common pattern is a wrapper table capped at 600px with width="100%", and inner columns set to percentages that sum to 100. On a 320px screen those columns compress; on desktop they expand to the cap. No media query required.
Where fluid alone breaks down is when a two-column layout compresses to the point where each column is too narrow to read. That’s when you need stacking, and stacking is where most builds go wrong.
Hybrid (spongy) design versus media-query stacking
There are two ways to make columns stack. The first uses media queries: at max-width: 480px, set the columns to display: block; width: 100%. Clean in theory. The problem is client support. Gmail’s apps historically ignored display overrides in some contexts, and Outlook desktop ignores media queries entirely, so your carefully stacked mobile layout never fires there.
The second approach is the “hybrid” or “spongy” pattern: inline-block columns with a max-width, plus ghost tables and conditional comments to force stacking in clients that need it. It’s more markup and uglier to maintain, but it stacks reliably in more clients, including ones that strip media queries. If your list skews toward older Android Gmail or corporate Outlook, hybrid is the safer bet. If your list is dominated by Apple Mail and modern Gmail, media queries are simpler and you can accept the fallback.
This is a genuine trade-off, not a rule. Test against your own list before committing.
Tap targets: the 44px rule and why it’s a floor
Apple’s Human Interface Guidelines put the minimum comfortable tap target at 44×44 points. Google’s Material guidance says 48×48dp. Treat 44px as the absolute floor for any link or button in an email, and aim for 48px on primary calls to action.
Here’s what beginners miss: the visual button can be smaller than the tap target. You can render a 32px-tall pill and still give it a 48px tap area using padding on the anchor or a wrapping table cell. The tappable region is what matters, not the painted rectangle. Padding on the <a> itself is the cleanest way to expand the hit area without changing the look.
Two more practical points. First, don’t stack tap targets closer than about 8px apart, or thumbs will hit the wrong one. Second, links inside body copy are a tap-target problem too. A single word like “here” is a terrible target on a phone. Either make the whole sentence a link or use a clearly padded standalone link. Inline text links are fine for supplementary navigation, but they should never be the only path to your primary action.
Buttons versus text links
Bulletproof buttons built with a table cell and background color beat image buttons every time. An image button doesn’t scale text, doesn’t respect the subscriber’s font settings, and disappears entirely when images are blocked, which is still common. If you must use an image, set explicit width and height and add alt text that reads like the button label.
Stacking behavior you can predict
Order matters more on mobile than desktop because the reading flow is strictly vertical. If your desktop layout is image-left, copy-right, the mobile stack should usually put the image first, then the copy, then the CTA. That means the source order in your HTML has to match the mobile order, and desktop uses table cells or floats to place them side by side. Never rely on CSS to reorder content for mobile, because the clients that don’t support reordering will show the wrong sequence.
Watch for these common stacking failures:
- Gutters that collapse to zero. Percentage-based padding on stacked columns can vanish at narrow widths. Use fixed pixel padding on the outer wrapper and let inner content be fluid.
- Images that overflow. Every image needs
max-width: 100%and a height set to auto, or it will blow out the layout on a 320px screen. Set the width attribute to the image’s native width and let CSS cap it. - Two-column “features” that become unreadable. A 50/50 split at 320px gives each column about 150px of usable width. That’s fine for an icon and a short label, not for a paragraph.
- Fixed-width tables inside fluid ones. A nested table with
width="300"will force horizontal scroll on a phone. Make nested tables percentage-based or accept the overflow.
One underused technique: build the mobile layout as the default and use a min-width media query to enhance for desktop. This “progressive enhancement” approach means the email is correct on the smallest screen even if every media query fails, and desktop clients simply get a wider version. It’s the opposite of how most teams build, and it’s more robust.
Where to host the site behind the list
None of the tactics in this article matter if the infrastructure behind them is slow,
poorly configured, or capped at a mailbox size you outgrow in a month. If you are setting up
a site, a landing page, or a sending domain from scratch, Hostinger is a sensible starting point: entry plans are cheap enough to
experiment with, the control panel exposes DNS records for SPF, DKIM and DMARC without a support
ticket, and the VPS tier is there when you outgrow shared hosting. What matters more than the
headline price is that it scales predictably as the list grows.
Typography and spacing that survive both screens
Body copy at 14px is readable on a desktop monitor and miserable on a phone. Set body text to at least 16px, and consider 17–18px for a mobile-heavy list. Line height around 1.4–1.5 keeps paragraphs from feeling cramped on small screens. Headlines can go larger, but cap them so a long headline doesn’t wrap into five lines on a phone.
Line length is the other lever. On desktop, a 600px column at 16px gives you roughly 70–80 characters per line, which is comfortable. On mobile that same text reflows to 35–45 characters, which is also fine. The danger is a narrow column on desktop: if you cap the email at 500px and use 18px text, lines get short and the layout feels like a phone screenshot pasted onto a monitor. Match your max-width to your font size.
Spacing between sections should be generous enough that the mobile stack doesn’t read as one undifferentiated block. A consistent 24–32px vertical gap between modules gives the eye somewhere to rest and makes the stacked order obvious.
Dark mode is a layout problem too
Dark mode isn’t just a color swap. It changes how your design reads. Logos with transparent backgrounds disappear against dark backgrounds. Thin light-gray dividers vanish. Buttons with light backgrounds and dark text invert poorly in clients that force-invert colors. Apple Mail and Outlook.com apply their own dark-mode transformations, and you don’t fully control them.
Practical mitigations: use a logo with a solid background or a version designed for dark backgrounds, avoid pure white backgrounds on modules where you can, and test your email with dark mode forced on in Apple Mail and Outlook. There’s no universal fix, but a design that relies on contrast rather than specific hex values survives better. Treat dark mode as a second rendering environment you have to check, not an afterthought.
Test against the clients that hold your list
This is the part most teams skip. They test in one or two clients and ship. The right approach is data-driven: pull your actual open-by-client report from your ESP, rank clients by share of opens, and test in that order. A typical B2B list might be 40% Outlook desktop, 25% Apple Mail, 20% Gmail mobile, and the rest a mix. A B2C list might be 60% Gmail mobile and 20% Apple Mail. Those two lists need different testing priorities, and a design that’s flawless in Gmail mobile can be a disaster in Outlook desktop.
Build a testing matrix around the top five clients by open share, plus one “worst case” client you know is problematic. Render in each, check the following:
- Does the layout hold at 320px width without horizontal scroll?
- Do columns stack in the intended order?
- Are all tap targets at least 44px?
- Does the primary CTA remain visible without scrolling past the first screen?
- Do images load with correct aspect ratios and alt text?
- Does dark mode preserve contrast?
Use a rendering service for the clients you can’t access directly, but don’t trust it blindly. Screenshots can differ from live rendering, especially in Gmail’s apps. Send real test emails to real devices for your top two or three clients. A render preview is a smoke test, not proof.
Litmus, Email on Acid, and the limits of previews
Both major rendering platforms are useful and both will show you a layout that looks fine while a real client breaks it. The gap is usually in dynamic content, dark mode, or font fallback. Budget for at least one live-device check per major campaign, especially if you’ve changed the template.
Accessibility is a design constraint, not a checklist
Semantic structure helps every client. Use real heading tags in order, give images meaningful alt text, and set a lang attribute on the HTML. Screen readers and some mobile clients use this structure to navigate. Tap targets, contrast ratios (4.5:1 for body text, 3:1 for large text), and readable font sizes all overlap with the mobile-first work you’re already doing, which is convenient: accessibility and mobile usability pull in the same direction.
One specific accessibility trap in email: using a table for layout is unavoidable, but don’t put meaningful content in a table cell with no reading order. If a screen reader hits your two-column feature block, it should read left column then right column in a sensible sequence, which is another reason source order has to match mobile order.
Related reading
Conclusion
Mobile-first email design isn’t a template you buy or a media query you paste in. It’s a set of decisions: build fluid and legible at 320px with no CSS, treat 44px as the floor for tap targets and expand hit areas with padding, make source order match mobile stack order so reordering never depends on CSS, and test against the clients that actually hold your list rather than the ones that look good in a preview.
The desktop experience doesn’t have to suffer. A fluid layout capped at 600px with sensible type sizes and generous spacing reads well on a monitor and adapts cleanly on a phone. The teams that get this right treat the two environments as one design with two expressions, not two separate builds. Start narrow, enhance wide, and verify in the clients your subscribers actually use.
Disclosure: this article contains an affiliate link. If you buy through it we may earn a commission at no extra cost to you. We only link to services we would recommend on merit.