ThisCalculator

Everyday

Email Design Best Practices: Layout, HTML, and More

Updated · Standard formula, shown below

Average pace 5.00 min/km
Average speed
12.00 km/h
Result
Finish time
50 min
You entered
Distance
10 km
You entered

Designing emails the right way means creating messages that render correctly across all major email clients, respect accessibility standards, and drive the reader toward a single, clear call-to-action. This article explains the core principles of email design—from HTML structure and responsive layout to typography and testing—so you can build emails that look great and perform well.

Why Email Design Is Different from Web Design

Email clients (Outlook, Gmail, Apple Mail, etc.) do not fully support modern HTML and CSS. Many still rely on table-based layouts, inline styles, and outdated rendering engines. This means what works on a website often breaks in an email. For example, CSS position: fixed is unreliable, and media queries are only partially supported. The safest approach is to code emails using a hybrid of tables and inline CSS, with a width around 600px, which has been the standard for decades. This ensures your design degrades gracefully when advanced features are ignored.

Core HTML Structure of an Email

Every email should start with a basic HTML skeleton that includes <!DOCTYPE html>, <html>, <head>, and <body>. Inside the body, use a single outer table (width 100%) to center the content, then an inner table with a fixed width (e.g., 600px) to hold the main layout. Use table rows and cells for columns, not divs. Inline styles are essential because many clients strip styles from the <head>. For example:

  • Use role="presentation" on layout tables to help screen readers.
  • Add align="center" to the outer table for older clients.
  • Use border="0" cellpadding="0" cellspacing="0" to avoid unwanted spacing.
  • Set a style="display:block" on images to prevent gaps.

Responsive Design and Mobile-Friendly Emails

Over half of all emails are opened on mobile devices, so responsive design is not optional. The most reliable method is the fluid hybrid approach: use a container table with a fixed width (e.g., 600px) and set a max-width: 100% style, allowing it to shrink on small screens. For columns, you can use display: inline-block with widths in percentages (e.g., 50% each) and media queries to stack them vertically on screens under 480px. Always test on real devices, not just in a desktop browser.

Typography and Color Choices

Use web-safe fonts like Arial, Helvetica, Georgia, or Verdana, because custom fonts often fallback to a default. Set a base font size of 14-16px for body text to ensure readability on mobile. Keep line-height between 1.4 and 1.6. For colors, maintain sufficient contrast between text and background (WCAG AA requires a ratio of at least 4.5:1 for normal text). Avoid using color alone to convey meaning—pair it with icons or text. Also, always include an alt attribute on images, because many clients block images by default.

Common Mistakes and How to Avoid Them

Here are frequent pitfalls that ruin email designs:

  • Using too many images: If images are disabled, the email becomes blank. Use a balance of text and images, and ensure the call-to-action is a text link as well.
  • Ignoring the preheader: The preheader text (the first few lines after the subject) is often left as random text. Set it explicitly to a summary or a secondary call-to-action.
  • Not testing across clients: Outlook uses Word’s rendering engine, which is notoriously bad with padding and margins. Test with tools like Litmus or Email on Acid (or send to yourself in various clients).
  • Forgetting the plain-text version: Many spam filters and some users prefer plain text. Always include a text-only version that contains the essential links.
  • Making the call-to-action too small: Apple’s guidelines recommend a minimum tap target of 44×44 pixels. Make buttons at least that size.

Accessibility in Email Design

Designing for accessibility improves the experience for everyone. Use semantic HTML (like <h1> for the main heading) and a logical reading order. Provide descriptive alt text for images, such as “Download our free guide” rather than “Image123.jpg”. Use a real text link for the call-to-action, not just a button image. Also, avoid using tables for non-tabular data, and include a “view in browser” link for those who cannot render the email properly.

How to Choose an Email Service Provider (ESP)

Your ESP handles deliverability, templates, and analytics. When choosing one, consider:

  • Deliverability: Look for providers with strong sender reputation and authentication (SPF, DKIM, DMARC).
  • Template editor: Some offer drag-and-drop builders, others require custom HTML. Choose based on your team’s skill.
  • Testing tools: In-built previews across clients are valuable.
  • Automation: If you need triggered emails (welcome, cart abandonment), ensure the ESP supports them.
  • Scalability: Pricing usually depends on subscriber count, so estimate growth.

Frequently Asked Questions

What is the ideal email width?

The standard is 600-650 pixels. This fits most desktop preview panes and scales well on mobile when you use fluid layouts. Anything wider may get cut off in Outlook’s preview pane.

Should I use images or text for buttons?

Use a real button made with HTML and CSS (an anchor tag styled as a block) with a text label. This ensures the button is clickable even when images are blocked, and it’s better for accessibility. If you must use an image, include a text link below it as a fallback.

Why does my email look different in Outlook?

Outlook uses Microsoft Word’s rendering engine, which does not support many CSS properties like padding on block elements, background images, or media queries. To minimize issues, use table-based layouts, add padding to table cells instead of divs, and test specifically in Outlook versions (2010, 2013, 2016, 2019 and Microsoft 365).

How do I make my emails mobile-friendly?

Use a responsive design with a single-column layout on mobile. Set the container table to width: 100% and max-width: 600px, and use media queries to adjust font sizes and stack columns. Also, increase padding and button sizes for touch.

What is a preheader and why is it important?

The preheader is the short summary text that appears after the subject line in many inboxes. It’s a prime spot to reinforce your message or add a secondary call-to-action. If you don’t set it, clients will pull arbitrary text from the email, which can look messy. Set it in a hidden div at the top of the email.

Can I use JavaScript in emails?

No. All major email clients strip out JavaScript for security reasons. Any interactive behavior must be achieved with HTML and CSS only, such as using the :hover pseudo-class for hover effects (though support is limited). For dynamic content, use personalization tokens that your ESP replaces before sending.

Related

Formula used
in t | Finish time | min | 50 | 0
in d | Distance | km | 10 | 0
out pace | Average pace | min/km | t / d | 2
out speed | Average speed | km/h | d / (t / 60) | 2

Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.