Email templates sent from Salesforce may not render as expected in Microsoft Outlook or other email clients. Common display issues include:
Important: Salesforce has no control over how Microsoft Outlook or other email clients render HTML email. A message created and sent from Salesforce may look different in the recipient's email program depending on their email client version and settings.
This article covers all standard Salesforce email template types created in both Salesforce Classic and Lightning Experience. For Custom HTML and Visualforce email templates, rendering issues are often caused by custom HTML or CSS code that does not comply with email client standards. Salesforce Support cannot debug custom HTML or CSS code, as these are considered out-of-scope customizations.
Use the following steps to isolate whether the rendering issue is specific to Outlook or affects all email clients.
If images and content display correctly in other email clients or a browser, Salesforce has processed the email correctly and the issue is specific to how Outlook renders HTML. There is no Salesforce email template setting that controls Outlook's rendering behavior.
If the org uses email relay or an external email service, try disabling it temporarily and send a test email directly from Salesforce to confirm whether the relay configuration is contributing to the rendering issue.
One common Outlook setting that affects email rendering is the automatic image download block. To check this setting:
Microsoft Office Outlook 2007 and later versions use the Microsoft Office Word HTML rendering engine instead of a standard web browser engine. This means Outlook renders HTML and CSS differently from browsers, which can cause email layouts to appear differently from their original design. This behavior is by design from Microsoft and is not something Salesforce can control or modify.
000385062

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.