Learn
Email HTML, explained plainly
Email clients are not browsers. These guides cover what actually breaks and how to build email that renders the same in Gmail, Apple Mail, and Outlook, then paste cleanly into your ESP.
- Why Email Breaks in Outlook, and How to Build So It Does Not
Outlook renders email with Microsoft Word, not a browser. Here is why that breaks layouts and how to build table-based, inline-CSS HTML that holds up.
Read the guide → - How to paste custom HTML into a Klaviyo email
A practical guide to pasting custom HTML into a Klaviyo email: the HTML block vs the full code editor, what survives, what breaks, and how to test it.
Read the guide → - How to paste custom HTML into Mailchimp
A practical guide to importing your own HTML email into Mailchimp: the paste-code path, required merge tags, what gets changed, and how to test before you send.
Read the guide → - What ESP-safe HTML email means
ESP-safe HTML email uses table layout, inline CSS, a 600px width, and bulletproof buttons so it renders the same in Gmail, Apple Mail, and Outlook.
Read the guide → - Inline CSS for Email: Why Your Styles Need to Move Into the Tags
Email needs inline CSS because many clients strip style blocks. Learn what gets removed, the media query exception, the tools to inline, and the common gotchas.
Read the guide → - Dark mode email design: how to build email that holds up when inboxes flip the colors
How Gmail, Apple Mail, and Outlook handle dark mode, why image text and transparent logos break, and how to build and test email that holds up.
Read the guide →
Skip the hand-coding
Mailwright builds ESP-safe email on your client's brand, so you do not have to fight Outlook by hand.
Get a free sample