7 Common Rendering Issues in Outlook HTML Emails

7 Common Rendering Issues in Outlook HTML Emails

See the source image

Why does Outlook frustrate email developers?

Let’s learn how to code Outlook HTML emails by looking at the most common rendering issues and solutions.

This isn’t an exhaustive list of Outlook email coding issues, but it covers the most common ones.

1. No margin/padding in Outlook

Outlook is one of the worst offenders when it comes to HTML email spacing.

Outlook removes padding in a variety of situations. Commonly ignored image padding can cause text to appear flush against an image. To avoid this, wrap the image in a table with margin, padding, or cellpadding.

In general, margin and cellpadding are safe in Outlook. This may necessitate more nested tables. Love them! In other email clients, the padding around the image may be too much.

Outlook desktop doesn’t support div tag styling. So any padding specified in a div is useless. Outlook only respects table>s, so stick to those.

2. Outlook and animated GIFs

Outlook emails and animated GIFS have a complicated relationship. But it’s gotten better over time.

Microsoft announced in 2019 that a new version of Outlook 365 would support GIFs. As of now, all Outlook clients except the older Windows desktop versions support animated GIFs (2007-2016).

For animated GIFs, Outlook will only show the first frame. So make sure your GIF starts with a good frame. Your GIF’s first frame should include a call-to-action or important information.

You could also target Outlook clients with a different still image. Get the code and see how this Outlook GIF solution works.

3. Outlook disregards link styling

In some cases, Outlook will not apply styling to hyperlinks in an email. One use of a> tags without href= attribute is as placeholders or anchors.

To make Outlook recognize the link styling, simply wrap it in a span and style it.

If you add a URL without http:// or https://, Outlook removes link styling.

Before publishing a URL, you might use URLs without the http:// or https:// protocol to code a new email template or test a campaign. This can wreak havoc on button links. Outlook loses your styles and looks broken.

To avoid this, include the protocol in all placeholder and template links. If not, you’ll need to restyle those links.

4. Outlook adds a border to table cells

Emails with table cells have a 1-pixel border in Outlook 2016. This isn’t a big deal unless you need your email template to be perfect.

Use “border-collapse: collapse;” embedded or inline to remove it. This CSS property determines whether cells share or not a border. Setting the property to collapse creates a single border.

5. Outlook ignores HTML item width and height

Outlook doesn’t support div styling.

When an email is rendered in Outlook, the div sections will have the same height as the text inside them, even if you specify a height/width in code.

Again, tables are the solution for Outlook HTML emails. We’ve seen it with other elements, but the div is the most common.

6. Controlling line height in Outlook

Outlook.com used to render emails taller than expected because it controlled line-height with CSS. That’s no longer an issue.

MSO styles will slightly tighten your lines. Try it if your spacing is off. Add “mso-line-height-rule:exactly;” before the line-height style.

7. CSS background images not supported

While CSS background images are supported in Outlook.com and Outlook 365, they are not in most desktop clients.

A CSS property background-image may also cause issues. Outlook 2016 and older email clients can’t handle regular image backgrounds.

Using Vector Markup Language (VML) to make Outlook backgrounds work in older versions (VML).

Leave a Reply