If you have built a web page, HTML email design looks familiar at first: the same tags, the same CSS properties, the same idea of styling text and images. Then you send a test and find that the layout falls apart in one inbox, the font changes in another, and the background color vanishes in a third. Email uses web languages, but it plays by different rules.

This beginner’s guide explains those rules as concepts, without a line-by-line build. You will learn why inbox apps treat code differently, which techniques survive almost everywhere, and what to check before you send. When you are ready to open a real file and work through it, a separate guide to HTML email templates takes the code apart section by section.

How email HTML differs from web HTML

A web page is opened in a browser, and modern browsers agree closely on how to display code. An email is opened inside someone else’s software, and every mail app decides for itself what to keep, what to rewrite and what to throw away.

Three differences follow from that:

  1. You do not control the renderer. The reader’s app picks the engine, and you cannot ask it to update.
  2. Mail apps sanitize code for safety. Anything that could run a program or pull in outside content is removed.
  3. The email sits inside another interface. Webmail places your message inside its own page, so it limits styles that could leak out and change the inbox itself.

Mailchimp’s list of what HTML email cannot safely include makes the practical consequence concrete. It lists JavaScript, iframes, Flash, embedded audio and video, forms and layered div elements as things not to use, and notes that only Apple Mail supports the HTML5 video and audio tags. Web developers rely on most of those every day.

Who renders your email

Rendering engines are the part of each mail app that turns code into what the reader sees, and they vary a lot.

  • Apple Mail on iPhone, iPad and Mac uses WebKit, the engine behind Safari, so it supports a wide range of modern CSS.
  • Gmail reads your styles and passes them through its own filter. Google’s Gmail CSS reference says it accepts styles inline and in style blocks, handles selectors by class, by element and by ID, and may ignore properties it does not support.
  • Outlook for Windows, in the 2007 to 2019 desktop versions, renders email with Microsoft Word. Litmus’s guide to rendering differences in Microsoft Outlook explains that this is why so many web techniques fail there. The Mac version of Outlook is built on WebKit instead, and the new Outlook for Windows uses a browser engine.

How much each matters depends on your list, but Litmus’s market share tracker gives a sense of scale. Its September 2026 figures show Apple ahead at 76.56% of tracked opens, Gmail second at 16.10% and desktop Outlook at 3.48%. A small share can still be a large group of readers if your audience works in offices, so most senders design for all three.

HTML email basics that work almost everywhere

Because support varies, HTML email relies on a small set of techniques that nearly every client understands. Think of them as the common language.

Tables for structure

On the web, layout is built with flexible boxes and grids. In email, it is still built mostly with HTML tables: rows and cells nested inside each other, each holding a block of content. Mailchimp’s own guide to HTML email recommends tables for layout. The reason is history. Tables were the layout tool when many of today’s rendering engines were written, and Word-based Outlook still handles them far better than modern layout CSS.

Newer methods are spreading. Can I Email’s page on display:grid counts 78.05% of clients as fully supporting it and another 4.88% as partly supporting it. That is promising, but it still leaves a group of clients where a grid layout would break. Until that gap closes, tables are the dependable choice.

Inline styles

On the web, styles usually live in one stylesheet. In email, the most reliable place for a style is directly on the element, in a style attribute. Embedded style blocks in the head are more widely supported than they used to be. Can I Email’s page on the style element puts combined full and partial support at about 78%, but partial support means some clients drop the block in certain cases.

So most email code does both. Core styles go inline, where every client sees them, and the style block holds extras such as phone adjustments and dark mode rules. Email tools often handle the inlining for you.

A fixed, modest width

Email content is usually held to about 600 px on desktop. Mailchimp’s guide to HTML email advises keeping emails no more than 600 pixels wide unless the layout is fluid. That width fits a reading pane beside an inbox list and shrinks cleanly on phones.

Images are not guaranteed

On a website, an image almost always appears. In email, it might not. Some apps wait for the reader’s permission before loading pictures, and some readers switch them off for good. Mailchimp’s design reference on using images in email notes that many programs block images by default, so the message should still make sense without them.

For beginners, that leads to three habits:

  • Host images online and link to them with full addresses. Mailchimp’s HTML email guide recommends absolute paths to publicly hosted images, since a file on your computer cannot be seen by anyone else.
  • Give each meaningful picture alt text, so a blocked one still says something.
  • Keep the words in text. A headline or price inside a picture disappears when images are blocked.

