We’ve all been there. You create a beautiful email with interesting GIFs, accessible buttons, and eye-catching images. Then you test it, and it looks great… except in Outlook, where it’s completely broken. People can’t engage the way you want them to with a broken email.
Outlook has been a plague of email marketers for a long time, but does it have to be? How can we work with it? Read on to find out how I came to love Outlook, despite its many faults. I’ll cover:
The many versions of Microsoft Outlook
The name “Outlook” covers several different email clients with a couple of different rendering engines and at least two different viewing settings. All of this can be a giant headache if you let it. Let’s dive in and see if we can straighten it out a bit.
These are the Windows desktop versions of Outlook. These use Word as the rendering engine, which made sense at a time when email was like writing letters. Ah, simpler times. But, for email marketers, it doesn’t cut it for rendering HTML emails.
120 DPI (dots per inch) adds to the complexity. Windows users can choose 120 DPI to increase their screen resolution. If they do, the desktop email clients will respect that and will update images and text to be larger. Which can wreak havoc on your email.
Outlook for Mac
This is the Mac desktop version of Outlook. It uses Webkit as the rendering engine. Which means it’s usually on par with Apple Mail and iOS as far as email rendering is concerned. If it looks good in your browser, there’s a decent chance it will look good here.
Outlook.com and the Outlook mobile apps
These clients use Webkit or Webkit-based rendering engines, so they provide good HTML rendering and don’t usually break your emails.
Outlook Office 365
There are two different versions of Outlook Office 365, the desktop email client and the web-based email client. The desktop version is similar to Outlook 2007-2019 and uses Word as a rendering engine (hard for email). The web-based email client uses Webkit or Blink and renders emails similarly to Outlook.com (much easier).
No more broken emails
Preview your emails across 90+ email clients, apps, and devices—including all versions of Outlook—to ensure an on-brand, error-free subscriber experience.
One Outlook to rule them all
In January, Microsoft announced their “One Outlook” vision to replace the desktop clients with one client that works everywhere starting sometime in 2022.
The new email client will be based on current Outlook web apps. So hopes are high that it’ll have a Webkit-based rendering engine and will render HTML emails well. Unfortunately, all those old desktop clients aren’t going to just disappear when that happens, so they’ll still have to be supported to some extent.
Do or do not, there is no try
Is your head spinning yet?
If it is, then let’s distill it for you: The key takeaway is that we’re working with two different rendering engines—Word and Webkit. Webkit is easier to code for, and Word is more difficult. Neither is really good or bad. They just require different approaches and have different quirks that need to be taken into consideration.
Let’s look at some of the common rendering issues in Outlook desktop clients and how to solve them.
Do include width and height attributes on your images
Outlook does not support CSS styles for widths and heights, and if you don’t include the width and height attributes, Outlook will display your image at its actual size. If you’re using retina images (which you should be), that means some giant images that’ll break your emails.
Do include ALT text
Don’t let Outlook’s security message speak for your images. Make sure to include ALT text in your images. Especially as Outlook doesn’t display images by default unless people turn the feature on.
Do use tables
Email has come a long way and you can use <div> blocks in lots of email clients, but Outlook isn’t one of them. Outlook will ignore most styles that you apply to your <div> tags including widths and paddings. So it’s important that you use <table> tags for your content instead.
Do use Outlook-specific code to solve rendering issues
This may not solve all your issues, but there are a lot of times that including some Outlook-specific CSS can help you solve a rendering issue that you’re only seeing on Outlook. Or you may hide a small block that isn’t working on Outlook, and use conditional code to show a version that would work for a specific version of Outlook. (More on conditional code later.)
Do add line heights to small images or table cells
Outlook sets a minimum height on table cells and images. So if you’re using a table cell as a spacer or have a small image, make sure to add a line height attribute to the element equal to the height that you want them to appear. For example:
Blog – Litmus