Known Issues in Email Rendering and Display

MailPoet designer editor was made to help you create incredible templates for your subscribers across all email clients. 

Although we would love to ensure the emails will be rendered properly on all email clients, it's not always possible as we can't control it for some email clients.

Versions of Outlook from Outlook 2007 to present, for example, are known to have multiple rendering issues that are not exclusive to MailPoet.

That's because Outlook versions since 2007 use Microsoft Word to render emails, and it renders restricted support for HTML and CSS.

Below are known issues or bugs with the rendering of templates designed with our editor.


Outlook 1px horizontal lines in the body

Since Outlook 2007, Outlook changed the HTML rendering engine from Internet Explorer to Microsoft Word-based engine for some reason. This results in limited HTML and CSS support limitations.

Happens on: Outlook 2016, 2019 and Office 365 when using Windows 10.

What can you do? Currently, the only workaround when using MailPoet is to open HTML emails in a web browser.


Buttons with a label on 2 lines or more are vertically collapsed to 1 line

Happens on: Outlook 2007, 2010, 2013 and 2016 on Win 7.

What can you do? Try to have a short line in the button and set the width to be wide.



Social icons: no padding or margins between icons in some Outlook versions

Happens on: Outlook 2007, 2010, 2013, 2016, 2019

What can you do? Choose to use social icons without a background colour.


Other issues:

  • When forwarding an email, the email does not render the same in the recipient's email client;
  • A few email clients have limited support for CSS background images and for some of the properties for controlling how the background image appears, not displaying the background image at all;
  • We don't recommend copy/pasting the content from another editor to our own editor. It can affect the rendering and cause issues in many email clients.
  • Buttons get duplicated after forwarding.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.