Some emails skip images altogether. The Simple Password Reset template has one heading, one short paragraph, a reset button, a 24 hour expiry line and a security note, with no images at all. The Refer a Colleague Note is a plain letter with a code box in a typewriter font. Both look the same whether images load or not.

When you do want a photo with words on it, put live text on top rather than baking it in. The Travel Destinations Newsletter opens with a full-bleed lake photo and a live headline, so the headline still reads with images off.

HTML vs plain text email

Every HTML email should travel with a plain-text version. Mailchimp’s HTML email guide explains how: the message is sent in a format called Multipart/Alternative MIME, which bundles both versions, and the reader’s mail program decides which one to show. Mailchimp creates the plain-text part automatically, and most other platforms do something similar.

The plain-text part matters for readers on very simple devices or with text-only settings. It is also a good discipline: if the plain version reads well, the HTML version probably has a clear message too.

There is a measurement trade-off to know about. Mailchimp notes that opens are tracked with a tiny transparent image in the HTML version, so it cannot track opens of plain-text emails.

Dark mode basics

Many readers set their phone or computer to dark mode, and mail apps respond in different ways. Some leave your colors alone, some invert only light backgrounds, and some invert everything. Litmus’s dark mode guide tracks this per client: in its table, Outlook.com applies a partial invert and Outlook 2021 on Windows applies a full invert.

As a beginner, you do not need to control every case. Two habits cover most of it:

  1. Avoid images that only work on white, like a dark logo with a transparent background.
  2. Check your email in a dark preview before sending.

Some templates are built for dark backgrounds from the start. The Dark Mode Tech Newsletter uses a dark-first design with a cyan rule, a lead story and two stories side by side, so there is little for a dark mode setting to flip.

Testing before you send

Since no two clients behave the same, testing is part of the design process rather than a final step.

A simple routine for beginners:

  1. Preview on desktop and phone widths. Our template pages let you switch between a 600 px desktop view and a 375 px mobile view, and between Light, Dark and Gmail modes.
  2. Send yourself real tests. Open them in at least one phone app, one webmail inbox and, if your readers use it, desktop Outlook.
  3. Turn images off once. Make sure the message and the button still come through.
  4. Click every link. Broken or wrong links are the most common avoidable mistake.
  5. Read the plain-text version. Check that it is readable and that links appear as full addresses.

Size is worth a glance too. HubSpot’s email design guide advises keeping the whole email under 102KB to avoid clipping. When a message is clipped, the end is what gets cut off, and the end is where your footer sits. The Monthly Statement Ledger template, a bank style statement with no images, comes in at 21 KB, well clear of that limit.

Where to go next

Once these concepts make sense, choose your path:

  • To change a design without touching code, our upcoming how-to on editing a template with no code walks through a visual editor.
  • To shape emails for small screens, read the coming guide that explains responsive email design with fluid and hybrid methods.
  • For visual choices such as type, color and contrast, go to our piece on email design.

You can also learn a great deal by reading working code. Every design in our template library, 258 of them across 28 categories, has a Copy HTML button, and copying is free without an account.

FAQ

Is HTML email design hard to learn?

The basics are not. If you know some HTML and CSS, the main adjustment is learning which techniques mail apps accept, and starting from a tested template removes most of the guesswork.

Can I use normal CSS in an email?

Some of it. Many properties work, but support varies by client, and some apps ignore embedded styles in certain cases. Inline styles for the essentials are the safe default.

Why does my email look different in Outlook?

Desktop Outlook for Windows, in its 2007 to 2019 versions, uses Microsoft Word to render email, and Word supports far less CSS than a browser. Table-based layouts and Outlook-only code are the usual fixes.

Do I still need a plain-text version?

Yes. It is sent alongside the HTML version, and the reader’s app chooses which to display. Most email platforms generate it for you, but read it once before sending.

Learning by example

HTML email design comes down to a few ideas: mail apps control the rendering, tables and inline styles are the common language, images may not load, a plain-text twin travels with every message, dark mode changes colors, and only testing tells you what readers will see. Keep those in mind and the odd behavior of inboxes starts to make sense. A good next step is to open a simple design, such as the Simple Password Reset, and read its code from top to bottom.