This article explains why a user's email signature in Salesforce displays raw HTML code as plain text instead of rendering the formatted signature when the signature is included in an email template via a merge field.
When a Salesforce user creates a signature using HTML formatting (such as bold text, colors, or clickable links) and that signature is referenced in an email template using the {{{sender.signature}}} merge field, the email template renders the HTML tags as visible text rather than formatted content.
For example, a signature containing <b>John Smith</b> in the user's signature settings would appear in the sent email as the literal text <b>John Smith</b> instead of displaying as John Smith in bold.
The {{{sender.signature}}} merge field in Salesforce Email Templates does not support HTML rendering. The signature merge field is designed to work with plain text only. When HTML code is stored in the signature field and then called by the merge field, Salesforce outputs the raw HTML as a text string rather than rendering it as formatted content.
This behavior is expected in Salesforce. The {{{sender.signature}}} merge field does not support HTML and only works with plain text signatures.
To ensure the signature displays correctly when used in email templates via merge fields, update the user's signature in Salesforce to use plain text only (no HTML tags, no formatting code).
To update a user's signature:
If users require an HTML-formatted signature in email templates, a Salesforce administrator can create a custom rich text field on the User object to store the HTML signature. Users then design their formatted signature in that field, and the email template references this custom field via its merge field syntax instead of {{{sender.signature}}}.
Steps for the administrator:
{{{User.HTML_Signature__c}}}).Note: This workaround requires the administrator to configure the field and update templates to use the new merge field.
Vote and comment on the Salesforce Community Idea - Signature Merge Field Support for HTML {{{sender.signature}}}
Trailblazer Community - Signature in HTML format
000389003

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.