Design
Designing emails that render everywhere
Single column, about 600px, live text over images, dark mode, alt text and accessible buttons: a practical design approach for every inbox.
Updated 7 min read
Designing for email is not like designing for the web. A web page is shown by a handful of modern browsers that broadly agree on the rules. An email is shown by dozens of apps, including desktop programs, webmail in different browsers, and phone apps, and each has its own ideas about which HTML and CSS it will support. Some strip out styles, some block images by default, and some change your colours when the reader uses dark mode.
The good news is that the approach which works best everywhere is also the simplest: one column, live text, sensible fallbacks and nothing that depends on a single app behaving perfectly. This guide explains that approach, step by step.
Start with a single column about 600px wide
A single column of content, roughly 600 pixels wide on desktop and full width on a phone, is the safest layout in email. It has become a convention for good reasons:
- It fits comfortably in desktop reading panes, which are often narrower than the screen.
- On a phone, it simply fills the screen; nothing needs to stack or rearrange.
- It reads in a clear order, top to bottom, which helps everyone, including screen-reader users.
- There's less to go wrong in apps with limited CSS support.
Multi-column layouts are possible, but they need extra code to collapse on small screens, and they break in more places. For most small business, charity and club newsletters, a single column with clear headings does the job better.
Use live text, not pictures of text
It's tempting to design a newsletter as one big image, such as a poster exported from a design app, because it looks exactly as you intended. It's also one of the most fragile choices you can make:
- Images are often blocked or slow to load. Some apps and many workplace systems don't show images until the reader allows them. An image-only email then looks blank.
- Screen readers can't read text inside images. Unless you write long alt text, which most people don't, the content is lost to blind and partially sighted readers.
- Text in images doesn't resize. On a phone, small text in a wide image becomes unreadable, and readers can't zoom it the way they can zoom real text.
- Search doesn't find it. Readers searching their inbox for "opening hours" won't find words that are only in a picture.
- It can look suspicious to filters. Mostly-image emails with very little text are a pattern often associated with spam.
Use live (real, selectable) text for everything important: headings, dates, prices, calls to action. Use images to show things, such as a product, a place or a person, not to carry words.
Choose fonts that are already there
Many email apps ignore web fonts, so whatever you choose needs a sensible fallback. A system font stack uses the font the reader's device already has:
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto,
Helvetica, Arial, sans-serif;
For a more traditional look, a serif stack such as Georgia, "Times New Roman", serif is widely available. If you do use a web font for headings, check that the fallback looks acceptable, because some readers will only ever see the fallback.
Keep body text at around 16px with comfortable line spacing (about 1.5). Smaller text is hard to read on phones, and some phone apps enlarge very small text automatically, which can upset your layout.
Write alt text for every image
Alt text is the description shown when an image doesn't load and read aloud by screen readers. Good alt text describes what the image is for, in the context of the email:
| Image | Weak alt text | Better alt text |
|---|---|---|
| Photo of a new seasonal cake | image1.jpg | Our new spiced pear cake, sliced on a wooden board |
| Logo at the top of the email | logo | Ashgrove Running Club |
| Decorative divider line | divider | (empty: alt="", so screen readers skip it) |
| Poster for an event | poster | Summer fete, Saturday 14 June, 11am to 4pm, on the village green |
For purely decorative images, use an empty alt attribute (alt="") rather than leaving it out. Without one, some screen readers read out the file name instead.
Make buttons that work without images
A call-to-action button made from an image disappears when images are blocked, which is exactly when you need it. Instead, build buttons from HTML and CSS: a link with padding and a background colour. These are often called "bulletproof" buttons because they survive image blocking.
<table role="presentation" cellpadding="0" cellspacing="0" border="0">
<tr>
<td style="border-radius:6px; background:#1d4ed8;">
<a href="https://example.co.uk/book"
style="display:inline-block; padding:14px 24px; font-family:Arial, sans-serif;
font-size:16px; font-weight:bold; color:#ffffff; text-decoration:none;
border-radius:6px;">Book your place</a>
</td>
</tr>
</table>
To make buttons accessible:
- Use clear, specific labels. "Book your place" or "Read the full report" says where the link goes; "Click here" doesn't. Screen-reader users often jump from link to link, hearing only the label.
- Make them big enough to tap. Aim for a button at least about 44px tall, with space around it so it's not easy to hit the wrong link.
- Keep good contrast. White text on a mid-grey or pale colour is hard to read. Use a contrast checker; the WCAG guidelines suggest at least 4.5:1 for normal-sized text.
- Have one main button. Several competing buttons make it harder to know what to do. Secondary links can be plain text links.
Plan for dark mode
Many readers use dark mode, and email apps handle it in different ways. Some leave your email alone, some invert only light backgrounds, and some invert almost everything. You can't fully control this, but you can design so that nothing breaks:
- Avoid text baked into images. It's another reason for live text: real text gets recoloured sensibly; text in an image doesn't.
- Use logos with transparent backgrounds carefully. A dark logo on a transparent background can vanish on a dark background. Add a subtle light outline or padding of the right colour, or place the logo on a solid background block.
- Don't rely on colour alone. If the meaning is in the colour, such as red text for a deadline, it may change. Use words too.
- Avoid pure white and pure black backgrounds for key blocks if you see harsh inversion in testing; slightly off-white often inverts more gracefully in some apps.
- Test it. Send a test to your own phone with dark mode switched on, and to a desktop app if you can.
Some apps support a prefers-color-scheme media query, which lets you supply your own dark colours. It's worth using if you write your own HTML, but treat it as an enhancement rather than something every reader will see.
Write and structure for scanning
Design isn't only visual. Most readers skim, so structure helps everyone:
- Use real headings to break up sections, with one clear topic each.
- Keep paragraphs short, typically two to four sentences.
- Make links descriptive and visibly links, usually underlined, especially within body text.
- Left-align body text. Centred paragraphs are harder to read beyond a line or two.
- Set the language of the email (for example
lang="en-GB") so screen readers pronounce it correctly. - Include a plain-text version. Most email tools generate one; check it reads sensibly.
Check support before you rely on a feature
When you want to use a particular HTML or CSS feature, such as background images, rounded corners or a media query, check whether the main email apps support it. Can I email is a free, well-maintained reference that shows support across email clients, much like similar tools do for web browsers.
If your audience is mostly on phones, which you can often see in your email software's reports, prioritise testing there. If you send to businesses, desktop Outlook may matter more, and it's the app where unusual code most often goes wrong.
A simple testing routine
- Send a test to yourself and to at least one other person who uses a different email app.
- Open it on a phone and on a computer.
- Turn images off, or view it in an app that blocks them, and check it still makes sense.
- Switch dark mode on and look again.
- Click every link and button.
- If you can, try reading it with your phone's built-in screen reader for a minute; it quickly reveals missing alt text and vague links.
Paid testing services show screenshots across many apps, but for most small senders these manual checks catch the important problems. Add them to your routine with our pre-send checklist, and if you'd rather start from working code, use the HTML email starter.